Okta Verify authenticator is active and restricts enrollment to FIPS-compliant devices
authenticator_okta_verify_fips_compliant
The Okta Verify authenticator (okta_verify) must be present, in the ACTIVE status, and configured to require FIPS-compliant devices for enrollment (settings.compliance.fips == REQUIRED).
Missing, inactive, and active-but-non-FIPS authenticators surface as distinct FAIL findings so the operator can act on the specific gap.
Risk
Without FIPS-required enrollment, users can authenticate with devices whose cryptographic modules are not FIPS-validated.
- Regulatory exposure under frameworks that mandate FIPS-validated cryptography
- Inconsistent assurance across the user population
- Weak baseline if the authenticator is active but the FIPS flag is
OPTIONALor unset
prowler okta --checks authenticator_okta_verify_fips_compliant
Recommendation
Ensure the Okta Verify authenticator is:
- Present in the org (
key = okta_verify) - In the
ACTIVEstatus - Configured so FIPS Compliance is Required (
settings.compliance.fips == REQUIRED)
If the organization does not require FIPS-validated authenticators, mute the check rather than disabling the FIPS toggle on a partial population.
Remediation
- Sign in to the Okta Admin Console as a Super Admin.
- Navigate to Security > Authenticators.
- Activate the Okta Verify authenticator if it is not already
ACTIVE. - Open the authenticator's settings and set FIPS Compliance to Users enrolling in Okta Verify can use FIPS compliant devices only.
- Save the authenticator.
Source Code
Resource Type
NotDefined