IAC-02.4: Out-of-Band Authentication (OOBA)
Mechanisms exist to implement Out-of-Band Authentication (OOBA) under specific conditions.
Control Question: Does the organization implement Out-of-Band Authentication (OOBA) under specific conditions?
General (4)
| Framework | Mapping Values |
|---|---|
| NIST 800-53 R4 | IA-2(13) |
| NIST 800-53 R5 (source) | IA-2(13) |
| NIST 800-53 R5 (NOC) (source) | IA-2(13) |
| NIST 800-63B | 5.1.3 |
US (1)
| Framework | Mapping Values |
|---|---|
| US CJIS Security Policy 5.9.3 (source) | IA-5(1) |
Capability Maturity Model
Level 0 — Not Performed
There is no evidence of a capability to implement Out-of-Band Authentication (OOBA) under specific conditions.
Level 1 — Performed Informally
C|P-CMM1 is N/A, since a structured process is required to implement Out-of-Band Authentication (OOBA) under specific conditions.
Level 2 — Planned & Tracked
C|P-CMM2 is N/A, since a well-defined process is required to implement out-of-Band Authentication (OOBA) under specific conditions.
Level 3 — Well Defined
Identification & Authentication (IAC) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Exist to require that a notice of proofing be delivered through an out-of-band channel to verify the user's address (physical or digital).
- An Identity & Access Management (IAM) function, or similar function, centrally manages permissions and implements “least privileges” Role Based Access Control (RBAC) practices for the management of user, group and system accounts, including privileged accounts.
- The Human Resources (HR) department governs personnel management operations and notifies IAM personnel of personnel role changes for RBAC-based provisioning and deprovisioning actions.
- An IT Asset Management (ITAM) function, or similar function, categorizes endpoint devices according to the data the asset stores, transmits and/ or processes and applies the appropriate technology controls to protect the asset and data that conform to industry-recognized standards for hardening (e.g., DISA STIGs, CIS Benchmarks or OEM security guides).
- An IT infrastructure team, or similar function, ensures that statutory, regulatory and contractual cybersecurity and data privacy obligations are addressed to ensure secure configurations are designed, built and maintained.
- Active Directory (AD), or a similar technology, is used to centrally manage identities and permissions. Only by exception due to a technical or business limitation are solutions authorized to operate a decentralized access control program for systems, applications and services.
Level 4 — Quantitatively Controlled
Identification & Authentication (IAC) efforts are metrics driven and provide sufficient management insight (based on a quantitative understanding of process capabilities) to predict optimal performance, ensure continued operations and identify areas for improvement. In addition to CMM Level 3 criteria, CMM Level 4 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs).
- Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs).
- Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties.
- Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review).
- Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes.
- Both business and technical stakeholders are involved in reviewing and approving proposed changes.
Level 5 — Continuously Improving
See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to implement Out-of-Band Authentication (OOBA) under specific conditions.
Assessment Objectives
- IAC-02.4_A01 out-of-band authentication mechanisms to be implemented are defined.
- IAC-02.4_A02 conditions under which out-of-band authentication is to be implemented are defined.
- IAC-02.4_A03 out-of-band authentication mechanisms are implemented under organization-defined conditions.
Technology Recommendations
Micro/Small
- Secure Baseline Configurations (SBC)
Small
- Secure Baseline Configurations (SBC)
Medium
- Secure Baseline Configurations (SBC)
- Identity & Access Management (IAM) program
Large
- Secure Baseline Configurations (SBC)
- Identity & Access Management (IAM) program
Enterprise
- Secure Baseline Configurations (SBC)
- Identity & Access Management (IAM) program