| name | IA-2(13)_out-of-band-authentication |
| description | Implement the following out-of-band authentication mechanisms under [organization-defined]: [organization-defined]. |
| category | authentication |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","ia-2-13","ia","enhancement"] |
| tech_stack | ["aws","azure","active-directory","linux","windows"] |
| cwe_ids | ["CWE-287"] |
| chains_with | ["IA-10","IA-11","SC-37"] |
| prerequisites | ["IA-2"] |
| severity_boost | {"IA-10":"Chain with IA-10 for comprehensive security coverage","IA-11":"Chain with IA-11 for comprehensive security coverage","SC-37":"Chain with SC-37 for comprehensive security coverage"} |
IA-2(13) Out-of-band Authentication
Enhancement of: IA-2
High-Level Description
Family: Identification and Authentication (IA)
Framework: NIST SP 800-53 Rev 5
Out-of-band authentication refers to the use of two separate communication paths to identify and authenticate users or devices to an information system. The first path (i.e., the in-band path) is used to identify and authenticate users or devices and is generally the path through which information flows. The second path (i.e., the out-of-band path) is used to independently verify the authentication and/or requested action. For example, a user authenticates via a notebook computer to a remote server to which the user desires access and requests some action of the server via that communication path. Subsequently, the server contacts the user via the user’s cell phone to verify that the requested action originated from the user. The user may confirm the intended action to an individual on the telephone or provide an authentication code via the telephone. Out-of-band authentication can be used to mitigate actual or suspected "man-in the-middle" attacks. The conditions or criteria for activation include suspicious activities, new threat indicators, elevated threat levels, or the impact or classification level of information in requested transactions.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for IA-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
