MITRE ATLAS · Coverage Assessment · Free Tool

MITRE ATLAS Coverage Calculator™: Measure Your AI Security Posture (2026)

Most organisations deploying AI believe they have adequate security controls. Very few can answer the actual question: which MITRE ATLAS attack techniques are those controls actually covering? The Coverage Calculator answers that question with a scored, benchmarked, export-ready report in under 10 minutes.

MITRE ATLAS Coverage Calculator™ — Start Your Assessment

Evaluate your AI security controls against the full MITRE ATLAS framework. Get coverage scores, gap analysis, prioritised recommendations, and a PDF report. Free, no signup required.

The Problem: Controls Without Coverage Visibility

Ask any CISO whether their organisation has AI security controls and the answer is usually yes. Ask them which MITRE ATLAS techniques those controls actually mitigate — and the answer becomes much less certain. This gap between "we have security" and "we know what we're protected against" is exactly what the Coverage Calculator addresses.

The challenge is structural. Traditional security maturity models weren't built for AI attack surfaces. A WAF, EDR, and SIEM might cover 80% of ATT&CK techniques. Against MITRE ATLAS, those same tools might cover 20% — because most AI attacks happen at the semantic layer, not the network or endpoint layer.

6
Threat domains evaluated
3
Assessment steps (AI inventory, controls, governance)
PDF
Export-ready board report included
<10m
Time to complete full assessment

How the Calculator Works — 3 Steps

Step 1 — AI Systems Inventory

Declare which types of AI systems you operate: LLM-powered applications, AI agents, RAG systems, autonomous workflows, or AI-integrated SaaS tools. This determines which ATLAS tactics and techniques are relevant to your environment — a company using only a customer-facing chatbot has a different ATLAS surface than one deploying autonomous agents with tool access.

Step 2 — Security Controls Assessment

For each relevant control area, indicate your current maturity level: none, basic, intermediate, or advanced. Controls are mapped to the ATLAS techniques they mitigate — so selecting "advanced prompt injection defences" credits you against AML.T0051, AML.T0054, and related techniques. The calculator uses weighted scoring so that high-risk techniques affect the overall score more heavily than lower-risk ones.

Step 3 — Governance & Compliance

Governance failures are responsible for a significant proportion of AI security incidents — untested systems, missing policies, and unmanaged third-party risk. Step 3 evaluates your governance posture: AI inventory management, security testing cadence, vendor assessment processes, and compliance framework coverage.

The Six ATLAS Threat Domains

Prompt Injection

Most common ATLAS attack category. Often undercovered despite high awareness.

Are prompts filtered and validated before reaching the model?
Is indirect injection via retrieved content monitored?
Are jailbreak attempts detected and logged?

️ RAG Security

Retrieval systems introduce unique risks rarely covered by traditional controls.

Are retrieval permissions enforced at chunk level?
Is cross-tenant data isolation validated?
Are knowledge bases monitored for poisoning?

Agent Security

Fastest-growing gap. Most agent deployments lack systematic security controls.

Are tool permissions scoped to minimum required?
Is MCP security validated?
Are workflow attacks tested pre-deployment?

Data Leakage

Sensitive information exposed through AI outputs or retrieval systems.

Are AI outputs monitored for sensitive data?
Is PII/classified data classified before AI ingestion?
Are exfiltration attempts logged?

Model Security

Model theft, inversion, and adversarial robustness rarely assessed.

Are models tested for adversarial robustness?
Is model behaviour monitored for anomalies?
Are extraction attempts rate-limited and detected?

AI Supply Chain

Third-party models and dependencies receive the least security scrutiny.

Are third-party AI models assessed before adoption?
Is an AI dependency inventory maintained?
Are vendor security changes monitored?

The Four Most Common Coverage Gaps

1

Agent Security — Pervasive Under-Coverage

