3.1.1 All security policies and operational procedures that are identified in Requirement 3 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
All security policies and operational procedures that are identified in Requirement 3 are: • Documented. • Kept up to date. • In use. • Known to all affected parties.
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
- Access request workflow output · Identity provider / directory
periodic reviewEvidence produced at each review
- Device authorization records · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- Authorized user roster · Policy repository / GRC workspace
- Examine identification process · Policy repository / GRC workspace
- Test unauthorized access denial · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Identity provider / directory 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
- Service accounts not enumerated
- BYOD authorization unclear
- Contractor devices missing from inventory
- No periodic review of authorization list
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.3.2 Wireless encryption keys rotated · 3.1.2 Roles and responsibilities for performing activities in Requirement 3 are documented, assigned, and understood