SFC environment Security requirements
draft-mglt-sfc-security-environment-req-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02

SFC Working Group                                        D. Migault, Ed.
Internet-Draft                                                  Ericsson
Intended status: Informational                              C. Pignataro
Expires: April 21, 2016                                         T. Reddy
                                                                   Cisco
                                                               C. Inacio
                                                            CERT/SEI/CMU
                                                        October 19, 2015

                 SFC environment Security requirements
             draft-mglt-sfc-security-environment-req-00.txt

Abstract

   This document provides environment security requirements for the SFC
   architecture.  Environment security requirements are independent of
   the protocols used for SFC - such as NSH for example.  As a result,
   the requirements provided in this document are intended to provide
   good security practices so SFC can be securely deployed and operated.
   These security requirements are designated as environment security
   requirements as opposed to the protocol security requirements.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 21, 2016.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of

Migault, et al.          Expires April 21, 2016                 [Page 1]
Internet-Draft    SFC environment Security requirements     October 2015

   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Requirements notation . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Terminology and Acronyms  . . . . . . . . . . . . . . . . . .   3
   4.  SFC Environment Overview  . . . . . . . . . . . . . . . . . .   3
   5.  Threat Analysis . . . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Attacks performed from the SFC Control Plane  . . . . . .   5
     5.2.  Attacks performed from the SFC Management Plane . . . . .   5
     5.3.  Attacks performed from the Tenant's Users Plane . . . . .   6
     5.4.  Attacks performed from the SFC Data Plane . . . . . . . .   8
   6.  Plane Isolation Requirements  . . . . . . . . . . . . . . . .  11
     6.1.  SFC Control Plane Isolation . . . . . . . . . . . . . . .  12
     6.2.  SFC Management Plane Isolation  . . . . . . . . . . . . .  12
     6.3.  Tenant's Users Data Plane Isolation . . . . . . . . . . .  13
   7.  SFC Data Plane Requirements . . . . . . . . . . . . . . . . .  13
   8.  Additional Requirements . . . . . . . . . . . . . . . . . . .  15
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   10. Privacy Considerations  . . . . . . . . . . . . . . . . . . .  15
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  15
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     13.2.  Informative References . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Requirements notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Introduction

   This document provides environment security requirements for the SFC
   architecture [I-D.ietf-sfc-architecture].  Environment security
   requirements are independent of the protocols used for SFC - such as
   NSH [I-D.ietf-sfc-nsh].  As a result, the requirements provided in