Information model for Client-Facing Interface to Security Controller
draft-kumar-i2nsf-client-facing-interface-im-02
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-04-30
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
I2NSF Working Group R. Kumar
Internet-Draft A. Lohiya
Intended status: Informational Juniper Networks
Expires: November 1, 2017 D. Qi
Bloomberg
N. Bitar
S. Palislamovic
Nokia
L. Xia
Huawei
April 30, 2017
Information model for Client-Facing Interface to Security Controller
draft-kumar-i2nsf-client-facing-interface-im-02
Abstract
This document defines information model for Client-Facing interface
to Security Controller based on the requirements identified in
[I-D.kumar-i2nsf-client-facing-interface-req]. The information model
defines various managed objects and relationship among these objects
needed to build the interface.
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 November 1, 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
Kumar, et al. Expires November 1, 2017 [Page 1]
Internet-Draft Client Interface Information Model April 2017
(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 . . . . . . . . . . . . . . 3
3. Information Model for Multi Tenancy . . . . . . . . . . . . . 4
3.1. Policy-Domain . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Policy-Tenant . . . . . . . . . . . . . . . . . . . . . . 5
3.3. Policy-Role . . . . . . . . . . . . . . . . . . . . . . . 5
3.4. Policy-User . . . . . . . . . . . . . . . . . . . . . . . 5
3.5. Policy-Management-Authentication-Method . . . . . . . . . 6
4. Information Model for Policy Endpoint Groups . . . . . . . . 6
4.1. Meta-Data-Source . . . . . . . . . . . . . . . . . . . . 7
4.2. User-Group . . . . . . . . . . . . . . . . . . . . . . . 7
4.3. Device-Group . . . . . . . . . . . . . . . . . . . . . . 8
4.4. Application-Group . . . . . . . . . . . . . . . . . . . . 8
4.5. Location-Group . . . . . . . . . . . . . . . . . . . . . 9
5. Information Model for Threat Prevention . . . . . . . . . . . 9
5.1. Threat-Feed . . . . . . . . . . . . . . . . . . . . . . . 9
5.2. Custom-List . . . . . . . . . . . . . . . . . . . . . . . 10
5.3. Malware-Scan-Group . . . . . . . . . . . . . . . . . . . 10
5.4. Event-Map-Group . . . . . . . . . . . . . . . . . . . . . 11
6. Information Model for Telemetry Data . . . . . . . . . . . . 11
6.1. Telemetry-Data . . . . . . . . . . . . . . . . . . . . . 11
6.2. Telemetry-Source . . . . . . . . . . . . . . . . . . . . 12
6.3. Telemetry-Destination . . . . . . . . . . . . . . . . . . 13
7. Information Model for Policy Instance . . . . . . . . . . . . 13
7.1. Policy-Calendar . . . . . . . . . . . . . . . . . . . . . 13
7.2. Policy-Action . . . . . . . . . . . . . . . . . . . . . . 14
7.3. Policy-Rule . . . . . . . . . . . . . . . . . . . . . . . 14
7.4. Policy-Instance . . . . . . . . . . . . . . . . . . . . . 15
Show full document text