← Back to Baseline

MB-0007

Automated Native Admin MFA provider configuration declared

MB-C02 Admin & Auth Hardening Critical

For a native Admin authentication deployment, Magento_TwoFactorAuth is declared enabled and resolved twofactorauth/general/force_providers names recognized native engines. Possible Adobe IMS mode, unforced providers or an unsupported provider require additional evidence. An empty force_providers setting does not prove MFA is disabled. This predicate does not prove enrollment, enforcement or absence of bypass.

Overview

For a native Admin authentication deployment, Magento_TwoFactorAuth is declared enabled and resolved twofactorauth/general/force_providers names recognized native engines. Possible Adobe IMS mode, unforced providers or an unsupported provider require additional evidence. An empty force_providers setting does not prove MFA is disabled. This predicate does not prove enrollment, enforcement or absence of bypass.

Why it Matters

A compromised Admin account can change code-facing configuration, customer data and payment behavior. MFA can reduce reliance on a password alone when it is actually enforced.

Module/provider declarations are useful deployment evidence, while enrollment, custom authentication and bypass resistance need their own review.

Verification Steps

Manual Verification

  1. Confirm the installed authentication mode.
  2. Check the deployed Magento_TwoFactorAuth declaration and resolve twofactorauth/general/force_providers from locked configuration, database and module defaults.
  3. Verify enrollment and actual login enforcement separately in a controlled account.

Command / Review Sample

php bin/magento module:status Magento_TwoFactorAuth
php bin/magento config:show twofactorauth/general/force_providers

Use the assessed Magento project and the appropriate application or read-only review account. Replace example hosts, paths and identifiers with the assessment scope; configuration and source fragments are illustrative.

Remediation / Fix Guidance

  1. Investigate and change: Identify native Admin authentication versus active Adobe IMS first. For native authentication, enable Magento_TwoFactorAuth and configure supported provider engines; complete enrollment for every administrator and verify recovery/bypass paths. For IMS, retain identity-provider MFA and enrollment evidence.
  2. Validate the change: Test allowed and unenrolled accounts in staging. Empty force_providers means no forced provider list, not proof that MFA is off; module flags alone cannot verify enforcement.
  3. Recheck MB-0007: Read back the effective setting or role/runtime state from the same source used by the check, then test the affected authentication, application or integration flow in staging. A changed file alone does not establish that the production worker uses it.

Examples

Illustrative examples only. Interpret them within the current revision criterion above; missing collection evidence is unresolved, never PASS.

Fail Example

Native authentication has Magento_TwoFactorAuth declared disabled.

Pass Example

Native authentication declares the module enabled and force_providers names a recognized configured engine; login enforcement is reviewed separately.

Scope and Evidence Limits

Rule revision: 4. Target modes: LOCAL.

For a native Admin authentication deployment, Magento_TwoFactorAuth is declared enabled and resolved twofactorauth/general/force_providers names recognized native engines. Possible Adobe IMS mode, unforced providers or an unsupported provider require additional evidence. An empty force_providers setting does not prove MFA is disabled. This predicate does not prove enrollment, enforcement or absence of bypass.

This check covers only the collected observation. Missing collection scope, external controls and runtime behavior require separate evidence.

Catalog coverage describes implementation capability, not a scan outcome. An incomplete manual review cannot establish that the criterion is satisfied.

References