ia-11-re-authentication

name	IA-11_re-authentication
description	Require users to re-authenticate when [organization-defined].
category	authentication
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","ia-11","ia"]
tech_stack	["aws","azure","active-directory","linux","windows"]
cwe_ids	["CWE-287"]
chains_with	["AC-3","AC-11","IA-2","IA-3","IA-4","IA-8"]
prerequisites	[]
severity_boost	{"AC-3":"Chain with AC-3 for comprehensive security coverage","AC-11":"Chain with AC-11 for comprehensive security coverage","IA-2":"Chain with IA-2 for comprehensive security coverage"}

IA-11 Re-authentication

High-Level Description

Family: Identification and Authentication (IA) Framework: NIST SP 800-53 Rev 5

In addition to the re-authentication requirements associated with device locks, organizations may require re-authentication of individuals in certain situations, including when roles, authenticators or credentials change, when security categories of systems change, when the execution of privileged functions occurs, after a fixed time period, or periodically.

What to Check

• Verify IA-11 Re-authentication is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for IA-11

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for IA-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 authentication settings	cloud_audit_iam_policies
hackbrowser-mcp	Test authentication mechanisms	browser_auth_test

Remediation Guide

Control Statement

Require users to re-authenticate when [organization-defined].

Implementation Guidance

In addition to the re-authentication requirements associated with device locks, organizations may require re-authentication of individuals in certain situations, including when roles, authenticators or credentials change, when security categories of systems change, when the execution of privileged functions occurs, after a fixed time period, or periodically.

Risk Assessment

Finding