Download
1 / 6
60 likes | 79 Views
This working group focuses on developing a framework for secure BGP deployment to address vulnerabilities and improve routing integrity on the global Internet. Recommendations aim to incentivize ISP adoption of secure protocols. Participants document threats, incidents, and solutions, evaluating technical maturity, costs, and security benefits. Ongoing work involves comparing solutions, encouraging incremental deployment, and quantifying security incidents and effectiveness. Project timeline includes milestones for implementing secure routing practices and performance metrics.
E N D
Working Group 6: Secure BGP Deployment December 16, 2011 Andy Ogielski, Renesys Jennifer Rexford, Princeton U. WG 6 Co-Chairs Communications Security, Reliability and Interoperability Council CSR C
Working Group 6: Secure BGP Deployment • Short Description: The Border Gateway Protocol (BGP) controls inter-domain packet traffic routing on the entire global Internet. BGP relies on trust among operators of gateway routers to ensure the integrity of the Internet routing infrastructure. Over the years, this trust has been compromised on a number of occasions, revealing fundamental weaknesses of this critical infrastructure. This Working Group willrecommend the framework for industry regarding incremental adoption of secure routingprocedures and protocols based on existing work in industry and research. The framework will include specific technical procedures and protocols. The framework will be proposed in a way suitable for opt-inby large Internet Service Providers (ISPs) in order to create incentives for a wider scale, incremental ISP deployment of secure BGP protocols and practices in a market-driven, cost-effective manner. • Duration: August 2011 – March 2013 Communications Security, Reliability and Interoperability Council CSR C
Working Group 6 – Participants Communications Security, Reliability and Interoperability Council CSR C
Working Group 6 - Work Completed • Documenting known threats • Real BGP security incidents, and known vulnerabilities • Identifying suite of BGP security solutions • Current best common practices (i.e., local filters) • Anomaly detection to flag and avoid suspicious routes • Global database of certified origins, with conventional configuration • Cache-to-router origin certification protocol to push filters • Cryptographic validation of the entire route (e.g., S-BGP) • Identifying dimensions for comparing solutions • Technical maturity, and cost to deploy and operate • Security benefits, and new attack surfaces • Feasibility of incremental deployment • Impact on autonomy of networks and nations
Working Group 6 – Ongoing Work Activity • Comparing the BGP security solutions • Analyzing each solution across all dimensions • Comparing with the other proposed solutions • Identifying ways to encourage incremental deployment • Identifying important usage scenarios • Number of BGP-speaking routers • Structure within and between networks • Frequency of BGP routing changes • Designing experimental methodology • Measurement infrastructure (e.g., RouteViews, Renesys) • Quantifying extent/scope of security incidents • Quantifying effectiveness of partial deployments • Safe active experiments with participating networks
Working Group 6 - Project Timeline • WG regular meetings • 1st and 3rd Tuesdays of each month • Soon, smaller groups on major sub-topics • WG Final Recommendations: March 2013 • Intermediate Milestones (Preliminary): • Secure Routing Implementation Practices – March 8, 2012 • Secure Routing Performance Metrics – September 12, 2012 • Secure Routing Performance Metrics – December 5, 2012
