About the Unified MITRE Navigator
Understanding the data sources, ingestion methodology, edge confidence classifications, and copyright attributions powering this cross-framework cyber knowledge graph.
Integrated MITRE Knowledge Bases
The Navigator harmonizes five distinct MITRE cybersecurity repositories into a single relational graph:
MITRE ATT&CK® (Enterprise & ICS)
Globally-accessible knowledge base of adversary tactics, techniques, and procedures (TTPs) based on real-world observations.
MITRE ATLAS™
Adversarial Threat Landscape for Artificial-Intelligence Systems — cataloguing vulnerabilities and attack patterns targeting ML models.
MITRE CAPEC™
Common Attack Pattern Enumeration and Classification — comprehensive dictionary of known patterns of attack employed by adversaries to exploit weaknesses.
MITRE D3FEND™
Knowledge graph of cybersecurity countermeasure techniques and digital artifact relationships designed to tailor defensive capabilities.
MITRE Engage™
Framework for planning and discussing adversary engagement, cyber deception, and denial activities aligned with ATT&CK.
Official Crosswalks vs. Inferred Semantic Links
To maintain strict analytical rigor, all connections in the knowledge graph are categorized by confidence:
Official MITRE Crosswalks
Direct cross-framework mappings published and maintained by MITRE:
- ATLAS → ATT&CK: Referenced via STIX
external_references. - CAPEC → ATT&CK: Explicitly declared via
Taxonomy_Mappingsin CAPEC-3. - D3FEND → ATT&CK: Extracted from D3FEND OWL ontology SPARQL query bindings (
off_tech_id). - Engage → ATT&CK: Sourced from official MITRE Engage crosswalk tables (
attack_mapping.json).
Inferred Semantic Links
Heuristic connections surfaced via automated natural language processing (TF-IDF keyword extraction & Jaccard similarity indexing):
- Identifies latent conceptual connections for techniques lacking official crosswalk records.
- Rendered with dashed lines in the canvas and marked with distinct inferred badges.
- Can be toggled off at any time via the filter bar to isolate purely official MITRE relationships.
Data Provenance & Prebuild Pipeline
The ingestion pipeline is executed at prebuild time via scripts/ingest.ts, producing a compact, static graph.json bundle with zero runtime backend dependencies.
| Framework | Raw Source File | Objects Ingested | Mapping Relationship |
|---|---|---|---|
| ATT&CK Enterprise | enterprise-attack.json | Top-level techniques (non-subtechniques) | Primary Anchor Taxonomy |
| ATT&CK ICS | ics-attack.json | Industrial Control System techniques | ICS Anchor Columns |
| ATLAS | stix-atlas.json | AI / ML attack patterns | analogue-of → ATT&CK |
| CAPEC | capec_attack_pattern.xml | Standard & Meta attack patterns | maps-to → ATT&CK |
| D3FEND | defend-full-mappings.json | Defensive countermeasures | mitigates → ATT&CK |
| Engage | activities.json | Engagement activities | counters → ATT&CK |