AC-19 Access control for mobile devices
Requires documented configuration settings, connection rules and implementation guidance for mobile devices the organization controls, including their use away from controlled areas, and explicit authorization before any
4
artefacts
0
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
none for this control
periodic reviewEvidence produced at each review
- Evidence of enforcement action on non-compliant or unenrolled devices · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- Mobile device standard covering encryption, lock, patching and off-site use · Policy repository / GRC workspace
- Mobile device management enrolment report reconciled to the device inventory · Policy repository / GRC workspace
- Authorization records for mobile device connection to each in scope system · 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
- Personally owned devices reach corporate mail with no enrolment or authorization
- Requirements stop at the device and ignore removable storage attached to it
- Inventory drifts, so devices that left the organization still hold valid connection profiles
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 sheet