ac-11-device-lock

name	AC-11_device-lock
description	Prevent further access to the system by [organization-defined] ;
category	authorization
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","ac-11","ac"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-284"]
chains_with	["AC-2","AC-7","IA-11","PL-4"]
prerequisites	[]
severity_boost	{"AC-2":"Chain with AC-2 for comprehensive security coverage","AC-7":"Chain with AC-7 for comprehensive security coverage","IA-11":"Chain with IA-11 for comprehensive security coverage"}

AC-11 Device Lock

High-Level Description

Family: Access Control (AC) Framework: NIST SP 800-53 Rev 5

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.

What to Check

• Verify AC-11 Device Lock is documented in SSP
• Validate all 2 control requirements are implemented
• Confirm control is operating effectively
• Review evidence of continuous monitoring for AC-11

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for AC-11 implementation details. Verify the organization has documented how this control is satisfied.

Step 2: Validate Implementation

# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null

Step 3: Test Operating Effectiveness

Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.

Tools

Tool	Purpose	Usage
cloud-audit-mcp	Check IAM policies and access controls	cloud_audit_iam_policies
hackbrowser-mcp	Test web application access controls	browser_auth_test

Remediation Guide

Control Statement

Prevent further access to the system by [organization-defined] ; and Retain the device lock until the user reestablishes access using established identification and authentication procedures.