300 lines
12 KiB
JSON
300 lines
12 KiB
JSON
{
|
||
"values": [
|
||
{
|
||
"entry": [
|
||
{
|
||
"description": "Or 'Unsolicited Bulk Email', this means that the recipient has not granted verifiable permission for the message to be sent and that the message is sent as part of a larger collection of messages, all having a functionally comparable content.",
|
||
"expanded": "Spam",
|
||
"value": "spam"
|
||
},
|
||
{
|
||
"description": "Discreditation or discrimination of somebody, e.g. cyber stalking, racism or threats against one or more individuals.",
|
||
"expanded": "Harmful Speech",
|
||
"value": "harmful-speech"
|
||
},
|
||
{
|
||
"description": "Child pornography, glorification of violence, etc.",
|
||
"expanded": "Child Porn/Sexual/Violent Content",
|
||
"value": "violence"
|
||
}
|
||
],
|
||
"predicate": "abusive-content"
|
||
},
|
||
{
|
||
"entry": [
|
||
{
|
||
"description": "System infected with malware, e.g. PC, smartphone or server infected with a rootkit.",
|
||
"expanded": "Infected System",
|
||
"value": "infected-system"
|
||
},
|
||
{
|
||
"description": "Command-and-control server contacted by malware on infected systems.",
|
||
"expanded": "C2 Server",
|
||
"value": "c2-server"
|
||
},
|
||
{
|
||
"description": "URI used for malware distribution, e.g. a download URL included in fake invoice malware spam.",
|
||
"expanded": "Malware Distribution",
|
||
"value": "malware-distribution"
|
||
},
|
||
{
|
||
"description": "URI hosting a malware configuration file, e.g. webinjects for a banking trojan.",
|
||
"expanded": "Malware Configuration",
|
||
"value": "malware-configuration"
|
||
}
|
||
],
|
||
"predicate": "malicious-code"
|
||
},
|
||
{
|
||
"entry": [
|
||
{
|
||
"description": "Attacks that send requests to a system to discover weaknesses. This also includes testing processes to gather information on hosts, services and accounts. Examples: fingerd, DNS querying, ICMP, SMTP (EXPN, RCPT, ...), port scanning.",
|
||
"expanded": "Scanning",
|
||
"value": "scanner"
|
||
},
|
||
{
|
||
"description": "Observing and recording of network traffic (wiretapping).",
|
||
"expanded": "Sniffing",
|
||
"value": "sniffing"
|
||
},
|
||
{
|
||
"description": "Gathering information from a human being in a non-technical way (e.g. lies, tricks, bribes, or threats).",
|
||
"expanded": "Social Engineering",
|
||
"value": "social-engineering"
|
||
}
|
||
],
|
||
"predicate": "information-gathering"
|
||
},
|
||
{
|
||
"entry": [
|
||
{
|
||
"description": "An attempt to compromise a system or to disrupt any service by exploiting vulnerabilities with a standardised identifier such as CVE name (e.g. buffer overflow, backdoor, cross site scripting, etc.)",
|
||
"expanded": "Exploitation of known Vulnerabilities",
|
||
"value": "ids-alert"
|
||
},
|
||
{
|
||
"description": "Multiple login attempts (Guessing / cracking of passwords, brute force).",
|
||
"expanded": "Login attempts",
|
||
"value": "brute-force"
|
||
},
|
||
{
|
||
"description": "An attack using an unknown exploit.",
|
||
"expanded": "New attack signature",
|
||
"value": "exploit"
|
||
}
|
||
],
|
||
"predicate": "intrusion-attempts"
|
||
},
|
||
{
|
||
"entry": [
|
||
{
|
||
"description": "Compromise of a system where the attacker gained administrative privileges.",
|
||
"expanded": "Privileged Account Compromise",
|
||
"value": "privileged-account-compromise"
|
||
},
|
||
{
|
||
"description": "Compromise of a system using an unprivileged (user/service) account.",
|
||
"expanded": "Unprivileged Account Compromise",
|
||
"value": "unprivileged-account-compromise"
|
||
},
|
||
{
|
||
"description": "Compromise of an application by exploiting (un)known software vulnerabilities, e.g. SQL injection.",
|
||
"expanded": "Application Compromise",
|
||
"value": "application-compromise"
|
||
},
|
||
{
|
||
"description": "Physical intrusion, e.g. into corporate building or data center.",
|
||
"expanded": "Burglary",
|
||
"value": "burglary"
|
||
}
|
||
],
|
||
"predicate": "intrusions"
|
||
},
|
||
{
|
||
"entry": [
|
||
{
|
||
"description": "Denial of Service attack, e.g. sending specially crafted requests to a web application which causes the application to crash or slow down.",
|
||
"expanded": "Denial of Service",
|
||
"value": "dos"
|
||
},
|
||
{
|
||
"description": "Distributed Denial of Service attack, e.g. SYN-Flood or UDP-based reflection/amplification attacks.",
|
||
"expanded": "Distributed Denial of Service",
|
||
"value": "ddos"
|
||
},
|
||
{
|
||
"description": "Software misconfiguration resulting in service availability issues, e.g. DNS server with outdated DNSSEC Root Zone KSK.",
|
||
"expanded": "Misconfiguration",
|
||
"value": "misconfiguration"
|
||
},
|
||
{
|
||
"description": "Physical sabotage, e.g cutting wires or malicious arson.",
|
||
"expanded": "Sabotage",
|
||
"value": "sabotage"
|
||
},
|
||
{
|
||
"description": "Outage caused e.g. by air condition failure or natural disaster.",
|
||
"expanded": "Outage",
|
||
"value": "outage"
|
||
}
|
||
],
|
||
"predicate": "availability"
|
||
},
|
||
{
|
||
"entry": [
|
||
{
|
||
"description": "Unauthorized access to information, e.g. by abusing stolen login credentials for a system or application, intercepting traffic or gaining access to physical documents.",
|
||
"expanded": "Unauthorised access to information",
|
||
"value": "unauthorised-information-access"
|
||
},
|
||
{
|
||
"description": "Unauthorised modification of information, e.g. by an attacker abusing stolen login credentials for a system or application or a ransomware encrypting data.",
|
||
"expanded": "Unauthorised modification of information",
|
||
"value": "unauthorised-information-modification"
|
||
},
|
||
{
|
||
"description": "Loss of data, e.g. caused by harddisk failure or physical theft.",
|
||
"expanded": "Data Loss",
|
||
"value": "data-loss"
|
||
}
|
||
],
|
||
"predicate": "information-content-security"
|
||
},
|
||
{
|
||
"entry": [
|
||
{
|
||
"description": "Using resources for unauthorized purposes including profit-making ventures, e.g. the use of e-mail to participate in illegal profit chain letters or pyramid schemes.",
|
||
"expanded": "Unauthorized use of resources",
|
||
"value": "unauthorized-use-of-resources"
|
||
},
|
||
{
|
||
"description": "Offering or Installing copies of unlicensed commercial software or other copyright protected materials (Warez).",
|
||
"expanded": "Copyright",
|
||
"value": "copyright"
|
||
},
|
||
{
|
||
"description": "Type of attack in which one entity illegitimately impersonates the identity of another in order to benefit from it.",
|
||
"expanded": "Masquerade",
|
||
"value": "masquerade"
|
||
},
|
||
{
|
||
"description": "Masquerading as another entity in order to persuade the user to reveal private credentials.",
|
||
"expanded": "Phishing",
|
||
"value": "phishing"
|
||
}
|
||
],
|
||
"predicate": "fraud"
|
||
},
|
||
{
|
||
"entry": [
|
||
{
|
||
"description": "Publicly accessible services offering weak crypto, e.g. web servers susceptible to POODLE/FREAK attacks.",
|
||
"expanded": "Weak crypto",
|
||
"value": "weak-crypto"
|
||
},
|
||
{
|
||
"description": "Publicly accessible services that can be abused for conducting DDoS reflection/amplification attacks, e.g. DNS open-resolvers or NTP servers with monlist enabled.",
|
||
"expanded": "DDoS amplifier",
|
||
"value": "ddos-amplifier"
|
||
},
|
||
{
|
||
"description": "Potentially unwanted publicly accessible services, e.g. Telnet, RDP or VNC.",
|
||
"expanded": "Potentially unwanted accessible services",
|
||
"value": "potentially-unwanted-accessible"
|
||
},
|
||
{
|
||
"description": "Publicly accessible services potentially disclosing sensitive information, e.g. SNMP or Redis.",
|
||
"expanded": "Information disclosure",
|
||
"value": "information-disclosure"
|
||
},
|
||
{
|
||
"description": "A system which is vulnerable to certain attacks. Example: misconfigured client proxy settings (example: WPAD), outdated operating system version, etc.",
|
||
"expanded": "Vulnerable system",
|
||
"value": "vulnerable-system"
|
||
}
|
||
],
|
||
"predicate": "vulnerable"
|
||
},
|
||
{
|
||
"entry": [
|
||
{
|
||
"description": "All incidents which don't fit in one of the given categories should be put into this class.",
|
||
"expanded": "Other",
|
||
"value": "other"
|
||
}
|
||
],
|
||
"predicate": "other"
|
||
},
|
||
{
|
||
"entry": [
|
||
{
|
||
"description": "Meant for testing.",
|
||
"expanded": "Test",
|
||
"value": "test"
|
||
}
|
||
],
|
||
"predicate": "test"
|
||
}
|
||
],
|
||
"predicates": [
|
||
{
|
||
"description": "Abusive Content.",
|
||
"expanded": "Abusive Content",
|
||
"value": "abusive-content"
|
||
},
|
||
{
|
||
"description": "Software that is intentionally included or inserted in a system for a harmful purpose. A user interaction is normally necessary to activate the code.",
|
||
"expanded": "Malicious Code",
|
||
"value": "malicious-code"
|
||
},
|
||
{
|
||
"description": "Information Gathering.",
|
||
"expanded": "Information Gathering",
|
||
"value": "information-gathering"
|
||
},
|
||
{
|
||
"description": "Intrusion Attempts.",
|
||
"expanded": "Intrusion Attempts",
|
||
"value": "intrusion-attempts"
|
||
},
|
||
{
|
||
"description": "A successful compromise of a system or application (service). This can have been caused remotely by a known or new vulnerability, but also by an unauthorized local access. Also includes being part of a botnet.",
|
||
"expanded": "Intrusions",
|
||
"value": "intrusions"
|
||
},
|
||
{
|
||
"description": "By this kind of an attack a system is bombarded with so many packets that the operations are delayed or the system crashes. DoS examples are ICMP and SYN floods, Teardrop attacks and mail-bombing. DDoS often is based on DoS attacks originating from botnets, but also other scenarios exist like DNS Amplification attacks. However, the availability also can be affected by local actions (destruction, disruption of power supply, etc.) – or by Act of God, spontaneous failures or human error, without malice or gross neglect being involved.",
|
||
"expanded": "Availability",
|
||
"value": "availability"
|
||
},
|
||
{
|
||
"description": "Besides a local abuse of data and systems the information security can be endangered by a successful account or application compromise. Furthermore attacks are possible that intercept and access information during transmission (wiretapping, spoofing or hijacking). Human/configuration/software error can also be the cause.",
|
||
"expanded": "Information Content Security",
|
||
"value": "information-content-security"
|
||
},
|
||
{
|
||
"description": "Fraud.",
|
||
"expanded": "Fraud",
|
||
"value": "fraud"
|
||
},
|
||
{
|
||
"description": "Open resolvers, world readable printers, vulnerability apparent from Nessus etc scans, virus signatures not up-to-date, etc",
|
||
"expanded": "Vulnerable",
|
||
"value": "vulnerable"
|
||
},
|
||
{
|
||
"description": "All incidents which don't fit in one of the given categories should be put into this class. If the number of incidents in this category increases, it is an indicator that the classification scheme must be revised",
|
||
"expanded": "Other",
|
||
"value": "other"
|
||
},
|
||
{
|
||
"description": "Meant for testing.",
|
||
"expanded": "Test",
|
||
"value": "test"
|
||
}
|
||
],
|
||
"version": 3,
|
||
"description": "Reference Security Incident Classification Taxonomy",
|
||
"namespace": "rsit"
|
||
}
|