MITRE ATLAS External Framework Crosswalk
Generated Evaluation Status
This section is generated from the framework manifest and compatibility report. Do not edit it manually.
- Framework ID:
mitre-atlas - Manifest:
docs/external-frameworks/mitre-atlas.json - Compatibility report:
./reports/mitre-atlas.compatibility.json - Evidence class:
SOURCE_REVIEWED - Independently reproducible:
False - Comparative-testing claim allowed:
False - Missing reproducibility gates:
shared_test_vector, raw_output, timestamp, runtime_configuration, source_version_or_hash, replay_commands, declared_expected_outcome, independent_reproduction - Evaluation result:
COMPATIBILITY_EVIDENCE_ONLY - Cycle status:
FIRST_FRAMEWORK_CYCLE_COMPLETE - Execution authority claim:
False - Next bounded action: Add executable observations, raw outputs, pinned versions, replay commands, and independent reproduction before making comparative-testing claims.
- Posting source: generated compatibility report
- Generated status is descriptive compatibility evidence only.
Generated Authored Analysis Boundary
This section is generated. Do not edit it manually.
- Framework ID:
mitre-atlas - Framework name:
MITRE ATLAS - Generated sections above this boundary may be rebuilt from registry, manifest, compatibility-report, and result artifacts.
- Authored analysis below this boundary may contain interpretation, notes, and framework-specific discussion.
- Generators must preserve authored analysis unless a future validator explicitly declares a migration path.
- Boundary rule: generated material is descriptive compatibility evidence only and does not create certification, endorsement, adoption, proof, or operational permission.
Generated Transition Mapping
This section is generated from the framework manifest. Do not edit it manually.
| Field | Generated Value |
|---|---|
framework_identity | MITRE ATLAS content v2026.06 |
source_reference | https://github.com/mitre-atlas/atlas-data/releases/tag/v2026.06 |
source_version | content 2026.06; v6-format distribution line |
allowed_use_boundary | adversarial AI threat-knowledge crosswalk evidence only |
claims | tactics, techniques, mitigations, case studies, relationships, and threat-informed review context |
non_claims | no admissibility proof, certification, endorsement, standing, execution authority, or commit-time authority |
input_artifact_type | pinned ATLAS release data and threat-context references |
output_artifact_type | crosswalk and bounded StegVerse governance compatibility evidence |
actor_or_authority_model | external threat-knowledge posture; no StegVerse actor authority inherited |
evidence_model | tactics, techniques, mitigations, case studies, relationships, and source-release identity |
policy_or_rule_model | mitigation and threat-informed policy reference comparison |
delegation_model | not established by ATLAS |
decision_or_result_model | threat-context evidence only |
execution_authority_claim | false |
receipt_or_trace_model | pinned public release, asset hash, wiki manifest, fixture, and generated validation reports |
reconstruction_model | pinned release plus crosswalk reconstructs the threat-context relationship and its limits |
SPE_overlap | may inform evidence and review posture, not standing determination |
StegVerse_ecosystem_overlap | Evidence Posture, Review Posture, Drift, Policy Reference, Reconstructability, Fail-Closed behavior |
fail_closed_conditions | missing source identity, mutable-only source reference, stale threat context, undefined mapping, or authority overclaim |
Generated mapping is compatibility evidence only.
Generated Framework Metadata
This section is generated from the external-framework registry. Do not edit it manually.
- Framework ID:
mitre-atlas - Name:
MITRE ATLAS - Registry status:
SOURCED-CROSSWALK-PROVISIONAL - Testbench state:
SOURCE_RECORDED_CROSSWALK_PROVISIONAL - Manifest path:
docs/external-frameworks/mitre-atlas.json - Source reference:
https://atlas.mitre.org/ - Metadata boundary: generated metadata is descriptive only; it does not create certification, endorsement, formalism adoption, admissibility proof, or execution authority.
Status
Relationship type: external framework crosswalk
Canonical StegVerse formalism source: Admissible-Existence
External framework role: adversarial AI threat knowledge base
Wiki role: threat-model observatory, evidence comparison, and relationship review
Evidence posture: PINNED_PUBLIC_RELEASE + BOUNDED_STEGVERSE_CROSSWALK
Runtime posture: NOT_APPLICABLE_AS_AUTHORITY_ENGINE
Standing: no standing created
Execution authority: none
Official Source And Version
The current bounded source identity used by this evaluation is the official MITRE ATLAS data release v2026.06, released 2026-06-30 from the mitre-atlas/atlas-data repository.
project: https://atlas.mitre.org/
data repository: https://github.com/mitre-atlas/atlas-data
pinned release: https://github.com/mitre-atlas/atlas-data/releases/tag/v2026.06
content version: 2026.06
release asset: ATLAS-2026.06.yaml
release asset SHA-256: b771de8b1489564b2838a709c7429849a9575dbd94073928817fe1a21661e70a
ATLAS separates knowledge-base content versioning from data-format versioning beginning with the 2026.05 / format 6.0.0 transition. This page therefore treats 2026.06 as the pinned content release and the v6 data model as a distinct format lineage. A mutable latest alias is not used as immutable source identity.
Evidence Provenance
| Evidence Class | Current Evidence | Status | Missing Fields |
|---|---|---|---|
| Official Framework Sources | Official MITRE ATLAS project, official atlas-data repository, pinned v2026.06 content release, and release asset SHA-256. | present_pinned_public_release | No source identity gap for the current bounded crosswalk. |
| Official Implementation Sources | ATLAS is evaluated here as a structured threat-knowledge base and machine-readable data distribution, not as an authorization runtime. Official repository data/validation tooling is source context only. | not_applicable_as_authorization_runtime | Runtime authorization evidence is not applicable to this evidence class. |
| Observed Behavior | No native MITRE ATLAS authorization or consequence-binding runtime behavior is claimed. | not_applicable_for_runtime_result | No runtime result is required for a bounded threat-context crosswalk. |
| Reproduced Behavior | No independent runtime reproduction is claimed. The pinned release identity and asset hash support source reconstruction, not execution reproduction. | not_applicable_for_runtime_result | Independent runtime reproduction would require a separately defined executable claim. |
| StegVerse Analysis | Pinned threat knowledge is mapped to Evidence Posture, Review Posture, Drift, Policy Reference, Reconstructability, and Fail-Closed behavior; six StegVerse case families exercise the mapping. | threat_context_crosswalk | Canonical merged-state validation is the remaining local gate. |
| Interoperability Assessment | The six-family StegVerse fixture tests whether threat evidence can influence review without becoming standing, delegation, or authority. | bounded_crosswalk_observed_by_canonical_validator | No certification or external endorsement is claimed. |
| Standing | Publication and mapping create no standing. | none_created | Standing must be independently reconstructed at the governed transition. |
Evidence classification:
F1: official MITRE ATLAS project/data sources, pinned content release v2026.06, release asset identity, and published release hash.
S1: StegVerse interpretation of ATLAS tactics, techniques, mitigations, case studies, and relationships as threat-context evidence rather than authority.
S2: StegVerse six-family governance mapping to Evidence Posture, Review Posture, Drift, Policy Reference, Reconstructability, and Fail-Closed behavior.
H1: any future claim that ATLAS itself grants standing, delegation, commit-time admissibility, certification, or execution authority remains prohibited unless separately evidenced and governed.
Framework-Term Definitions
| Native MITRE ATLAS Term | Definition For This Wiki | Reconciliation Class | Admissibility Relationship |
|---|---|---|---|
| MITRE ATLAS | External adversarial-AI threat knowledge base evaluated at pinned content release v2026.06. | new | Preserved as framework-native threat-context terminology; it is not a StegVerse authority source. |
| Tactic | High-level adversarial objective represented by ATLAS. | adjacent | Supports Review Posture and threat-context organization. |
| Technique | Described adversarial method or behavior represented by ATLAS. | adjacent | Supports Evidence Posture, Drift review, and failure-context reconstruction. |
| Mitigation | Defensive guidance associated with adversarial techniques or threat conditions. | adjacent | May inform Policy Reference and Boundary Conditions; mitigation guidance is not proof of implementation. |
| Case study | ATLAS record describing adversarial-AI activity or scenario context. | adjacent | May support evidence provenance and reconstruction, subject to source and applicability review. |
| Relationship | Structured association among ATLAS objects in the machine-readable knowledge base. | adjacent | Supports reconstructable threat-context linkage; relationship data does not confer authority. |
| Content version | Release identity for the ATLAS knowledge content. | new | Must be pinned for freshness and reconstruction. |
| Data-format version | Version lineage for the machine-readable ATLAS representation. | new | Must remain distinct from content identity to avoid semantic/version drift. |
What MITRE ATLAS Claims And Demonstrates
MITRE ATLAS provides structured adversarial-AI threat knowledge including tactics, techniques, mitigations, case studies, and relationships. Its official data repository also provides machine-readable distribution artifacts and validation/data-management tooling for the ATLAS data model.
Those capabilities establish threat taxonomy and threat-context evidence. They do not establish actor delegation, StegVerse standing, commit-time admissibility, consequence binding, or execution authority.
StegVerse Evidence Installed
The repository already contains the following bounded evaluation machinery and it is treated as supporting evidence rather than as proof that MITRE itself executed StegVerse tests:
manifest: docs/external-frameworks/mitre-atlas.json
benchmark fixture: docs/external-frameworks/fixtures/mitre-atlas-benchmark-fixture.v0.1.json
governance compatibility cases: tests/fixtures/external-frameworks/mitre-atlas-governance-compatibility-cases.v1.json
case families: 6
simulation_only: true
canonical validation path: .github/workflows/validate-chain-continuation.yml
The six StegVerse case families are:
| Family | Bounded Expected Posture |
|---|---|
| positive alignment | Threat context may support ALLOW only when independent authority, policy, scope, and freshness predicates remain satisfied. |
| framework denial / negative result | A critical unmitigated threat maps to DENY within the evaluated scope. |
| authority / delegation failure | Threat context cannot restore expired or absent delegation; result remains DENY. |
| stale / missing evidence | Stale technique or threat-context evidence fails closed. |
| malformed / undefined result | Mapping errors fail closed. |
| semantic divergence guard | Threat or mitigation evidence for one scope cannot authorize a different consequence scope. |
The canonical external-framework validator has observed all six MITRE ATLAS case families in the repository-wide compatibility contract. This is a StegVerse governance test of the installed mapping; it is not runtime execution of MITRE ATLAS as an authorization engine.
Failure Classes Exercised
UNMITIGATED_THREAT
AUTHORITY_DRIFT
STALE_THREAT_CONTEXT
ATLAS_MAPPING_ERROR
SCOPE_DIVERGENCE
The positive case carries no failure class when all independently evaluated StegVerse predicates are satisfied.
Governance-Chain Placement
MITRE ATLAS belongs upstream of commit-time admissibility as threat-context and review evidence:
pinned ATLAS release / tactic / technique / mitigation / case-study reference
-> Evidence Posture + Review Posture + Drift / Policy Reference context
-> Commitment Candidate evidence set
-> independent standing / delegation / policy / scope / freshness reconstruction
-> commit-time admissibility decision
-> consequence binding only if separately authorized
ATLAS evidence can change the evidence available to the gate. It does not become the gate and does not inherit authority from its inclusion.
Claims Versus Demonstrated Abilities
| Question | Current Evidence |
|---|---|
| Is an official public source identified? | Yes. |
| Is a current public release pinned? | Yes: content v2026.06. |
| Is an immutable release-asset hash recorded? | Yes. |
| Are content and data-format versions distinguished? | Yes. |
| Does ATLAS provide structured threat knowledge? | Yes, according to the official project/data release. |
| Has StegVerse authored a six-family compatibility contract? | Yes. |
| Has the repository canonical validator exercised those six case families? | Yes, as bounded StegVerse mapping tests. |
| Is native MITRE ATLAS runtime authorization execution claimed? | No. |
| Is independent interoperability certification claimed? | No. |
| Does threat classification create StegVerse standing? | No. |
| Does ATLAS grant execution authority? | No. |
Non-Capabilities And Non-Claims
MITRE ATLAS is not a StegVerse canonical formalism.
MITRE ATLAS does not prove transition admissibility.
MITRE ATLAS does not establish actor identity or delegation.
MITRE ATLAS does not grant execution authority inside StegVerse.
Threat-informed review is evidence/review context, not authority.
The StegVerse six-case fixture is simulation/crosswalk evidence, not a MITRE certification or endorsement.
Publication of this page creates no standing.
Current Completion Gate
The locally available source identity, immutable release asset hash, mapping fixture, six-family compatibility contract, governance-chain placement, terminology reconciliation, evidence-provenance contract, and non-capability boundaries are now installed. The remaining local gate is canonical validation of this repaired merged page/manifest state. If those MITRE-specific source, manifest, terminology, page, benchmark, provenance, and governance-compatibility checks pass, this evaluation can reach LOCAL_WORK_COMPLETE_BOUNDED_THREAT_CROSSWALK without inventing runtime or certification evidence.
Challenge Path
A reader may challenge this reflection by identifying the exact source, version, mapping, failure class, governance-chain placement, or non-claim at issue and supplying inspectable evidence for correction.
Mandatory Footer
This page reflects a bounded admissibility packet. Publication does not create standing. The reflected claim inherits only the standing that can be reconstructed from the referenced evidence, authority, and admissibility conditions.