2.1.2 Roles and responsibilities for performing activities in Requirement 2 are documented, assigned, and understood
Roles and responsibilities for performing activities in Requirement 2 are documented, assigned, and understood.
5
artefacts
2
held by a system
2
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- RACI for configuration management · Cloud console / configuration management
- Job descriptions referencing config duties · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Signed acknowledgements · HR system / LMS
- Interview confirmations · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Org chart · Policy repository / GRC workspace
First move
Start with the 2 of 5 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Roles not assigned in writing
- Missing acknowledgements
- Stale 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 sheet2.1.1 All security policies and operational procedures that are identified in Requirement 2 are: • Documented. • Kept up to date. • In use. • Known to all affected parties · 2.2.1 Configuration standards are developed, implemented, and maintained to: • Cover all system components. • Address all known security vulnerabilities. • Be consistent with industry-accepted system hardening standards or vendor hardening recommendations. • Be updated