12.1.4 CISO or equivalent responsibility
Responsibility for information security is formally assigned to a Chief Information Security Officer or other knowledgeable member of executive management.
5
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
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
- Board minutes referencing CISO updates · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Executive appointment letter or job description · Document repository
- Org chart showing CISO reporting line · Document repository
- Charter document outlining authority · Policy repository / GRC workspace
- Bio confirming knowledge and qualifications · Document 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
- No executive owner
- CISO buried in IT
- No board visibility
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 sheet12.1.3 Information security roles and responsibilities defined and acknowledged · 12.2.1 Acceptable use policies for end-user technologies