CMMC v2.0 (DoD contractors) with 5 levels and C3PAO assessment prep

version
0.1.0
GitHub stars
436

Install

/plugin install cmmc@grc-engineering-suite

Run it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.

Contents

Discovered from source

Skills 2

CMMC Assessment Objective Source Guide

Review required: This is an unverified working aid, not an authoritative assessment or legal determination. Verify objective wording, labels, applicability, scoring, and crosswalks in official sources and obtain qualified CMMC review. If a source or contract is unavailable, mark the conclusion unverified; do not infer compliance.

The previous local objective catalog and revision crosswalk have been removed because their exact wording, labels, and mappings were not verified. Do not reconstruct an exact catalog from memory or present this guide as a verbatim reference.

Source-based lookup

  1. Check the solicitation or contract, assessment level and current program rules. Use 32 CFR 170.14, 170.15, 170.16, and 170.17 as appropriate. Level 1 mapping is specified separately; do not assume the Level 2 process applies unchanged.
  2. Consult NIST SP 800-171A (June 2018) for assessment procedures and NIST SP 800-171 Rev 2 for requirement text where applicable. The NIST publication was withdrawn and superseded, but is incorporated by reference in the CMMC regulation; verify current incorporation and applicable edition.
  3. Locate the precise requirement and copy only its source-verified determination statement and label. Some determination statements are lettered and others are not: 3.13.11 is unlettered in the June 2018 publication. Never invent a letter suffix. Record source, edition and location; if inaccessible, say the objective is unverified.
  4. Identify appropriate examine, interview and test activities based on the source, assessment scope and evidence. These are potential methods, not a mandatory universal artifact list. Separate observations from decisions and avoid inventing evidence or certification outcomes.
  5. For scoring and conditional status, check 32 CFR 170.24 and 32 CFR 170.21, including all restrictions. CA.L2-3.12.4 cannot be on a Level 2 POA&M; IA.L2-3.5.3 is subject to the point-value restrictions.

Revision transition

Use NIST's CUI project resources for revision comparison and verify individual mappings in NIST publications. A crosswalk is a planning aid, not proof that one revision satisfies another or that a requirement is met. Under Rev 2, 3.3.7 requires capability to compare and synchronize clocks with an authoritative source; it does not prescribe NTP. Do not change the contractually applicable edition based solely on a newer publication.

CMMC Expert

Review required: This material is an unverified working aid, not an authoritative assessment or legal determination. Verify every control, objective, scope, assessment type, scoring and contractual claim against current official sources and obtain qualified CMMC and contracting review before use. If a source or contract is unavailable, mark the conclusion unverified; do not infer compliance.

Deep, practitioner-grade expertise in the Cybersecurity Maturity Model Certification (CMMC) v2.0 for Department of Defense contractors. Built from the authoritative chain: NIST SP 800-171 Rev 2 (control text), NIST SP 800-171A (June 2018) (assessment procedures), 32 CFR Part 170 (CMMC program rule), and 48 CFR / DFARS Part 204.75 (acquisition rule).

1. Program Overview & Authority

Purpose: Standardize verification of NIST SP 800-171 cybersecurity controls across the Defense Industrial Base (DIB) protecting Controlled Unclassified Information (CUI) and Federal Contract Information (FCI).

Authority chain:

  • 32 CFR Part 170 — CMMC program rule. Effective December 16, 2024.
  • 48 CFR / DFARS Part 204.75 — Acquisition rule that puts CMMC into contracts. Effective November 10, 2025.
  • DFARS 252.204-7012 — Pre-existing CUI safeguarding + 72-hour cyber incident reporting clause.
  • DFARS 252.204-7019 — Solicitation provision requiring a current NIST 800-171 self-assessment score in SPRS.
  • DFARS 252.204-7020 — Contract clause giving DoD/DIBCAC the right to verify SPRS assessments.
  • DFARS 252.204-7021 — The primary CMMC certification requirement clause.
  • DFARS 252.204-7025 — Solicitation provision identifying the required CMMC level for a given procurement.

Authoritative sources to cite in deliverables:

  • NIST SP 800-171 Rev 2 — https://doi.org/10.6028/NIST.SP.800-171r2 (Final, including updates as of 01-28-2021; withdrawn May 14, 2024 but remains operative for CMMC).
  • NIST SP 800-171A (June 2018) — assessment procedures, 320 objectives.
  • CMMC Assessment Guide L2 (current version on dodcio.defense.gov).
  • CMMC Scoping Guide L2.
  • CMMC Scoring Methodology.
  • 32 CFR Part 170 (89 FR 83214, Oct. 15, 2024).

Implementation status requires current verification

The Department announced on July 13, 2026 that Phase II requirements were suspended while Phase I self-assessment requirements remain in place; the announcement also describes a program review. See the official announcement and current resource links. Do not represent the originally published phase dates as the current rollout. Check for subsequent changes and review the actual contract, regulations and guidance before advising on required assessment type or timing.


2. CMMC Levels (L1 / L2 / L3)

LevelNamePracticesSourceAssessmentPOA&M AllowedCycle
Level 1Foundational15FAR 52.204-21Self onlyNo — neverAnnual self + annual affirmation
Level 2Advanced110NIST SP 800-171 Rev 2Self or C3PAOYes — restricted (see §11)Triennial + annual affirmation
Level 3Expert134 (110 + 24 selected from 800-172)NIST SP 800-171 Rev 2 + 800-172DCMA DIBCACPer DIBCAC methodologyTriennial + annual affirmation

