Information Model for Consumer-Facing Interface to Security Controller
draft-kumar-i2nsf-client-facing-interface-im-07

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

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07

I2NSF Working Group                                             R. Kumar
Internet-Draft                                                 A. Lohiya
Intended status: Informational                          Juniper Networks
Expires: January 18, 2019                                          D. Qi
                                                               Bloomberg
                                                                N. Bitar
                                                         S. Palislamovic
                                                                   Nokia
                                                                  L. Xia
                                                                  Huawei
                                                                J. Jeong
                                                 Sungkyunkwan University
                                                           July 17, 2018

 Information Model for Consumer-Facing Interface to Security Controller
            draft-kumar-i2nsf-client-facing-interface-im-07

Abstract

   This document defines an information model for Consumer-Facing
   interface to Security Controller based on the requirements identified
   in [I-D.ietf-i2nsf-client-facing-interface-req].  The information
   model defines various managed objects and relationship among these
   objects needed to build the interface.  The information model is
   organized based on the "Event-Condition-Event" (ECA) policy model
   defined by a capability information model for Interface to Network
   Security Functions (I2NSF) [I-D.ietf-i2nsf-capability].

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 https://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 18, 2019.

Kumar, et al.           Expires January 18, 2019                [Page 1]
Internet-Draft Consumer-Facing Interface Information Model     July 2018

Copyright Notice

   Copyright (c) 2018 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
   (https://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 the Document  . . . . . . . . . . . . . .   5
   3.  Information Model for Policy  . . . . . . . . . . . . . . . .   5
     3.1.  Event Sub-Model . . . . . . . . . . . . . . . . . . . . .   7
       3.1.1.  Event-Map-Group . . . . . . . . . . . . . . . . . . .   8
     3.2.  Condition Sub-Model . . . . . . . . . . . . . . . . . . .   8
     3.3.  Action Sub-Model  . . . . . . . . . . . . . . . . . . . .  10
   4.  Information Model for Multi-Tenancy . . . . . . . . . . . . .  10
     4.1.  Policy-Domain . . . . . . . . . . . . . . . . . . . . . .  11
     4.2.  Policy-Tenant . . . . . . . . . . . . . . . . . . . . . .  12
     4.3.  Policy-Role . . . . . . . . . . . . . . . . . . . . . . .  12
     4.4.  Policy-User . . . . . . . . . . . . . . . . . . . . . . .  12
     4.5.  Policy Management Authentication Method . . . . . . . . .  13
   5.  Information Model for Policy Endpoint Groups  . . . . . . . .  14
     5.1.  Tag-Source  . . . . . . . . . . . . . . . . . . . . . . .  14
     5.2.  User-Group  . . . . . . . . . . . . . . . . . . . . . . .  15
     5.3.  Device-Group  . . . . . . . . . . . . . . . . . . . . . .  15
     5.4.  Application-Group . . . . . . . . . . . . . . . . . . . .  16
     5.5.  Location-Group  . . . . . . . . . . . . . . . . . . . . .  16
   6.  Information Model for Threat Prevention . . . . . . . . . . .  17
     6.1.  Threat-Feed . . . . . . . . . . . . . . . . . . . . . . .  17
     6.2.  Custom-List . . . . . . . . . . . . . . . . . . . . . . .  18
     6.3.  Malware-Scan-Group  . . . . . . . . . . . . . . . . . . .  18
   7.  Information Model for Telemetry Data  . . . . . . . . . . . .  18
     7.1.  Telemetry-Data  . . . . . . . . . . . . . . . . . . . . .  19