250 lines
9.5 KiB
JSON
250 lines
9.5 KiB
JSON
{
|
||
"taxonomies": [
|
||
{
|
||
"version": 1,
|
||
"name": "accessnow",
|
||
"description": "Access Now"
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "admiralty-scale",
|
||
"description": "The Admiralty Scale (also called the NATO System) is used to rank the reliability of a source and the credibility of an information."
|
||
},
|
||
{
|
||
"version": 4,
|
||
"name": "adversary",
|
||
"description": "An overview and description of the adversary infrastructure."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "analyst-assessment",
|
||
"description": ""
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "binary-class",
|
||
"description": ""
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "circl",
|
||
"description": "CIRCL Taxonomy is a simple scheme for incident classification and area topic where the incident took place."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "csirt_case_classification",
|
||
"description": "FIRST CSIRT Case Classification."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "cssa",
|
||
"description": ""
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "de-vs",
|
||
"description": "Taxonomy for the handling of protectively marked information in MISP with German (DE) Government classification markings (VS)"
|
||
},
|
||
{
|
||
"version": 2,
|
||
"name": "dhs-ciip-sectors",
|
||
"description": "DHS critical sectors as described in https://www.dhs.gov/critical-infrastructure-sectors."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "diamond-model",
|
||
"description": "The Diamond Model for Intrusion Analysis, a phase-based model developed by Lockheed Martin, aims to help categorise and identify the stage of an attack."
|
||
},
|
||
{
|
||
"version": 3,
|
||
"name": "dni-ism",
|
||
"description": "ISM (Information Security Marking Metadata) V13 as described by DNI.gov (Director of National Intelligence - US)."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "domain-abuse",
|
||
"description": "Taxonomy to tag domain names used for cybercrime."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "ecsirt",
|
||
"description": "eCSIRT incident classification Appendix C of the eCSIRT EU project including IntelMQ updates."
|
||
},
|
||
{
|
||
"version": 201601,
|
||
"name": "enisa",
|
||
"description": "ENISA Threat Taxonomy - A tool for structuring threat information as published in https://www.enisa.europa.eu/topics/threat-risk-management/threats-and-trends/enisa-threat-landscape/etl2015/enisa-threat-taxonomy-a-tool-for-structuring-threat-information"
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "estimative-language",
|
||
"description": "Estimative language - including likelihood or probability of event based on the Intelligence Community Directive 203 (ICD 203) (6.2.(a))."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "euci",
|
||
"description": "EU classified information (EUCI) means any information or material designated by a EU security classification, the unauthorised disclosure of which could cause varying degrees of prejudice to the interests of the European Union or of one or more of the Member States as described in http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32013D0488&from=EN"
|
||
},
|
||
{
|
||
"version": 2,
|
||
"name": "eu-marketop-and-publicadmin",
|
||
"description": "Market operators and public administrations that must comply to some notifications requirements under EU NIS directive."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "europol-event",
|
||
"description": "EUROPOL type of events taxonomy."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "europol-incident",
|
||
"description": "EUROPOL class of incident taxonomy."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "fr-classif",
|
||
"description": "French gov information classification system."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "iep",
|
||
"description": "Forum of Incident Response and Security Teams (FIRST) Information Exchange Policy (IEP) framework."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "information-security-indicators",
|
||
"description": "Information security indicators have been standardized by the ETSI Industrial Specification Group (ISG) ISI. These indicators provide the basis to switch from a qualitative to a quantitative culture in IT Security Scope of measurements: External and internal threats (attempt and success), user's deviant behaviours, nonconformities and/or vulnerabilities (software, configuration, behavioural, general security framework). ETSI GS ISI 001-1 (V1.1.2): ISI Indicators"
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "kill-chain",
|
||
"description": "Cyber Kill Chain from Lockheed Martin as described in Intelligence-Driven Computer Network Defense Informed by Analysis of Adversary Campaigns and Intrusion Kill Chains."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "malware_classification",
|
||
"description": "Malware classification based on a SANS whitepaper about malware."
|
||
},
|
||
{
|
||
"version": 3,
|
||
"name": "misp",
|
||
"description": "Internal MISP taxonomy."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "ms-caro-malware",
|
||
"description": "Malware Type and Platform classification based on Microsoft's implementation of the Computer Antivirus Research Organization (CARO) Naming Scheme and Malware Terminology."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "ms-caro-malware-full",
|
||
"description": "Malware Type and Platform classification based on Microsoft's implementation of the Computer Antivirus Research Organization (CARO) Naming Scheme and Malware Terminology."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "nato",
|
||
"description": "Marking of Classified and Unclassified materials as described by the North Atlantic Treaty Organization, NATO."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "open_threat",
|
||
"description": "Open Threat Taxonomy v1.1 base on James Tarala of SANS ref. - http://www.auditscripts.com/resources/open_threat_taxonomy_v1.1a.pdf"
|
||
},
|
||
{
|
||
"version": 5,
|
||
"name": "osint",
|
||
"description": "Open Source Intelligence - Classification (MISP taxonomies)."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "PAP",
|
||
"description": "The Permissible Actions Protocol - or short: PAP - was designed to indicate how the received information can be used."
|
||
},
|
||
{
|
||
"version": 3,
|
||
"name": "tlp",
|
||
"description": "The Traffic Light Protocol - or short: TLP - was designed with the objective to create a favorable classification scheme for sharing sensitive information while keeping the control over its distribution at the same time. Extended with TLP:EX:CHR."
|
||
},
|
||
{
|
||
"version": 2,
|
||
"name": "veris",
|
||
"description": "Vocabulary for Event Recording and Incident Sharing (VERIS)."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "stealth_malware",
|
||
"description": "Classification based on malware stealth techniques."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "targeted-threat-index",
|
||
"description": "The Targeted Threat Index is a metric for assigning an overall threat ranking score to email messages that deliver malware to a victim’s computer. The TTI metric was first introduced at SecTor 2013 by Seth Hardy as part of the talk “RATastrophe: Monitoring a Malware Menagerie” along with Katie Kleemola and Greg Wiseman."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "stix-ttp",
|
||
"description": "Representation of the behavior or modus operandi of cyber adversaries (a.k.a TTP) as normalized in STIX"
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "accessnow",
|
||
"description": "AccessNow Taxonomy"
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "passivetotal",
|
||
"description": "Tags for RiskIQ's passivetotal service"
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "vocabulaire-des-probabilites-estimatives",
|
||
"description": "Vocabulaire des probabilités estimatives"
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "DML",
|
||
"description": "The Detection Maturity Level (DML) model is a capability maturity model for referencing ones maturity in detecting cyber attacks. It's designed for organizations who perform intel-driven detection and response and who put an emphasis on having a mature detection program."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "action-taken",
|
||
"description": "Action taken"
|
||
},
|
||
{
|
||
"version": 2,
|
||
"name": "analyst-assessment",
|
||
"description": "A series of assessment predicates describing the analyst capabilities to perform analysis. These assessment can be assigned by the analyst him/herself or by another party evaluating the analyst."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "binary-class",
|
||
"description": "Custom taxonomy for types of binary file."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "ddos",
|
||
"description": "Distributed Denial of Service - or short: DDoS - taxonomy supports the description of Denial of Service attacks and especially the types they belong too."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "event-assessment",
|
||
"description": "A series of assessment predicates describing the event assessment performed to make judgement(s) under a certain level of uncertainty."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "rt_event_status",
|
||
"description": "Status of events used in Request Tracker."
|
||
},
|
||
{
|
||
"version": 1,
|
||
"name": "tor",
|
||
"description": "Taxonomy to describe Tor network infrastructure"
|
||
}
|
||
],
|
||
"path": "machinetag.json",
|
||
"url": "https://raw.githubusercontent.com/MISP/misp-taxonomies/master/",
|
||
"description": "Manifest file of MISP taxonomies available.",
|
||
"license": "CC-0",
|
||
"version": "20170303"
|
||
}
|