Two-factor authentication not enforced for the organization
At a glance
Base severity
Area
Platform
Evidence level
Benchmark reference
Reads the export, not the device
ConfigProof reads a configuration export. This control is evaluated against the objects in that file, and it reports what the file says. It does not connect to the device and sees no traffic, so a finding here describes the configuration, not what the firewall is doing right now.
Why it matters
An administrator whose password is phished or reused elsewhere can be impersonated, giving full control of every network in the organization.
How to fix it
Web interface
The steps below are written for the web interface. A finding raised on your own export carries the same steps with your object names filled in.
- In the Meraki Dashboard: Organization > Settings > Security > Two-factor authentication: Force users to set up and use two-factor authentication.
Command line
This analyzer version writes no command text for this control. The steps above are the remediation it offers.
How to confirm the fix
- In the Meraki Dashboard: Organization > Settings > Security shows two-factor authentication enforced.
Limits
- No limitation is recorded for this control beyond the one that applies to all of them: it reads a configuration export.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Administrators and Access
- MX-MGT-001Appliance management reachable from any address
- MX-MGT-002Local status page without authentication
- MRK-MGT-002Full administrator without two-factor authentication
- MRK-MGT-003Many full organization administrators
- MRK-MGT-004Administrator inactive for a long time
- MRK-MGT-005API keys usable from any address
- MRK-MGT-006Account lockout not enforced
- MRK-MGT-007Dashboard sign-in not limited by address
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.