An Extension of I2NSF Framework for Security Management Automation in Cloud-Based Security Services

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 22 February 2022.¶

Copyright Notice

Copyright (c) 2021 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

Interface to Network Security Functions (I2NSF) defines a framework and interfaces for interacting with Network Security Functions (NSFs) [RFC8192][RFC8329]. Note that an NSF is defined as software that provides a set of security-related services, such as (i) detecting unwanted activity, (ii) blocking or mitigating the effect of such unwanted activity in order to fulfill service requirements, and (iii) supporting communication stream integrity and confidentiality [RFC8329]. The NSF can be implemented as a Virtual Network Function (VNF) in a Network Functions Virtualization (NFV) environment [ETSI-NFV][I-D.ietf-i2nsf-applicability].¶

This document describes an extension of the framework of Interface to Network Security Functions (I2NSF) for Security Management Automation (SMA) in cloud-based security services. The security management automation includes a security polity translation and a feedback-based security service enforcement. This document specifies an augmented architecture of the I2NSF framework for the SMA services with a new system component and a new interface.¶

For reliable management for networked security services, this document proposes a network management and verification facility using a decentralized audit system (e.g., blockchain [Bitcoin]). This audit system can facilitate the non-repudiation of configuration commands and monitoring data generated in the I2NSF framework.¶

Therefore, with the security service automation, this document facilitates the foundation of Intent-Based Networking (IBN) for intelligent security services [I-D.irtf-nmrg-ibn-concepts-definitions].¶

2. Terminology

This document uses the terminology described in [RFC8329] and [I-D.ietf-i2nsf-applicability]. In addition, the following terms are defined below:¶

• Security Management Automation (SMA): It means that a high-level security policy from a user (or administrator) is well-enforced in a target I2NSF system. The high-level security policy can be translated into the corresponding low-level security policy by a security policy translator and dispatched to appropriate NSFs. Through the monitoring of the NSFs, the activity and performace of the NSFs is monitored and analyzed. If needed, the security rules of the low-level security policy are augmented or new security rules are generated and configured to appropriate NSFs.¶
• Security Policy Translation (SPT): It means that a high-level security policy is translated to a low-level security policy that can be understood and configured by an NSF for a specific security service, such as firewall, web filter, deep packet inspection, DDoS-attack mitigation, and anti-virus.¶
• Feedback-Based Security Management (FSM): It means that a security service is evolved by updating a security policy (having security rules) and adding new security rules for detected security attacks by processing and analzing the monitoring data of NSFs.¶

   +------------+
   | I2NSF User |
   +------------+
          ^
          | Consumer-Facing Interface
          v
+-------------------+     Registration     +-----------------------+
|Security Controller|<-------------------->|Developer's Mgmt System|
+-------------------+      Interface       +-----------------------+
          ^      ^
          |      |
          |      |  Application Interface  +-----------------------+
          |      +------------------------>|    I2NSF Analyzer     |
          |                                +-----------------------+
          | NSF-Facing Interface              ^       ^       ^
          |                                   |       |       |
          |                                   |       |       |
          |    +------------------------------+       |       |
          |    |              +-----------------------+       |
          |    |              |   Monitoring Interface        |
          v    v              v                               v
   +----------------+ +---------------+   +-----------------------+
   |      NSF-1     |-|     NSF-2     |...|         NSF-n         |
   |   (Firewall)   | | (Web Filter)  |   |(DDoS-Attack Mitigator)|
   +----------------+ +---------------+   +-----------------------+

3. I2NSF Framework for Security Management Automation

This section summarizes the I2NSF framework as defined in [RFC8329]. As shown in Figure 1, an I2NSF User can use security functions by delivering high-level security policies, which specify security requirements that the I2NSF user wants to enforce, to the Security Controller via the Consumer-Facing Interface (CFI) [I-D.ietf-i2nsf-consumer-facing-interface-dm].¶

4. Inter-Interface Automatic Policy Mapping

To facilitate Security Policy Translation (SPT), Security Controller needs to have a security policy translator that performs the translation of a high-level security policy into the corresponding low-level security policy. For the automatic SPT services, the I2NSF framework needs to bridge a high-level YANG data model and a low-level YANG data model in an automatic manner [I-D.ietf-i2nsf-applicability][I-D.yang-i2nsf-security-policy-translation]. Note that a high-level YANG data model is for the I2NSF Consumer-Facing Interface [I-D.ietf-i2nsf-consumer-facing-interface-dm], and a low-level YANG data model is for the I2NSF NSF-Facing Interface [I-D.ietf-i2nsf-nsf-facing-interface-dm].¶

Figure 2 shows automatic mapping of high-level and low-level data models. Automatic Data Model Mapper takes a high-level YANG data module for the Consumer-Facing Inteface and a low-level YANG data module for the NSF-Facing Interface. It then constructs a mapping table associating the data attributes (or variables) of the high-level YANG data module with the corresponding data attributes (or variables) of the low-level YANG data module. Also, it generates a set of production rules of the grammar for the construction of an XML file of low-level security policy rules.¶

