PS-9 Position descriptions
Requires security and privacy roles and responsibilities to be written into organizational position descriptions, so that expectations are part of the role rather than an add on.
4
artefacts
1
held by a system
1
at each review
moderate
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
- Change records showing descriptions updated when responsibilities changed · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
- Evidence of coverage across privileged and security relevant roles · Identity provider / directory
governing documentDocuments that govern the control
- Sample position descriptions showing security and privacy responsibilities · Policy repository / GRC workspace
- Alignment between position descriptions and role based training requirements · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Policy repository / GRC workspace); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Security responsibilities named only in dedicated security roles
- Descriptions updated for new hires while incumbents keep older versions
- Privacy responsibilities omitted entirely
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 sheetPS-8 Personnel sanctions · PT-1 Policy and Procedures. Develop, document, and disseminate to [organization-defined]: [organization-defined] personally identifiable information processing and transparency policy that: Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and Is consistent