Cybersecurity & Governance

Keeping CMMC Evidence Current During the Phase II Pause

Keep CMMC self-assessment evidence traceable during the Phase II pause, with practical guidance on scope, SSPs, versions, remediation, and human review.

A pause in an implementation phase does not keep an organization’s security evidence current. Systems change, people move into new roles, and an assessment record can stop describing the environment it was intended to explain. The useful question for a defense contractor is not simply when the next phase starts. It is whether today’s records still support today’s self-assessment.

As of October 7, 2026, the Department’s official CMMC guidance states that Phase II is suspended, while Phase I self-assessment requirements remain in place. It identifies NIST SP 800-171 Revision 2 as the interim baseline for Level 2, with self-assessments and select government-led assessments. The suspension does not remove applicable obligations to safeguard covered defense information under DFARS 252.204-7012 (U.S. Department of War Chief Information Officer, n.d.).

This guide focuses on maintaining a reviewable evidence trail, not determining your organization’s CMMC status. Check current official guidance, applicable solicitations, contracts, and flow-down requirements with qualified personnel before making an assessment or contractual decision. Meritwright LLC is independent of the government; this article is general educational information, not legal advice or an official compliance determination.

Start with the right scope and framework version

Before collecting more documents, establish what the assessment covers. Record the organization, environment, system boundary, responsible owners, and applicable assessment level. Keep that scope with the evidence so a reviewer can distinguish material for the assessed environment from material for another location, business unit, or system.

Version control matters here. NIST superseded Revision 2 with Revision 3 in May 2024, but that does not automatically change the CMMC baseline identified in the Department’s current guidance. Do not silently substitute a newer checklist or combine requirement identifiers from different revisions. Label the source, revision, and assessment objectives used in each assessment record, and preserve them when requirements change (National Institute of Standards and Technology, n.d.).

The Revision 2 and SSP examples below primarily concern Level 2. They should not be read as additional requirements for Level 1. Match the evidence process to the level and obligations that actually apply to your organization.

Keep the system security plan aligned with the environment

A system security plan, or SSP, should describe the environment being assessed, not just the environment that existed when the document was first written. Revision 2 requirement 3.12.4 calls for developing, documenting, and periodically updating plans that explain boundaries, operating environments, implementation, and connections to other systems (Ross et al., 2020).

As a practical maintenance step, review the SSP when a relevant change occurs: a new service provider, identity system, remote-access arrangement, data flow, or responsibility. Compare the description with the actual environment. If they differ, record the discrepancy and update the relevant documentation rather than allowing a polished plan to conceal an unresolved gap.

Keep a short revision history explaining what changed, who reviewed it, and which supporting records were affected. The purpose is to make the plan understandable and maintainable, not to produce a longer document.

Connect each conclusion to supporting evidence

An evidence folder becomes more useful when someone can explain why each item is there. A practical index can connect:

  • Requirement and objective: the exact identifier and framework version being assessed.
  • Implementation: how the organization says it meets the requirement in the defined scope.
  • Supporting record: where the relevant document, configuration export, observation, or test result is kept.
  • Context: the system, source, collection date, and period covered.
  • Review: who evaluated it, what conclusion they reached, and any limitations.
  • Follow-up: the finding or remediation record when support is incomplete.

These are recommended organizational fields, not a mandatory government template. Link to controlled source records rather than creating uncontrolled copies for every requirement. Where one record supports several objectives, explain the relevant section or observation for each relationship.

The official Level 2 assessment guide describes examination, interviews, and testing as assessment methods. A policy states an expectation; it does not, by itself, demonstrate that every relevant safeguard operates as described. Choose evidence and assessment activities that address the objective, rather than treating the existence of a file as sufficient support (U.S. Department of Defense Chief Information Officer, 2024).

Track freshness as well as collection dates

For day-to-day evidence management, ask two separate questions: when was this collected, and does it still represent the environment?

A recent screenshot may cover only one system. An older architecture diagram may still be accurate, or may have become misleading after a network change. Record the evidence’s coverage and the conditions that would trigger review, not just its age.

Useful internal labels include current, review due, changed, superseded, missing, and unverified. Define what each means for your team. Set review intervals according to the evidence type, relevant changes, risk, and applicable requirements. This article does not prescribe a universal evidence expiry period or replace required assessment and affirmation schedules.

Preserve versions without overstating what a hash proves

Keep the version reviewed for an assessment alongside later replacements, subject to your approved retention policy. Record why an item was superseded and which decision relied on it. A controlled snapshot of the evidence index, SSP revision, findings, and review records can help reconstruct the basis of an assessment at a particular time.

Where appropriate, a cryptographic hash can help detect whether a file differs from a previously recorded version. It does not establish that the content is true, that its original source is trustworthy, or that a safeguard meets a requirement. A hash stored in an editable record also needs protection if it is to be useful as an integrity reference.

Keep evidence in an authorized location with access controls, protected recovery copies, and a retention process. Evidence can reveal sensitive configurations or contain protected information. Do not move it into an unapproved tool, public sharing link, or external AI service merely to simplify review. Local storage alone does not establish compliant handling.

Document gaps and verify remediation

When support is incomplete, make the uncertainty visible. Record the affected requirement, observed gap, responsible owner, planned action, due date, and the evidence needed to verify completion. Closing a ticket should not automatically mean the original assessment conclusion is now supported. Review the resulting state and preserve that verification.

Keep ordinary remediation tracking separate from a formal CMMC assessment plan of action and milestones, or POA&M. The Level 2 assessment guide distinguishes operational plans of action from assessment POA&Ms (U.S. Department of Defense Chief Information Officer, 2024). Current CMMC guidance says Level 1 does not permit POA&Ms and Level 2 permits them only under defined conditions. An internal backlog is not blanket permission to leave requirements unmet or claim conditional status (U.S. Department of War Chief Information Officer, n.d.).

Make human review explicit

A defensible record should explain who made a conclusion and on what basis. Give reviewers enough context to evaluate relevance, coverage, freshness, and contradictory information. Preserve unresolved questions and escalation decisions rather than allowing a dashboard to hide them.

Evidence preparation is also distinct from official reporting. For applicable offers, DFARS 252.204-7019 addresses current assessment scores in the Supplier Performance Risk System, or SPRS. An internal evidence index or software export does not submit those results or replace the required process. Have authorized personnel verify the applicable reporting and affirmation steps through current official channels (48 C.F.R. § 252.204-7019, 2026).

Why this workflow matters to Regivance

Regivance is in development. It is being designed to assist organizations with this operational problem: connecting scope, requirements, assessment objectives, implementation details, supporting evidence, versions and hashes, human review, findings, remediation, decisions, and snapshots in a governed workflow.

For teams preparing for CMMC, that is a useful evidence-management direction, not a claim that the product is available or certifies compliance. Planned features and supported framework versions remain subject to change. Confirm the released product’s actual capabilities and baseline support before relying on it for a particular assessment.

Regivance is designed to support organizing, reviewing, tracing, and maintaining evidence while keeping qualified human judgment central. It does not replace an authorized assessor, issue an official compliance determination, or submit information to government systems on an organization’s behalf.

The immediate step is available without any new software: select one important requirement and trace it from the defined scope through implementation, supporting records, review, and any open remediation. If another qualified person cannot follow that trail, improve the record before treating the conclusion as dependable.

References