HomeIncident briefing
Back to the library
INCIDENT #047 · SECURITY

The payment gateway lockout

Medium25 minutesPro lab

The incident

Houston payments network. Five metro routers provide two directions around the region before the service handoff. A client at .10 can use the primary service, but a client at .200 in the same subnet cannot. Both clients can reach the monitoring destination. Investigate the two service networks from R1: 10.206.224.0/24 to 10.206.234.0/24 (TCP/443), and 10.206.225.0/24 to 10.206.235.0/24 (TCP/8443).

Your objective

Restore both authorized service transports and return reachability, including clients and service hosts in both halves of the primary subnet. Keep R2 blocked from both service transports, keep SSH blocked to both service subnets, and preserve monitoring between R1 and R4. Do not change physical topology or addressing. These are network forwarding checks, not application-level transactions.

The network

Network topology6 devices 6 links

The payment gateway lockout — network topologyR1: Client metro. R2: North metro. R3: Northeast metro. R4: South metro. R5: Service metro. R6: Service gateway. R1 connects to R2. R2 connects to R3. R3 connects to R5. R5 connects to R4. R4 connects to R1. R5 connects to R6. Connections show physical links, not service health.R1 ↔ R2 · 10.206.240.0/30R2 ↔ R3 · 10.206.241.0/30R3 ↔ R5 · 10.206.242.0/30R5 ↔ R4 · 10.206.243.0/30R4 ↔ R1 · 10.206.244.0/30R5 ↔ R6 · 10.206.245.0/30R1Client metroR1 · Client metro · Starting deviceR2North metroR2 · North metroR3NortheastmetroR3 · Northeast metroR4South metroR4 · South metroR5Service metroR5 · Service metroR6ServicegatewayR6 · Service gateway
Physical links · Service health not shown
6 devices · Cisco IOS syntax · Simulated network

What you’ll practice

acl wildcardssource matchingsubnet boundaries

Interview exercises are inspired by common industry competencies. They are not proprietary interview questions.