merge
commit
39da2f6e16
|
@ -151,7 +151,7 @@
|
|||
{
|
||||
"description": "Criminal motivation on the dark web: A categorisation model for law enforcement. ref: Janis Dalins, Campbell Wilson, Mark Carman. Taxonomy updated by MISP Project",
|
||||
"name": "dark-web",
|
||||
"version": 3
|
||||
"version": 4
|
||||
},
|
||||
{
|
||||
"description": "Data classification for data potentially at risk of exfiltration based on table 2.1 of Solving Cyber Risk book.",
|
||||
|
@ -378,6 +378,26 @@
|
|||
"name": "information-security-indicators",
|
||||
"version": 1
|
||||
},
|
||||
{
|
||||
"description": "Describes the target of cyber training and education.",
|
||||
"name": "interactive-cyber-training-audience",
|
||||
"version": 1
|
||||
},
|
||||
{
|
||||
"description": "The technical setup consists of environment structure, deployment, and orchestration.",
|
||||
"name": "interactive-cyber-training-technical-setup",
|
||||
"version": 1
|
||||
},
|
||||
{
|
||||
"description": "The training environment details the environment around the training, consisting of training type and scenario.",
|
||||
"name": "interactive-cyber-training-training-environment",
|
||||
"version": 1
|
||||
},
|
||||
{
|
||||
"description": "The training setup further describes the training itself with the scoring, roles, the training mode as well as the customization level.",
|
||||
"name": "interactive-cyber-training-training-setup",
|
||||
"version": 1
|
||||
},
|
||||
{
|
||||
"description": "The interception method used to intercept traffic.",
|
||||
"name": "interception-method",
|
||||
|
@ -491,7 +511,7 @@
|
|||
{
|
||||
"description": "Taxonomy to classify phishing attacks including techniques, collection mechanisms and analysis status.",
|
||||
"name": "phishing",
|
||||
"version": 4
|
||||
"version": 5
|
||||
},
|
||||
{
|
||||
"description": "After an incident is scored, it is assigned a priority level. The six levels listed below are aligned with NCCIC, DHS, and the CISS to help provide a common lexicon when discussing incidents. This priority assignment drives NCCIC urgency, pre-approved incident response offerings, reporting requirements, and recommendations for leadership escalation. Generally, incident priority distribution should follow a similar pattern to the graph below. Based on https://www.us-cert.gov/NCCIC-Cyber-Incident-Scoring-System.",
|
||||
|
@ -511,7 +531,7 @@
|
|||
{
|
||||
"description": "Reference Security Incident Classification Taxonomy",
|
||||
"name": "rsit",
|
||||
"version": 1002
|
||||
"version": 1003
|
||||
},
|
||||
{
|
||||
"description": "Status of events used in Request Tracker.",
|
||||
|
@ -620,5 +640,5 @@
|
|||
}
|
||||
],
|
||||
"url": "https://raw.githubusercontent.com/MISP/misp-taxonomies/main/",
|
||||
"version": "20210621"
|
||||
"version": "20210920"
|
||||
}
|
||||
|
|
|
@ -114,77 +114,77 @@
|
|||
},
|
||||
{
|
||||
"value": "challenges-target-network",
|
||||
"expended": "Challenges: Network Target",
|
||||
"expanded": "Challenges: Network Target",
|
||||
"description": "The target in this challenge is network."
|
||||
},
|
||||
{
|
||||
"value": "challenges-target-host",
|
||||
"expended": "Challenges: Host Target",
|
||||
"expanded": "Challenges: Host Target",
|
||||
"description": "The target in this challenge is host."
|
||||
},
|
||||
{
|
||||
"value": "challenges-target-application",
|
||||
"expended": "Challenges: Application Target",
|
||||
"expanded": "Challenges: Application Target",
|
||||
"description": "The target in this challenge is application."
|
||||
},
|
||||
{
|
||||
"value": "challenges-target-protocol",
|
||||
"expended": "Challenges: Protocol Target",
|
||||
"expanded": "Challenges: Protocol Target",
|
||||
"description": "The target in this challenge is protocol."
|
||||
},
|
||||
{
|
||||
"value": "challenges-target-data",
|
||||
"expended": "Challenges: Data Target",
|
||||
"expanded": "Challenges: Data Target",
|
||||
"description": "The target in this challenge is data."
|
||||
},
|
||||
{
|
||||
"value": "challenges-target-person",
|
||||
"expended": "Challenges: Person Target",
|
||||
"expanded": "Challenges: Person Target",
|
||||
"description": "The target in this challenge is person."
|
||||
},
|
||||
{
|
||||
"value": "challenges-target-physical",
|
||||
"expended": "Challenges: Physical Target",
|
||||
"expanded": "Challenges: Physical Target",
|
||||
"description": "The target in this challenge is physical."
|
||||
},
|
||||
{
|
||||
"value": "challenges-type-foot-printing",
|
||||
"expended": "Challenges: Foot-printing Type",
|
||||
"expanded": "Challenges: Foot-printing Type",
|
||||
"description": "Foot-printing is needed to solve this challenge."
|
||||
},
|
||||
{
|
||||
"value": "challenges-type-scanning",
|
||||
"expended": "Challenges: Scanning Type",
|
||||
"expanded": "Challenges: Scanning Type",
|
||||
"description": "Scanning is needed to solve this challenge."
|
||||
},
|
||||
{
|
||||
"value": "challenges-type-enumeration",
|
||||
"expended": "Challenges: Enumeration Type",
|
||||
"expanded": "Challenges: Enumeration Type",
|
||||
"description": "Enumeration is needed to solve this challenge."
|
||||
},
|
||||
{
|
||||
"value": "challenges-type-pivoting",
|
||||
"expended": "Challenges: Pivoting Type",
|
||||
"expanded": "Challenges: Pivoting Type",
|
||||
"description": "Pivoting is needed to solve this challenge."
|
||||
},
|
||||
{
|
||||
"value": "challenges-type-exploitation",
|
||||
"expended": "Challenges: Exploitation Type",
|
||||
"expanded": "Challenges: Exploitation Type",
|
||||
"description": "Exploitation is needed to solve this challenge."
|
||||
},
|
||||
{
|
||||
"value": "challenges-type-privilege-escalation",
|
||||
"expended": "Challenges: Privilege escalation Type",
|
||||
"expanded": "Challenges: Privilege escalation Type",
|
||||
"description": "Privilege escalation is needed to solve this challenge."
|
||||
},
|
||||
{
|
||||
"value": "challenges-type-covering-tracks",
|
||||
"expended": "Challenges: Covering tracks Type",
|
||||
"expanded": "Challenges: Covering tracks Type",
|
||||
"description": "Covering tracks is needed to solve this challenge."
|
||||
},
|
||||
{
|
||||
"value": "challenges-type-maintaining",
|
||||
"expended": "Challenges: maintaining Type",
|
||||
"expanded": "Challenges: maintaining Type",
|
||||
"description": "Maintaining access is needed to solve this challenge."
|
||||
}
|
||||
]
|
||||
|
|
Loading…
Reference in New Issue