No external authentication for the device CLI
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
Local-only CLI accounts lack central control, multi-factor authentication and an audit trail; NSA recommends RADIUS for users.
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 FMC (or cdFMC): System > Users > External Authentication > add a RADIUS or LDAP object > enable Shell Authentication; Devices > Platform Settings > External Authentication > enable it for the device. Deploy.
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
- On the FTD CLI (read only): show running-config aaa, and confirm an aaa authentication line for SSH.
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
- FTD-MGT-001SSH to the device allowed from any address
- FTD-MGT-002HTTPS management allowed from any address or the outside
- FTD-MGT-003Telnet management enabled
- FTD-MGT-008No login banner
- FTD-MGT-015Management session timeouts too long
- FTD-MGT-016Weak TLS for management or VPN
- FTD-MGT-019Several local CLI users with Config access
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.