MISP
/
misp-taxonomies
mirror of https://github.com/MISP/misp-taxonomies
2
0
Fork 0
Code Issues Releases Wiki Activity

Rework of the NIS taxonomy

pull/107/head
iglocska 2018-07-18 15:53:41 +02:00
parent 9d70038030
commit c7c721d2b0
6 changed files with 116 additions and 184 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
nis-impact/README.md
View File

@ -1,49 +0,0 @@
# Admiralty Scale
The Admiralty Scale (also called the NATO System) is used to rank the reliability of a source and
the credibility of an information.
## Source Reliability
<dl>
<dt>A</dt>
<dd>Completely reliable</dd>
<dt>B</dt>
<dd>Usually reliable<dd>
<dt>C</dt>
<dd>Fairly reliable </dd>
<dt>D</dt>
<dd>Not usually reliable</dd>
<dt>E</dt>
<dd>Unreliable</dd>
<dt>F<dt>
<dd>Reliability cannot be judged</dd>
</dl>
## Information Credibility
<dl>
<dt>1</dt>
<dd>Confirmed by other sources</dd>
<dt>2</dt>
<dd>Probably true</dd>
<dt>3</dt>
<dd>Possibly true</dd>
<dt>4</dt>
<dd>Doubtful</dd>
<dt>5</dt>
<dd>Improbable</dd>
<dt>6</dt>
<dd>Truth cannot be judged</dd>
</dl>
# Machine-parsable Admiralty Scale
The repository contains a [JSON file including the machine-parsable tags](machinetag.json)
along with their human-readable description. The software can use both
representation on the user-interface and store the tag as machine-parsable.
~~~~
admiralty-scale:source-reliability="b"
~~~~

BIN
nis-nature/.machinetag.json.swp
View File

Binary file not shown.

49
nis-nature/README.md
View File

@ -1,49 +0,0 @@
# Admiralty Scale
The Admiralty Scale (also called the NATO System) is used to rank the reliability of a source and
the credibility of an information.
## Source Reliability
<dl>
<dt>A</dt>
<dd>Completely reliable</dd>
<dt>B</dt>
<dd>Usually reliable<dd>
<dt>C</dt>
<dd>Fairly reliable </dd>
<dt>D</dt>
<dd>Not usually reliable</dd>
<dt>E</dt>
<dd>Unreliable</dd>
<dt>F<dt>
<dd>Reliability cannot be judged</dd>
</dl>
## Information Credibility
<dl>
<dt>1</dt>
<dd>Confirmed by other sources</dd>
<dt>2</dt>
<dd>Probably true</dd>
<dt>3</dt>
<dd>Possibly true</dd>
<dt>4</dt>
<dd>Doubtful</dd>
<dt>5</dt>
<dd>Improbable</dd>
<dt>6</dt>
<dd>Truth cannot be judged</dd>
</dl>
# Machine-parsable Admiralty Scale
The repository contains a [JSON file including the machine-parsable tags](machinetag.json)
along with their human-readable description. The software can use both
representation on the user-interface and store the tag as machine-parsable.
~~~~
admiralty-scale:source-reliability="b"
~~~~

69
nis-nature/machinetag.json
View File

