CrossCheck: Input Validation for WAN Control Systems
summary
CrossCheck validates SDN controller inputs by repairing telemetry via democratic trust propagation and then cross-checking controller topology and demand against the hardened telemetry. Deployed as a four‑week shadow system in a production WAN, it detects the single invalid‑input incident while sustaining 0% false positives. Simulations show 100% detection of demand perturbations of 5% or more and near‑zero false positives even with up to 30% corrupted telemetry, preventing historical outages driven by bad inputs.
AI-written summary · about
chapters (12)
- 0:00CrossCheck and network outages
- 1:23Incorrect inputs in controllers
- 3:29Input-induced outages examples
- 5:13Why input validation is hard
- 6:37Cross-check inputs with telemetry
- 8:03Telemetry redundancy enables corroboration
- 10:13CrossCheck system design
- 12:22Evaluating CrossCheck's effectiveness
- 13:44Detecting buggy inputs
- 15:06Resilience to buggy telemetry
- 16:07Shadow deployment caught bug
- 17:12Conclusion and future
related talks
29mAttacking the Brain: Races in the SDN Control Plane
36mNetwork Machinery: A United-Front for Network Troubleshooting with CRDs
39mHow to cut the cost of continuous cyber compliance
44mHow to Test SDN, or Software‑Defined Networks?
26mInfrastructure as Code for Enterprise: SD-WAN and Zero Trust
48mAbusing Software Defined Networks
23mVeriFlow: Verifying Network-Wide Invariants in Real Time
40mSecurity & Chaos Engineering: Resilient Distributed Systems
