1 / 8

Operational Requirements for Secured BGP

Explore the operational requirements and challenges of Secured BGP deployment, costs involved, policy complexities, and phased implementation strategies. Learn why security solutions must evolve despite potential limitations.

leena
Télécharger la présentation

Operational Requirements for Secured BGP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Steven M. Bellovin, Columbia University John Ioannidis, Columbia University Randy Bush, IIJ Operational Requirementsfor Secured BGP

  2. Metagoal • Must support today's uses of BGP • Must support all legal policies • May require minor changes to how such policies are carried out, but it's better if no changes are required, especially downstream

  3. Objections • New failure modes • Cost • Capital and operational • Dirty data • Applies to any possible solution • Some ISPs won't publish policies • Phased deployment

  4. New Failure Modes • Yes – there are new ways to lose connectivity • Secured BGP is designed to reject some routes; mistakes or buggy software can trigger this • Of course, routing misconfigurations and attacks can cause loss of connectivity, too – remember AS 7007?

  5. Cost • Capital costs • Some initial outlay; Moore's Law will help • Operational expenses • ISPs and RIRs must run CAs • Big problem is likely to be customer care • Who pays? What's the incentive? • Database cleanup • RIRs have already been working on this • Good area for government funding

  6. Policies • Policies are hard to intuit • Some proposed solutions require knowledge of policies; some ISPs won't publish them • Only solutions are to find a security solution that doesn't require that, or to persuade the ISPs that they're wrong • The latter hasn't worked well in the past

  7. Phased Deployment • Can't deploy everywhere at once, even within an ISP • Should give preference to solutions that work well in a phased deployment scenario • Add tuning knobs for “security radius”? • Must have mechanism for authoritative determination of whether or not an advertisement should have been signed

  8. Security Warning • We don't have to have perfect security • However... it doesn't make sense to go to great effort to deploy a solution that the attackers can bypass • Critical routers have been compromised in the past; there's no reason to think that can't happen again

More Related