@ -1,69 +0,0 @@
{
"namespace": "nis-nature",
"description": "This taxonomy is used to classify the nature of the incident, i.e. the type of threat that triggered the incident, the severity of that threat.",
"version": 1,
"predicates": [
{
"value": "root-cause",
"expanded": "Root cause category",
"description": "The Root cause category is used to indicate what type event or threat triggered the incident."
},
{
"value": "severity",
"expanded": "Severity of the threat",
"description": "The severity of the threat is used to indicate, from a technical perspective, the potential impact, the risk associated with the threat. For example, the severity is high if an upcoming storm is exceptionally strong, if an observed DDoS attack is exceptionally powerful, or if a software vulnerability is easily exploited and present in many different systems. For example, in certain situations a critical software vulnerability would require concerted and urgent work by different organizations."
}
],
"values": [
{
"predicate": "root-cause",
"entry": [
{
"value": "system-failures",
"expanded": "System failures",
"description": "The incident is due to a failure of a system, i.e. without external causes. For example a hardware failure, software bug, a flaw in a procedure, etc. triggered the incident."
},
{
"value": "natural-phenomena",
"expanded": "Natural phenomena",
"description": "The incident is due to a natural phenomenon. For example a storm, lightning, solar flare, flood, earthquake, wildfire, etc. triggered the incident."
},
{
"value": "human-errors",
"expanded": "Human errors",
"description": "The incident is due to a human error, i.e. system worked correctly, but was used wrong. For example, a mistake, or carelessness triggered the incident."
},
{
"value": "malicious-actions",
"expanded": "Malicious actions",
"description": "The incident is due to a malicious action. For example, a cyber-attack or physical attack, vandalism, sabotage, insider attack, theft, etc., triggered the incident."
},
{
"value": "third-party-failures",
"expanded": "Third party failures",
"description": "The incident is due to a disruption of a third party service, like a utility. For example a power cut, or an internet outage, etc. triggered the incident."
}
]
},
{
"predicate": "severity",
"entry": [
{
"value": "high",
"expanded": "High",
"description": "High severity, potential impact is high."
},
{
"value": "medium",
"expanded": "Medium",
"description": "Medium severity, potential impact is medium."
},
{
"value": "high",
"expanded": "High",
"description": "Low severity, potential impact is low."
}
]
}
]
}

9
nis/README.md Normal file
View File

@ -0,0 +1,9 @@
# NIS Cybersecurity Incident Taxonomy
The taxonomy is meant for large scale cybersecurity incidents, as mentioned in the Commission Recommendation of 13 September 2017, also known as the blueprint. It has two core parts: The nature of the incident, i.e. the underlying cause, that triggered the incident, and the impact of the incident, i.e. the impact on services, in which sector(s) of economy and society.
The repository contains a [JSON file including the machine-parsable tags](machinetag.json)
along with their human-readable description. The software can use both
representation on the user-interface and store the tag as machine-parsable.

124
nis-impact/machinetag.json → nis/machinetag.json
View File