Most organisations deploy AI agents "to try things out" and never formalise permission governance, workflow security testing, or MCP security validation. Agents accumulate permissions and capability with no systematic security review. Average ATLAS agent coverage in assessments: under 30%.

2

RAG Access Controls — Governance vs Technical Reality

Many organisations have a data governance policy that says access is controlled. Very few have technically validated that chunk-level access control is actually enforced in their RAG system. The gap between the governance document and the technical control is where cross-tenant leakage happens.

3

Runtime Monitoring — Testing Without Watching

Organisations test AI systems before deployment, then have minimal visibility into what those systems do in production. AI attacks are often invisible to traditional monitoring — they show up in prompt logs and output logs, which most organisations aren't collecting or alerting on.

4

Third-Party AI Risk — The Unexamined Surface

Most AI systems depend on foundation models, external APIs, plugins, and MCP connectors that receive little or no security review. Each one is a potential supply chain attack vector. Most organisations don't maintain an AI dependency inventory, let alone a security assessment of each vendor.

Sample Coverage Report

MITRE ATLAS Coverage Assessment — Sample Output

Organisation type: SaaS company with RAG system + customer-facing AI agent
71%
Moderate Risk

Coverage by domain:
Prompt Injection: 88% ████████░░
RAG Security: 62% ██████░░░░
Agent Security: 41% ████░░░░░░
Data Leakage: 75% ███████░░░
Model Security: 55% █████░░░░░
Supply Chain: 38% ███░░░░░░░

Top 3 Recommendations:
1. Implement MCP permission validation (closes AML.T0080, AML.T0090)
2. Deploy runtime AI monitoring (closes AML.T0057, AML.T0060)
3. Conduct third-party model assessment (closes AML.T0010, AML.T0110)

Estimated risk reduction from top 3: +22% coverage, -38% residual risk

Who Should Use the Coverage Calculator?

CISOs

Baseline AI security posture, prioritise investments, and produce board-level risk reporting from the PDF export

Security Architects

Identify specific ATLAS technique gaps in current control design and prioritise remediation by risk weight

Compliance Teams

Map ATLAS coverage to NIST AI RMF, EU AI Act, SOC 2, and ISO 27001 — the calculator includes framework cross-references

️

Risk Committees

Track AI security maturity over time with repeatable quarterly assessments and trend-visible coverage scores

Start With the Threat Explorer

Not sure which ATLAS techniques matter most for your environment? Use the Threat Explorer to understand each technique — attack paths, real examples, kill chains — before running the coverage assessment.

Frequently Asked Questions

What does the coverage score actually measure?
The score measures the percentage of risk-weighted MITRE ATLAS techniques your declared security controls address. Each ATLAS technique has a risk weight based on real-world exploitability and potential impact. Controls receive coverage credit based on their maturity level. The score isn't a pass/fail — it's a benchmark that shows where you stand and where the highest-ROI improvements are.
Is the Coverage Calculator free?
Yes — fully free, no account or signup required. PDF report generation is also free. The calculator is part of HexTyx's free tool suite alongside the MITRE Threat Explorer™ and AI Security Assessment™.
How often should I run a coverage assessment?
Minimum quarterly — and after any major AI deployment, architecture change, or new agent integration. Coverage changes when your AI systems change, so it's not a one-time exercise. The calculator is designed for repeatable use: run it quarterly and track coverage trends over time.
Can I use the PDF report for compliance documentation?
Yes. The PDF report includes your overall coverage score, tactic-by-tactic breakdown, gap analysis, and recommendations — formatted for executive and board review. It can support NIST AI RMF documentation, EU AI Act risk assessments, SOC 2 evidence collection, and ISO 27001 risk register updates.
What if my score is low?
A low score is the most useful output — it tells you exactly where to focus. The recommendations section prioritises gaps by risk weight and estimated coverage gain, so you know which controls to implement first for the highest risk reduction per investment dollar. Most organisations see their highest-ROI improvements in agent security, runtime monitoring, and third-party AI vendor assessment.

Related Resources