Acronyms used here (correctly):

  • OSA — Organization Seeking Assessment.
  • OSC — Organization Seeking Certification (used specifically in C3PAO context; OSA/OSC are largely interchangeable in practice).
  • C3PAO — Certified Third-Party Assessor Organization. Accredited by the Cyber AB.
  • CCA — Certified CMMC Assessor. Assessment personnel must meet the applicable Tier 3 investigation or equivalence requirements in 32 CFR 170.9(b)(3)–(4).
  • CCP — Certified CMMC Professional (support role).
  • DIBCAC — Defense Industrial Base Cybersecurity Assessment Center (DCMA's assessment arm; conducts L3 assessments and high-water-mark L2 verifications).
  • DC3 — DoD Cyber Crime Center (recipient of malware samples under DFARS 7012).
  • eMASS — Enterprise Mission Assurance Support Service (DoD system where C3PAO assessment results are posted).
  • SPRS — Supplier Performance Risk System (where self-assessment scores and CMMC Status live).

Who needs what:

  • Verify the solicitation or contract and applicable clauses before assigning a status; if unavailable, leave it unverified.
  • FCI-only subcontracts subject to 32 CFR 170.23 require L1 (Self); CUI subcontract minimums depend on the prime requirement. The DFARS 252.204-7021(f) flow-down excludes commercially available off-the-shelf items.
  • The contract specifies the required CMMC level and assessment type, including any Level 3 requirement.

3. NIST 800-171 Rev 2 — 14 Families, 110 Controls

These are the only 14 families in Rev 2. Any reference to Asset Management (AM), Recovery (RE), Risk Management (RM), or Situational Awareness (SA) as 800-171 families is incorrect — those names belong to CMMC v1.0 or to other catalogs.

#IDFamilyControls
1ACAccess Control22
2ATAwareness and Training3
3AUAudit and Accountability9
4CMConfiguration Management9
5IAIdentification and Authentication11
6IRIncident Response3
7MAMaintenance6
8MPMedia Protection9
9PSPersonnel Security2
10PEPhysical Protection6
11RARisk Assessment3
12CASecurity Assessment4
13SCSystem and Communications Protection16
14SISystem and Information Integrity7
TOTAL110

Numbering scheme: Chapter.Family.Requirement (e.g., 3.1.1 = Chapter 3, AC family, Requirement 1). Each requirement is either Basic (high-level) or Derived (technical implementation specifics) in Rev 2.


4. Assessment objectives

Consult NIST SP 800-171A (June 2018) directly for the applicable assessment objective and determination statements. Some statements are lettered; others, including 3.13.11, are unlettered. Verify labels and wording in the source; do not invent letter suffixes.

5. Assessment Methods — Examine / Interview / Test

Per NIST SP 800-171A (June 2018), assessors use exactly three methods (not four). The verb "Determine" that opens each assessment objective is not a method — it's the assessor's overall judgment, supported by E/I/T evidence.

MethodWhat it isDepth attributes
ExamineReviewing, inspecting, observing, studying, or analyzing assessment objects (specifications, mechanisms, activities)Basic / Focused / Comprehensive
InterviewDiscussions with individuals or groups to facilitate understanding, achieve clarification, or obtain evidenceBasic / Focused / Comprehensive
TestExercising assessment objects under specified conditions to compare actual vs. expected behaviorBasic (black box) / Focused (gray box) / Comprehensive (white box)

Assessment objects assessors examine or test:

  • Specifications — policies, procedures, plans, SSP, designs, requirements.
  • Mechanisms — hardware, software, firmware controls.
  • Activities — operations, exercises, backup runs.
  • Individuals — system owners, admins, security personnel, users.

Evidence planning: Documents, technical artifacts, and interviews are possible assessment inputs; select methods and objects appropriate to the requirement, assessment scope, and official assessment guidance. No universal three-item evidence requirement is implied.


6. CUI & FCI — Definitions, Marking, Boundary

FCI — Federal Contract Information

  • Information provided by or generated for the Government under a contract.
  • Not intended for public release.
  • FCI and CUI definitions can overlap; identify each under its applicable definition.
  • FCI alone does not categorically trigger a CMMC assessment. Check 32 CFR 170.3, the solicitation or contract, applicable phase-in and exceptions, and the required status.
  • Examples: pricing, delivery schedules, contract-related correspondence.

CUI — Controlled Unclassified Information

  • Information requiring safeguarding or dissemination controls per law, regulation, or government-wide policy.
  • Governed by 32 CFR Part 2002 and the CUI Registry at cui.archives.gov.
  • The CUI Registry contains the authoritative list of CUI categories (organized under ~20 organizational index groupings), each with its own marking and handling rules.
  • CUI alone does not categorically trigger a CMMC assessment or select its level. Check 32 CFR 170.3, the solicitation or contract, applicable phase-in and exceptions, and the required status.
  • DFARS 252.204-7012 alone does not establish that a contractor possesses CUI. Examine contract information, markings and flows; consult the contracting officer when uncertain. See 48 CFR 252.204-7012.

Two flavors:

  • CUI Basic — review the applicable CUI safeguarding rules and contractual requirements, including when 800-171 applies.
  • CUI Specified — the underlying authority specifies particular safeguarding or dissemination requirements; consult the relevant CUI Registry category.

Confidentiality impact value: No less than FIPS 199 moderate.

Boundary scoping: Assess the relevant system and asset categories under 32 CFR 170.19; do not assume that only assets directly handling CUI are relevant.

Marking expectations:

  • Banner markings on the document.
  • Category identification (e.g., CUI//SP-PRVCY).
  • Dissemination controls if applicable.

7. CMMC Scoping Guide — Asset Categories

Per 32 CFR 170.19 and the CMMC L2 Scoping Guide, each asset falls into one of five categories. Proper categorization can dramatically reduce assessment burden and cost.

CategoryWhat it isCMMC treatment
CUI AssetsProcess, store, or transmit CUIAll 110 controls apply
Security Protection AssetsProvide security services to CUI Assets (firewalls, IDS/IPS, SIEM, VPN, MDM, patch mgmt, AD/LDAP) — may not touch CUI directlyApplicable security requirements apply
Contractor Risk Managed Assets (CRMA)Can, but are not intended to, process, store, or transmit CUI because of policies, procedures and practicesSSP review; limited checks may be warranted under Table 3
Specialized AssetsCan process, store, or transmit CUI but cannot be fully secured, including certain OT, IoT and GFEDocument and manage using risk-based policies; SSP review, not other CMMC security requirements at Level 2
Out-of-Scope AssetsCannot process, store, or transmit CUI, do not protect CUI assets, and are physically or logically separatedPrepare to justify inability to process, store or transmit CUI; in-scope categories cannot be out of scope

Scope-Reduction Plays

  1. CMMC enclave — isolate CUI into a dedicated environment; assess all applicable asset categories, including security protection assets outside the enclave.
  2. Remove CUI from systems that don't need it; reassess their asset category rather than assuming they exit scope.
  3. FedRAMP-authorized CSP — document shared responsibilities; authorization does not eliminate customer-side obligations.
  4. Genuinely isolated systems — air-gapped test networks with no path to CUI.

CUI Identification — Required Before Scoping

  1. Map every contract containing DFARS 252.204-7012 or 7021.
  2. Identify what data Government provides or contractor generates that qualifies as CUI.
  3. Trace CUI flow — email, file shares, cloud, mobile, backups, vendors.
  4. Document in SSP, including data flow diagrams (C3PAOs expect these).

8. ESP / CSP Rules

The most commonly misunderstood area of CMMC. ESPs and CSPs follow different rules.

Cloud Service Provider (CSP)

A CSP is a cloud service provider; a CSP may also be an ESP, including when it processes, stores, or transmits Security Protection Data (SPD) without CUI.

  • For an external cloud service provider handling covered defense information under DFARS 7012, the clause requires security requirements equivalent to the FedRAMP Moderate baseline and specified incident-related obligations; review the contract and applicable clause. See 48 CFR 252.204-7012(b)(2)(ii)(D).
  • For Level 2 certification, the cloud offering processing CUI must be FedRAMP Moderate (or higher) authorized or meet equivalent security requirements in accordance with DoD policy; the on-premises infrastructure connecting to it is in scope. CRM security requirements must be documented or referenced in the SSP. See 32 CFR 170.17(c)(5).
  • Do not assume every CSP is outside assessment scope: see the SPD-only row below. FedRAMP authorization alone does not resolve customer responsibilities.

Common CSP options for CUI:

Verify the exact offering and authorization boundary in the FedRAMP Marketplace and applicable DoD policy; platform names alone do not establish authorization, equivalence, or suitability for specific data.

ITAR/EAR caution: A CSP can be FedRAMP-authorized and technically eligible — but still ineligible to process specific CUI categories due to export-control restrictions on foreign-national access. Evaluate CUI category restrictions independently of FedRAMP authorization.

External Service Provider (ESP)

An ESP can be a CSP or a non-CSP. Classify the service using what it processes, stores, or transmits, not merely whether it is cloud-based.

Common ESPs: MSSPs (SOC, SIEM), MSPs (patching, endpoint management), outsourced IT/AD admins, physical security monitoring vendors.

Level 2 scoping: 32 CFR 170.19(c)(2)(i), Table 4 distinguishes:

Data handledCSPNon-CSP ESP
CUI, with or without SPDMeet FedRAMP requirements in 48 CFR 252.204-7012Services are in the OSA assessment scope and assessed as part of that assessment
SPD without CUIServices are in scope and assessed as Security Protection AssetsServices are in scope and assessed as Security Protection Assets
Neither CUI nor SPDDoes not meet the CMMC definition of an ESPDoes not meet the CMMC definition of an ESP

Under 170.19(c)(2)(ii), document the ESP, relationship and services in the SSP, and describe them in the service description and CRM. Voluntary ESP certification may reduce the ESP's effort during the OSA assessment; it does not automatically exempt services from assessment. For non-CSP ESPs handling CUI, 170.17(c)(6) addresses Level 2 certification, including assessment of services used to meet OSA requirements against all Level 2 requirements. Level 3 has a separate Table 6; Level 1 scoping differs.


9. Subcontractor Flow-Down (32 CFR 170.23)

Per the regulation (unless DoD specifies otherwise), the prime contractor determines the CMMC level required for each subcontractor based on the data the sub will handle.

Prime's requirementSub handling FCI onlySub handling CUI
L2 (Self)L1 minimumL2 (Self) minimum
L2 (C3PAO)L1 minimumL2 (C3PAO) minimum
L3 (DIBCAC)L1 minimumL2 (C3PAO) minimum (unless DoD specifies higher)

Prime obligations:

  • Verify subcontractor CMMC compliance at time of award, not just at solicitation response.
  • Verify via SPRS (sub's CMMC Status should be visible — access mechanics still maturing).
  • Include DFARS 252.204-7021 flow-down clause in subcontracts.

Practical advisory: Build supplier cybersecurity verification into procurement processes; check current phase-in and applicable contract requirements.


10. SPRS Scoring Mechanics

Score vs. Status — Two Different Things

ConceptWhat it isWhere it lives
SPRS ScoreNumerical (e.g., 98/110) from DoD Assessment Methodology self-assessmentSPRS (contractor-submitted)
CMMC StatusCategorical (Conditional L2 / Final L2 / etc.) from a CMMC assessment under 32 CFR 170SPRS (self) or eMASS (C3PAO)

A DFARS assessment score alone does not establish CMMC Level 2 (Self) status; consult 32 CFR 170.16 for assessment, status, and affirmation requirements.

DoD Assessment Methodology — Three Tiers

Under DFARS 252.204-7019/7020:

TierConducted byRigorSPRS effect
BasicContractor selfLow (honor system)Contractor submits score
MediumDoD records/interview reviewMediumDoD adjusts score if gaps found
HighDIBCAC on-siteHighDIBCAC score supersedes contractor's

Scoring Formula

SPRS = 110 − Σ (deductions for not-implemented or partially-implemented controls)
  • Starting score: 110.
  • Point weights per practice: 5 (High criticality), 3 (Medium), 1 (Low) — set by the CMMC Scoring Methodology.
  • Deduction: Apply the specified scoring methodology, not discretionary partial credit. 32 CFR 170.24 specifies adjusted deductions for IA.L2-3.5.3 and SC.L2-3.13.11 in particular circumstances; the requirements remain NOT MET when not fully implemented.
  • Conditional Level 2: assessment score divided by the total number of Level 2 requirements must be ≥ 0.8, alongside all other POA&M conditions. This is a weighted score, not a count of MET practices. See 32 CFR 170.21(a)(2).
  • Final status: 110/110 with all practices Met (no open POA&Ms).
  • Score can go negative (theoretical floor around −203).

Practice Weights

Consult the enumerated weights and exceptions in 32 CFR 170.24; do not infer a weight from a practice name.


11. POA&M Rules — Critical Section

A Plan of Action & Milestones is a time-bound documented plan to remediate identified deficiencies. Under CMMC, POA&Ms are not a general remediation tool — they are tightly restricted.

The Three Golden Rules

Rule 1 — Level 1 = NO POA&Ms ever. Per 32 CFR 170.21(a)(1). All 15 FAR 52.204-21 practices must be fully implemented at time of self-assessment submission. No exceptions.

Rule 2 — Level 2 POA&Ms require a passing score of ≥ 80%. Per 32 CFR 170.21(a)(2)(i). Assessment score ÷ total number of Level 2 requirements must be ≥ 0.8, and the other conditions in 32 CFR 170.21(a)(2) must also be met. This is not a count of MET practices.

Rule 3 — Only 1-point practices on POA&M, with one exception. Per 32 CFR 170.21(a)(2)(ii). No practice on a POA&M may have a point value greater than 1. The single exception: SC.L2-3.13.11 (FIPS-validated cryptography) may be on a POA&M at its 3-point value only if encryption is in use but not yet FIPS-validated. If encryption is not employed at all, 3.13.11 carries its full 5-point weight and is not POA&M-eligible.

FIPS encryption and conditional status

Under 32 CFR 170.24, the deduction is 3 points if encryption is employed but not FIPS-validated, and 5 if encryption is not employed. The former may be included on a Level 2 POA&M only when all applicable conditions in 32 CFR 170.21 are satisfied. Encryption alone does not establish eligibility or that the requirement is MET.

Controls That CANNOT Be on a POA&M

Per 32 CFR 170.21(a)(2)(iii), the following are explicitly ineligible regardless of point value:

  • AC.L2-3.1.20 and AC.L2-3.1.22 (CUI data)
  • CA.L2-3.12.4 (system security plan)
  • PE.L2-3.10.3, PE.L2-3.10.4 and PE.L2-3.10.5 (CUI data)

The point-value restriction and encryption exception in Rule 3 also apply. Verify all conditions against the current regulation.

Valid POA&M Entry — Required Fields

  1. Description of the deficiency (specific practice + why not met).
  2. Responsible party (named individual, not "IT department").
  3. Resource requirements (budget, personnel, tooling).
  4. Specific milestone dates (not "TBD" or "within 6 months").
  5. Estimated completion date within the 180-day conditional window.
  6. Current status, updated as remediation progresses.

Closeout Process

  1. Remediate within 180 days.
  2. Conduct closeout assessment (self or C3PAO — matching original assessment type).
  3. Post results in the applicable system and verify that all conditions for Final status have been met.
  4. Confirm the resulting status; do not assume an automatic upgrade.

If POA&M Not Closed in 180 Days

  • Conditional CMMC Status expires.
  • Review award eligibility, contractual obligations and the path to a current status with the contracting officer and qualified counsel; do not assume consequences or a particular reassessment path.

Operational POA&M vs. CMMC POA&M

Operational POA&Ms (continuous improvement tracking under normal NIST practice) are separate from CMMC assessment POA&Ms (formal regulatory constructs with 180-day clocks). Don't conflate them.


12. Findings Language

At the assessment objective level, each AO produces one of:

  • Satisfied — the objective is met based on evidence collected.
  • Other Than Satisfied (OTS) — the objective is not met.

At the practice level, the rollup is:

  • MET — all AOs within the practice are Satisfied.
  • NOT MET — one or more AOs are Other Than Satisfied. Applicable adjusted deductions under 32 CFR 170.24 do not create a PARTIAL practice status.
  • NOT APPLICABLE — control does not apply to the assessed scope (must be justified and documented in the SSP).

Findings language convention in deliverables:

  • State the AO citation (e.g., 3.1.1[a]).
  • State the method that produced the finding (Examine / Interview / Test).
  • State the artifact or response that demonstrates the gap.
  • Map to the SPRS point impact (1 / 3 / 5).
  • Identify POA&M eligibility status.

13. C3PAO Assessment Lifecycle

Pre-Assessment

  1. OSC selects C3PAO from the Cyber AB marketplace.
  2. Scope determination under 32 CFR 170.19 — asset categorization, CUI boundary.
  3. Documentation review — C3PAO reviews SSP, policies, procedures before going on-site.
  4. Readiness/gap assessment (optional but strongly recommended). A C3PAO cannot both consult and certify the same OSC — readiness reviews must come from a different C3PAO or independent consultant.
  5. Artifact preparation — evidence packages mapped to 800-171A objectives.

Assessment

  1. Initiation — CMMC UID assigned (10-character identifier).
  2. Team composition — at least two people: a Lead CCA and at least one other CCA; additional CCAs and CCPs may participate. A separate CCA performs quality assurance and cannot be a member of the team for that assessment. See 32 CFR 170.9(b)(12)–(13).
  3. Assessment activities — Examine / Interview / Test against every applicable AO.
  4. Scoring — each practice MET or NOT MET per its AOs.
  5. POA&M determination — which gaps qualify for POA&M.

Post-Assessment

  1. C3PAO posts results to CMMC-eMASS; CMMC Status (Conditional or Final) appears in SPRS.
  2. Certificate of CMMC Status issued.
  3. Evidence retention: the OSC hashes artifact files used as assessment evidence with a NIST-approved hashing algorithm and retains the hashed artifacts for 6 years from the CMMC Status Date. The OSC provides the C3PAO the artifact names, hash values, and algorithm used for upload to CMMC-eMASS. See 32 CFR 170.17(c)(4).
  4. C3PAO uploads the artifact names, hash values, and algorithm used to CMMC-eMASS as part of the assessment results. See 32 CFR 170.17(a)(1)(i)(J).

C3PAO Rules (32 CFR 170.9 / 170.11)

  • Accredited by the Cyber AB.
  • Assessment personnel must meet Tier 3 investigation or applicable equivalence requirements under 170.9(b)(3)–(4).
  • Level 2 certification assessment activities must be performed on the information system within the assessment scope under 170.9(b)(15).
  • Prohibited from providing consulting/implementation services to OSCs they certify.
  • Assessment information is strictly confidential.

L2 (Self) — Non-C3PAO Process

  1. Self-assess against 800-171A objectives.
  2. Apply 32 CFR 170.19 scoping.
  3. Score per 32 CFR 170.24.
  4. Upload to SPRS.
  5. Senior official affirms per 32 CFR 170.22.
  6. CMMC Status posted in SPRS.

14. Annual Affirmation & False Claims Act Risk

Annual Affirmation (32 CFR 170.22)

Under 32 CFR 170.22(a)–(b), each OSA's authorized senior-level Affirming Official submits the affirmation in SPRS, attesting that all applicable requirements for the status are implemented and will remain implemented for all systems within the relevant assessment scope. The regulation does not prescribe a blanket attestation that no material changes have occurred.

Submit upon Conditional status, upon Final status, after POA&M closeout where applicable, and annually following a Final status date; Level 1 is at completion and annually thereafter. Level 3 requires annual affirmations of both Level 2 (C3PAO) and Level 3 (DIBCAC) status. See 170.22(a)(3), (b)(1)–(4).

False Claims Act Exposure

CMMC creates real FCA exposure — context every client conversation should include:

  • FCA liability: Up to 3× government damages + per-claim penalties for knowingly false certifications.
  • DOJ Civil Cyber-Fraud Initiative addresses certain cybersecurity-related false claims; consult current DOJ guidance and counsel.
  • Recent precedent: Multiple multi-million-dollar settlements against defense contractors that falsely certified cybersecurity compliance.
  • Personal liability: The signing senior official is personally certifying.

What creates exposure:

  1. Submitting an inflated SPRS score.
  2. Knowingly false annual affirmation.
  3. Certifying a bid as CMMC-compliant when the OSC knows it isn't.
  4. Prime contractor knowingly ignoring sub's false claims.

No safe-harbor assurance: accurate reporting and remediation do not by themselves establish contract eligibility, satisfy all obligations, or insulate an organization or individual from liability. CMMC conditional status has specific eligibility and closeout rules in 32 CFR 170.21. Consult qualified legal counsel about the facts and applicable obligations.


15. Revision transition

For applicable CMMC requirements, consult 32 CFR 170.14 and the contract to identify the incorporated edition. Do not substitute NIST SP 800-171 Rev 3 for an applicable Rev 2 requirement. For transition planning, use NIST's Rev 2 to Rev 3 comparison resources and verify individual mappings; a crosswalk does not establish compliance. Rev 2 requirement 3.3.7 does not prescribe NTP; consult NIST SP 800-171 Rev 2.

16. Candidate Level 2 review topics

These are prompts for evidence review, not automatic failures. Determine applicability, examine the relevant source and actual implementation, and obtain qualified assessor review before making a finding.

  • MFA: Review coverage of local and network access to privileged accounts and network access to non-privileged accounts under 3.5.3. SMS or push alone is not automatically a failure of that requirement; check the applicable contract and any additional requirements separately.
  • Access authorization: Review authorized users, processes and devices, access restrictions, and least privilege under 3.1.1 and 3.1.5. Missing periodic account-review records alone do not automatically establish failure of those requirements; investigate other relevant evidence and requirements.
  • Other topics: Review configuration baselines, incident response, security logging, cryptographic protection, vulnerability scanning, and system security plans against the applicable requirement and evidence. Missing or incomplete evidence warrants investigation, not an invented outcome.

17. Authoritative Sources

Primary

  • NIST SP 800-171 Rev 2 — https://doi.org/10.6028/NIST.SP.800-171r2
  • NIST SP 800-171A (June 2018) — assessment procedures
  • NIST SP 800-172 — Enhanced Security Requirements (L3 source)
  • 32 CFR Part 170 — CMMC program rule (89 FR 83214, Oct. 15, 2024; effective Dec. 16, 2024)
  • 48 CFR Part 204.75 (DFARS) — CMMC acquisition rule (effective Nov. 10, 2025)
  • DFARS 252.204-7012 / -7019 / -7020 / -7021 / -7025
  • FAR 52.204-21 — Basic Safeguarding (CMMC L1 source)
  • 32 CFR Part 2002 — CUI program rule
  • CUI Registry — cui.archives.gov

CMMC Program Documents

  • CMMC Model v2.0
  • CMMC Assessment Guide — Level 1
  • CMMC Assessment Guide — Level 2
  • CMMC Assessment Guide — Level 3
  • CMMC Scoping Guide — Level 1
  • CMMC Scoping Guide — Level 2
  • CMMC Scoring Methodology
  • DoD Assessment Methodology (basis for SPRS scoring)

Authoritative locations: dodcio.defense.gov/CMMC/, cyber.mil, cyberab.org, sprs.csd.disa.mil, dibnet.dod.mil (incident reporting).


Capabilities

This skill supports:

  • CMMC level selection and CUI boundary scoping
  • Per-control (and per-AO) implementation guidance for all 110 800-171 Rev 2 practices
  • SSP development, review, and gap mapping
  • Assessment objective-level evidence planning
  • C3PAO assessment readiness preparation
  • POA&M development with eligibility validation against 32 CFR 170.21
  • SPRS score calculation against the CMMC Scoring Methodology
  • ESP/CSP scoping decisions and FedRAMP equivalency analysis
  • Subcontractor flow-down planning
  • Annual affirmation workflow and FCA-risk advisory
  • Rev 2 → Rev 3 crosswalk and ODP planning
  • DFARS clause interpretation across 7012, 7019, 7020, 7021, 7025

Commands 5

CMMC Assessment

Use /cmmc:assess <level> [scope] for a preliminary readiness review, not an official assessment or certification. Ask for the applicable contract, assessment type, boundary, review period, and authoritative source edition. Record unknowns rather than guessing. Verify current requirements and program status before advising.

The existing cmmc-expert and cmmc-assessment-objectives skills provide background and source-based objective navigation. For a Level 2 practice, use /cmmc:evidence-checklist <practice-id> to create an evidence review worksheet. Level 1 and Level 3 require separate source- and contract-specific review; do not extrapolate the Level 2 workflow to them.

For each in-scope requirement, provide its source and version, evidence references, observed gaps, limitations, reviewer, and next actions. Mark items without sufficient evidence not assessed. Do not claim certification, invent a readiness percentage, or assume a third-party assessment is required for every Level 2 contract. Any final assessment outcome requires authorized human review.

Sources

Example

/cmmc:assess 2 "Access Control"

When no scope or evidence is provided, output questions and unassessed items, not findings or a passing score.

CMMC Domain Guidance

Review required: This material is an unverified working aid, not an authoritative assessment or legal determination. Verify every control, objective, scope, assessment type, scoring and contractual claim against current official sources and obtain qualified CMMC and contracting review before use. If a source or contract is unavailable, mark the conclusion unverified; do not infer compliance.

Provides detailed implementation guidance for CMMC v2.0 domains and their associated practices.

Arguments

  • $1 - Domain abbreviation (required: AC, AT, AU, CM, IA, IR, MA, MP, PS, PE, RA, CA, SC, SI)
  • $2 - CMMC level (optional: 1, 2, 3 - shows practices for that level)

See the DoD CMMC Model Overview v2.13 for Levels 1–3 and 32 CFR 170.14 for regulatory requirements. Level 1 identifiers map to NIST assessment objectives as specified in 32 CFR 170.15(c)(1)(ii).

14 CMMC Domains

Access Control (AC)

Controls who can access systems and data based on approved authorizations.

Key practices:

  • AC.L1-b.1.i: Limit access to authorized users
  • AC.L1-b.1.ii: Limit access to transaction types
  • AC.L1-b.1.iii: External connections control (maps to 3.1.20 objectives); AC.L2-3.1.20 applies at Level 2
  • AC.L1-b.1.iv: Control public information (maps to 3.1.22 objectives); AC.L2-3.1.22 applies at Level 2

Audit and Accountability (AU)

Maintains audit logs to detect and respond to cyber incidents.

Key practices:

  • AU.L2-3.3.1: Create/protect audit records
  • AU.L2-3.3.2: Ensure actions traced to users
  • AU.L2-3.3.8: Protect audit information

Awareness and Training (AT)

Ensures personnel are trained in cybersecurity.

Key practices:

  • AT.L2-3.2.1: Security awareness training
  • AT.L2-3.2.2: Personnel training for security roles
  • AT.L2-3.2.3: Recognize and report insider threat indicators

Configuration Management (CM)

Establishes and maintains baseline configurations.

Key practices:

  • CM.L2-3.4.1: Baseline configurations
  • CM.L2-3.4.2: Security configuration settings
  • CM.L2-3.4.7: Least functionality principle

Identification and Authentication (IA)

Verifies identities of users and devices.

Key practices:

  • IA.L1-b.1.v: Identify users/devices
  • IA.L1-b.1.vi: Authenticate users/devices
  • IA.L2-3.5.3: Multi-factor authentication (MFA)
  • IA.L2-3.5.7: Password complexity and change of characters
  • IA.L2-3.5.10: Store/transmit passwords encrypted

Incident Response (IR)

Detects and responds to cybersecurity incidents.

Key practices:

  • IR.L2-3.6.1: Incident handling capability
  • IR.L2-3.6.2: Track/document/report incidents
  • IR.L2-3.6.3: Test incident response capability

Maintenance (MA)

Manages system maintenance and repair.

Key practices:

  • MA.L2-3.7.1: Perform scheduled maintenance
  • MA.L2-3.7.2: Control tools, techniques, mechanisms and personnel used to conduct maintenance
  • MA.L2-3.7.5: Multifactor authentication for nonlocal maintenance

Media Protection (MP)

Protects digital and non-digital media.

Key practices:

  • MP.L1-b.1.vii: Sanitize/destroy media
  • MP.L2-3.8.1: Protect/control media
  • MP.L2-3.8.2: Limit access to CUI on media

Personnel Security (PS)

Screens and monitors personnel.

Key practices:

  • PS.L2-3.9.1: Screen personnel
  • PS.L2-3.9.2: Protect CUI during personnel actions

Physical Protection (PE)

Limits physical access to systems and facilities.

Key practices:

  • PE.L1-b.1.viii: Limit physical access
  • PE.L1-b.1.ix (first phrase): Escort visitors
  • PE.L1-b.1.ix (second phrase): Maintain physical access logs

Risk Assessment (RA)

Manages organizational risk to operations and assets.

Key practices:

  • RA.L2-3.11.1: Periodic risk assessments
  • RA.L2-3.11.2: Scan for vulnerabilities
  • RA.L2-3.11.3: Remediate vulnerabilities

Security Assessment (CA)

Develops and implements activities to assess security effectiveness.

Key practices:

  • CA.L2-3.12.1: Periodic security assessments
  • CA.L2-3.12.2: Develop and implement plans of action
  • CA.L2-3.12.4: System security plans

System and Communications Protection (SC)

Monitors and controls communications at system boundaries.

Key practices:

  • SC.L1-b.1.x: Boundary protection
  • SC.L2-3.13.8: Transmission confidentiality/integrity
  • SC.L2-3.13.11: Cryptographic protection

System and Information Integrity (SI)

Identifies and manages information system flaws.

Key practices:

  • SI.L1-b.1.xii: Identify/report/correct flaws
  • SI.L1-b.1.xiii: Malicious code protection
  • SI.L1-b.1.xiv: Update malicious code protection (maps to 3.14.4 objectives); SI.L2-3.14.4 applies at Level 2

Output

  1. Domain Overview: Purpose and objectives
  2. Practice List: All practices in domain by level
  3. Implementation Guidance: How to satisfy each practice
  4. Common Gaps: Typical deficiencies found
  5. Evidence Requirements: What C3PAOs look for
  6. NIST Mapping: Correlation to NIST 800-171

Examples

# Get guidance for Access Control domain
/cmmc:domain-guidance AC

# See Level 2 practices for Incident Response
/cmmc:domain-guidance IR 2

# Review Audit and Accountability requirements
/cmmc:domain-guidance AU

CMMC Level 2 Evidence Review Worksheet

Use /cmmc:evidence-checklist <practice-id> to prepare a draft, not an assessment or certification. If the request is for Level 1 or 3, stop and consult the applicable official guide; do not apply this Level 2 worksheet as though it covered those levels.

Sources and boundaries

  • NIST SP 800-171 Rev. 2, requirements, and NIST SP 800-171A, assessment procedures. Check the edition required by the applicable program and contract; do not silently substitute Rev. 3.
  • 32 CFR Part 170 and the current DoD CMMC resources. Confirm current program guidance and contractual requirements with the responsible assessor or counsel.
  • The former checklist asserted universal quarterly reviews, four consecutive quarters, three-year retention and fixed sample sizes. Do not treat those assertions as CMMC requirements. Establish any such requirement from an applicable authoritative source or contract; otherwise label it as a local choice.

Workflow

  1. Ask for the assessment type, applicable contract and requirements edition, assessment boundary, practice ID, and intended review period. Mark unknowns not provided; do not infer scope or assessment outcomes.
  2. Look up the exact practice and its assessment objective and determination statements in the applicable official assessment source. List each source-verified objective or determination statement identifier, if present and cite the source and version. Use the existing cmmc-assessment-objectives skill as a navigation aid, not a substitute for the source.
  3. For each objective, identify candidate examine, interview, and test activities appropriate to the boundary. Identify artifact owners and a secure evidence reference. Suggestions are not mandatory evidence or a universal sampling rule.
  4. Record observed evidence, gaps, limitations, and a human review decision separately. Do not mark an objective met without supporting evidence and authorized assessor review. Do not generate or infer a compliance percentage or certification.
  5. Store evidence and the completed worksheet only in approved, access-controlled storage. Never commit actual evidence, credentials, CUI, personal data, or sensitive links to source control. Determine retention, transmission and access rules with the data owner.

Worksheet template

# Level 2 practice evidence review — DRAFT
Assessment type / contract / source edition: [not provided]
Boundary and review period: [not provided]
Practice and source URL: [not provided]
Assessor / reviewer: [not provided]

| Objective ID and source | Candidate E/I/T activity | Evidence reference / owner | Observation and limitation | Human review status |
|---|---|---|---|---|
| [ID] | [activity] | [secure reference] | [observed facts or not provided] | [not reviewed] |

Open questions / gaps: [not provided]
Next action and owner: [not provided]

Synthetic walkthrough

For /cmmc:evidence-checklist AC.L2-3.1.1, first verify the source edition and objective wording and any identifiers in the official assessment source. If no boundary or evidence is supplied, the worksheet must leave those fields not provided, list no invented observations, and leave human review not reviewed. An access inventory could be a candidate for examination, subject to the assessor's scoping decision; it alone is not proof that the practice is met.

CMMC Level Selection

Review required: This material is an unverified working aid, not an authoritative assessment or legal determination. Verify every control, objective, scope, assessment type, scoring and contractual claim against current official sources and obtain qualified CMMC and contracting review before use. If a source or contract is unavailable, mark the conclusion unverified; do not infer compliance.

Helps determine the appropriate CMMC level required for your organization based on DoD contract types and data sensitivity.

Arguments

  • $1 - Contract type (optional: prime, subcontractor, service-provider)
  • $2 - Data type (optional: FCI, CUI, classified)

Selection Criteria

Data Types

FCI (Federal Contract Information):

  • Contract details, pricing, technical data
  • Verify the solicitation or contract and applicable clause; if Level 1 (Self) is specified, annual self-assessment and affirmation apply. If unavailable, leave the conclusion unverified.

CUI (Controlled Unclassified Information):

  • Technical data, export-controlled info, ITAR
  • Level and assessment type depend on the applicable solicitation, contract and current program requirements; Level 2 may be self-assessed or C3PAO-assessed.

Classified Information:

  • Beyond CMMC scope
  • Requires NISPOM/ICD 503 compliance

Contract Types

Prime Contractor:

  • Direct contract with DoD
  • Verify the applicable solicitation or contract, specified level and assessment type; data sensitivity alone does not determine the result.

Subcontractor:

  • Requirements depend on the subcontract and applicable flow-down, not automatic inheritance of the prime’s level. 32 CFR 170.23 specifies minimum levels by data and prime requirement.

Service Provider:

  • Cloud/IT services to DoD contractors
  • Determine the provider’s role, data handled, applicable contract, and scope under 32 CFR 170.19; do not automatically assign a Level 2 status. For cloud services handling covered defense information, check applicable DFARS 252.204-7012 requirements.

Selection Matrix

Data TypeContract TypeMinimum LevelAssessment Type
FCI onlyAnyVerify applicable contract; Level 1 if specifiedAnnual self-assessment and affirmation when Level 1 applies
CUIPrime/SubVerify applicable contractLevel 2 may be self or C3PAO; verify contract
CUIPrimeVerify applicable contractVerify contract and current requirements

The DFARS 252.204-7021(f) flow-down excludes commercially available off-the-shelf items; verify the actual clause, subcontract and applicable exceptions. Without the contract, the requirement is unverified.

Output

  1. CMMC Level: Contract-verified requirement, or unverified if unavailable
  2. Justification: Why this level is required
  3. Assessment Requirements: Self vs third-party
  4. Timeline Considerations: Assessment frequency
  5. Cost Implications: Estimated assessment costs

Examples

# Determine level for prime contractor with CUI
/cmmc:level-select prime CUI

# Assess requirements for subcontractor
/cmmc:level-select subcontractor CUI

# Evaluate service provider needs
/cmmc:level-select service-provider

CMMC Practice Check

Review required: This material is an unverified working aid, not an authoritative assessment or legal determination. Verify every control, objective, scope, assessment type, scoring and contractual claim against current official sources and obtain qualified CMMC and contracting review before use. If a source or contract is unavailable, mark the conclusion unverified; do not infer compliance.

Validates implementation of specific CMMC v2.0 practices and provides evidence guidance.

Arguments

  • $1 - Practice ID (required, e.g., AC.L2-3.1.1, IA.L2-3.5.7)
  • $2 - Check type (optional: implementation, evidence, gaps)

Practice ID Format

Structure: [DOMAIN].[LEVEL]-[REQUIREMENT]

  • Domain: Two-letter abbreviation (AC, IA, SI, etc.)
  • Level: L1, L2, or L3
  • Requirement: FAR clause paragraph for Level 1; NIST SP 800-171 Rev 2 number for Level 2; selected NIST SP 800-172 number with e suffix for Level 3

Examples:

  • AC.L1-b.1.i - Access Control, Level 1, NIST 3.1.1
  • IA.L2-3.5.7 - Identification & Authentication, Level 2, NIST 3.5.7 (password complexity and change of characters)
  • AU.L2-3.3.1 - Audit & Accountability, Level 2, NIST 3.3.1 (Audit records)

Check Types

Implementation Check

Validates that the practice is properly implemented:

  • Technical controls in place
  • Processes documented
  • Responsibilities assigned
  • Operating effectiveness

Evidence Check

Reviews evidence artifacts for C3PAO assessment:

  • Documentation completeness
  • Evidence currency (recent)
  • Artifact authenticity
  • Coverage of practice requirements

Gap Analysis

Identifies deficiencies in current state:

  • Missing controls
  • Partial implementations
  • Documentation gaps
  • Remediation priorities

See the DoD CMMC Model Overview v2.13 for Levels 1–3 and 32 CFR 170.14 for regulatory requirements. Level 1 identifiers map to NIST assessment objectives as specified in 32 CFR 170.15(c)(1)(ii).

Common Practices

Access Control

  • AC.L1-b.1.i: Limit system access to authorized users, processes, devices
  • AC.L1-b.1.ii: Limit system access to types of transactions/functions
  • AC.L1-b.1.iii: Verify and control external information system connections (maps to 3.1.20 objectives); AC.L2-3.1.20 applies at Level 2

Identification & Authentication

  • IA.L1-b.1.v: Identify information system users
  • IA.L1-b.1.vi: Authenticate (or verify) identities
  • IA.L2-3.5.3: MFA for local and network access to privileged accounts and network access to non-privileged accounts
  • IA.L2-3.5.7: Password complexity and change of characters
  • IA.L2-3.5.8: Prohibit password reuse for a specified number of generations
  • IA.L2-3.5.10: Store and transmit only cryptographically-protected passwords

Incident Response

  • IR.L2-3.6.1: Establish incident handling capability
  • IR.L2-3.6.2: Track, document, and report incidents

System Integrity

  • SI.L1-b.1.xii: Identify, report, and correct information system flaws
  • SI.L1-b.1.xiii: Provide protection from malicious code
  • SI.L1-b.1.xiv: Update malicious code protection mechanisms (maps to 3.14.4 objectives); SI.L2-3.14.4 applies at Level 2

Output

  1. Practice Definition: What the practice requires
  2. Implementation Guidance: How to satisfy the practice
  3. Evidence Examples: What artifacts to provide
    • Policies and procedures
    • Screenshots/configurations
    • Logs and reports
    • Test results
  4. Common Deficiencies: What C3PAOs flag
  5. Pass/Fail Criteria: Assessment thresholds
  6. Remediation Steps: If gaps identified

Examples

# Check MFA implementation for Level 2
/cmmc:practice-check IA.L2-3.5.3 implementation

# Review evidence for access control
/cmmc:practice-check AC.L1-b.1.i evidence

# Gap analysis for incident response
/cmmc:practice-check IR.L2-3.6.1 gaps

# Verify audit logging implementation
/cmmc:practice-check AU.L2-3.3.1

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/frameworks/cmmc
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70