Citizen traffic to a municipal app drops after a new cloud security appliance is inserted in path. Packet captures show arrivals at the appliance but not egress toward the app. What is the most likely cause?
Select an answer to reveal the explanation.
Short Explanation
Packets walk into the appliance and never walk out—classic wrong map or wrong allow list on the box itself. Check its routes and ACLs before ripping into the app code.
Full Explanation
When a mid-path security appliance receives packets but does not forward them, common causes are incorrect next-hop routes, deny ACLs/firewall rules, or policy-based forwarding mistakes on that device. Application CORS, CI base images, and replica lag do not explain in-path packet drops observed at the appliance boundary.