--- 1/draft-ietf-i2nsf-terminology-04.txt 2018-01-03 08:13:27.322289524 -0800 +++ 2/draft-ietf-i2nsf-terminology-05.txt 2018-01-03 08:13:27.614296465 -0800 @@ -1,23 +1,23 @@ I2NSF S. Hares Internet-Draft J. Strassner Intended status: Informational Huawei -Expires: January 07, 2018 D. Lopez +Expires: July 06, 2018 D. Lopez Telefonica I+D L. Xia Huawei H. Birkholz Fraunhofer SIT - July 03, 2017 + January 03, 2018 Interface to Network Security Functions (I2NSF) Terminology - draft-ietf-i2nsf-terminology-04.txt + draft-ietf-i2nsf-terminology-05.txt Abstract This document defines a set of terms that are used for the Interface to Network Security Functions (I2NSF) effort. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. @@ -26,25 +26,25 @@ 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 07, 2018. + This Internet-Draft will expire on July 06, 2018. Copyright Notice - Copyright (c) 2017 IETF Trust and the persons identified as the + 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 (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 @@ -59,22 +59,22 @@ 5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 6.1. Informative References . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 1. Introduction This document defines the terminology for the Interface to Network Security Functions (I2NSF) effort. This section provides some background on I2NSF; a detailed problem statement can be found in - [I-D.ietf-i2nsf-problem-and-use-cases]. Motivation and comparison to - previous work can be found in [I-D.ietf-i2nsf-gap-analysis]. + [RFC8192]. Motivation and comparison to previous work can be found + in [I-D.ietf-i2nsf-gap-analysis]. Enterprises are now considering using network security functions (NSFs) hosted by service providers due to the growing challenges and complexity in maintaining an up-to-date secure infrastructure that complies with regulatory requirements, while controlling costs. The hosted security service is especially attractive to small- and medium-size enterprises who suffer from a lack of security experts to continuously monitor, acquire new skills and propose immediate mitigations to ever increasing sets of security attacks. Small- and medium-sized businesses (SMBs) are increasingly adopting cloud-based @@ -161,56 +161,56 @@ Bespoke: Something made to fit a particular person, customer, or company. Bespoke security management: Security management systems that are made to fit a particular customer. Boolean Clause: A logical statement that evaluates to either TRUE or FALSE. Also called Boolean Expression. Capability: A set of features that are available from an I2NSF - Component. These functions may, but do not have to, be used. All + Component. These features may, but do not have to, be used. All Capabilities are announced using the I2NSF Registration - Interface. + Interface. Capabilities are a type of I2NSF Metadata. Component: An encapsulation of software that communicates using Interfaces. A Component may be implemented by hardware and/or software, and be represented using a set of classes. In general, a Component encapsulates a set of data structures and a set of algorithms that implement the function(s) that it provides. Constraint: A Constraint is a limitation or restriction. Constraints may be associated with any type of object (e.g., Events, Conditions, and Actions in Policy Rules). Constraint Programming: A type of programming that uses constraints to define relations between variables in order to find a - feasible (and not necessarily optimal) solution. + feasible (but not necessarily optimal) solution. Context: The Context of an Entity is a collection of measured and/ or inferred knowledge that describe the state and the environment in which an Entity exists or has existed. (from http://www.ietf.org/mail-archive/web/i2nsf/current/msg00762.html). Controller: A Controller is a management Component that contains control plane functions to manage and facilitate information - sharing, as well as execute security functions. This definition - is based on that in [I-D.ietf-sacm-terminology]. + sharing. An I2NSF COntroller may also execute security functions. + This definition is based on that in [I-D.ietf-sacm-terminology]. Control Plane: In the context of I2NSF, the Control Plane is an architectural Component that provides common control functions to all I2NSF Components, including some or all of the following: authentication, authorization, accounting, auditing, and Capability discovery and negotiation. The Control Plane orchestrates the operation of the Data Plane according to guidance and/or input from the Management Plane. I2NSF Components - with Interfaces to the Control Plane have knowledge of the + with Interfaces to the Control Plane may have knowledge of the Capabilities of other I2NSF Components within a particular I2NSF administrative domain. This definition is based on that in [I-D.ietf-sacm-terminology]. See also: Data Plane, Management Plane. Customer: A business role of an entity that is involved in the definition and/or consumption of services, and the possible negotiation of a contract to use services from a Provider. Data Center (DC): A facility used to house data processing and @@ -222,21 +222,21 @@ Data Integrity: Defined in [RFC4949] as "the property that data has not been changed, destroyed, or lost in an unauthorized or accidental manner." Data Model: A representation of concepts of interest to an environment in a form that is dependent on data repository, data definition language, query language, implementation language, and protocol (typically one or more of these ). Note the difference between a data **model** and a data **structure**. - [I-D.ietf-supa-generic-policy-data-model]. + See also: Information Model. Data Plane: In the context of I2NSF, the Data Plane is an architectural Component that provides operational functions to enable an I2NSF Component to provide and consume packets and flows. See also: Control Plane, Management Plane. Data Provenance: A historical record of the sources, origins and evolution of data that is influenced by inputs, entities, functions and processes. @@ -278,22 +278,21 @@ I2NSF Action: An I2NSF Action is used to control and monitor aspects of flow-based NSFs. An I2NSF Action, when used in the context of an (imperative) I2NSF Policy Rule, may be executed only when the Event and the Condition clauses of its owning I2NSF Policy Rule evaluate to true. The execution of this I2NSF Action may be influenced by applicable metadata. Examples of I2NSF Actions include providing intrusion detection and/or protection, web and flow filtering, and deep packet inspection for packets and flows. - (based on [I-D.ietf-supa-generic-policy-info-model]). See also - I2NSF Condition, I2NSF Event, I2NSF Policy Rule. + See also: I2NSF Condition, I2NSF Event, I2NSF Policy Rule. I2NSF Agent: A software Component that implements an NSF. It typically plays the roles of I2NSF Consumer and I2NSF Producer. For example, it can receive provisioning information and requests for operational and/or monitoring data from an I2NSF Component, and can provide these and other data to I2NSF Consumers. It can also receive I2NSF Policy Rules to change the configuration of one or more network devices, optionally transform each I2NSF Policy Rule into an alternate form (e.g., one that is directly consummable by the network device), and then execute the I2NSF @@ -306,148 +305,148 @@ I2NSF Condition: An I2NSF Condition is defined as a set of attributes, features, and/or values that are to be compared with a set of known attributes, features, and/or values in order to determine whether or not the set of Actions in that (imperative) I2NSF Policy Rule can be executed or not. An I2NSF Condition, when used in the context of an (imperative) I2NSF Policy Rule, may be executed only when the Event clause of its owning I2NSF Policy Rule evaluates to true. Examples of an I2NSF Condition include matching attributes of a packet or flow, and comparing the internal state of an NSF to a desired state. - (based on [I-D.ietf-supa-generic-policy-info-model]). See also - I2NSF Action, I2NSF Event, I2NSF Policy Rule. + See also: I2NSF Action, I2NSF Event, I2NSF Policy Rule. I2NSF Consumer: A Consumer is a Role that is assigned to an I2NSF - Component that contains functions to provide information to other - I2NSF Components. Examples include providing I2NSF Policy Rules - to other I2NSF Components. See also: I2NSF Consumer-Facing + Component that contains functions to request information from, + and/or use services provided by, other I2NSF Components. Examples + include requesting Capabilities and I2NSF Policy Rules from + another I2NSF Component. See also: I2NSF Consumer-Facing Interface, I2NSF Producer, I2NSF Producer-Facing Interface, Role. I2NSF Consumer-Facing Interface: An Interface dedicated to requesting information from I2NSF Producers. This is typically defined per I2NSF administrative domain. For example, this Interface could be used to request a set of I2NSF Flow Security - Policy Rules from a Controller, or from one or more + Policy Rules from an I2NSF Controller, or from one or more individual NSFs. See also: I2NSF Consumer, I2NSF Provider, I2NSF NSF-Facing Interface, Interface. I2NSF Directly Consummable Policy Rule: An I2NSF Policy Rule is said to be directly consummable if a network device can execute it without translating its content or structure. See also I2NSF Indirectly Consummable Policy Rule, I2NSF Policy Rule. I2NSF Indirectly Consummable Policy Rule: An I2NSF Policy Rule is said to be indirectly consummable if a network device can NOT execute it without first translating its content or structure. See also I2NSF Directly Consummable Policy Rule, I2NSF Policy Rule. I2NSF Event: An I2NSF Event is defined as any important occurrence in time of a change in the system being managed, and/or in the environment of the system being managed. An I2NSF Event, when used in the context of an (imperative) I2NSF Policy Rule, is used to determine whether the Condition clause of that Policy Rule can be evaluated or not. Examples of an I2NSF Event include time and user actions (e.g. logon, logoff, and actions that violate an - ACL). (based on [I-D.ietf-supa-generic-policy-info-model]). - See also I2NSF Action, I2NSF Condition, I2NSF Policy Rule. + ACL). See also I2NSF Action, I2NSF Condition, I2NSF Policy Rule. I2NSF Management System: I2NSF Consumers and Producers operate within the scope of a network management system, which serves as a collection and distribution point for I2NSF security provisioning, monitoring, and other operations. I2NSF NSF-Facing Interface: An Interface dedicated to providing I2NSF Services. For example, this could provide Anti-Virus, (D)DoS, or IPS Services. This is also called the "NSF-Facing Interface". See also: Interface, I2NSF Consumer Interface. I2NSF Policy Rule: An I2NSF Policy Rule is an imperative statement that is used as a means to monitor and control the changing and/or maintaining of the state of one or more managed objects. It - consists of three Boolean clauses (Event, Condition, and Action). + consists of three clauses (Event, Condition, and Action). The + Event and Condition clauses are Boolean clauses, while the Action + clause consists of a set of one or more I2NSF Actions. In this context, "manage" means that one or more of the following six fundamental operations are supported: create, read, write, - delete, start, and stop). Note that for this release of I2NSF, + delete, start, and stop. Note that for this release of I2NSF, only imperative policy rules are in scope. An example of an I2NSF Policy Rule is, in pseudo-code: IF is TRUE IF is TRUE THEN execute END-IF END-IF - This is based on [I-D.ietf-supa-generic-policy-info-model]. - I2NSF Producer: A Producer is a Role that is assigned to an I2NSF - Component that contains functions to send information and/or - commands to another I2NSF Component (e.g., for describing, - communicating, and/or executing policies, or for transmitting - data). See also: I2NSF Consumer, I2NSF Consumer-Facing Interface, - I2NSF Producer, I2NSF Producer-Facing Interface, Role. + Component that contains functions to send information, and/or + provide services, to another I2NSF Component (e.g., for + describing, communicating, and/or executing policies, or for + transmitting data and/or metadata). See also: I2NSF Consumer, + I2NSF Consumer-Facing Interface, I2NSF Producer, I2NSF + Producer-Facing Interface, Role. I2NSF Registry: A repository where I2NSF data and metadata - information are stored and maintained. I2NSF Components can - connect to the I2NSF Registry using the I2NSF Registration - Interface; the actions that an I2NSF Component can performing - SHOULD be defined using an Access Control mechanism. Examples - of information that SHOULD be registered include Capability data, - as well as consistent defintions of data and I2NSF Components. + information (e.g., alarms and Capabilities, respectively) are + stored and maintained. I2NSF Components can connect to the I2NSF + Registry using the I2NSF Registration Interface. + Operations performed on an I2NSF Registry SHOULD be defined using + an Access Control mechanism. Examples of information that SHOULD + be registered include Capability metdata, as well as consistent + defintions of data and I2NSF Components. See also: Access Control, I2NSF Component, I2NSF Consumer, I2NSF Provider, I2NSF Registration Interface. I2NSF Registration Interface: An Interface dedicated to requesting information from, and writing information about, - I2NSF Components. See also: I2NSF Component, I2NSF Consumer, - I2NSF Provider, I2NSF Registry. + I2NSF Components and Capabilities. See also: I2NSF Component, + I2NSF Consumer, I2NSF Provider, I2NSF Registry. I2NSF Service: A set of functions, provided by an I2NSF Component, which provides data communication, processing, storage, - presentation, maniuplation, or other functions that can be + presentation, manipulation, or other functions that can be consumed by I2NSF Components. Exemplary I2NSF Services include Anti-Virus, Authentication, Authorization, Firewall, and IPS Services. See also: I2NSF Component, Interface. Information Model: A representation of concepts of interest to an environment in a form that is independent of data repository, data definition language, query language, implementation language, and protocol. See also: Data Model. - (from [I-D.ietf-supa-generic-policy-info-model]). Interface: A set of operations one object knows it can invoke on, and expose to, another object. It is a subset of all operations that a given object implements. The same object may have multiple types of interfaces to serve different purposes. See also: I2NSF Component, I2NSF Consumer-Facing Interface, I2NSF Registration Interface, Interface Group, NSF-Facing Interface Interface Group: A set of Interfaces that are related in purpose and which share the same communication mechanisms. See also: Interface. Intrusion Detection System (IDS): A system that detects network intrusions via a variety of filters, monitors, and/or probes. An IDS may be stateful or stateless. See also: IPS. Intrusion Protection System (IPS): A system that protects against network intrusions. An IPS may be stateful or stateless. See also: IDS. - Management Domain: A collection Entities that share a common + Management Domain: A collection of Entities that share a common purpose, which has the following three behavioral features: 1) a set of administrators are assigned to govern the Entities that are contained in a Management Domain - 2) a set of application are defined that are responsible for + 2) a set of applications are defined that are responsible for executing one or more governance operations 3) a set of management mechanisms, such as Policy Rules, are defined to govern the behavior of the Entities contained - in the Mangement Domain. + in the Management Domain. Management Plane: In the context of I2NSF, the Management Plane is an architectural Component that provides common functions to define the behavior of I2NSF Components. The primary use of the Management Plane is to formulate behavioral commands and forward them to the Control Plane. The Control Plane then translates them into a form that can be consumed by I2NSF components. The Management Plane may also instantiate and manage I2NSF Policy Rules. The Management Plane is also responsible for handling and acting on OAM data, which may influence the decision-making @@ -481,37 +480,37 @@ Object Constraint Language (OCL): A constraint programming language that is used to specify restrictions on functionality. (from http://www.ietf.org/mail-archive/web/i2nsf/current/msg00762.html) Profile: A structured representation of information that uses a pre-defined set of capabilities of an object, typically in a specific context. Zero or more Capabilities may be changed at runtime. This may be used to simplify how this object interacts with other objects in its environment. -Remote Attestation: A functoin that enables changes to an Entity to + Remote Attestation: A function that enables changes to an Entity to be detected by authorized parties (e.g., applications or users). Direct Anonymous Attestation preserves the privacy of the user, whereas remote attestation may not. See also: Attestation, Direct Anonymous Attestation. Role: An abstraction of a Component that models context-specific views and responsibilities of an object as separate Role objects. Role objects can optionally be attached to, and removed from, the object that the Role object describes at runtime. This provides three important benefits. First, it enables different behavior to be supported by the same Component for different contexts. Second, it enables the behavior of a Component to be adjusted dynamically (i.e., at runtime, in response to changes in context) by using one or more Roles to define the behavior desired for each context. Third, it decouples the Roles of a Component from - the Applications use that Component. + the Applications that use the Component. Tenant: A group of users that share common access privileges to the same software. An I2NSF tenant may be physical or virtual, and may run on a variety of systems or servers. 3. IANA Considerations No IANA considerations exist for this document. 4. Security Considerations @@ -527,54 +526,41 @@ Mohammed Boucadair 6. References 6.1. Informative References [I-D.ietf-i2nsf-gap-analysis] Hares, S., Moskowitz, R., and Zhang, D., "Analysis of Existing work for I2NSF", draft-ietf-i2nsf-gap-analysis-03 (work in progress), March 2017. - [I-D.ietf-i2nsf-problem-and-use-cases] + [RFC8192] Hares, S., Dunbar, L., Lopez, D., Zarny, M., and C. - Jacquenet, "I2NSF Problem Statement and Use cases", draft- - ietf-i2nsf-problem-and-use-cases-16 (work in progress), - May 2017. + Jacquenet, "I2NSF Problem Statement and Use cases", + RFC 8192, July 2017. [I-D.ietf-netmod-acl-model] Bogdanovic, D., Sreenivasa, K., Huang, L., Blair, D., "Network Access Control List (ACL) YANG Data Model", - draft-ietf-netmod-acl-model-11 (work in progress), - June 2017. + draft-ietf-netmod-acl-model-14 (work in progress), + October 2017. [I-D.ietf-opsawg-firewalls] Baker, F. and P. Hoffman, "On Firewalls in Internet Security", draft-ietf-opsawg-firewalls-01 (work in progress), October 2012. [I-D.ietf-sacm-terminology] Birkholz, H., Lu, J., Strassner, J., Cam-Wignet, N., "Secure Automation and Continuous Monitoring (SACM) - Terminology", draft-ietf-sacm-terminology-12, - March 2017 - - [I-D.ietf-supa-generic-policy-data-model] - Strassner, J., Halpern, J., and S. van der Meer, "Generic - Policy Data Model for Simplified Use of Policy - Abstractions (SUPA)", draft-ietf-supa-generic-policy- - data-model-04 (work in progress), June 2017. - - [I-D.ietf-supa-generic-policy-info-model] - Strassner, J., Halpern, J., and S. van der Meer, "Generic - Policy Information Model for Simplified Use of Policy - Abstractions (SUPA)", draft-ietf-supa-generic-policy- - info-model-03 (work in progress), May 2017. + Terminology", draft-ietf-sacm-terminology-14, + December 2017. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2975] Aboba, B., Arkko, J., and D. Harrington, "Introduction to Accounting Management", RFC 2975, DOI 10.17487/RFC2975, October 2000, . [RFC3234] Carpenter, B. and S. Brim, "Middleboxes: Taxonomy and Issues", RFC 3234, DOI 10.17487/RFC3234, February 2002,