Control statement
Address information security and privacy issues in the development, documentation, and updating of a critical infrastructure and key resources protection plan.
Discussion
Protection strategies are based on the prioritization of critical assets and resources. The requirement and guidance for defining critical infrastructure and key resources and for preparing an associated critical infrastructure protection plan are found in applicable laws, executive orders, directives, policies, regulations, standards, and guidelines.
From control text to operational evidence
Use Critical Infrastructure Plan as a testable risk decision. Translate the official statement into accountable people, repeatable processes, configured technology, and evidence that demonstrates the outcome over time. In this family, pay particular attention to enterprise program governance, accountability, resources, metrics, and organization-wide risk decisions.
Implementation workflow
- Define the control boundary, responsible owner, inherited portions, and systems or processes in scope.
- Resolve each organization-defined parameter before declaring the control implemented.
- Document how the implementation satisfies every clause of the official control statement.
- Collect evidence as a normal byproduct of operation rather than only before an assessment.
- Review exceptions, changes, and monitoring results on a risk-based cadence.
Evidence examples
- program charters and policies
- governance meeting records
- risk and performance metrics
- resource and responsibility assignments
Common failure patterns
- program metrics count activity instead of outcomes
- system-level risks never reach enterprise governance
- responsibilities assigned without authority or resources
- privacy and security managed in separate silos
Questions practitioners should ask
- What risk decision is this control intended to support in this system?
- Which parts are implemented locally, inherited, shared, or not applicable—and what evidence supports that decision?
- Do the documented narrative, deployed configuration, operating process, and collected evidence agree?
- What event or threshold requires the implementation to be reviewed or changed?
Assessment objectives and methods
Show the assessment objective
- PM-08[01]information security issues are addressed in the development of a critical infrastructure and key resources protection plan;
- PM-08[02]information security issues are addressed in the documentation of a critical infrastructure and key resources protection plan;
- PM-08[03]information security issues are addressed in the update of a critical infrastructure and key resources protection plan;
- PM-08[04]privacy issues are addressed in the development of a critical infrastructure and key resources protection plan;
- PM-08[05]privacy issues are addressed in the documentation of a critical infrastructure and key resources protection plan;
- PM-08[06]privacy issues are addressed in the update of a critical infrastructure and key resources protection plan.
Examine
- Information security program plan
- privacy program plan
- critical infrastructure and key resources protection plan
- procedures addressing the development, documentation, and updating of the critical infrastructure and key resources protection plan
- HSPD 7
- National Infrastructure Protection Plan
- other relevant documents or records
Interview
- Organizational personnel with information security and privacy program planning and plan implementation responsibilities
- organizational personnel responsible for developing, documenting, and updating the critical infrastructure and key resources protection plan
- organizational personnel with information security and privacy responsibilities
Test
- Organizational processes for developing, documenting, and updating the critical infrastructure and key resources protection plan
- mechanisms supporting the development, documentation, and updating of the critical infrastructure and key resources protection plan
Related controls
These relationships come from the official OSCAL catalog. They indicate useful dependencies or context, not automatic inheritance or equivalence.
Authoritative sources
Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. Official control requirements and interpretations remain with NIST and the responsible authorizing organization.