PL-1 Policy and Procedures
a. Develop, document, and disseminate to 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 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 organization-defined frequency and following organization-defined events; and 2. Procedures organization-defined frequency and following organization-defined events.
Source: NIST SP 800-53 Rev 5, PL-1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST SP 800-53 Rev 5 in the compliance library.
Base controls and their enhancements. Which apply follows the baseline you are assessed against (for example FedRAMP Moderate or High, or the low, moderate and high baselines of SP 800-53B). Text in square brackets is a parameter your organisation sets.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Planning policy and procedures · Policy repository / GRC workspace
- System security plan · Policy repository / GRC workspace
- Privacy plan · Policy repository / GRC workspace
First move
Common gaps auditors find
- Planning policy does not address who owns security and privacy plans, rules of behavior and architecture across entities
- Planning procedures are not updated following events such as changes to the enterprise architecture or assessment findings
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetPE-23 Facility Location · PL-2 System Security and Privacy Plans