EvidenceSheet

PL-8 Security and Privacy Architectures

Develop, document, maintain security/privacy architectures; review annually.

6
artefacts
0
held by a system
2
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

  • Rules of behaviour signed by users including privileged personnel · Identity provider / directory
  • Security planning meeting minutes with stakeholder attendance · HR system / LMS

governing documentDocuments that govern the control

  • Control implementation statement for PL-8 citing the system mission and inheritance from common controls · Document repository
  • Privacy and security integration documentation · Policy repository / GRC workspace
  • System security plan with control allocation matrix · Policy repository / GRC workspace
  • Information security architecture diagrams current within twelve months · 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

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 sheet

PL-4(1) Rules of Behavior | Social Media and External Site/application Usage Restrictions. Include in the rules of behavior, restrictions on: (a) Use of social media, social networking sites, and external sites/applications; (b) Posting organizational information · PL-10 Baseline Selection. Select a control baseline for the system