This guide covers Level 1 (Self), Level 2 (Self) and Level 2 (C3PAO).
Only Level 2 (C3PAO) comes from a certification assessment by a C3PAO; the other two come from your own self-assessment, so the rest of this guide uses the rule’s term, CMMC status.
What the rule requires after you have a status
Under 32 CFR 170.22, the Affirming Official affirms continuing compliance after every assessment, including a POA&M closeout, and annually thereafter.
| CMMC Status | Assessment repeats | Affirmation | Current under DFARS 252.204-7021 | POA&M | Artifacts kept |
|---|---|---|---|---|---|
| Level 1 (Self) | Every year (170.15) | At completion, then annually (170.22) | Final: not older than 1 year | Not permitted (170.21) | Six years from the CMMC Status Date (170.15) |
| Level 2 (Self) | Every three years (170.16) | At each assessment, including a POA&M closeout, then annually after the Final CMMC Status Date (170.16, 170.22) | Conditional: not older than 180 days; Final: not older than 3 years | Allowed for a Conditional status within the 170.21 limits; closeout self-assessment within 180 days (170.21) | Six years from the CMMC Status Date (170.16) |
| Level 2 (C3PAO) | Every three years, by a C3PAO (170.17) | At each assessment, including a POA&M closeout, then annually after the Final CMMC Status Date (170.17, 170.22) | Conditional: not older than 180 days; Final: not older than 3 years | Allowed for a Conditional status within the 170.21 limits; closeout by a C3PAO within 180 days (170.21) | Six years from the CMMC Status Date, as hashed artifacts (170.17) |
The “current” column comes from DFARS 252.204-7021, the contract clause that defines when a status counts as current; the other columns come from 32 CFR part 170.
After a successful closeout, the CMMC Status Date stays the date of the Conditional status; a Final that follows a Conditional gets no new date.
The annual affirmation guide covers who the Affirming Official is and how the affirmation is entered in SPRS.
What makes a status lapse or need a new assessment
Under DFARS 252.204-7021, a CMMC status is current only with an affirmation of continuous compliance not older than one year.
A missed annual affirmation therefore means the status no longer counts as current under the clause.
The status counts as current only with no changes in compliance with the CMMC requirements since the status date.
A Final Level 1 (Self) status is current for no more than one year, and a Final Level 2 status for no more than three years.
If the POA&M is not successfully closed out within the 180-day timeframe, the Conditional CMMC Status for the information system expires.
If a Conditional status expires during a contract, standard contractual remedies apply, and the company is ineligible for new awards that require that status, or higher, for that information system until it achieves a new one.
Under 32 CFR 170.16 and 170.17, DoD may conduct a DCMA DIBCAC assessment of a company with a Level 2 status, and if it shows the requirements were not achieved or maintained, its results take precedence over the existing status.
Changes to the assessment scope
32 CFR part 170 does not say which changes to systems or to the assessment scope require a new assessment.
The nearest text in the rule is the affirmation itself, which attests that the company has implemented and will maintain all applicable requirements for all information systems in the assessment scope.
DFARS 252.204-7021 says CMMC assessments will not duplicate other DoD assessments, except in rare circumstances when a reassessment may be necessary, for example when there are indications of issues with cybersecurity or compliance.
The clause also has you report to the contracting officer any changes in the CMMC UIDs generated in SPRS during the contract.
DoD’s CMMC scoping guides, which state that they do not have the force and effect of law, say a new assessment is required if there are significant architectural or boundary changes to the previous assessment scope, such as expansions of networks or mergers and acquisitions.
They also say that operational changes inside the existing boundary, such as adding or removing resources in a way that follows the existing system security plan, do not require a new assessment and may be covered by the annual affirmation.
Neither the rule nor the scoping guides say what makes a change significant.
Until DoD says more, a practical approach is to write down each change to your systems or scope, and why you decided it did or did not call for a new assessment.
The requirements that never finish
The security requirements in CMMC Level 2 are identical to the 110 requirements in NIST SP 800-171 Revision 2, even though NIST has withdrawn Revision 2 and replaced it with Revision 3.
The table lists the requirements whose own sentence, or whose NIST SP 800-171A assessment objectives, make them recur: periodically, on an ongoing basis, or each time something happens.
Where a requirement says “periodically”, NIST SP 800-171A has you define the frequency and then meet it, and the CMMC scoring rule needs evidence that you did.
NIST SP 800-171 Revision 2 sets no number for these frequencies.
| Requirement | What recurs | Wording (NIST SP 800-171 Rev 2) | How often | Applies at |
|---|---|---|---|---|
| 3.1.12 | Remote access sessions | “Monitor and control remote access sessions.” | Ongoing | Level 2 |
| 3.3.3 | The events you log | “Review and update logged events.” | When your defined review process says (3.3.3[a]) | Level 2 |
| 3.4.1 | Baseline configurations and the system inventory | “Establish and maintain baseline configurations and inventories of organizational systems” | Maintained (reviewed and updated) throughout the system life cycle (3.4.1[c], [f]) | Level 2 |
| 3.4.3 | Changes to systems | “Track, review, approve or disapprove, and log changes to organizational systems.” | Each change | Level 2 |
| 3.4.9 | User-installed software | “Control and monitor user-installed software.” | Ongoing | Level 2 |
| 3.10.2 | The physical facility | “Protect and monitor the physical facility and support infrastructure for organizational systems.” | Ongoing | Level 2 |
| 3.10.3 | Visitors | “Escort visitors and monitor visitor activity.” | Each visit | Level 1 and Level 2 |
| 3.11.1 | Risk assessment | “Periodically assess the risk to organizational operations” | A frequency you define (3.11.1[a]) | Level 2 |
| 3.11.2 | Vulnerability scans | “Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.” | A frequency you define (3.11.2[a]), and when new vulnerabilities are identified | Level 2 |
| 3.12.1 | Security control assessment | “Periodically assess the security controls in organizational systems” | A frequency you define (3.12.1[a]) | Level 2 |
| 3.12.3 | Security control monitoring | “Monitor security controls on an ongoing basis” | Ongoing | Level 2 |
| 3.12.4 | The system security plan | “Develop, document, and periodically update system security plans” | A frequency you define (3.12.4[g]) | Level 2 |
| 3.13.1 | Communications at system boundaries | “Monitor, control, and protect communications” | Ongoing | Level 1 and Level 2 |
| 3.13.13 | Mobile code | “Control and monitor the use of mobile code.” | Ongoing | Level 2 |
| 3.13.14 | Voice over IP | “Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.” | Ongoing | Level 2 |
| 3.14.3 | Security alerts and advisories | “Monitor system security alerts and advisories and take action in response.” | Ongoing | Level 2 |
| 3.14.4 | Malicious code protection | “Update malicious code protection mechanisms when new releases are available.” | When new releases are available | Level 1 and Level 2 |
| 3.14.5 | Malicious code scans | “Perform periodic scans of organizational systems and real-time scans of files from external sources” | A frequency you define (3.14.5[a]), and in real time for files from external sources | Level 1 and Level 2 |
| 3.14.6 | System monitoring | “Monitor organizational systems, including inbound and outbound communications traffic” | Ongoing | Level 2 |
At Level 1, the four requirements marked “Level 1 and Level 2” are assessed against the NIST SP 800-171A objectives of the matching NIST requirement, as 32 CFR 170.15 maps them.
Security awareness training (3.2.1 and 3.2.2) and incident response testing (3.6.3) set no frequency in their requirement text or NIST SP 800-171A objectives.
For training, the discussion in NIST SP 800-171 says organizations determine the content and frequency themselves.
A year of upkeep
Each line is one of three kinds: required, with its citation; DoD guidance, with its source; or a common practice you can adapt.
| When | What | Basis |
|---|---|---|
| Continuously | Keep every requirement for your status implemented. | Required by 32 CFR 170.22 |
| Continuously | Monitor security controls to confirm they stay effective. | Required by NIST SP 800-171 3.12.3 |
| Continuously | Monitor security alerts and advisories, and act on them. | Required by NIST SP 800-171 3.14.3 |
| Continuously | Monitor communications at the system boundary. | Required by NIST SP 800-171 3.13.1 |
| Continuously | Monitor systems and traffic to detect attacks. | Required by NIST SP 800-171 3.14.6 |
| At the frequency you define | Scan for vulnerabilities. | Required by NIST SP 800-171 3.11.2 |
| At the frequency you define | Scan your systems for malicious code. | Required by NIST SP 800-171 3.14.5 |
| At the frequency you define | Review and update the events you log. | Required by NIST SP 800-171 3.3.3 |
| At the frequency you define | Assess risk. | Required by NIST SP 800-171 3.11.1 |
| At the frequency you define | Assess whether your security controls are effective. | Required by NIST SP 800-171 3.12.1 |
| At the frequency you define | Update the system security plan. | Required by NIST SP 800-171 3.12.4 |
| Monthly | Consider reviewing patch status and open plans of action. | Common practice |
| Monthly | Consider checking that backups finish and can be restored. | Common practice |
| Quarterly | Consider reviewing user accounts and removing access no one needs. | Common practice |
| Quarterly | Consider checking your evidence for anything stale or expired. | Common practice |
| Yearly | The Affirming Official affirms in SPRS. | Required by 32 CFR 170.22 |
| Yearly | Level 1: conduct a new self-assessment and enter the results in SPRS. | Required by 32 CFR 170.15 |
| Yearly | Consider reviewing your policies before the affirmation. | Common practice |
| Yearly | Consider refreshing security awareness training. | Common practice |
| Yearly | Consider testing your incident response plan. | Common practice |
| Every three years | Level 2: complete a new self-assessment or C3PAO assessment within three years of the CMMC Status Date. | Required by 32 CFR 170.16 and 170.17 |
| Within 180 days of a Conditional status | Close out the POA&M with a closeout assessment. | Required by 32 CFR 170.21 |
| On a change | Track, review, approve or disapprove, and log changes to systems. | Required by NIST SP 800-171 3.4.3 |
| On a change | Keep baseline configurations and the system inventory reviewed and updated. | Required by NIST SP 800-171 3.4.1 |
| On a change | Scan for vulnerabilities when new ones affecting your systems are identified. | Required by NIST SP 800-171 3.11.2 |
| On a change | Update malicious code protection when new releases are available. | Required by NIST SP 800-171 3.14.4 |
| On a change | Tell the contracting officer about any change in your CMMC UIDs. | Required by DFARS 252.204-7021 |
| On a change | DoD’s scoping guides say a new assessment is required after significant architectural or boundary changes. | DoD guidance (CMMC scoping guides) |
Evidence to keep, and for how long
Keep the evidence as you go: assessment artifacts must be retained for six years from the CMMC Status Date.
After a C3PAO assessment, the artifacts must also be hashed with a NIST-approved hashing algorithm, and the list of artifact names and hash values goes into the CMMC instance of eMASS.
Evidence has to be final: the CMMC scoring rule does not accept working papers, drafts, or unofficial or unapproved policies.
The system security plan has to be up to date at the time of assessment; without it, the finding is that an assessment could not be completed.
NIST SP 800-171 3.3.1 has you define retention requirements for audit records and retain them as defined.
It sets no retention period of its own.
Between assessments, it helps to keep dated records of each recurring task, such as scan reports, log reviews, change tickets and training records.
Which kinds of tool do what
A tracking tool records status and reminds you of dates; it does not implement a control.
A requirement is MET when all of its applicable objectives are satisfied based on evidence, and NOT MET when one or more is not.
| Kind of tool | What it does | NIST SP 800-171 requirements it supports |
|---|---|---|
| Compliance tracking and evidence | Records the status of each requirement, stores evidence and reminds you of dates such as the annual affirmation. | 3.12.1 control assessment, 3.12.3 control monitoring, 3.12.4 system security plan |
| Log collection and review | Collects audit logs in one place and alerts on unusual activity. | 3.3.3 logged events, 3.14.6 system monitoring |
| Vulnerability scanning and patching | Finds known vulnerabilities and deploys fixes. | 3.11.2 vulnerability scans, 3.14.3 alerts and advisories |
| Endpoint protection | Scans for malicious code, keeps its protection updated and controls what users install. | 3.14.4 malicious code protection, 3.14.5 malicious code scans, 3.4.9 user-installed software |
| Identity and access | Controls sign-in and remote access, and records who connected. | 3.1.12 remote access sessions |
| Training | Delivers and records security awareness training. | 3.2.1 and 3.2.2 (frequency you determine) |
| Backup | Copies data on a schedule and protects the copies. | 3.8.9 backup CUI (no frequency set) |
| Ticketing for changes and incidents | Records each change request and incident, with who approved or handled it. | 3.4.3 changes to systems, 3.6.2 incidents |
For named products, compared from their own sites, see the row on staying compliant after the assessment in the best CMMC compliance software guide.
How CMMCSync helps
The Foundations plan (Free) includes an annual affirmation workflow. Drift detection flags controls that regressed, evidence that went stale and policies that expired between assessments, so your Affirming Official can see what changed before affirming. POA&M management and SPRS score tracking are on the Maintain plan. Compare plans on the pricing page.
Sources
- 32 CFR 170.4, Acronyms and definitions
- 32 CFR 170.15, CMMC Level 1 self-assessment and affirmation requirements
- 32 CFR 170.16, CMMC Level 2 self-assessment and affirmation requirements
- 32 CFR 170.17, CMMC Level 2 certification assessment and affirmation requirements
- 32 CFR 170.19, CMMC scoping
- 32 CFR 170.21, Plan of Action and Milestones requirements
- 32 CFR 170.22, Affirmation
- 32 CFR 170.24, CMMC Scoring Methodology
- DFARS 252.204-7021, Contractor Compliance with the CMMC Level Requirements
- NIST SP 800-171 Revision 2, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations
- NIST SP 800-171A (June 2018), Assessing Security Requirements for Controlled Unclassified Information
- DoD CIO, CMMC Scoping Guide Level 1, Version 2.13 (September 2024)
- DoD CIO, CMMC Scoping Guide Level 2, Version 2.13 (September 2024)
General information, not legal advice.