NIST SP 800-53 Rev 5
PL - Planning

NIST SP 800-53 Rev 5 PL-1: Policy and procedures for planning

Requires a planning policy with supporting procedures to be developed, approved, disseminated to defined personnel, owned by a named official, and reviewed and updated on a defined frequency and after defined events.

What else in your programme already covers this

This control maps to 82 controls across 25 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 12 controls

  • 1.1.1 NSC policies and procedures documented
  • 11.1.1 Testing policy documented
  • 12.1.1 An overall information security policy is: • Established. • Published. • Maintained. • Disseminated to all relevant personnel, as well as to relevant vendors and business partners
  • 12.1.2 The information security policy is: • Reviewed at least once every 12 months. • Updated as needed to reflect changes to business objectives or risks to the environment
  • 2.1.1 All security policies and operational procedures that are identified in Requirement 2 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
  • 4.1.1 All security policies and operational procedures that are identified in Requirement 4 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
  • 5.1.1 All security policies and operational procedures that are identified in Requirement 5 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
  • 6.1.1 All security policies and operational procedures that are identified in Requirement 6 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
  • 7.1.1 All security policies and operational procedures that are identified in Requirement 7 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
  • 9.1.1 All security policies and operational procedures that are identified in Requirement 9 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
  • 3.1.1 All security policies and operational procedures that are identified in Requirement 3 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
  • 8.1.1 All security policies and operational procedures that are identified in Requirement 8 are: • Documented. • Kept up to date. • In use. • Known to all affected parties

ISO 27701:2019 · 8 controls

  • 5.3.1 Leadership and commitment
  • 5.3.2 Policy
  • 5.4 Planning
  • 5.4.2 Information security objectives and planning to achieve them
  • 5.6.1 Operational planning and control
  • 6.2 Information security policies
  • 6.2.1 Management direction for information security
  • 8.1 General
  • NIST-CSF-GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission
  • NIST-CSF-GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders
  • NIST-CSF-GV.RM-02 Risk appetite and risk tolerance statements are established, communicated, and maintained
  • NIST-CSF-GV.RM-04 Strategic direction that describes appropriate risk response options is established and communicated
  • NIST-CSF-GV.RR-01 Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving
  • NIST-CSF-GV.SC-09 Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycle

ISO 22301:2019 · 7 controls

  • 5.2 Policy
  • 5.2.1 Establishing the business continuity policy
  • 5.2.2 Communicating the business continuity policy
  • 6.1 Actions to address risks and opportunities
  • 6.1.1 Determining risks and opportunities
  • 6.2.1 Establishing business continuity objectives
  • 8.4.1 General

ISO/IEC 42001:2023 · 7 controls

  • 5.1 Leadership and commitment
  • 5.2 Policy
  • 6.1 Actions to address risks and opportunities
  • 6.1.1 General
  • 7.5.1 General
  • 8.1 Operational planning and control
  • A.2.2 AI policy
  • ADMF-1.1 Establish data management governance functions
  • ADMF-2.2 Define objectives, scope and considerations (what and why)
  • ADMF-2.3 Establish the data management approach (how)
  • ADMF-2.4 Embed data management in corporate governance and policy
  • ADMF-6.5 Update policies, procedures and processes

ISO 27001:2022 · 4 controls

  • 5.1 Policies for information security
  • 5.20 Addressing information security within supplier agreements
  • 5.31 Legal, statutory, regulatory and contractual requirements
  • 5.37 Documented operating procedures

SOC 2 · 4 controls

  • SOC2-CC3.1 COSO principle 6: Specifies objectives to identify and assess risks
  • SOC2-CC4.1 COSO principle 16: Selects and develops ongoing and separate evaluations
  • SOC2-CC5.3 COSO principle 12: Deploys control activities through policies and procedures
  • SOC2-CC9.1 Identifies, selects and develops risk mitigation activities

HIPAA Security Rule · 3 controls

ISO 27002:2022 · 3 controls

  • 5.1 Policies for information security
  • 5.31 Legal, statutory, regulatory and contractual requirements
  • 5.37 Documented operating procedures

C5 (Germany) · 2 controls

  • C5-SP-01 Documentation, communication and provision of policies and instructions
  • C5-SP-02 Review and Approval of Policies and Instructions
  • ITSG33-PL Planning (PL)
  • ITSG33-RMP-2 Information System Security Risk Management Activities / ISSIP (Annex 2)

NIST SP 800-66 Rev 2 · 2 controls

CIS Controls v8 · 1 control

  • CIS-15.2 Establish and Maintain a Service Provider Management Policy
  • CCM-GRC-01 Governance Program Policy and Procedures

FedRAMP High · 1 control

  • PL-1 Policy and Procedures

FedRAMP Moderate · 1 control

  • PL-1 Policy and Procedures
  • PL-1 Policy and Procedures
  • PL-1 Policy and Procedures
  • PL-1 Policy and Procedures

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in PL - Planning

You are reading one control. How much of NIST SP 800-53 Rev 5 have you already done?

NIST SP 800-53 Rev 5 PL-1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-53 Rev 5 your existing evidence covers. Hold ISO 27001:2022 and 163 of 300 NIST SP 800-53 Rev 5 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 342 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

The graph holds this control, the 82 it maps to, and the evidence behind each claim, over MCP and REST.