Figure 3 shows high-to-low security policy translation. A security policy translator is a component of Security Controller. The translator consists of three components such as Policy Data Extractor, Policy Attribute Mapper, and Policy Constructor.¶

       High-level YANG Data Module   Low-level YANG Data Model
                   |                              |
                   V                              V
         +---------+------------------------------+---------+
         |           Automatic Data Model Mapper            |
         +------------------------+-------------------------+
                                  |
                                  V
                       Data Model Mapping Table

         +--------------------------------------------------+
         |                                                  |
         |                    I2NSF User                    |
         |                                                  |
         +------------------------+-------------------------+
                                  | Consumer-Facing Interface
                                  |
                      High-level Security Policy
         Security                 |
         Controller               V
         +------------------------+-------------------------+
         |  Security Policy       |                         |
         |  Translator            V                         |
         |  +---------------------+----------------------+  |
         |  |                                            |  |
         |  |         +-------------------------+        |  |
         |  |         |  Policy Data Extractor  |        |  |
         |  |         +-------------------------+        |  |
         |  |                                            |  |
         |  |         +-------------------------+        |  |
         |  |         | Policy Attribute Mapper |        |  |
         |  |         +-------------------------+        |  |
         |  |                                            |  |
         |  |         +-------------------------+        |  |
         |  |         |    Policy Constructor   |        |  |
         |  |         +-------------------------+        |  |
         |  |                                            |  |
         |  +---------------------+----------------------+  |
         |                        |                         |
         |                        V                         |
         +------------------------+-------------------------+
                                  |  NSF-Facing Interface
                                  |
                       Low-level Security Policy
                                  |
                                  V
         +------------------------+-------------------------+
         |                                                  |
         |                      NSF(s)                      |
         |                                                  |
         +--------------------------------------------------+

Policy Data Extractor extracts attributes related to a security policy from a high-level security policy XML file that is delivered from an I2NSF User to a Security Controller [I-D.ietf-i2nsf-consumer-facing-interface-dm].¶

Policy Attribute Mapper maps the attributes and their values of a high-level security policy to the corresponding attributes and their values of a low-level security policy.¶

Policy Constructor constructs a low-level security policy XML file that is delivered from the Security Controller to an appropriate NSF [I-D.ietf-i2nsf-nsf-facing-interface-dm].¶

5. Security Audit System

The I2NSF framework is weak to both an inside attack and a supply chain attack since it trusts in NSFs provided by Developer's Management System (DMS) and assumes that NSFs work for their security services appropriately. [I-D.ietf-i2nsf-applicability].¶

To detect the malicious activity of either an insider attacker with its DMS or a supply chain attacker with its compromised DMS, a security audit system is required for the I2NSF framework. For this audit service in the I2NSF framework, a decentralized security audit system (e.g., blockchain [Bitcoin]) is required. This audit system can facilitate the non-repudiation of configuration commands and monitoring data generated in the I2NSF framework.¶

A security audit system has four main objectives such as follows:¶

• To check the existence of a security policy, a management system and its procedures;¶
• To identify and understand the existing vulnerabilities and risks of a supply chain attacker;¶
• To review existing security controls on operational, administrative and managerial issues;¶
• To provide recommendations and corrective actions for further improvement.¶

+-----------------------------+                      +----------------+
|         I2NSF User          |                      |Developer's Mgmt|
|                             +--------------+       |     System     |
+--------------+--------------+              |       +--------+-------+
               | Consumer-Facing Interface   |                |
               |                             |                |
   High-level Security Policy                |                |
               |                             |                |
               |                             |                |
               V                             |                V
+--------------+--------------+              |      +---------+--------+
|                             |              V      |     Security     |
|     Security Controller     +------------->+----->|       Audit      |
|                             |              ^      |      System      |
+--------------+--------------+              |      |(e.g., Blockchain)|
               |  NSF-Facing Interface       |      +---------+--------+
               |                             |                ^
   Low-level Security Policy                 |                |
               |                             |                |
               V                             |                |
+--------------+--------------+              |       +--------+-------+
|            NSF(s)           |              |       | I2NSF Analyzer |
|                             +--------------+       |                |
+-----------------------------+                      +----------------+

Figure 4 shows activity auditing with a security audit system in the I2NSF framework. All the components in the I2NSF framwork report its activities (such as configuration commands and monitoring data) to Security Audit System (e.g., Blockchain) as transactions. The security audit system can analyze the reported activities from the I2NSF components to detect malicious activities such as supply chain attack.¶

In order to determine a minimum set of controls required to reduce the risks from a supply chain attacker, the security audit system should analyze the activities of all the components in the I2NSF framework periodically, evaluate possible risks, and take an action to such risks since vulnerabilities and threats may change in different environments over time.¶

6. Security Considerations

The same security considerations for the I2NSF framework [RFC8329] are applicable to this document.¶

7. IANA Considerations

This document does not require any IANA actions.¶

Appendix A. Acknowledgments

This work was supported in part by Institute of Information & Communications Technology Planning & Evaluation (IITP) grant funded by the Korea Ministry of Science and ICT (MSIT) (2020-0-00395, Standard Development of Blockchain based Network Management Automation Technology). This work was supported by the IITP grant funded by the Korea MSIT (R-20160222-002755, Cloud based Security Intelligence Technology Development for the Customized Security Service Provisioning).¶

Appendix B. Contributors

This document is made by the group effort of I2NSF working group. Many people actively contributed to this document, such as Linda Dunbar, Yoav Nir, and Qin Wu. The authors sincerely appreciate their contributions.¶

The following are co-authors of this document:¶

Yunchul Choi Electronics and Telecommunications Research Institute 218 Gajeong-Ro, Yuseong-Gu Daejeon, 34129 Republic of Korea EMail: pjs@etri.re.kr¶

Younghan Kim School of Electronic Engineering Soongsil University 369, Sangdo-ro, Dongjak-gu Seoul 06978 Republic of Korea EMail: younghak@ssu.ac.kr¶

Authors' Addresses