ac-2-11-usage-conditions

name	AC-2(11)_usage-conditions
description	Enforce [organization-defined] for [organization-defined].
category	authorization
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","ac-2-11","ac","enhancement"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-284"]
chains_with	[]
prerequisites	["AC-2"]
severity_boost	{}

AC-2(11) Usage Conditions

Enhancement of: AC-2

High-Level Description

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

Specifying and enforcing usage conditions helps to enforce the principle of least privilege, increase user accountability, and enable effective account monitoring. Account monitoring includes alerts generated if the account is used in violation of organizational parameters. Organizations can describe specific conditions or circumstances under which system accounts can be used, such as by restricting usage to certain days of the week, time of day, or specific durations of time.

What to Check

• Verify AC-2(11) Usage Conditions is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for AC-2(11)
• Verify enhancement builds upon base control AC-2

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for AC-2(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

Enforce [organization-defined] for [organization-defined].

Implementation Guidance

Specifying and enforcing usage conditions helps to enforce the principle of least privilege, increase user accountability, and enable effective account monitoring. Account monitoring includes alerts generated if the account is used in violation of organizational parameters. Organizations can describe specific conditions or circumstances under which system accounts can be used, such as by restricting usage to certain days of the week, time of day, or specific durations of time.