Someone senior is accountable for security risk, the organization has said how much risk it will accept, it knows which systems it runs and how important each is, and each system in scope has started a security plan.
| Artifact | Main controls | What it records |
|---|
| Information Security Program Plan | PM-1 | The program’s structure, roles and the common controls it provides |
| Risk Management Strategy | PM-9 | Risk tolerance, assumptions, constraints and priorities |
| System inventory | PM-5 | Every system, its owner and its security categorization |
| Security categorization worksheet | RA-2 | Each system’s impact level, from the information it handles |
| System Security Plan | PL-2 | For each system: boundary, environment and how each control is met |
| Rules of Behavior | PL-4 | What users agree to before they get access |
| Risk assessment report | RA-3 | Threats, likelihood and impact for a system or the organization |
| Artifact | Type | Main controls | Status |
|---|
| Planning Policy | Policy | PL-1 | Draft |
| Planning Decision Worksheet | Decision worksheet | PL-1 | Draft |
| Program Management Policy | Policy | PM-1 | Draft |
| Program Management Decision Worksheet | Decision worksheet | PM-1 | Draft |
| Risk Assessment Policy | Policy | RA-1 | Draft |
| Risk Assessment Decision Worksheet | Decision worksheet | RA-1 | Draft |
| Information Security Program Plan | Plan | PM-1, PM-2, PM-3, PM-6, PM-10, PM-29 | Draft |
| Risk Assessment Report | Report | RA-3, RA-3(1) | Draft |
| Risk Management Strategy | Plan | PM-9, PM-28, PM-29, PM-31 | Draft |
| Risk Register | Form or register | RA-3, RA-7 | Draft |
| Rules of Behavior | Form or register | PL-4, PL-4(1), PE-17 | Draft |
| Security Categorization Worksheet | Form or register | RA-2 | Draft |
| System Inventory | Form or register | PM-5, PM-5(1) | Draft |
| System Security Plan | Plan | PL-2, RA-2, CM-8, CA-3, CA-5 | Draft |
- Who is the senior official accountable for security risk, and who authorizes each system to operate.
- How much risk the organization accepts, stated so a system owner can apply it.
- Which systems are in scope, and the impact level of each.
- Which control baseline each system starts from (Low, Moderate or High).
| Role | Responsibility in this stage |
|---|
| Senior leader | Appoints the accountable officials and approves the risk management strategy |
| Chief Information Security Officer | Writes the program plan and the strategy; maintains the inventory |
| System owner | Categorizes the system and starts its security plan |
| Authorizing official | Accepts the categorization and the baseline for each system |
From the organization-level tasks of SP 800-37 Rev. 2, described on the Prepare step page. The mapping is the author’s judgment.
| Task | How this stage meets it |
|---|
| P-1 Risk management roles | The program plan names the accountable officials and their delegations |
| P-2 Risk management strategy | The Risk Management Strategy |
| P-3 Risk assessment, organization | The organization-level risk assessment report |
| P-6 Impact-level prioritization (optional) | The system inventory ranks systems within each impact level |
Independent guidance, not an official NIST publication. Control text is from NIST SP 800-53 Rev. 5 and SP 800-53A (public domain). Original content is licensed CC BY 4.0; program templates and the downloadable kit are dedicated to the public domain under CC0 1.0.