ac-3-13-attribute-based-access-control

name	AC-3(13)_attribute-based-access-control
description	Enforce attribute-based access control policy over defined subjects and objects and control access based upon [organization-defined].
category	authorization
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","ac-3-13","ac","enhancement"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-284"]
chains_with	[]
prerequisites	["AC-3"]
severity_boost	{}

AC-3(13) Attribute-based Access Control

Enhancement of: AC-3

High-Level Description

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

Attribute-based access control is an access control policy that restricts system access to authorized users based on specified organizational attributes (e.g., job function, identity), action attributes (e.g., read, write, delete), environmental attributes (e.g., time of day, location), and resource attributes (e.g., classification of a document). Organizations can create rules based on attributes and the authorizations (i.e., privileges) to perform needed operations on the systems associated with organization-defined attributes and rules. When users are assigned to attributes defined in attribute-based access control policies or rules, they can be provisioned to a system with the appropriate privileges or dynamically granted access to a protected resource. Attribute-based access control can be implemented as either a mandatory or discretionary form of access control. When implemented with mandatory access controls, the requirements in AC-3(3) define the scope of the subjects and objects covered by the policy.

What to Check

• Verify AC-3(13) Attribute-based Access Control is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for AC-3(13)
• Verify enhancement builds upon base control AC-3

How to Test

Step 1: Review Documentation

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