OIS-02 Information Security Policy
Top management adopts an information security policy and issues it to internal staff, external personnel and cloud customers, setting out why security matters, the security objectives and target level, the core security
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Information security policy carrying dated approval by the executive board or equivalent body · Policy repository / GRC workspace
- Publication or distribution record proving the policy reached employees and contracted personnel · HR system / LMS
- Customer facing copy of the policy or the portal location where customers obtain it · Policy repository / GRC workspace
- Organisation chart naming the security roles and reporting lines the policy declares · 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
- Policy signed off by a security manager instead of top management
- Security objectives and target protection level stated generically with no link to business goals
- External personnel and cloud customers are never given sight of the policy
- Declared security organisation no longer matches the current reporting structure
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 sheetOIS-01 Information Security Management System (ISMS) · OIS-03 Interfaces and Dependencies