PL-1 Policy and Procedures
Develop and review planning policy at least annually.
5
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
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
- Rules of behaviour signed by users including privileged personnel · Identity provider / directory
governing documentDocuments that govern the control
- Control implementation statement for PL-1 citing the system mission and inheritance from common controls · Document repository
- Concept of operations describing system mission and data flows · Document repository
- Privacy and security integration documentation · Policy repository / GRC workspace
- System security plan with control allocation matrix · 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
- Planning artefacts lack version history and approval signatures
- Privacy considerations addressed separately from security planning
- System security plan not refreshed after material system changes
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-17 Alternate Work Site · PL-2 System Security and Privacy Plans