CMMC
Translate a defense solicitation’s cybersecurity requirements into an assessment plan.
NIST SP 800-37 Rev. 2, 800-53 and 800-53A
Take a system from preparation and categorization through assessment, authorization and monitoring.
U.S. federal information systems and other organizations adopting the RMF, subject to applicable agency and program rules.
A defensible authorization package and a decision by the responsible authorizing official where required.
An authorizing official makes the decision and accepts risk. Selecting controls or producing a security plan is an input to that decision.
Monitor progress against the target, failed control tests and gaps that leave a critical service exposed.
Fill this in with your sponsor and send it to the people who own the work.
NIST Risk Management Framework 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 Prepare and categorize the system · System owner + risk manager [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. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Select one service and test a high-impact control with its owner. Record what actually happened, what failed and the proposed target. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
An agency moves an internal service to managed infrastructure. The owner records common controls inherited from the host and separates those from application controls that still need local tests before the authorizing official reviews risk.
Check the specific certification requirements for a federal cloud service offering.
Checklist, instructions and 12 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Prepare and categorize the system | System owner + risk manager | During planning and scope changes | Set a start date | System boundary; Classification memo; Role map | Open |
| Select, tailor and implement controls | Security architect + common control providers | Before assessment | Set a start date | SSP; Control matrix; Monitoring plan | Open |
| Assess controls and present residual risk | Assessor + system owner | Before the authorizing official’s review | Set a start date | Test workpapers; Assessment report; Remediation plan | Open |
| Authorize and keep the decision current | Authorizing official + monitoring lead | At decision and throughout operation | Set a start date | External decision; Monitoring evidence; Change decisions | 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 mission, information types, stakeholders and the boundary. Determine and approve categorization and assign participants.
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.
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.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Select applicable baselines and tailor based on risk and agency rules. Document common and hybrid controls, implementations and monitoring in the plan.
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 different person can operate the control or test it using the matrix and its evidence links.
Give the baseline to control owners and the assessor before walkthroughs or sampling.
Fictional details. Use the same fields with evidence from your work.
A person who receives the plan can tell when to act, what to check and where to save the result.
Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.
Develop tests, collect evidence and address weaknesses. Assemble the security plan, findings and remediation information needed for the decision.
Fictional details. Use the same fields with evidence from your work.
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
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.
Record risk acceptance or conditions. Monitor controls and significant changes and present impacts under the agency’s ongoing authorization approach.
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.
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 minutes identify the person who approved each action and the date the decision will be revisited.
Give owners the actions and add the approved record to the relevant audit or governance file.