03.15.03 Rules of Behavior
Establish and provide rules of behavior describing user responsibilities; require acknowledgment before authorizing access; review and update on defined frequency.
2
artefacts
0
held by a system
1
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
- User acknowledgment records · HR system / LMS
governing documentDocuments that govern the control
- AUP · 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
- no acknowledgment for existing users
- AUP not refreshed annually
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 sheet03.15.02 System Security Plan · 03.16.01 Security Engineering Principles