NIST SP 800-53 Rev. 5 PM-28 — Risk Framing

What this control requires

Identify and document assumptions, constraints, priorities, trade-offs, and organizational risk tolerance affecting risk assessments, responses, and monitoring. Distribute the results of risk framing activities to relevant personnel and review/update them regularly to reflect changes in organizational conditions. This control supports the Governance capability within the Program Management family.

In plain English

Identify and document assumptions, constraints, priorities, trade-offs, and organizational risk tolerance affecting risk assessments, responses, and monitoring. In practice, this means you can prove you policy management-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within Program Management, the assessor will trace your implementation back to the catalogue reference (Control PM-28) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

• Policy. Document the trigger, the owner and the cadence.
• Review. Document the trigger, the owner and the cadence.
• Changes. Document the trigger, the owner and the cadence.
• Control. Document the trigger, the owner and the cadence.
• Identify. Document the trigger, the owner and the cadence.
• Scope: management, conditions, personnel, assessments, review, capability, policy.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Risk Framing.

Common pitfalls

• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• SOC 2 (2017 TSC) CC4.1 — Control Monitoring
• HIPAA (45 CFR Part 164) 164.308(a)(5)(i) — Security Awareness and Training
• BSI C5:2020 SP-01 — Documentation, communication and provision of policies and instructions
• CIS Controls v8 7.1 — Establish and Maintain a Vulnerability Management Process
• ISO/IEC 27001:2022 A.5.5 — Contact with authorities

Related controls in NIST SP 800-53 Rev. 5

• Control PM-27 — Privacy Reporting
• Control SC-1 — Policy And Procedures
• Control CA-2(1) — Independent Assessors
• Control PM-5 — System Inventory
• Control CM-11 — User-Installed Software
• Control PL-3 — System Security Plan Update

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control PM-28

Topics: governance riskcontinuous monitoringpatch managementpolicy management