Skip to content

Stage 1: Foundation

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.

ArtifactMain controlsWhat it records
Information Security Program PlanPM-1The program’s structure, roles and the common controls it provides
Risk Management StrategyPM-9Risk tolerance, assumptions, constraints and priorities
System inventoryPM-5Every system, its owner and its security categorization
Security categorization worksheetRA-2Each system’s impact level, from the information it handles
System Security PlanPL-2For each system: boundary, environment and how each control is met
Rules of BehaviorPL-4What users agree to before they get access
Risk assessment reportRA-3Threats, likelihood and impact for a system or the organization
ArtifactTypeMain controlsStatus
Planning PolicyPolicyPL-1Draft
Planning Decision WorksheetDecision worksheetPL-1Draft
Program Management PolicyPolicyPM-1Draft
Program Management Decision WorksheetDecision worksheetPM-1Draft
Risk Assessment PolicyPolicyRA-1Draft
Risk Assessment Decision WorksheetDecision worksheetRA-1Draft
Information Security Program PlanPlanPM-1, PM-2, PM-3, PM-6, PM-10, PM-29Draft
Risk Assessment ReportReportRA-3, RA-3(1)Draft
Risk Management StrategyPlanPM-9, PM-28, PM-29, PM-31Draft
Risk RegisterForm or registerRA-3, RA-7Draft
Rules of BehaviorForm or registerPL-4, PL-4(1), PE-17Draft
Security Categorization WorksheetForm or registerRA-2Draft
System InventoryForm or registerPM-5, PM-5(1)Draft
System Security PlanPlanPL-2, RA-2, CM-8, CA-3, CA-5Draft
  • 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).
RoleResponsibility in this stage
Senior leaderAppoints the accountable officials and approves the risk management strategy
Chief Information Security OfficerWrites the program plan and the strategy; maintains the inventory
System ownerCategorizes the system and starts its security plan
Authorizing officialAccepts 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.

TaskHow this stage meets it
P-1 Risk management rolesThe program plan names the accountable officials and their delegations
P-2 Risk management strategyThe Risk Management Strategy
P-3 Risk assessment, organizationThe 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.