11.1.2 Testing roles assigned
Roles and responsibilities for performing activities in Requirement 11 are documented, assigned, and understood.
5
artefacts
1
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
- Vendor scope documents for pen tests and scans · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Training records · HR system / LMS
governing documentDocuments that govern the control
- RACI for testing activities · Policy repository / GRC workspace
- Acknowledgement of role assignments · Policy repository / GRC workspace
- Job descriptions citing duties · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Vulnerability scanner / patch tooling on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Vendor scope unclear
- No internal owner
- Acknowledgements missing
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 sheet11.1.1 Testing policy documented · 11.2.1 Wireless AP detection