Diamond Model
Links adversary, capability, infrastructure, and victim in one event.
What it is
The Diamond Model of Intrusion Analysis frames every intrusion event around four linked vertices: adversary, capability, infrastructure, and victim.
Why it matters
Pivoting across those relationships (say, from infrastructure to other victims) drives analysis and attribution and structures how findings connect across an investigation.
In practice
Linking two intrusions by shared C2 infrastructure to infer a common adversary.
What to look for
- Each event described by adversary, capability, infrastructure and victim.
- Pivots from one point, such as infrastructure, to new events.
Common mistake
Leaving a vertex blank and moving on. The empty corner is often the next pivot.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
- Indicator Extractor
Pull every IOC out of a log or a report, then score the domains against published string heuristics.
- PCAP Triage
A first pass over a capture: conversations, protocol mix, DNS, HTTP hosts and TLS names.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
MISP Open source
An open source platform for storing, correlating and sharing threat indicators.
-
OpenCTI Open source
Organizes intelligence as linked STIX objects, from actors down to indicators.
-
VirusTotal Commercial
Pivots between files, domains and IPs to find related infrastructure.
-
ATT&CK Navigator Open source
Shows a group's known techniques on the ATT&CK matrix.
Read next
- MITRE ATT&CK: A public knowledge base of real adversary tactics and techniques.
- Pyramid of Pain: Ranks indicators by how much they hurt attackers to lose.
- Command and Control: The channel an attacker uses to control compromised hosts.