DCS-03 Secure Area Policy and Procedures
Maintain approved procedures for keeping offices, rooms and facilities a safe and secure working environment, and review them at least annually.
4
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
- Annual review record · Document repository
- Evidence of application, such as area designations and their controls · Document repository
governing documentDocuments that govern the control
- The secure area procedure with approver and date · Policy repository / GRC workspace
- Communication to staff working in those areas · 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
- Procedure covers the datacentre and omits offices where data is handled
- Annual review missed
- Designations exist on paper with no matching physical control
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 sheetDCS-02 Off-Site Transfer Authorization Policy and Procedures · DCS-04 Secure Media Transportation Policy and Procedures