NIST Risk Management Framework
Apply Prepare, Categorize, Select, Implement, Assess, Authorize, and Monitor as a risk-based system lifecycle.
On this page · 4 sections
Applicability & intent
NIST SP 800-37 integrates security and privacy risk management into system development, authorization, and continuous monitoring.
- Document why nist risk management framework applies, what is in scope, and who is accountable.
- Translate obligations into owned, testable outcomes with proportionate evidence.
- Track exceptions, residual risk, changes, and corrective actions through governance review.
Governance lifecycle
- 01
Confirm scope, context, interested parties, legal or contractual basis, and authoritative sources.
- 02
Identify desired outcomes, owners, dependencies, existing controls, and evidence sources.
- 03
Assess design and operating effectiveness using representative, time-bound evidence.
- 04
Record gaps, risk, interim protections, target dates, and approval decisions.
- 05
Verify remediation, report residual risk, and schedule reassessment when context changes.
Evidence & assurance
| Evidence family | Assurance question |
|---|---|
| system boundary and categorization | Does governance establish accountable direction? |
| selected and implemented control baseline | Does the process operate consistently? |
| assessment, authorization, and monitoring records | Can the claimed outcome be independently verified? |
Evidence should be attributable, current, protected, reproducible, and linked to an accountable owner. A document alone does not demonstrate that a control operates effectively.
Readiness decisions
- Prepare organization and system context first.
- Keep authorization decisions tied to current evidence.
- Feed monitoring changes back into risk decisions.