Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is the Diamond Model of Intrusion Analysis?

The Diamond Model describes every intrusion as an adversary using a capability over some infrastructure against a victim, giving analysts a disciplined way to pivot between the four.

Illustration for the cybersecurity term Diamond Model
Home / Blog / Cybersecurity Terms / What Is the Diamond Model of Intrusion Analysis?
17 November 2026

What Is the Diamond Model of Intrusion Analysis?

What Is the Diamond Model of Intrusion Analysis?

Every malicious event can be written as a short sentence: an adversary deploys a capability over some infrastructure against a victim. That sentence is the Diamond Model of Intrusion Analysis, published in 2013 by Sergio Caltagirone, Andrew Pendergast, and Christopher Betz. It gives analysts a fixed shape to fill in, and—more usefully—it tells them where to look next when one corner is still blank.

The Four Corners

The edges matter as much as the corners. The line between adversary and victim carries motive, which analysts call the socio-political axis. The line between capability and infrastructure carries tradecraft, the technology axis. Reading the diamond along those two axes is what separates intelligence from a list of blocked indicators.

Meta-Features

Each event also carries meta-features that turn isolated findings into a narrative: a timestamp, the kill chain phase it belongs to, the result (success, failure, unknown), the direction of the activity, the methodology such as phishing or credential stuffing, and the resources the adversary needed. Later work added a confidence value, because most of what an analyst records early in an investigation is inference rather than fact.

Pivoting

The model earns its keep through pivoting: using any known corner to discover the others. A typical sequence from a single reported phishing email looks like this.

  1. Start at the victim: one user, one mailbox, one message.
  2. Pivot to infrastructure: the sending domain and the link target.
  3. Pivot through passive DNS and certificate transparency to the other domains hosted on the same address or sharing a certificate.
  4. Pivot to capability: the payload hash, the loader family, the way the macro is obfuscated.
  5. Pivot back to victims: who else in the estate received mail from that cluster, or resolved those domains.

Each hop produces a new diamond. Related diamonds chained in kill chain order form an activity thread, and threads that share features are grouped into activity groups—the raw material for naming and tracking a threat cluster before attribution is possible.

How It Sits Beside the Kill Chain and ATT&CK

These three models answer different questions and are strongest together. The cyber kill chain describes the sequence of an intrusion. MITRE ATT&CK catalogues the techniques used at each step. The Diamond Model describes the relationships inside a single event and shows the analyst where the next lead is. A mature report usually uses all three: ATT&CK technique IDs inside the capability corner, kill chain phase as a meta-feature, and activity threads to show the whole operation.

Using It in Practice

For a UK security team, the model is most valuable as a note-taking discipline. Record every observation against one of the four features, mark your confidence, and leave blanks visible rather than guessing. Blank corners become collection requirements: if infrastructure is known but capability is not, that is an instruction to retrieve the sample, not an acceptable gap.

It also tempers the urge to attribute early. Shared infrastructure can mean a shared bulletproof host rather than a shared adversary, and shared capability can simply mean a leaked builder. Keep the evidence in the corners and the inference in the confidence field, which is also what the NCSC expects in a credible incident report.

Analysts who work this way naturally climb the pyramid of pain, moving from disposable indicators towards adversary behaviour. If you want that discipline applied to your own alerts and feeds, our ThreatMon CTI are built around it.

FAQ – Frequently Asked Questions

Do I Need All Four Features to Record an Event?

No. Most events start with one or two known corners, usually victim and infrastructure. The model is designed for incomplete knowledge: you record what you have observed, mark your confidence, and treat each empty corner as a collection requirement. Filling a corner through pivoting is the normal analytical workflow rather than a precondition for using the model.

Is the Diamond Model a Replacement for the Cyber Kill Chain?

No, they complement each other. The kill chain orders an intrusion into phases, while the Diamond Model describes the relationships within a single event. Analysts link diamonds in kill chain order to build an activity thread, so a complete picture usually uses both, with MITRE ATT&CK technique identifiers describing the capability in detail.

How Does the Model Help with Attribution?

It separates evidence from inference. Infrastructure and capability overlaps are recorded as observed features, while any claim about the adversary stays a confidence-rated hypothesis. That structure stops teams from treating a shared hosting provider or a leaked tool as proof of a common actor, which is the most common attribution mistake in incident reporting.

What Tooling Supports the Diamond Model?

Most threat intelligence platforms and case management tools can hold the four features as structured fields, and STIX objects map onto them reasonably well. Passive DNS, certificate transparency logs, and malware sandboxes supply the pivot data. The model itself is tool-agnostic, so many teams simply enforce the four headings in their investigation template.

Related Terms

You May Be Interested In These

What Is FedRAMP?

Cybersecurity Terms

17 November 2026

What Is FedRAMP?

Read More
What Is a Cloud Compliance Audit?

Cybersecurity Terms

17 November 2026

What Is a Cloud Compliance Audit?

Read More
What Is Detection Testing Automation?

Cybersecurity Terms

17 November 2026

What Is Detection Testing Automation?

Read More