12.2.1 Acceptable use policies for end-user technologies
Acceptable use policies for end-user technologies are documented and implemented, addressing approval, authentication, inventory, acceptable use, and remote access controls.
5
artefacts
0
held by a system
3
at each review
hard
to go live
Document repository
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
- Personnel acknowledgement records · HR system / LMS
- Enforcement evidence (DLP, MDM) · Endpoint management (MDM / EDR)
- Annual review records · Document repository
governing documentDocuments that govern the control
- Acceptable Use Policy document covering required topics · Policy repository / GRC workspace
- Remote access guidance · Document repository
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
- AUP missing required topics
- Enforcement weak
- Acknowledgements stale
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 sheet12.1.4 CISO or equivalent responsibility · 12.3.1 Targeted risk analysis documented for requirements that specify one