PL-2 System security and privacy plans
Requires system security and privacy plans that align to the enterprise architecture, define the system components and operational context, name role holders, identify information types and the security categorization wi
5
artefacts
0
held by a system
1
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
- Review and update history following change, assessment or monitoring findings · SIEM / log platform
governing documentDocuments that govern the control
- Approved system security and privacy plan covering each required element · Policy repository / GRC workspace
- Approval signature by the authorizing official or delegate · Document repository
- Record showing the security and privacy plan was issued to its defined recipients · Policy repository / GRC workspace
- Access controls preventing unauthorized disclosure or modification of the system security and privacy plan · 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
- Plan describes the system as designed rather than as it now runs
- Control implementation statements copied between systems without tailoring
- Plan updated at reauthorization only, so it is stale for most of its life
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 sheetPL-1 Policy and procedures for planning · PL-4 Rules of behavior