@ -1,27 +1,46 @@
{
"namespace": "nis-impact",
"description": "This taxonomy is used to classify the impact of the incident, i.e. the impact it has on services, in which sector(s) of the economy and society.",
"namespace": "nis",
"description": "The taxonomy is meant for large scale cybersecurity incidents, as mentioned in the Commission Recommendation of 13 September 2017, also known as the blueprint. It has two core parts: The nature of the incident, i.e. the underlying cause, that triggered the incident, and the impact of the incident, i.e. the impact on services, in which sector(s) of economy and society.",
"version": 1,
"predicates": [
{
"value": "sectors-impacted",
"value": "impact-sectors-impacted",
"expanded": "Sectors impacted",
"description": "The impact on services, in the real world, indicating the sectors of the society and economy, where there is an impact on the services."
},
{
"value": "severity",
"value": "impact-severity",
"expanded": "Severity of the impact",
"description": "The severity of the impact, nationally, in the real world, for society and/or the economy, i.e. the level of disruption for the country or a large region of the country, the level of risks for health and/or safety, the level of physical damages and/or financial costs."
"description": "The severity of the impact, nationally, in the real world, for society and/or the economy, i.e. the level of disruption for the country or a large region of the country, the level of risks for health and/or safety, the level of physical damages and/or financial costs.",
"exclusive": true
},
{
"value": "outlook",
"value": "impact-outlook",
"expanded": "Outlook",
"description": "The outlook for the incident, the prognosis, for the coming hours, considering the impact in the real world, the impact on services, for the society and/or the economy"
"description": "The outlook for the incident, the prognosis, for the coming hours, considering the impact in the real world, the impact on services, for the society and/or the economy",
"exclusive": true
},
{
"value": "nature-root-cause",
"expanded": "Root cause category",
"description": "The Root cause category is used to indicate what type event or threat triggered the incident.",
"exclusive": true
},
{
"value": "nature-severity",
"expanded": "Severity of the threat",
"description": "The severity of the threat is used to indicate, from a technical perspective, the potential impact, the risk associated with the threat. For example, the severity is high if an upcoming storm is exceptionally strong, if an observed DDoS attack is exceptionally powerful, or if a software vulnerability is easily exploited and present in many different systems. For example, in certain situations a critical software vulnerability would require concerted and urgent work by different organizations.",
"exclusive": true
},
{
"value": "test",
"expanded": "Test",
"description": "A test predicate meant to test interoperability between tools. Tags contained within this predicate are to be ignored."
}
],
"values": [
{
"predicate": "sectors-impacted",
"predicate": "impact-sectors-impacted",
"entry": [
{
"value": "energy",
@ -81,47 +100,118 @@
]
},
{
"predicate": "severity",
"predicate": "impact-severity",
"entry": [
{
"value": "red",
"expanded": "Red",
"description": "Very large impact"
"description": "Very large impact",
"colour": "#CC0033"
},
{
"value": "yellow",
"expanded": "Yellow",
"description": "Large impact."
"description": "Large impact.",
"colour": "#FFC000"
},
{
"value": "green",
"expanded": "Green",
"description": "Minor impact."
"description": "Minor impact.",
"colour": "#339900"
},
{
"value": "white",
"expanded": "White",
"description": "No impact."
"description": "No impact.",
"colour": "#ffffff"
}
]
},
{
"predicate": "outlook",
"predicate": "impact-outlook",
"entry": [
{
"value": "improving",
"expanded": "Improving",
"description": "Severity of impact is expected to decrease in the next 6 hours."
"description": "Severity of impact is expected to decrease in the next 6 hours.",
"colour": "#339900"
},
{
"value": "stable",
"expanded": "Stable",
"description": "Severity of impact is expected to remain the same in the 6 hours."
"description": "Severity of impact is expected to remain the same in the 6 hours.",
"colour": "#FFC000"
},
{
"value": "worsening",
"expanded": "Worsening",
"description": "Severity of impact is expected to increase in the next 6 hours."
"description": "Severity of impact is expected to increase in the next 6 hours.",
"colour": "#CC0033"
}
]
},
{
"predicate": "nature-root-cause",
"entry": [
{
"value": "system-failures",
"expanded": "System failures",
"description": "The incident is due to a failure of a system, i.e. without external causes. For example a hardware failure, software bug, a flaw in a procedure, etc. triggered the incident."
},
{
"value": "natural-phenomena",
"expanded": "Natural phenomena",
"description": "The incident is due to a natural phenomenon. For example a storm, lightning, solar flare, flood, earthquake, wildfire, etc. triggered the incident."
},
{
"value": "human-errors",
"expanded": "Human errors",
"description": "The incident is due to a human error, i.e. system worked correctly, but was used wrong. For example, a mistake, or carelessness triggered the incident."
},
{
"value": "malicious-actions",
"expanded": "Malicious actions",
"description": "The incident is due to a malicious action. For example, a cyber-attack or physical attack, vandalism, sabotage, insider attack, theft, etc., triggered the incident."
},
{
"value": "third-party-failures",
"expanded": "Third party failures",
"description": "The incident is due to a disruption of a third party service, like a utility. For example a power cut, or an internet outage, etc. triggered the incident."
}
]
},
{
"predicate": "nature-severity",
"entry": [
{
"value": "high",
"expanded": "High",
"description": "High severity, potential impact is high.",
"colour": "#CC0033"
},
{
"value": "medium",
"expanded": "Medium",
"description": "Medium severity, potential impact is medium.",
"colour": "#FFC000"
},
{
"value": "high",
"expanded": "High",
"description": "Low severity, potential impact is low.",
"colour": "#339900"
}
]
},
{
"predicate": "test",
"entry": [
{
"value": "test",
"expanded": "Test",
"description": "Test value meant for testing interoperability. Tags with this value are to be ignored.",
"colour": "#F81894"
}
]
}