Weak pre-shared key
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
A weak key can be guessed offline from one captured handshake, giving the attacker the network and its traffic.
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: Wireless > Access control > select the SSID > Password: a random key of 20 characters or more; consider 802.1X or identity PSK instead of one shared key.
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
- Confirm the new key's length in the Dashboard; the Collector measures it again at the next collection without exporting it.
Limits
- Judged from the Collector's measurements of the key (length, character classes, a common-password match), never from the key itself. An SSID without measurements is counted as not read.
Compliance references
No benchmark recommendation is mapped to this control in this version.
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.