manage.get.gov/docs/compliance/dist/system-security-plans/ato/ac-11.md
Logan McDonald 1d3dfdb8d5
Add compliance documentation to source control (#116)
* add initial setup of compliance-trestle
2022-09-14 08:46:43 -04:00

2 KiB

implementation-status control-origination
c-not-implemented
c-inherited-cloud-gov
c-inherited-cisa
c-common-control
c-system-specific-control

ac-11 - [catalog] Device Lock

Control Statement

  • [a] Prevent further access to the system by No value found ; and

  • [b] Retain the device lock until the user reestablishes access using established identification and authentication procedures.

Control guidance

Device locks are temporary actions taken to prevent logical access to organizational systems when users stop work and move away from the immediate vicinity of those systems but do not want to log out because of the temporary nature of their absences. Device locks can be implemented at the operating system level or at the application level. A proximity lock may be used to initiate the device lock (e.g., via a Bluetooth-enabled device or dongle). User-initiated device locking is behavior or policy-based and, as such, requires users to take physical action to initiate the device lock. Device locks are not an acceptable substitute for logging out of systems, such as when organizations require users to log out at the end of workdays.

Control assessment-objective

further access to the system is prevented by No value found; device lock is retained until the user re-establishes access using established identification and authentication procedures.


What is the solution and how is it implemented?


Implementation a.

Add control implementation description here for item ac-11_smt.a


Implementation b.

Add control implementation description here for item ac-11_smt.b