Requirements for Client-Facing Interface to Security Controller
draft-ietf-i2nsf-client-facing-interface-req-03

Document Type Active Internet-Draft (i2nsf WG)
Last updated 2017-07-16
Replaces draft-kumar-i2nsf-client-facing-interface-req
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document (wg milestone: Jun 2016 - Adopt requirements f... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
I2NSF Working Group                                             R. Kumar
Internet-Draft                                                 A. Lohiya
Intended status: Informational                          Juniper Networks
Expires: January 17, 2018                                          D. Qi
                                                               Bloomberg
                                                                N. Bitar
                                                         S. Palislamovic
                                                                   Nokia
                                                                  L. Xia
                                                                  Huawei
                                                           July 16, 2017

    Requirements for Client-Facing Interface to Security Controller
            draft-ietf-i2nsf-client-facing-interface-req-03

Abstract

   This document captures requirements for Client-Facing interface to
   the Security Controller as defined by [I-D.ietf-i2nsf-framework].
   The interface is expressed using objects and constructs understood by
   Security Admin as opposed to vendor or device specific expressions
   associated with individual product and feature.  This document
   identifies a broad set of requirements needed to express Security
   Policies based on User-constructs which are well understood by the
   User Community.  This gives ability to decouple policy definition
   from policy enforcement on a specific security functional element, be
   it a physical or virtual.

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 January 17, 2018.

Kumar, et al.           Expires January 17, 2018                [Page 1]
Internet-Draft        Client Interface Requirements            July 2017

Copyright Notice

   Copyright (c) 2017 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
   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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions Used in this Document . . . . . . . . . . . . . .   4
   3.  Guiding principle for Client-Facing Interface definition  . .   5
     3.1.  User-construct based modeling . . . . . . . . . . . . . .   5
     3.2.  Basic rules for Client-Facing Interface definition  . . .   6
     3.3.  Deployment Models for Implementing Security Policies  . .   7
   4.  Functional Requirements for the Client-Facing Interface . . .  10
     4.1.  Requirement for Multi-Tenancy in Client-Facing interface   11
     4.2.  Requirement for Authentication and Authorization of
           Client-Facing interface . . . . . . . . . . . . . . . . .  12
     4.3.  Requirement for Role-Based Access Control (RBAC) in
           Client-Facing interface . . . . . . . . . . . . . . . . .  12
     4.4.  Requirement to protect Client-Facing interface from
           attacks . . . . . . . . . . . . . . . . . . . . . . . . .  13
     4.5.  Requirement to protect Client-Facing interface from
           misconfiguration  . . . . . . . . . . . . . . . . . . . .  13
     4.6.  Requirement to manage policy lifecycle with rich set of
           controls  . . . . . . . . . . . . . . . . . . . . . . . .  13
     4.7.  Requirement to define dynamic Policy Endpoint Group . . .  14
     4.8.  Requirement to express rich set of Policy Rules . . . . .  16
     4.9.  Requirement to express rich set of Policy Actions . . . .  17
     4.10. Requirement for consistent policy enforcement . . . . . .  19
     4.11. Requirement to detect and correct policy conflicts  . . .  19
     4.12. Requirement for backward compatibility  . . . . . . . . .  19
Show full document text