Step 1 of 3: Identity
CMMC 2.0
Phase 3 · Evidence & auditAutomated drift monitoring, control degradation alerts, and continuous attestation state engine.
Basis: Continuous Monitoring & Baselines
/cmmc/driftDoD Cybersecurity Maturity Model Certification (CMMC 2.0 / NIST SP 800-171)
3 steps, completed in order. Each step is validated against the schema before the next unlocks.
Step 1 of 3
Complete the Identity fields. Each value is validated against the schema before the next step unlocks.
Domain entity ID (required)
entityIdThe organisation or system this record is about — lowercase with dashes, e.g. acme-corp-hq. Pick one you have used before, or type a new id to create it.
Step 2 of 3
Complete the Detection fields. Each value is validated against the schema before the next step unlocks.
Drift event type (required)
eventTypeEnter drift event type.
Severity (required)
severityEnter severity.
Affected controloptional
affectedControlIdEnter affected control.
Detected byoptional
sourceSystemConnector or monitor that raised the event.
Patternoptional
patternIsolated events and systemic ones need different responses.
Step 3 of 3
Complete the Investigation fields. Each value is validated against the schema before the next step unlocks.
Material to compliance posture (required)
materialToComplianceImmaterial drift is recorded but does not move readiness.
Investigation notesoptional
investigationNotesEnter investigation notes.
Continue with the next guide in this framework's table of contents.
Immutable evidence custody, SHA-256 integrity verification, and custody transition locking.
Read guide Phase 3 · Evidence & auditImmutable cryptographic hash chains linking evidence items to executive attestation verdicts.
Read guide Phase 3 · Evidence & auditTelemetry collection for assessment compute tokens, verification runs, and tenant billing limits.
Read guide