Skip to main content

IAC-17: Biometric Authentication

IAC 5 — Medium Protect

Mechanisms exist to ensure biometric-based authentication satisfies organization-defined biometric quality requirements for false positives and false negatives.

Renumbered: Formerly IAC-10.12 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, IAC-17 was Periodic Review of Account Privileges. That control is now IAC-12.

Control Question: Does the organization ensure biometric-based authentication satisfies organization-defined biometric quality requirements for false positives and false negatives?

General (3)
Framework Mapping Values
NIST 800-53 R4 IA-5(12)
NIST 800-53 R5.2 IA-05(12)
NIST 800-82 R3 IA-05(12)
US (2)
Framework Mapping Values
USA Federal DoD Zero Trust Execution Roadmap v1.1 1.9.2 1.9.3
USA Federal IRS 1075 2021 IA-5(CE-12)
APAC (1)
Framework Mapping Values
APAC Malaysia RMiT 2025 A3-2(b) A11-2(f)

Capability Maturity Model

Level 0 — Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 — Performed Informally

Identification & Authentication (IAC) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with IAC domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Identity & Access Management (IAM)-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ IAM controls are primarily administrative in nature (e.g., policies & standards) to manage accounts and permissions. ▪ IT and/or cybersecurity personnel identify and implement IAM cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements.

Level 2 — Planned & Tracked

SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts).

Level 3 — Well Defined

Identification & Authentication (IAC) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with IAC domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with IAC domain capabilities are well-documented and kept current by process owners. ▪ An Identity & Access Management (IAM) team, or similar function, is appropriately staffed and supported to implement and maintain IAC domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of IAM operations (e.g., directory services, Authenticate, Authorize and Audit (AAA) solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with IAC domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to ensure biometric-based authentication satisfies organization-defined biometric quality requirements for false positives and false negatives.

Level 4 — Quantitatively Controlled

Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.

Level 5 — Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

Assessment Objectives

  1. IAC-17_A01 biometric quality requirements for biometric-based authentication are defined.
  2. IAC-17_A02 mechanisms that satisfy organization-defined biometric quality requirements are employed for biometric-based authentication.

Evidence Requirements

E-IAC-13 Authenticator Types

Documented evidence of system authenticator types.

Identity & Access Management

Technology Recommendations

Micro/Small

  • Use fingerprint/face recognition on personal devices where available

Small

  • Biometric authentication policy for approved use cases

Medium

  • Formal biometric authentication policy
  • Approved biometric use cases and controls

Large

  • Enterprise biometric authentication deployment
  • Privacy and data protection controls for biometrics

Enterprise

  • Enterprise biometric authentication platform
  • Privacy-compliant biometric data handling
  • Fallback authentication mechanisms
  • BIPA/GDPR compliance

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.