Customer prefix 203.0.113.0/22 announced from unintended AS — suspected BGP route leak
A hard Network Engineering scenario on BGP Leak.
Start a graded attempt against this scenario. Your response is scored by the same deterministic rubric used across the catalog. Email and evidence content stay hidden until you start.
Launches this exact scenario. One of 3 templates in this Track + Difficulty pool.
catalog id · network-bgp-route-leak
What this scenario practices, mapped to recognized frameworks.
Educational mapping only. Not a compliance attestation.
- BGP path-change triage
- Coordinated peer-rollback discipline
- Data Manipulation · ImpactT1565 · TA0040PartialLow confidence
Trains defensive reasoning when a routing change has external impact.
- Network Traffic AnalysisD3-NTAMappedMedium confidence
Trains the traffic-visibility posture for path-change diagnosis.
- Protective Technology · ProtectPR.PT · PRMappedHigh confidence
Trains the protective-technology baseline behind BGP policy.
- Continuous Monitoring · DetectDE.CM · DEMappedHigh confidence
Trains the monitoring discipline for routing telemetry.
- IR lifecycle phaseDetection & AnalysisMappedHigh confidence
Trains structured triage of unexpected BGP path changes.
- IR lifecycle phaseContainment, Eradication & RecoveryMappedMedium confidence
Trains coordinated peer-level rollback and containment.
- Document Network Topology2.MMappedHigh confidence
Trains the topology baseline.
- Detecting Relevant Threats and TTPs3.AMappedMedium confidence
Trains the routing-anomaly detection baseline.
- Network Infrastructure ManagementControl 12MappedHigh confidence
Trains the network-management control.
- Network Monitoring and DefenseControl 13MappedMedium confidence
Trains the monitoring discipline behind routing review.