NIST SP 800-53 Rev 5
PL - Planning

NIST SP 800-53 Rev 5 NIST800-PL-1: PL-1 Policy and Procedures

a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (one or more): organization-level; mission/business process-level; system-level] planning policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the planning policy and the associated planning controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the planning policy and procedures; and c. Review and update the current planning: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

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 1.1.1 Requirement 1 policies and procedures governed
  • 11.1.1 11.1.1 Requirement 11 policies and procedures managed
  • 12.1.1 12.1.1 Overall information security policy established and disseminated
  • 12.1.2 12.1.2 Security policy reviewed annually and updated as needed
  • 2.1.1 2.1.1 Requirement 2 policies and procedures governed
  • 4.1.1 4.1.1 Requirement 4 policies and procedures maintained and communicated
  • 5.1.1 5.1.1 Requirement 5 policies and procedures maintained and communicated
  • 6.1.1 6.1.1 Requirement 6 policies and procedures maintained and communicated
  • 7.1.1 7.1.1 Requirement 7 policies and procedures maintained
  • 9.1.1 9.1.1 Requirement 9 policies and procedures maintained
  • 3.1.1 3.1.1 Requirement 3 policies and procedures maintained and in use
  • 8.1.1 8.1.1 Requirement 8 policies and procedures maintained

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 Cybersecurity Framework 2.0 · 8 controls

  • 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 AI 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

ASEAN Data Management Framework · 5 controls

  • 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 CC3.1 Objectives specified clearly enough to assess risk (COSO principle 6)
  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption

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

APRA CPS 220 Risk Management · 2 controls

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

CCSDS 350.0-G-3 - Space Communications Security (Consultative Committee for Space Data Systems) · 2 controls

Canada ITSG-33 - IT Security Risk Management · 2 controls

  • ITSG33-PL Planning (PL)
  • ITSG33-RMP-2 Information System Security Risk Management Activities / ISSIP (Annex 2)

NIST SP 800-66 Rev 2 · 2 controls

Australia My Health Records Act 2012 · 1 control

CIS Controls v8 · 1 control

  • CIS-15.2 Establish and Maintain a Service Provider Management Policy

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

  • 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

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-53 Rev 5 HIGH · 1 control

  • PL-1 PL-1 Policy and Procedures

NIST SP 800-53 Rev 5 LOW · 1 control

  • PL-1 PL-1 Policy and Procedures

NIST SP 800-53 Rev 5 MODERATE · 1 control

  • PL-1 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 NIST800-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 1014 NIST SP 800-53 Rev 5 controls already carry evidence.

If you hold ISO 27001:202216.1% covered · 851 gapsIf you hold ISO 27002:202210.8% covered · 904 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.110.2% covered · 911 gapsIf you hold CIS Controls v810.1% covered · 912 gapsIf you hold NIST SP 800-171 Rev 310.1% covered · 912 gapsIf you hold C5 (Germany)9.6% covered · 917 gaps

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.

See the released pairs, $299 eachBrowse the graph free

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.

MCP endpointAll NIST SP 800-53 Rev 5 controls