A practical guide to MITRE ATT&CK threat modelling
MITRE ATT&CK gives security teams a shared language for describing how adversaries operate. Instead of treating a breach as an abstract event, teams can connect plausible intrusion paths with observable tactics, techniques and procedures. That makes threat modelling more concrete, testable and aligned with the telemetry already flowing into a SIEM.
Used effectively, the matrix supports decisions rather than replacing them. It does not assign business risk, guarantee complete coverage or turn every mapped technique into a control. A practical exercise combines ATT&CK knowledge with asset criticality, threat actor intent, attack likelihood and the cost of missed detection. The result is a prioritised defensive plan that security leaders, operational teams and executives can act on.
Why ATT&CK belongs in threat modelling
Threat modelling answers four linked questions: what matters, who may target it, how they could reach it and where defenders could observe or interrupt them. For example, an Australian online retailer may value payment services and customer accounts above a campaign landing page, while a hospital will rank patient records, clinical systems and safety-critical operations differently. The scenario should drive the model, not the matrix.
ATT&CK adds an evidence-based catalogue of adversary behaviour drawn from real-world observations and community reporting. Mapping a threat narrative to relevant tactics can expose assumptions hidden in diagrams, such as expecting every intrusion to begin with malware. It also gives incident responders and detection engineers common terminology, improving workshops and handovers across a distributed organisation.
Build the model around assets and attack paths
Begin by defining crown-jewel assets, critical services, trust boundaries and likely threat actors. A concise statement such as “an attacker seeks valid administrator credentials to export payment data from the ecommerce platform” creates a testable scenario. Capture the starting position, objective, required access, possible persistence and likely operational constraints. For a cloud platform, include identity tenants, CI/CD pipelines, secrets and third-party integrations rather than focusing only on perimeter firewalls.
Then plot a small number of end-to-end attack paths instead of listing every possible technique. Link each step to a condition, an adversary action and a defender opportunity. This approach supports likelihood analysis and creates a clear baseline for red-team testing or purple-team exercises. Keep alternative paths when they introduce materially different controls, such as compromising a managed service provider rather than attacking the target directly.
Map behaviour to tactics and techniques
Mapping should track behaviour and intent, not simply copy matrix cells into a spreadsheet. Select the tactics relevant to the modelled actor and objective, then link each technique to available logs, an existing detection, a preventive control and a response action. MITRE ATT&CK Navigator can organise the mapping and show coverage, while Sigma rules, SIEM correlation searches and EDR telemetry provide practical implementation options.
Avoid false precision by documenting why each mapping is plausible and where confidence is low. A technique may change between intrusion sets, and some attacks leave few host-based traces. Where visibility is weak, strengthen identity analytics, network telemetry or cloud audit logs before writing detections. Also distinguish a mapped capability from a validated detection: only the latter has been tested against relevant scenarios.
Create a detection and control backlog
Prioritise gaps using business impact, exposure, adversary plausibility, detection confidence and response effort. The following recommendations turn the matrix into an actionable backlog rather than a static reference.
- Prioritise techniques that appear in credible attack paths and affect critical services, not those merely common in public reporting.
- Map each priority technique to specific telemetry owners, alert logic and escalation steps, including out-of-hours coverage.
- Link preventive, detective and recovery controls so a missed detection still has a defined containment option.
- Record evidence gaps, expected false-positive rates and the business consequence of an undetected attack.
- Test mappings through tabletop scenarios, purple-team exercises and targeted detection validation.
Review the backlog whenever a new incident, material architecture change or regulatory obligation alters the operating context. Assign an owner and review date to every item, and measure progress through detection coverage and validated response time rather than the number of mapped techniques.
Test the model against Australian realities
Stress-test the model against Australian operating conditions rather than importing a generic overseas threat profile. Sydney and Melbourne hosts may combine corporate offices, colocation infrastructure and cloud workloads, while branches in Brisbane, Perth or regional areas can rely on different links and support arrangements. Include those dependencies, Australian time-zone handoffs and the reality that specialist incident response capacity may need to be reached across borders.
Regulatory context also shapes priorities. The Australian Signals Directorate’s Essential Eight provides a useful governance layer, while APRA’s CPS 230 is relevant to many financial institutions and OAIC guidance and the Privacy Act matter for health and customer data. These obligations do not map cleanly to ATT&CK, so link each required control to the attack paths it addresses and retain evidence for boards, regulators and insurers.
Turn findings into an operational response
Run a structured workshop with security operations, architecture, application owners, risk and the business. Use ATT&CK-derived scenarios to probe the team’s ability to detect credential abuse, container escape, malicious cloud API use and persistence on an unmanaged endpoint. A purple-team test then challenges those assumptions with safe adversary emulation and validates both telemetry and escalation.
Infoziant Security can help turn the exercise into an operational roadmap through vulnerability assessment and penetration testing, managed monitoring, SIEM tuning and tailored compliance support. Organisations can request a free VAPT report, use its findings to seed an ATT&CK-informed workshop and trial a focused engagement that tests priority attack paths, closes telemetry gaps and measures detection coverage.