| name | IA-13(2)_verification-of-identity-assertions-and-access-tokens |
| description | The source and integrity of identity assertions and access tokens are verified before granting access to system and information resources. |
| category | authentication |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","ia-13-2","ia","enhancement"] |
| tech_stack | ["aws","azure","active-directory","linux","windows"] |
| cwe_ids | ["CWE-287"] |
| chains_with | [] |
| prerequisites | ["IA-13"] |
| severity_boost | {} |
IA-13(2) Verification of Identity Assertions and Access Tokens
Enhancement of: IA-13
High-Level Description
Family: Identification and Authentication (IA)
Framework: NIST SP 800-53 Rev 5
This includes verification of digital signatures protecting identity assertions and access tokens, as well as included metadata. Metadata includes information about the access request such as information unique to user, system or information resource being accessed, or the transaction itself such as time. Protected system and information resources could include connected networks, applications, and APIs.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for IA-13(2) 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
The source and integrity of identity assertions and access tokens are verified before granting access to system and information resources.
Implementation Guidance
This includes verification of digital signatures protecting identity assertions and access tokens, as well as included metadata. Metadata includes information about the access request such as information unique to user, system or information resource being accessed, or the transaction itself such as time. Protected system and information resources could include connected networks, applications, and APIs.