Start hereRead the solicitation and map data
~143 days leftOpen step
Guide library
Certification North America

CMMC

Cybersecurity Maturity Model Certification

Translate a defense solicitation’s cybersecurity requirements into an assessment plan.

Who it applies to

U.S. DoD contractors and relevant subcontractors handling Federal Contract Information or Controlled Unclassified Information under covered solicitations.

What you’ll produce

Required CMMC status and continuing affirmation for the applicable assessment scope.

Check the actual solicitation and contract clauses. The assessment route and allowed remediation differ by required status.

Check official publications for this guide
TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What does this contract actually require?
Have Contracts confirm the solicitation language, required level and assessment type, relevant dates, and subcontractor flowdown. Check current DoD rollout announcements because phases and clauses may change.
Can we contain the sensitive work?
Price the proposed controlled environment, remote access and provider dependencies before committing. Decide which teams and subcontractors will handle FCI or CUI and on which systems.
Who can make the affirmation?
Name the authorized affirming official and security owner. Reserve money and time for an independent assessment where required, remediation, closeout and maintaining status.

How to spend the first week

  1. Read the actual contract documents with Contracts and project delivery. Trace one representative FCI or CUI handoff through recipients, collaboration tools and storage.
  2. Draft the boundary and identify external providers, subcontractors and any systems that protect the environment. Confirm scope with the security lead.
  3. Agree the work and resourcing required for the assessment type, plus the evidence package the affirming official will review.

What to review each week

Report unverified practices, ineligible or expiring corrective actions, subcontractors without required status and the next affirmation date.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

