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.
5
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
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
- Approved planning policy with scope, approver and date · Policy repository / GRC workspace
- Evidence the planning policy reached the personnel or roles it defines · Policy repository / GRC workspace
- Written designation of the official accountable for the planning policy and procedures · Policy repository / GRC workspace
- Procedures covering security plan development, review and maintenance · Policy repository / GRC workspace
- Review record for the planning policy and procedures against the defined frequency and triggering events · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Policy exists but no procedure describes how security plans are maintained between authorizations
- Planning treated as a one off project activity rather than an ongoing obligation
- No review cadence defined for the planning policy, so it silently ages
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. Plan the location or site of the facility where the system resides considering physical and environmental hazards; and For existing facilities, consider the physical and environmental hazards in the organizational risk management · PL-2 System security and privacy plans