1.1.2 Roles and responsibilities for Requirement 1
Roles and responsibilities for performing activities in Requirement 1 are documented, assigned, and understood.
5
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
- Signed acknowledgements from assigned personnel · HR system / LMS
- Interview notes confirming understanding · Policy repository / GRC workspace
governing documentDocuments that govern the control
- RACI matrix for NSC activities · Policy repository / GRC workspace
- Job descriptions referencing NSC duties · Policy repository / GRC workspace
- Org chart showing reporting lines · 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
- Roles assigned only verbally
- No acknowledgement records
- Outdated job descriptions
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 sheet1.1.1 NSC policies and procedures documented · 1.2.1 NSC configuration standards defined