CMMC kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Read the solicitation and map data · Contracts lead + security [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Read the actual contract documents with Contracts and project delivery. Trace one representative FCI or CUI handoff through recipients, collaboration tools and storage.
2. Draft the boundary and identify external providers, subcontractors and any systems that protect the environment. Confirm scope with the security lead.
3. Agree the work and resourcing required for the assessment type, plus the evidence package the affirming official will review.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
The whole journeyabout 143 days across 4 steps
  1. 01Read the solicitation and map dataContracts lead + security · ~14 days
  2. 02Implement and document required practiceSecurity engineering + control owners · ~70 days
  3. 03Complete the required assessmentAssessment lead + C3PAO or DIBCAC if required · ~45 days
  4. 04Affirm and maintain statusAffirming official + contracts · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 11 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Read the solicitation and map dataContracts lead + securityBefore bid and awardSet a start dateClause matrix; CUI flow map; Scope boundaryOpen
Implement and document required practiceSecurity engineering + control ownersBefore assessmentSet a start dateSSP; Evidence set; Remediation trackerOpen
Complete the required assessmentAssessment lead + C3PAO or DIBCAC if requiredAt required assessment and award milestonesSet a start dateAssessment result; Required status; Remediation datesOpen
Affirm and maintain statusAffirming official + contractsAnnually and when contract requiresSet a start dateAffirmation record; Subcontractor status logOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Read the solicitation and map data

    Who Contracts lead + security When Before bid and award

    Identify required level/status and FCI or CUI flow, including subcontractors. Confirm assessment boundary and applicable contract clauses.

    How to do this step

    Before you start

    Solicitation, clauses and attachments, work statement, data requirements, vendor arrangements and network architecture.

    1. Record the clause, assessment type, level, dates and flowdown in a clause matrix. Ask Contracts to resolve ambiguities with the appropriate contracting contact.
    2. Follow actual FCI or CUI from receipt to destruction through email, endpoints, backups, cloud platforms and subcontractors. Document assets that provide security protection.
    3. Draw the assessment boundary using the applicable scoping categories and include where regulated data crosses to outside providers.

    What a reviewer should see

    The contract matrix identifies the required status and links it to the CUI or FCI flows and assessed environment.

    When to escalate

    Raise unclear marking, data outside the proposed boundary or a subcontractor unable to meet a required clause.

    What to produce

    Clause matrixSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

    CUI flow mapDiagram worksheet

    Gather first

    • System and vendor inventory
    • Examples of live transactions or data events
    • Approved boundaries and information categories

    How to prepare it

    1. Sketch an entry point, storage location, processing system and recipient for each flow. Label arrows with what moves and in which direction.
    2. Show trust boundaries, geographic locations, contracts or interconnections that matter. Include administrative access, backups and deletion paths where relevant.
    3. Walk through a real end-to-end transaction with engineering and operations. Save an accessible diagram and keep the reviewed flow register beside it.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Source
    Web checkout
    Destination
    Billing API in EU region
    Data and purpose
    Order reference and billing email to send the receipt
    Protocol and boundary
    HTTPS, crosses from public network into hosted production
    Owner and validation
    Billing owner, validated against request logs on 2026-11-12

    Check before handing it over

    An engineer can trace collection to deletion, and a reviewer can see every crossing or third-party handoff.

    Use the worksheet to design the diagram. Share the diagram with the people confirming scope, transfers or controls.

    Scope boundaryMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

  2. 02

    Implement and document required practice

    Who Security engineering + control owners When Before assessment

    Map the required baseline, write the system security plan and gather objective evidence. Track only eligible items in any remediation plan.

    How to do this step

    Before you start

    Scope, applicable assessment objectives, system security plan when required, configurations and provider documentation.

    1. Map each applicable objective to the actual configuration, procedure, accountable person and evidence source.
    2. Run a walkthrough using a real sanitized example, such as provisioning a user, and collect the interview, record or test evidence needed to support the objective.
    3. Record gaps with interim steps, due dates and owners. Review eligibility under the applicable Plan of Action and Milestones rules before relying on a conditional result.

    What a reviewer should see

    An assessor can map a practice to the scope, configuration and an observed operation or retained evidence without receiving unnecessary CUI.

    When to escalate

    Escalate a gap that prohibits conditional status or a security function the provider cannot substantiate.

    What to produce

    SSPMemo

    Gather first

    • Approved system boundary
    • Architecture, data flows, controls and service commitments
    • Current reporting instructions or system plan template

    How to prepare it

    1. Explain who uses the system, the commitments it supports and how people, processes, software, infrastructure and data fit together.
    2. Walk through actual transactions or requests and identify the relevant controls and shared responsibilities. Cover dependencies and any criteria or requirements in the agreed template.
    3. Validate each section with the technical owner against live architecture, procedures and evidence. Lock the approved version and reconcile it to diagrams and control records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Service and objective
    Hosted invoice service receives orders, calculates amounts and sends PDF receipts.
    Boundary and inputs
    Accepted production order events, account identifiers and billing records
    How it works
    Payment result updates invoice status. Release pipeline deploys code with approval.
    Shared roles
    Customer controls user configuration. Hosting vendor manages physical infrastructure.
    Evidence and review
    Architecture v3, deployment records and service-owner review

    Check before handing it over

    The written description, diagrams and control records agree. A reviewer can understand end-to-end operation.

    Send the approved draft to management and the independent evaluator. Transfer it to the prescribed system plan or report template when needed.

    Evidence setSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

    Remediation trackerSpreadsheet

    Gather first

    • Finding, risk or test exception
    • Root-cause analysis
    • Named owner, due date and expected evidence

    How to prepare it

    1. Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
    2. Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
    3. Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Finding or risk
    F-008, a departed contractor retained production access
    Cause and effect
    HR event never reached IAM. Admin access remained active.
    Action and owner
    Revoke access and alert on failed HR sync. IAM lead.
    Due and status
    2026-11-28, in progress
    Closure test
    Simulate departure and verify access disappears within policy
    Approver and evidence
    Risk owner, ticket IAM-114 and retest results

    Check before handing it over

    The closure test addresses the original problem and has a dated result from an independent reviewer where required.

    Send open items and decisions to governance, audit or the assessor on the applicable cadence.

  3. 03

    Complete the required assessment

    Who Assessment lead + C3PAO or DIBCAC if required When At required assessment and award milestones

    Use the self-assessment or external route specified for the contract. Verify status, identifiers and any conditional remediation deadline.

    How to do this step

    Before you start

    Approved scope, finalized evidence, required assessment route and documented remediation eligibility.

    1. Coordinate a self-assessment or the required independent or government assessment using the contract’s route and applicable program rules.
    2. Reconcile results to the assessed scope and record the exact status, dates and remaining items. For allowed conditional results, schedule completion and required closeout before expiry.
    3. Check the official record and share approved status details with Contracts. Link assessment findings to assigned work tickets.

    What a reviewer should see

    The result shows the assessed environment, date, status and any closeout evidence. Contract staff can match it to the solicitation requirement.

    When to escalate

    Raise a failed objective or status mismatch that could affect award or performance before representing compliance.

    What to produce

    Assessment resultIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

    Required statusIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

    Remediation datesSpreadsheet

    Gather first

    • Finding, risk or test exception
    • Root-cause analysis
    • Named owner, due date and expected evidence

    How to prepare it

    1. Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
    2. Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
    3. Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Finding or risk
    F-008, a departed contractor retained production access
    Cause and effect
    HR event never reached IAM. Admin access remained active.
    Action and owner
    Revoke access and alert on failed HR sync. IAM lead.
    Due and status
    2026-11-28, in progress
    Closure test
    Simulate departure and verify access disappears within policy
    Approver and evidence
    Risk owner, ticket IAM-114 and retest results

    Check before handing it over

    The closure test addresses the original problem and has a dated result from an independent reviewer where required.

    Send open items and decisions to governance, audit or the assessor on the applicable cadence.

  4. 04

    Affirm and maintain status

    Who Affirming official + contracts When Annually and when contract requires

    Submit applicable affirmations, assess scope changes and flow obligations to relevant subcontractors.

    How to do this step

    Before you start

    Assessment result and scope, affirmation instructions, change log and subcontractor obligations.

    1. Have the authorized official review the status, applicability and supporting evidence before completing the required affirmation through the designated system.
    2. Track annual affirmation dates and applicable reassessments. Evaluate material changes to the environment or information flows before relying on existing coverage.
    3. Verify applicable subcontractor assessment status and flowdowns for new awards and changed work. Preserve the verification date and scope.

    What a reviewer should see

    Contracts can retrieve the current status, scope and affirmation record and show which subcontractors and flows it verified.

    When to escalate

    Escalate expired status, boundary changes or a planned subcontract award without required evidence.

    What to produce

    Affirmation recordIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

    Subcontractor status logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    Every open item has a next action and closed items have a verifiable record of closure or delivery.

    Use the log at case reviews and provide a restricted copy only where the engagement requires it.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes