FedRAMP
Choose a FedRAMP certification path for a cloud service used by U.S. federal agencies.
Cybersecurity Maturity Model Certification
Translate a defense solicitation’s cybersecurity requirements into an assessment plan.
U.S. DoD contractors and relevant subcontractors handling Federal Contract Information or Controlled Unclassified Information under covered solicitations.
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.
Report unverified practices, ineligible or expiring corrective actions, subcontractors without required status and the next affirmation date.
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.
Checklist, instructions and 11 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Read the solicitation and map data | Contracts lead + security | Before bid and award | Set a start date | Clause matrix; CUI flow map; Scope boundary | Open |
| Implement and document required practice | Security engineering + control owners | Before assessment | Set a start date | SSP; Evidence set; Remediation tracker | Open |
| Complete the required assessment | Assessment lead + C3PAO or DIBCAC if required | At required assessment and award milestones | Set a start date | Assessment result; Required status; Remediation dates | Open |
| Affirm and maintain status | Affirming official + contracts | Annually and when contract requires | Set a start date | Affirmation record; Subcontractor status log | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Identify required level/status and FCI or CUI flow, including subcontractors. Confirm assessment boundary and applicable contract clauses.
Solicitation, clauses and attachments, work statement, data requirements, vendor arrangements and network architecture.
The contract matrix identifies the required status and links it to the CUI or FCI flows and assessed environment.
Raise unclear marking, data outside the proposed boundary or a subcontractor unable to meet a required clause.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Map the required baseline, write the system security plan and gather objective evidence. Track only eligible items in any remediation plan.
Scope, applicable assessment objectives, system security plan when required, configurations and provider documentation.
An assessor can map a practice to the scope, configuration and an observed operation or retained evidence without receiving unnecessary CUI.
Escalate a gap that prohibits conditional status or a security function the provider cannot substantiate.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Use the self-assessment or external route specified for the contract. Verify status, identifiers and any conditional remediation deadline.
Approved scope, finalized evidence, required assessment route and documented remediation eligibility.
The result shows the assessed environment, date, status and any closeout evidence. Contract staff can match it to the solicitation requirement.
Raise a failed objective or status mismatch that could affect award or performance before representing compliance.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Submit applicable affirmations, assess scope changes and flow obligations to relevant subcontractors.
Assessment result and scope, affirmation instructions, change log and subcontractor obligations.
Contracts can retrieve the current status, scope and affirmation record and show which subcontractors and flows it verified.
Escalate expired status, boundary changes or a planned subcontract award without required evidence.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.