Traffic analysis on the municipal guest VLAN shows scanning probes toward staff subnets that policy says must remain isolated. What does this monitoring result indicate?
Select an answer to reveal the explanation.
Short Explanation
Guests poking at staff subnets means the velvet rope fell down—isolation failed. Your traffic monitor just detected a policy break that attackers would love. Celebrate only after the wall is rebuilt, not while scans cross the line.
Full Explanation
Traffic analysis on the municipal guest VLAN showing scanning probes toward staff subnets that policy says must remain isolated indicates a guest isolation or segmentation policy failure that detection should escalate for remediation. Guest clients should not be able to probe staff address space; observed scanning means ACLs, PVLANs, firewall rules, or WLAN roles are insufficient or broken. Successful microsegmentation with no further action required contradicts the observed probes. Claiming OWE alone guarantees Layer-3 reachability control into staff VLANs confuses link encryption with segmentation. Normal CAPWAP keepalives misclassified as guest-to-staff attacks would not present as guest VLAN scanning toward staff subnets. Civic guest networks adjacent to staff and payment systems make isolation failures high-priority detections. Exam caveat: encryption of guest air traffic does not replace Layer-2/Layer-3 isolation from staff networks. Operational check: reproduce guest-to-staff reachability in a controlled test, remediate role/ACL/firewall rules, retest until probes fail, monitor continuously for recurrence, and notify stakeholders if staff subnets were exposed during the failure window.