HomeIncident briefing
Back to the library
INCIDENT #076 · SECURITY

The lower half of the client subnet works

Hard25 minutesPro lab

The incident

HTTPS from 10.156.10.1 is allowed but the same service from 10.156.10.200 is denied. Both clients are in the approved /24. Find the source-address boundary in the policy.

Your objective

Restore the documented application transport flows and return reachability. Keep SSH blocked, preserve the working telemetry branch, and do not remove security boundaries or change interface addresses.

The network

Network topology4 devices 3 links

The lower half of the client subnet works — network topologyR1: Client edge. R2: Transit core. R3: Application edge. R4: Telemetry edge. R1 connects to R2. R2 connects to R3. R2 connects to R4. Connections show physical links, not service health.R1 ↔ R2 · 10.156.12.0/30R2 ↔ R3 · 10.156.23.0/30R2 ↔ R4 · 10.156.24.0/30R1Client edgeR1 · Client edge · Starting deviceR2Transit coreR2 · Transit coreR3ApplicationedgeR3 · Application edgeR4Telemetry edgeR4 · Telemetry edge
Physical links · Service health not shown
Link addressing (3)
  • R1 R210.156.12.0/30
  • R2 R310.156.23.0/30
  • R2 R410.156.24.0/30
4 devices · Cisco IOS syntax · Simulated network

What you’ll practice

acl ordermulti service validationacl wildcardssubnet boundaries

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