Re: [sidr] Route Leaks and BGP Security

Shane Amante <shane@castlepoint.net> Mon, 21 November 2011 23:08 UTC

Return-Path: <shane@castlepoint.net>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B29F11E8128 for <sidr@ietfa.amsl.com>; Mon, 21 Nov 2011 15:08:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.947
X-Spam-Level:
X-Spam-Status: No, score=-1.947 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, J_CHICKENPOX_22=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ML4evbB51USX for <sidr@ietfa.amsl.com>; Mon, 21 Nov 2011 15:08:55 -0800 (PST)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by ietfa.amsl.com (Postfix) with ESMTP id 6561111E80D5 for <sidr@ietf.org>; Mon, 21 Nov 2011 15:08:55 -0800 (PST)
Received: by dog.tcb.net (Postfix, from userid 0) id D446F268063; Mon, 21 Nov 2011 16:08:54 -0700 (MST)
Received: from host2.tcb.net (64.78.235.218 [64.78.235.218]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Mon, 21 Nov 2011 16:08:54 -0700 (MST) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.235.218; client-port=63039; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <CAL9jLaZvCe2U6Y=BbZxsfF+BDOqQuV18Ac6N_6Fxxc=Cpms1jg@mail.gmail.com>
Date: Mon, 21 Nov 2011 16:08:53 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D344AD5-B101-4BC1-8522-2259DB9853E4@castlepoint.net>
References: <20111117040124.18551.47190.idtracker@ietfa.amsl.com> <0863194F-7564-40A9-BB73-ABF8BB97C3AB@tcb.net> <CAL9jLaZvCe2U6Y=BbZxsfF+BDOqQuV18Ac6N_6Fxxc=Cpms1jg@mail.gmail.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] Route Leaks and BGP Security
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2011 23:08:56 -0000

Hi Chris,

On Nov 20, 2011, at 10:35 PM, Christopher Morrow wrote:
> On Wed, Nov 16, 2011 at 11:23 PM, Danny McPherson <danny@tcb.net> wrote:
>> 
>> Team,
>> I've updated this draft based on some feedback received already.  Given
>> the discussion at the WG session, and the list discussion as of late, I'd like
>> to ask that it become a WG item and used to inform the BGP Threat Model
>> document -- particularly with regards to what's an acceptable residual risk and
>> what is not.  Once that's comprehensive it can be used to inform secure routing
>> requirements documents in the working group, and then we can begin assessing
>> the feasibility of reducing various risks.
> 
> "The authors believe the capability to prevent leaks should be a	
> first-order engineering objective in any secure routing architecture."
> 
> So, in the simple scenario laid out, the customer is filtered by the
> isp's, no? and the filter data is built with something like:  take irr
> data, meld with rpki data, create filter-lists.
> 
> The rpki data gives the isps an ability to filter the customer
> announcements, which would stop the leaks. Is the thing you really
> want to outline in a draft the process to link the
> resource-certification data with the existing IRR data and create
> better prefix/as-path filters?

As the -01 draft states:
---snip---
  Discussion of out of band methods to mitigate this attack are beyond
  the scope of this document, as it's objective is to inform routing
  protocol design choices currently being considered within the IETF's
  SIDR Working Group.
---snip---


> I think one item that was asked for on the list (or perhaps in the
> meeting) was: How can you know a route you see is a leak?
> 
> Taken another way, in the case of your example:
> 
> victim - isp2 - attacker - isp1
> 
> how is the victim to know that this path isn't proper?
> what in the update says that?

That's the point.  :-)  At present, nothing being "secured" in the UPDATE, (specifically AS_PATH wrt BGPSec), will tell you that the UPDATE was sent through a legitimate control-plane path vs. an illegitimate control-plane path.

In today's networks, the means to control the propagation of a particular BGP route are through configuration of 'policy' locally on routers, (ASBR's/PE's), that look for a combination of /one or more/ _BGP_attributes_ in the BGP route itself to limit its propagation.  As one specific example, an operator of an AS typically configures their ingress ASBR's to assign a specific standard BGP community that says something like:
- this is a customer route;
- this is a peer route
(I would note that these BGP standard communities are 'local' to and only have meaning within the operator of their particular AS.  An operator should NOT or would NOT "trust" third-parties, e.g.: their customers or peers, to set and send these communities to them for lots of obvious reasons).

When a BGP route travels to that operator's egress ASBR's, the egress ASBR then has a locally configured policy that looks for the locally significant BGP community string that says: "this is a customer route", in which case the route is sent out of both peer & customer eBGP sessions.  OTOH, if the eBGP policy at the egress ASBR determines, based on the locally significant BGP community string assigned to a BGP route, "this is a peer route", the action in that locally configured policy at peer eBGP sessions is to drop (not announce outbound) that particular UPDATE; whereas, the action at customer eBGP sessions is to announce that UPDATE outbound.

Locally significant BGP communities + locally configured policy are just one method that could be used, but likely the most widely used.  Depending on the size of one's network other BGP Attributes + locally configured policy may be used.


> is there other data that could be used (outside of bgp) to tell the
> victim that the path is improper?

IMHO, and as I think Russ has pointed out, BGP was only (?) designed to express reachability, not to carry or forward _policy_.  At present, nothing in the BGP protocol disseminates _policy_[1].  Instead, policy to control propagation of BGP routing information is only known to routers via out-of-band configuration (through CLI or NETCONF), either manually or through automated methods.

-shane

[1] The only minor exception I can think of to this is the well-known NO_EXPORT or NO_ADVERTISE BGP communities.  However, those have an extremely limited scope -- specifically, both communities are only exchanged between _directly_ connected adjacent ASN's.  I would add that since BGPSec does not make any attempt to sign the BGP community Attribute, it follows that even in this most limited case BGPSec is not able to certify (authenticate?) that a given BGP route *should* or *should not* be propagated to AS'es 2+ hops away.  What if one stripped the NO_EXPORT or NO_ADVERTISE community off and re-announced that BGP route -- is that not considered a MiTM attack, just as bad (or, worse?) as fraudulently inserting one's self into the AS_PATH?