A municipal wireless report recommends replacing PEAP-MSCHAPv2 on the county staff SSID with EAP-TLS and enforcing certificate validation. What makes that remediation high quality for Enterprise Wi-Fi risk?
Select an answer to reveal the explanation.
Short Explanation
PEAP-MSCHAPv2 is the soft underbelly of many Enterprise SSIDs—password-ish and trust-tricky. Jumping to EAP-TLS with real cert checks puts hard credentials and validated trust in play. Cleaning SSID cosmetics or sliding back to PSK is not remediation.
Full Explanation
PEAP with MSCHAPv2 remains a frequent Enterprise Wi-Fi risk class because weak password hygiene and user acceptance of untrusted certificates enable credential-oriented attack surfaces. Remediation that upgrades to EAP-TLS (or other strong certificate-based EAP profiles) and enforces proper server-certificate validation materially reduces those risks. Cosmetic SSID changes, downgrading guests to obsolete crypto, or collapsing Enterprise into a lobby PSK do not address the underlying authentication weakness.