cATO: write the system security plan
The Controls tab is the SSP, one control at a time.
Write a control:
1. Open Controls and pick a family, or search by id or title.
2. Choose a control. Its NIST statement is shown with your parameter values filled in, and with FedRAMP's parameters when you chose a FedRAMP baseline.
3. Set the implementation status: implemented, partial, planned, alternative or not applicable.
4. Set responsibility: this system, shared with a provider, or inherited from a provider. Shared and inherited need a provider from the Overview tab.
5. Write the implementation statement: how this system meets the control.
6. Fill in the parameters your organization defines.
7. If you added components, describe how each one contributes.
Everything saves as you type; the status next to the title says when it last saved.
Components:
Add the software, hardware, services, policies and interconnections in the boundary at the top of the Controls tab. A component that is named in a control cannot be removed until it is taken out of those controls.
Assessment:
An assessor records satisfied or other than satisfied, the method (examine, interview, test) and what they looked at. The person who last edited a control cannot assess it. If the control is edited after its assessment, the page says so.
SP 800-171 Rev 3 and CMMC:
The SP 800-171 Rev 3 mapping shows how your implemented controls cover each Rev 3 requirement, through the 800-53 source controls NIST lists for it. It does not compute a CMMC level. CMMC Level 2 is assessed against SP 800-171 Rev 2: choose the NIST SP 800-171 Rev 2 baseline for that. Its 110 requirements and the 320 SP 800-171A assessment objectives come from NIST's own CSV files (NIST publishes no OSCAL for Rev 2). Each Rev 2 requirement shows its objectives and its Rev 3 successor; the SP 800-53 controls shown beside it come through that Rev 3 successor and are a transition reference, because NIST publishes Rev 2's own 800-53 mapping only in the PDF. Automated checks attach to SP 800-53 controls, so on a Rev 2 system attach evidence to each requirement yourself.
Ask Wally:
Wally can look up a control's statement and parameters, or tell you where your SSP stands, and walk you through any of these steps.