CPS 234 para 19 Policy Direction to All Responsible Parties
The information security policy framework must give direction on the responsibilities of every party obliged to maintain information security, including staff, contractors, consultants, related parties, third parties and
3
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
- Acknowledgement records for staff and contractors · HR system / LMS
governing documentDocuments that govern the control
- Policy clauses addressed to each party type · Policy repository / GRC workspace
- Contractual or terms of use flow down to third parties and customers · Vendor register / contract repository
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 addressed to employees only
- No evidence the policy reached third parties or customers
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 sheetCPS 234 para 18 Information Security Policy Framework · CPS 234 para 20 Information Asset Classification