ac-2-13-disable-accounts-for-high-risk-individuals

name	AC-2(13)_disable-accounts-for-high-risk-individuals
description	Disable accounts of individuals within [organization-defined] of discovery of [organization-defined].
category	authorization
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","ac-2-13","ac","enhancement"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-284"]
chains_with	["AU-6","SI-4"]
prerequisites	["AC-2"]
severity_boost	{"AU-6":"Chain with AU-6 for comprehensive security coverage","SI-4":"Chain with SI-4 for comprehensive security coverage"}

AC-2(13) Disable Accounts for High-risk Individuals

Enhancement of: AC-2

High-Level Description

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

Users who pose a significant security and/or privacy risk include individuals for whom reliable evidence indicates either the intention to use authorized access to systems to cause harm or through whom adversaries will cause harm. Such harm includes adverse impacts to organizational operations, organizational assets, individuals, other organizations, or the Nation. Close coordination among system administrators, legal staff, human resource managers, and authorizing officials is essential when disabling system accounts for high-risk individuals.

What to Check

• Verify AC-2(13) Disable Accounts for High-risk Individuals is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for AC-2(13)
• 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(13) 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

Disable accounts of individuals within [organization-defined] of discovery of [organization-defined].

Implementation Guidance