KR20210054439A - Interface yang data model facing i2nsf network security capabilities - Google Patents

Abstract

The present invention relates to an interface YANG data model facing interface to network security functions (I2NFS) network security capabilities to design an information model for an interface facing network security functions (NSF) in I2NFS and a YANG data model for a security service. According to the present invention, a method for allowing a network operation management system to provide a security service in a security management system comprises the following steps of: receiving a first security policy of a high-level from an I2NSF user; receiving, from a developer management system, available security services; generating a second security policy of a lower level corresponding to the first security policy on the basis of the security service; and transmitting a packet including the second security policy for setting the generated second security policy to each of a plurality of NSFs as an NSF instance. Each of the network operation management system and the plurality of NSFs is connected to an I2NSF-NSF facing interface, and the second security policy includes at least one of 1) blocking SNS access during business hours, 2) blocking malicious VoIP (Voice over Internet Protocol) or malicious Voice over LTE (VoLTE) packets, or 3) to mitigate flood of http and https to company web servers.

Description

Interface YANG data model facing I2NSF network security capabilities {INTERFACE YANG DATA MODEL FACING I2NSF NETWORK SECURITY CAPABILITIES}

This specification relates to a data model, and in more detail, defines an information model for an interface facing Network Security Functions (NSF) and a YANG data model for security services in I2NSF (Interface to Network Security Functions). For.

Connecting networks around the world provides quick access to information regardless of geographic distance. The Internet is essentially a number of networks in which different levels of hierarchies are interconnected.

The Internet operates according to TCP/IP (Transmission Control Protocol/Internet Protocol) published by the Internet Engineering Task Force (IETF), and TCP/IP can be found in Request For Comments (RFC) 703 and RFC 791 issued by the IETF. .

An object of the present specification is to propose a method for designing an information model for an interface facing Network Security Functions (NSF) and a YANG data model for security services in I2NSF (Interface to Network Security Functions).

In addition, the present specification proposes a specific information model for three security capabilities (eg, network security capabilities) such as network security control, content security control, and attack mitigation control, and a method for designing the corresponding data model.

The technical problems to be achieved in the present specification are not limited to the technical problems mentioned above, and other technical problems that are not mentioned will be clearly understood by those of ordinary skill in the technical field to which the present specification belongs from the following description. I will be able to.

In one aspect of the present specification, in a method for a network operation management system to provide a security service in a security management system, a high-level first security policy is received from an I2NSF (Interface to Network Security Functions) user. The step of doing; Receiving, from a developer management system, available security services; Generating a second low-level security policy corresponding to the first security policy based on the security service; And transmitting a packet including the second security policy for setting the generated second security policy to each of a plurality of Network Security Functions (NSFs) to an NSF instance; including, the network operation management system and the Each of the plurality of NSFs is connected by an I2NSF NSF-facing interface, and the second security policy is at least one or more 1) blocking SNS access during business hours, 2) malicious Voice over Internet Protocol (VoIP) or malicious Voice over LTE (VoLTE) It may include blocking packets or 3) mitigating the flood of http and https to corporate web servers.

In addition, the second security policy may include a policy rule to be applied, and basic operation information indicating an operation for a general security function.

In addition, the policy rule includes policy information and rule information, and the policy information and the rule information include an event clause indicating a system change, a condition clause indicating an application condition of the policy rule, and It may include an action clause indicating a security function performed when the event clause and the condition clause are satisfied.

In addition, based on the second security policy for blocking access to SNS during the business hours, the policy rule provides time information for applying the policy rule only during the business hours and a source IP address for inspecting a transmission packet. It may contain more.

Further, based on the time information and the source IP address, when the URL (Uniform Resource Locator) address of the transmission packet is a predetermined URL address of a specific SNS, transmission of the transmission packet may be blocked.

In addition, based on the second security policy for blocking the malicious VoIP or the malicious VoLTE packet, the policy rule further includes 1) an IP address and 2) a port number to which the malicious VoIP or malicious VoLTE packet is received. Can include.

Also, based on 1) the IP address and 2) the port number, a packet matching the voice ID of the malicious VoIP or the malicious VoLTE packet may be blocked.

In addition, based on the second security policy for mitigating the flood of http and https to the company web server, the policy rule is 1) IP address and 2) of the packet received by the company web server. It may further include a port number.

In addition, based on 1) the IP address and 2) the port number, if the packet received by the company web server exceeds an allowable reception rate per hour, the packet received by the company web server can be blocked. .

In addition, the policy rule may further include information related to a range of IP addresses to be matched.

Another aspect of the present specification is a security management system for providing a security service, comprising: an I2NSF (Interface to Network Security Functions) user who creates a high-level first security policy; A developer management system that provides security services; Receiving the first security policy from the I2NSF user, receiving the security service from the developer management system, based on the security service, a second low-level corresponding to the first security policy A network operation management system for generating a security policy and transmitting a packet including the second security policy for setting the generated second security policy to each of a plurality of Network Security Functions (NSFs) to an NSF instance; And a plurality of Network Security Functions (NSFs) receiving the second security policy from the network operation management system, wherein each of the network operation management system and the plurality of NSFs is connected by an I2NSF NSF-facing interface, and the first 2 The security policy is at least one or more 1) blocking access to SNS during business hours, 2) blocking malicious VoIP (Voice over Internet Protocol) or malicious VoLTE (Voice over LTE) packets, or 3) flooding the company's web server with http and https It may include something to alleviate (flood).

In I2NSF (Interface to Network Security Functions), you can design an information model for interfaces facing Network Security Functions (NSF) and a YANG data model for security services.

In addition, it is possible to design specific information models and corresponding data models for three security capabilities (eg, network security capabilities): network security control, content security control, and attack mitigation control.

The effects obtainable in the present specification are not limited to the above-mentioned effects, and other effects not mentioned may be clearly understood by those of ordinary skill in the art from the following description. will be.

The accompanying drawings, which are included as part of the detailed description to aid in understanding of the present specification, provide embodiments of the present specification, and describe technical features of the present specification together with the detailed description.
1 illustrates an Interface to Network Security Functions (I2NSF) system according to an embodiment of the present specification.
2 illustrates an architecture of an I2NSF system according to an embodiment of the present specification.
3 shows an example of an overall I2NSF information model design to which the present specification can be applied.
4 shows an example of an overview of a network security information sub-model to which the present specification can be applied.
5 shows an example of extension of a network security information sub-model to which the present specification can be applied.
6 shows an example of extension of a network security information sub-model event class to which the present specification can be applied.
7 shows an example of extension of a network security information sub-model condition class to which the present specification can be applied.
8 shows an example of extension of a network security information sub-model action to which the present specification can be applied.
9 shows an example of a high-level model of an I2NSF security function to which the present specification can be applied.
10 shows an example of a network security function information model to which the present specification can be applied.
11 shows an example of an attack mitigation function information model to which the present specification can be applied.
12 illustrates a data model structure for network security policy identification according to an embodiment of the present specification.
13 illustrates a data model structure for an event rule according to an embodiment of the present specification.
14A to 14D illustrate a data model structure for a condition rule according to an embodiment of the present specification.
15 illustrates a data model structure for an action rule according to an embodiment of the present specification.
16 is an example of I2NSF IPsec (IP Security) to which the present specification can be applied.
16A to 18T illustrate a YANG data module of an I2NSF NSF-Facing-Interface according to an embodiment of the present specification.
19A to 19F illustrate Extensible Markup Language (XML) configuration of low-level security policy rules according to an embodiment of the present specification.
20 is an embodiment to which the present specification may be applied.

Hereinafter, preferred embodiments according to the present specification will be described in detail with reference to the accompanying drawings. The detailed description to be disclosed below with the accompanying drawings is intended to describe exemplary embodiments of the present specification, and is not intended to represent the only embodiments in which the present specification may be practiced. The detailed description below includes specific details to provide a thorough understanding of the present specification. However, one of ordinary skill in the art appreciates that the present specification may be practiced without these specific details.

In some cases, in order to avoid obscuring the concept of the present specification, well-known structures and devices may be omitted, or may be illustrated in a block diagram format centering on core capabilities of each structure and device.

Specific terms used in the following description are provided to help the understanding of the present specification, and the use of these specific terms may be changed in other forms without departing from the technical spirit of the present specification.

Recently, a basic standard interface for NFV-based security functions has been developed by the I2NSF (Interface to Network Security Functions) working group. It is part of an international Internet standards body called the Internet Engineering Task Force (IETF).

The purpose of I2NSF is to define a standardized interface for heterogeneous network security function(s) (NSF) provided by multiple security solution vendors.

In the I2NSF architecture, users do not need to consider in detail the management of NSF(s) (NSF management eventually requires the enforcement of security policies), and users are required to protect network resources in the user's network system. Protection policy can be defined. In addition, standardized interfaces from multiple vendors to NSF(s) can simplify the configuration and management of tasks for heterogeneous NSF(s).

1 illustrates an Interface to Network Security Functions (I2NSF) system according to an embodiment of the present specification.

Referring to FIG. 1, the I2NSF system includes an I2NSF user, a network operator management system, a developer's management system, and/or at least one Interface to Network Security Function (NSF). do.

I2NSF users communicate with the network operation management system through the I2NSF Consumer-Facing Interface. The network operation management system communicates with the NFC(s) through the I2NSF NSF-Facing Interface. The developer management system communicates with the network operation management system through the I2NSF Registration Interface. Hereinafter, each component (I2NSF component) and each interface (I2NSF interface) of the I2NSF system will be described.

I2NSF users

I2NSF users are I2NSF components that request information from other I2NSF components (eg, network operation management systems) and/or use services (eg, network security services) provided by other I2NSF components (eg, developer management systems). . For example, the I2NSF user may be an overlay network management system, an enterprise network manager system, another network domain manager, or the like.

A target performing a role assigned to such an I2NSF user component may be referred to as an I2NSF consumer. An example of an I2NSF consumer is the need to dynamically notify the underlay network to allow, rate-limit, or deny flow based on a specific field of the packet over a time span. Video-conference network managers, Enterprise network administrators and management systems who need to request provider networks to enforce specific I2NSF policies for specific flows, An IoT management system may be included that sends a request to the underlay network to block flows that match a set of specific conditions.

I2NSF users can create and distribute high-level security policies. Specifically, I2NSF users need to use a network security service to protect network traffic from various malicious attacks. In order to request this security service, I2NSF users can create a high-level security policy for the security service they want and notify the network operation management system.

Meanwhile, in the process of preparing a high-level security policy, I2NSF users consider the type of NSF(s) required to realize a security service or security policy rule configuration for each NSF(s). I can't.

In addition, the I2NSF user may be notified of security event(s) occurring within the underlying NSF(s) by the network operation management system. By analyzing their security event(s), I2NSF users can identify new attacks and update (or create) high-level security policies to cope with the new attacks. As such, I2NSF users can define, manage, and monitor security policies.

Network operation management system

The network operation management system is a component that serves as a collection and distribution point for security provision, monitoring, and other operations. For example, the network operation management system may be a security controller. This network operation management system may be managed by a network security administrator, and may be referred to as an I2NSF management system.

One of the main roles of the network operations management system (or security controller) is to translate high-level security policies (or policy rules) from I2NSF users into low-level security policy rules for specific NSF(s). ). After receiving the high-level security policy from the I2NSF user, the network operation management system (or security controller) may first determine the type of NSF(s) required to enforce the policy required by the I2NSF user. In addition, the network operation management system (or security controller) may create a low-level security policy for each required NSF(s). Eventually, the network operation management system (or security controller) can set the generated low-level security policy to each NSF(s).

In addition, the network operation management system (or security controller) monitors the NSF(s) running in the system, and various information about each NSF(s) (e.g., network access information and workload) State, etc.). In addition, the network operation management system (or security controller) can dynamically manage the pool of NSF instances through dynamic life-cycle management of NSF instances with the help of the developer management system. have.

NSF

NSF is a logical entity or software component that provides security-related services. For example, NFC may receive a low-level security policy, detect malicious network traffic based on this, and block or mitigate it. Through this, the integrity and confidentiality of the network communication stream can be guaranteed.

Developer management system

The developer management system is an I2NSF component that sends information to other I2NSF components (eg, I2NSF users, network operation management systems), and/or provides services (eg, network security services). The developer management system may also be referred to as a vendor's management system. An object that performs a role assigned to such a developer management system may be referred to as an I2NSF producer.

The developer management system may be managed by a third-party security vendor that provides NSF(s) to the network operations management system. There may be multiple developer management system(s) from various security vendors.

I2NSF consumer-facing interface (briefly, consumer-facing interface (CFI))

CFI is an interface to the user's I2NSF system, located between the I2NSF user and the network operation management system. By being designed in this way, it hides the details of the underlying NSF(s) and provides the user with only an abstract view of the NSF(s).

This CFI can be used to allow different users of a given I2NSF system to define, manage and monitor security policies for specific flows within the management domain. High-level security policies (or policy rules) created by I2NSF users can be delivered to the network operation management system through this CFI.

I2NSF NSF-facing interface (simply, NSF-facing interface (NFI))

The NFI is an interface located between the network operations management system (or security controller) and the NSF(s).

The NFI can be used to specify and monitor flow-based security policies enforced by one or more NSFs. For example, an I2NSF system can use a flow-based NSF. Here, the flow-based NSF is an NSF that examines network flow according to a set of policies to reinforce security characteristics. The flow-based security by this flow-based NSF means that packets are inspected in the order they are received, and there is no modification to the packet according to the inspection process. Interfaces to flow-based NSFs can be classified as follows:

-NSF Operational and Administrative Interface: a group of interfaces used by the I2NSF management system to program the operational state of the NSF; This interface group also contains management control capabilities. The I2NSF policy rule represents one way to change this interface group in a consistent way. Since applications and I2NSF components need to dynamically control the behavior of the traffic they transmit and receive, most of the I2NSF effort is focused on this interface group.

-Monitoring Interface: an interface group used by the I2NSF management system to obtain monitoring information from one or more selected NSFs; Each interface in this interface group can be a query or report-based interface. The difference between the two is that the query-based interface is used by the I2NSF management system to obtain information, whereas the report-based interface is used by NSF to provide the information. The capabilities of this interface group can also be defined by other protocols such as SYSLOG and DOTS. The I2NSF management system may take one or more actions based on receipt of the information. This must be specified by the I2NSF policy rules. This interface group does not change the NSF's operational state.

As such, NFI can be developed using a flow-based paradigm. A common trait of flow-based NSF is to process packets based on the content (eg, header/payload) and/or context (eg, session state and authentication state) of the received packet. This feature is one of the requirements to define the operation of the I2NSF system.

On the other hand, the I2NSF management system does not need to use all the capabilities of a given NSF, nor does it need to use all available NSFs. Thus, this abstraction allows NSF features to be treated as building blocks by the NSF system. Therefore, developers are free to use the security capabilities defined by the NSF, which are vendor- and technology-independent.

I2NSF registration interface (briefly, registration interface (RI))

RI is an interface located between the network operation management system and the developer management system. NSFs offered by different vendors may have different capabilities. Thus, in order to automate the process of using the different types of security capabilities provided by different vendors, vendors need to have dedicated interfaces to define their NSF capabilities. This dedicated interface may be referred to as an I2NSF registration interface (RI).

The capabilities of the NSF can be pre-configured or dynamically retrieved through the I2NSF registration interface. If new capabilities exposed to consumers are added to NSF, the capabilities of that new capability need to be registered in the I2NSF registry through the I2NSF registration interface so that interested management and control entities can know them. have.

2 illustrates an architecture of an I2NSF system according to an embodiment of the present specification. The I2NSF system of FIG. 2 shows the configuration of the I2NSF user and network operation management system in more detail than the I2NSF system of FIG. 1. In FIG. 2, descriptions overlapping with those described above in FIG. 1 will be omitted.

Referring to FIG. 2, the I2NSF system includes an I2NSF user, a security management system, and an NSF instance layer. The I2NSF user layer includes an application logic, a policy updater, and an event collector as components. The security management system layer includes a security controller and a developer management system. The security controller of the security management system layer includes a security policy manager and an NSF capability manager as components.

The I2NSF user layer communicates with the security management system layer through a consumer-facing interface. For example, the policy updater and event collector at the I2NSF user layer communicate with the security controller at the security management system layer through a consumer-facing interface. In addition, the security management system layer communicates with the NFC instance layer through the NSF-facing interface. For example, the security controller of the security management system layer communicates with the NSF instance(s) of the NFC instance layer through the NSF-facing interface. In addition, the developer management system of the security management system layer communicates with the security controller of the security management system layer through the registration interface.

The I2NSF user layer of FIG. 2, the security controller component of the security management system layer, the developer management system component, and the NSF instance layer of the security management system layer are respectively the I2NSF user component, network operation management system component, developer management system component, and NSF of FIG. Corresponds to the component. In addition, the consumer-facing interface, NSF-facing interface and registration interface of FIG. 2 correspond to the consumer-facing interface, NSF-facing interface and registration interface of FIG. 1. Hereinafter, newly defined components included in each layer will be described.

I2NSF users

As described above, the I2NSF user layer includes three components: Application Logic, Policy Updater, and Event Collector. Each role and operation will be described as follows.

Application logic is a component that creates a high-level security policy. To this end, the application logic receives an event for updating (or generating) a high-level policy from the event collector, and updates (or generates) the high-level policy based on the collected event. After that, the higher level policy is sent to the policy updater for distribution to the security controller. To update (or create) a higher level policy, the event collector receives the events sent by the security collector and sends them to the application logic. Based on this feedback, the application logic can update (or create) the higher level security policy.

In FIG. 2, the application logic, the policy updater, and the event collector are shown as separate configurations, but the present specification is not limited thereto. In other words, each is a logical component, and may be implemented as one or two components in the I2NSF system.

Security management system

As described above, the security controller of the security management system layer includes two components such as a security policy manager and an NSF capability manager.

Security policy managers can receive high-level policies from the policy updater through CFI, and map these policies to multiple low-level policies. This low-level policy relates to a given NSF capability registered with the NSF capability manager. In addition, the security policy manager can communicate this policy to the NSF(s) through the NFI.

The NSF Capability Manager can specify the capabilities of the NSF registered by the Developer Management System, and share it with the Security Policy Manager, in order to create a low-level policy related to a given NSF capability. Whenever a new NSF is registered, the NSF capability manager can request the developer management system to register the NSF's capability in the NSF capability manager's management table through the registration interface. The developer management system is another part of the security management system for registering new NSF capabilities as NSF capability managers.

In FIG. 2, the security policy manager and the NSF capability manager are shown as separate configurations, but are not limited thereto in the present specification. In other words, each is a logical component, and may be implemented as one component in the I2NSF system.

NSF Instances

As shown in Figure 2, the NSF instance layer includes NSFs. At this time, all NSFs are located in this NSF instance layer. Meanwhile, after mapping the higher level policy to the lower level policy, the security policy manager delivers the policy to the NSF(s) through the NFI. In this case, NFC may detect malicious network traffic and block or mitigate it based on the received low-level security policy.

Rapid development of virtualization systems requires advanced security capabilities in a variety of scenarios (eg, network devices in an enterprise network, user equipment in a mobile network, devices in the Internet or resident access users, etc.).

Produced by several security vendors, NSF can provide customers with a variety of security capabilities. In other words, NSF can provide security services for a given network traffic by combining multiple NSFs regardless of whether they are implemented with physical or virtual capabilities.

Security capability refers to a set of security-related capabilities that can be used for security policy enforcement purposes. The security capability is independent of the security control mechanism actually implemented, and every NSF has a registered set of capabilities that NSF can provide.

Security Capabilities are market leaders that provide a way to define custom security protections by unambiguously describing the security capabilities provided by a particular NSF. In addition, security capabilities can be described in a vendor-neutral way of security capabilities.

In other words, when designing a network, there is no need to mention a specific product, and features can be considered for each capability.

As described above, there can be two types of I2NSF interfaces that can be used to provide security policies as follows.

-Interface between I2NSF users and applications and security controller (Consumer-Facing Interface): A service-oriented interface that provides a communication channel between NSF data and service users and the network operation management system (or security controller).

I2NSF Consumer-Facing Interface can be used to exchange security information between various applications (eg OpenStack or various BSS / OSS components) and security controllers. The design goal of the Consumer-Facing Interface is to separate the specification of the security service from the implementation.

-NSF interface (e.g. firewall, intrusion prevention or anti-virus) and security controller (NSF-Facing Interface): The NSF-Facing Interface is used to separate the security management scheme from the NSF set and various implementations, implemented by NSF. It is independent in the way it becomes (for example: virtual machine or real appliances, etc.).

Hereinafter, an object-oriented information model for network security, content security, and attack mitigation capabilities along with the associated I2NSF policy object will be described.

Terms used in the information model in this specification can be defined as follows.

AAA: Access control, Authorization, Authentication

ACL: Access Control List

(D)DoD: (Distributed) Denial of Service (attack)

ECA: Event-Condition-Action

FMR: First Matching Rule (resolution strategy)

FW: Firewall

GNSF: Generic Network Security Function

HTTP: HyperText Transfer Protocol

I2NSF: Interface to Network Security Functions

IPS: Intrusion Prevention System

LMR: Last Matching Rule (resolution strategy)

MIME: Multipurpose Internet Mail Extensions

NAT: Network Address Translation

NSF: Network Security Function

RPC: Remote Procedure Call

SMA: String Matching Algorithm

URL: Uniform Resource Locator

VPN: Virtual Private Network

Information model design

The starting point of the design of the Capability Information Model is to classify the types of security capabilities. For example, to classify types of security capabilities such as "IPS", "antivirus" and "VPN concentrator".

Alternatively, the “packet filter” may be classified as a storage device capable of allowing or rejecting packet delivery according to various conditions (eg, source and destination IP address, source and destination port, and IP protocol type field, etc.).

However, for other devices such as stateful firewalls or application layer filters, more information is needed. These devices filter packets or communications, but differ in the state of categorizing and maintaining packets and communications.

Analog considerations can be taken into account in the channel protection protocols. Here, the channel protection protocols can protect packets through a symmetric algorithm that can be negotiated with an asymmetric cipher, operate at different layers and support different algorithms and protocols.

For secure protection, these protocols should be subject to integrity, optionally confidentiality, anti-reply protection, and peer authentication.

Capability Information Model Overview

The capability information model defines a security capability model that provides the basis for the automatic management of NSF. The capability information model allows the security controller to properly identify and manage NSFs, and also includes allowing NSFs to properly declare capabilities so that they can be used in the correct way.

Some basic design principles for security and the system to manage them are as follows.

-Independence: Each security capability must be an independent capability with minimal overlap or dependency on other capabilities. This allows you to freely use and combine each security capability. More importantly, changing to one ability does not affect the other.

It follows the Single Responsibility Principle [Martin] [OODSRP].

-Abstraction: Each capability must be defined in a vendor-independent manner and connected to a well-known interface to provide a standardized capability to describe and report processing results. Thus, interoperability with multiple supply vendors can be improved.

-Automation: The system should be able to auto-discover, auto-negotiate, and auto-update security capabilities (ie, without user intervention). This automation capability is particularly useful for managing multiple NSFs.

It is essential to add smart services (e.g.: analysis, refinement, capability inference and optimization) to the adopted security scheme. This capability is supported by many design patterns such as Observer Pattern [OODOP], Mediator Pattern [OODMP], and Message Exchange Patterns [Hohpe].

-Scalability: The management system must have the ability to scale up/down or scale in/out. Therefore, due to this scalability, various performance requirements derived from changeable network traffic or service requests can be satisfied. Additionally, security capabilities that are affected by scalability can help determine whether scaling should be invoked by supporting reporting statistics to the security controller.

Following the above principles, an abstract and vendor-neutral set of capabilities with standard interfaces can be defined. It provides an unambiguous definition of the security provided by the set of NSFs used and the Capability model that allows the set of NSFs to be used at any given time.

The security controller compares the requirements of users and applications to the currently available set of capabilities and selects the NSF required to meet those requirements.

In addition, when unknown threats (e.g., zero-day exploits and unknown malware) are reported by the NSF, new capabilities may be created and/or existing capabilities may be updated (e.g., its By updating signatures and algorithms). As a result, existing NSFs are hardened (and/or created new NSFs) to cope with new threats.

New capabilities can be transferred to and stored in a central repository or stored individually in the vendor's local repository. In both cases, the standard interface makes the update process easy.

ECA Policy Model Overview

The "Event-Condition-Action" (ECA) policy model is used as the basis for the design of I2NSF policy rules. At this time, terms related to the I2NSF policy can be defined as follows (refer to [I-D.draft-ietf-i2nsf-terminology]):

-Event: An event occurs when a managed system changes and/or at a critical point in the managed system's environment. The event can be used to determine whether the condition clause of an I2NSF policy rule can be evaluated when used in the context of an I2NSF policy rule. Examples of I2NSF events may be time and user actions (eg: logon, logoff, and actions that violate ACLs).

-Condition: A condition is defined as a set of attributes, capabilities and/or values to be compared with a set of known attributes, characteristics and/or values, and may or may not execute its (imperative) I2NSF policy rule. Examples of I2NSF conditions may include comparing the matching attribute of the packet or flow and the internal state of the NSF to the desired state.

-Action: Actions are used to control and monitor aspects of flow-based NSF when event and condition clauses are satisfied. NSF provides security capabilities by executing various actions. Examples of I2NSF tasks may include intrusion detection and/or protection, web and flow filtering, and providing deep packet inspection for packets and flows.

The I2NSF policy rule consists of three Boolean clauses: Event clause, Condition clause, and Action clause.

The Boolean clause means a logical statement that evaluates to TRUE or FALSE, and can consist of one or more terms.

If there is more than one term, the Boolean clause connects the terms using logical linking elements (ie, AND, OR, and NOT). In this case, the logical connection element may have the same meaning as in Table 1 below.

Technically, "policy rules" can actually act as a container that aggregates not only metadata but also "events", "actions" and "conditions" described earlier.

The ECA policy model described earlier is very generic and can be easily extended and avoids the potential constraints that could limit the implementation of general security capabilities.

Relationship to external information model

3 shows an example of an overall I2NSF information model design to which the present specification can be applied.

The I2NSF NSF-Facing Interface uses the capabilities of NSF to select and manage NSFs, and this is done using the following approach.

1) Each NSF registers its capabilities in the management system when it "participates", so that the capability can be used in the management system.

2) The security controller selects the set of capabilities required to meet the requirements of the security service in all available NSFs it manages.

3) The security controller uses the capability information model to match the selected capabilities to the vendor-independent NSF.

4) The security controller takes the above information and creates or uses one or more data models of the competency information model to manage the NSF.

5) You can start controlling and monitoring.

This approach can assume that an external information model is used to define the concept of ECA policy rules and their components (eg events, conditions and action objects, etc.). Through this, I2NSF policy rules can be classified into subclasses from the external information model (see I-D.draft-ietf-i2nsf-terminology).

In this specification, the data model represents the concept of interest in the environment in a format dependent on the storage of data, a data definition language, a query language, an implementation language, and a protocol.

In addition, the information model represents the concept of interest in the environment in a form independent of data storage, data definition language, query language, implementation language, and protocol.

Capabilities can be defined as classes (eg: a set of objects representing a set of common characteristics and behaviors) (see I-D.draft-ietf-supa-generic-policy-info-model).

Each capability can consist of one or more model elements (eg: attributes, methods, or relationships) that differentiate them from all other objects in the system. Capabilities are generally some kind of metadata (i.e. information that describes and/or prescribes an object's behavior).

Thus, each capability can be used by an external information model to define metadata (preferably in the form of a class hierarchy). Thus, capabilities can be subclassed in the external metadata model.

The capabilities sub-model is used to advertise, create, select, and manage specific sets of security capabilities that are independent of the type and vendor of devices that contain NSFs.

In other words, users of the NSF-Facing Interface do not take into account whether NFC is virtualized or hosted, who the NSF vendor is, or the set of entities the NSF communicates with (e.g., firewall or IPS).

Instead, the user considers only the set of capabilities that NSF has, such as packet filtering and deep packet inspection.

The design of the entire ISNSF information model is shown in FIG. 3.

All of the external models shown in FIG. 3 may be based on the SUPA information model (see I-D.draft-ietf-supa-generic-policy-info-model). The class of the capability sub-model inherits the set of metadata aggregates (AggregatesMetadata) from the external metadata information model.

The external ECA information model shown in FIG. 3 provides a minimum class set representing a general ECA policy rule and a class set representing events, conditions, and actions that can be aggregated by the general ECA policy rule.

Through this, I2NSF can reuse these general models for other purposes as well as create new subclasses or add properties and relationships to express I2NSF-related concepts.

In this specification, it is assumed that the external ECA information model has the ability to collect meta data. Capabilities can be classified into subclasses from the appropriate class of the external metadata information model.

This allows the ECA entity to add metadata to the appropriate ECA entity using metadata and existing aggregations.

Let's look at each part of the information model below.

I2NSF Capability Information Model: Theory of Operation

Capabilities are generally used to represent NSF functions that can be called. Since capabilities are objects, they can be used in sections describing events, conditions, and/or actions of I2NSF ECA policy rules.

The I2NSF capability information model embodies a predefined meta data model. Application of I2NSF capabilities can be performed by modifying the predefined ECA policy rule information model that defines how to use, manage, or manipulate a set of capabilities. In this approach, the I2NSF policy rule can act as a container consisting of three clauses: an event clause, a condition clause, and an action clause.

When the I2NSF policy engine receives a series of events, it matches those events with the events of the active ECA policy rule. Matching the event triggers the evaluation of the conditional clause of the matching I2NSF policy rule. The conditional clause is evaluated, and if it matches, the set of actions in the matching I2NSF policy rule can be executed.

Initial NSFs Capability Categories

Hereinafter, we will look at three general functions: network security, content security, and attack mitigation. Both the number of categories and the type of functions within a specific category as viewed in the present specification may be expanded.

Network Security Capabilities

Network security is a category to describe how to inspect and process network traffic using predefined security policies.

The inspection portion may be a packet processing engine that inspects packets passing through the network either directly or in the context of the flow to which the packet is associated. From the perspective of packet processing, the depth of the packet header and/or payload that can be implemented, the various flow and context states that can be maintained, and the operation that can be applied to the packet or flow may vary depending on implementation.

Content Security Capabilities

Content security is another category of security functions applied to the application program layer. For example, by analyzing the content of traffic transmitted from the application program layer and using the content security function, various security functions required can be identified.

This can include defense against intrusions, virus scanning, filtering malicious URLs or junk e-mail, blocking illegal web access, or preventing malicious data retrieval.

In general, each type of threat in content security has its own set of attributes and must be handled using a set of methods that are unique to that type of content. Therefore, these functions are characterized by unique content-specific security functions.

Attack Mitigation Capabilities

Attack mitigation capabilities are used to detect and mitigate various types of network attacks. Today's common network attacks can be defined as follows.

-DDoS attack:

Network layer DDoS attacks: SYN flood, UDP flood, ICMP flood, IP fragment flood, IPv6 routing header attack, and IPv6 duplicate address detection attack are examples.

Application layer DDoS attacks: Examples include HTTP flood, https flood, cache bypass HTTP floods, WordPress XML RPC floods, and ssl DDoS.

-Single packet attack:

Scanning and sniffing attacks: IP sweep, port scanning, etc.

Bad packet attacks: Ping of Death, Teardrop, etc.

Special packet attack: oversized ICMP, Tracert, IP time stamp option packet, etc.

Each type of network attack has its own network behavior and packet/flow characteristics. Therefore, each type of attack requires special security features that are advertised as a set of capabilities for detection and mitigation. The implementation and management of these security categories. Attack mitigation controls can be very similar to content security control categories.

Information Sub-Model for Network Security Capabilities

The purpose of the capability information sub-model is to define the concept of capabilities and to be able to aggregate capabilities into appropriate objects. Hereinafter, a sub-model of network security, content security, and attack mitigation functions will be described.

Information Sub-Model for Network Security

4 shows an example of an overview of a network security information sub-model to which the present specification can be applied.

The purpose of the Network Security Information sub-model is to define how network traffic is defined and to determine whether one or more network security functions should be applied to the traffic.

In FIG. 4, ECA policy rules are defined in an external ECA information model along with events, conditions, and action objects. The network security sub-model can extend all of these objects to define extensions to security-related ECA policy rules and (general) event, condition, and action objects.

I2NSF policy rules are a special type of policy rule in the form of event condition action (ECA). Policy rules, components of policy rules (e.g. events, conditions, actions and resolution policies, basic actions and some extensions such as external data) and optionally metadata, one-way and two-way traffic through NSF It can be applied to both.

Network Security Policy Rule Extensions

5 shows an example of extension of a network security information sub-model to which the present specification can be applied.

5 shows an example of a more detailed design of an ECA policy rule subclass included in a network security information submodel. This shows how more specific network security policies are transferred and extended from the SecurityECAPolicyRule class.

A new kind of specific network security policy can be created by following the pattern of class design.

SecurityECAPolicyRule is located at the top of the I2NSF ECA policy rule hierarchy. This rule is transferred from the (external) generic ECA policy rule and represents the specialization of these generic ECA policy rules to add security-related ECA policy rules.

SecurityECAPolicyRule includes all properties, methods, and relationships defined in the super class, and adds additional concepts necessary for network security.

The six SecurityECAPolicyRule subclasses extend the SecurityECAPolicyRule class to represent six types of Network Security ECA Policy Rules. (External) General ECAPolicyRule class can define basic information in the form of properties such as unique object ID as well as description and other necessary information.

Network Security Policy Rule Operation

The network security policy consists of one or more ECA policy rules, which are composed of the information model described above. In the simple case where the event and condition clauses are unchanged, the actions of one policy rule can invoke additional network security actions from another policy rule. Network security policy inspects traffic and performs basic processing as follows.

1. NSF evaluates the event clause of a given SecurityECAPolicyRule (which may be general or specific to security, as shown in FIG. 3). You can use the security event object to perform all or part of the evaluation described below.

If the Event clause evaluates to TRUE, the condition clause of this SecurityECAPolicyRule is evaluated. Otherwise, the execution of the SecurityECAPolicyRule is stopped and the next SecurityECAPolicyRule can be evaluated.

2. Thereafter, the conditional clause can be evaluated. All or part of the evaluation described below can be performed using the security requirements object. If the condition clause evaluates to TRUE, it is defined as "matching" SecurityECAPolicyRule. Otherwise, the execution of the SecurityECAPolicyRule is stopped and the next SecurityECAPolicyRule can be evaluated.

3. A set of tasks to be executed is retrieved, and a solution strategy is used to define the order of execution. In Step 3), the process may include the use of optional external data related to SecurityECAPolicyRule.

4. Execution can take one of three forms:

a. If more than one action is selected, the NSF can perform the action defined by the solution strategy. For example, a resolution strategy can allow only a single action (eg: FMR or LMR) to be executed, or all actions can be executed (optionally or in a specific order).

In these and other cases, the NSF function should clearly define how to execute.

You can use security action objects to perform all or part of the execution described below. If the default action is grant or mirror, the NSF first performs that function and then checks whether a particular security function is referenced in the rule. If it is “Yes”, go to Step 5. If No, traffic is allowed.

b. If there is no selected operation and there is a basic operation, the basic operation may be performed. Otherwise, nothing is done.

c. Otherwise, traffic may be denied.

5. NSF can be configured to use the referenced security function when other security functions (e.g., conditions and/or actions implied by the antivirus or IPS profile NSF) are referenced in the SecurityECAPolicyRule's action set. For example: check condition or action enforcement).

After that, the execution can be terminated.

Network Security Event Sub-Model

6 shows an example of extension of a network security information sub-model event class to which the present specification can be applied.

6 shows an example of a design of an event subclass included in a network security information submodel.

The four Event classes of FIG. 6 extend (external) general Event classes to represent important events in network security. (External) General Event class can be assumed to define basic event information in attribute form such as unique event ID, description, and date and time of event occurrence.

Network Security Condition Sub-Model

7 shows an example of extension of a network security information sub-model condition class to which the present specification can be applied.

7 shows a more detailed design of a condition subclass included in the network security information submodel.

The six condition classes shown in FIG. 7 represent conditions related to network security by extending the (external) general condition class. Since the (external) general condition class is abstract, it is assumed that data model optimization can be defined.

It is assumed that the general condition class defines basic condition information in the form of properties such as a unique object ID, description, and a mechanism to link zero or more metadata objects.

Network Security Action Sub-Model

8 shows an example of extension of a network security information sub-model action to which the present specification can be applied.

8 shows a more detailed design of the action subclass included in the network security information sub-model. The four operation classes of FIG. 8 represent tasks for performing a network security control function by extending the (external) general operation class.

The three operation classes of FIG. 8 represent tasks related to network security by extending the (external) general operation class. (External) Since Generic Action class is abstract, data model optimization can be defined.

It is assumed that a generic action class defines basic action information in the form of attributes, such as a unique object ID, description, and a mechanism to attach zero or more metadata objects.

Information Model for I2NSF Capabilities

9 shows an example of a high-level model of an I2NSF security function to which the present specification can be applied.

As shown in FIG. 9, the I2NSF functional model is composed of a number of functions representing various content security and attack mitigation functions. Each function protects against certain types of threats at the application layer.

9 shows a general I2NSF security function class called SecurityCapability. This allows you to add common properties, relationships, and behaviors to this class without affecting the design of the external metadata information model. All I2NSF security features are subclassed in the SecuritCapability class.

Information Model for Content Security Capabilities

10 shows an example of a network security function information model to which the present specification can be applied.

10 shows exemplary types of content security Generic Network Security Function (GNSF).

As shown in FIG. 10, content security may consist of a number of unique security functions. Each of these capabilities can protect content from certain types of threats at the application layer.

Content security may be a Generic Network Security Function (GNSF) type as shown in FIG. 10.

Information Model for Attack Mitigation Capabilities

11 shows an example of an attack mitigation function information model to which the present specification can be applied.

As shown in FIG. 11, attack mitigation may consist of several GNSFs. Each can protect content from certain types of network attacks. Acknowledge mitigation security is a type of GNSF that summarizes well-defined security functions.

Structure and purpose of the I2NSF security policy

One. I2NSF Security Policy Rule

I2NSF security policy rules represent policy rules for general network security functions. The object of the policy rule may be defined as policy information and rule information. This may include ECA policy rules such as Event Clause Objects, Condition Clause Objects, Action Clause Objects, Resolution Strategy and Default Action.

2. Event Clause

As discussed above, events can occur when a managed system changes and/or at an important point in the managed system's environment.

Event Clause Objects can be used to determine whether the condition clause of an I2NSF policy rule can be evaluated when used in the context of an I2NSF policy rule. The target of the event clause may be defined as a user security event, a device security event, a system security event, and a time security event. The subject of the event clause can be extended according to the specific vendor event function.

3. Condition Clause

A condition is defined as a set of attributes, functions, and/or values to be compared with a set of known attributes, features, and/or values, as described above, and may or may not execute the (imperative) I2NSF policy rule.

These objects can be defined as packet security conditions, packet payload security conditions, target security conditions, user security conditions, context conditions, and general context conditions.

Objects of Action clauses can be extended according to specific vendor condition functions.

4. Action Clause

Actions are used to control and monitor aspects of flow-based NSF when event and condition clauses are met. NSF provides security functions by executing various actions. The object of the action clause can be defined as an input action, a transmission action, and an application profile action, and the object of the action section can be extended according to a specific vendor action function.

Data model structure

Hereinafter, a data model proposed in the present specification will be described.

The structure of the data model proposed in this specification is considered as follows.

-Consideration of ECA policy model by aggregation of Event, Condition, and Action clauses

-Consideration of ability algebra.

-Consider NSF functional categories (e.g. network security, content security and attack mitigation functions).

-Definition of network security event class, network security condition class, and network security work class.

12 illustrates a data model structure for network security policy identification according to an embodiment of the present specification.

The data model for identifying the network security policy may be configured as shown in FIG. 12.

The data model for identifying the network security policy may be composed of a security policy, an event clause container, a condition clause container, and an action clause container.

The data field of the security policy contains the policy name, rules, resolution-strategy, fixed action and rule group.

The resolution strategy is used to determine how to resolve conflicts that occur between actions of the same or different policy rules that match and contain a particular NSF. The solution strategy may be defined as First Matching Rule (FMR), Last Matching Rule (LMR), Priority Matching Rule (PMRE), and Priority Matching Rule (PMRN). The solution strategy can be extended according to the specific supplier's job function. The solution strategy is described in detail in [draft-ietf-i2nsf-capability].

The default action can be used to execute the I2NSF policy rule when there is no rule matching the packet. Default action can be defined as pass, delete, reject, warning and mirror. The default action can be extended according to the specific vendor's action function. The default action is described in detail in [draf-ietf-i2nsf-capability].

The rule group is a name for identifying rules, description, priority, enable, session-aging-time, long-connection, time-intervals, event-clause-container, condition-clause-container, and action-clause for describing rules. May contain -container.

The long-connection can include enable and during to set the duration to which the rule can be applied.

In addition, the action-clause-container may include absolute-time-interval and periodic-time-interval so that a periodic time can be set in addition to the absolute time of the applied rule.

absolute-time-interval is a start-time? to set the start time and end time to set the time when the rule is applied or the time when the application ends. And end-time? It may include.

The periodic-time-interval may include day and month for setting a periodic time to which the rule is applied.

The rule-group consists of groups in which rules can be grouped and managed, and the data fields for each group include group-name, rule-range, enable, and description.

The event-clause-container, condition-clause-container and action-clause-container can be used by policy rules to aggregate “events”, “actions” and “conditions”.

13 illustrates a data model structure for an event clause according to an embodiment of the present specification.

As described above, an event refers to an event that occurs when a managed system is changed and/or at an important point in the environment of the managed system.

Objects for the event clause shown in FIG. 13 may be defined as a user security event, a device security event, a system security event, and a time security event. These objects can be extended according to specific vendor event functions, and additional event objects for more general network security functions can be added.

14A to 14G illustrate a data model structure for a condition rule according to an embodiment of the present specification.

As described above, the condition rule is defined as a set of attributes, functions and/or values to be compared with a set of known attributes, features and/or values, and may or may not execute the (imperative) I2NSF policy rule.

Objects for condition rules are packet security ipv4 condition, packet security ipv6 condition, packet security tcp condition, packet security udp condition, packet security icmp condition, packet security url-category condition, packet security voice condition, packet security ddos condition, packet security It may include payload conditions and context conditions.

The condition rule of the context may be defined as an ACL number condition, an application condition, a target condition, a user condition, and a geographic condition.

Objects for these condition rules can be extended according to specific vendor condition functions, and condition objects for more general network security functions can be added.

In addition, as shown in FIG. 14, the data model structure for condition rules may set rules related to addresses and port numbers.

In FIG. 14F, in order to manage the state of an application to which the rule can be applied, data fields of application-condition include application-description?, application-object*, application-group*, application-label*, and category.

In addition, rules may be applied according to URL (Uniform Resource Locator), and for this purpose, the data field of url-category-condition includes pre-defined-category* and user-defined-category*.

15 illustrates a data model structure for an action rule according to an embodiment of the present specification.

Action rules are used to control and monitor aspects of flow-based NSF when events and conditions are met.

The object of the action rule can be defined as an ingress action for a packet action, an egress action or a log action for a packet action, and an advanced action for further inspection. Briefing rules may be extended depending on the specific supplier action function.

In the structure of the data model for the condition rule and action rule shown in FIGS. 14A to 15, since a container structure is used, multiple conditions can be applied.

16 is an example of I2NSF IPsec (IP Security) to which the present specification can be applied. Referring to Figure 16, I2NSF IPsec will be used to define the method required to manage IPsec parameters to create IPsec Security Associations between two NSFs via the Internet Key Exchange (IKE) v2 protocol or a security controller. I can. For I2NSF IPsec, two cases are considered: an IKE case (ie, IPsec through IKE) and an IKE-less case (ie, IPsec is not through IKE, but through a security controller).

16A to 18T illustrate a YANG data module of an I2NSF NSF-Facing-Interface according to an embodiment of the present specification.

16A to 18T, a YANG data model for security policy rules of network security functions may be set.

Hereinafter, an information model for NSF monitoring will be described.

Interfaces provided by NSFs (e.g. FW, IPS, Anti-DDOS or Anti-Virus functions) to management entities (e.g. NMS, security controllers) to configure security functions This is called "I2NSF NSF-Facing Interface" (refer to ID.ietf-i2nsf-terminology).

The monitoring part means acquiring important information about the NSF. Notifications, events, records, counters. When done in a timely and comprehensive manner, NSF monitoring plays a very important role in the overall security framework. Monitoring information generated by NSF can be an early indication of malicious activity or abnormal behavior or potential signs of a denial of service attack.

NSF monitoring data can be used in the following situations.

As explained above, monitoring plays a very important role in the overall security framework. Monitoring the NSF provides very important information to the security controller in maintaining the prescribed security posture. In addition to this, there are other reasons for monitoring NSFs, such as:

-Security administrators can configure policies that trigger on specific events that occur in NSF or in the network. The security controller monitors the specified event and, when an event occurs, configures additional security functions according to policy.

-Events triggered by NSF as a result of security policy violations can be used by Security Information and Event Management (SIEM) to detect suspicious activity.

-You can use NSF's event and activity logs to build advanced analytics such as behavior and predictions to improve your security posture.

-The security controller can use NSF's events to achieve high availability. Corrective action can be taken such as failed NSF restart, NSF horizontal scaling, etc.

-NSF's event and activity logs can help in debugging and root cause analysis of operational problems.

-NSF's activity records can be used to create historical data for operational and business reasons.

Classification of NSF monitoring data

Maintaining a strong security posture requires not only configuring NSF security policies, but also continuously monitoring NSFs by consuming observable information. This allows security administrators to assess what is happening in the network in a timely manner.

It is impossible to block all internal and external threats based on the static security state. To achieve this goal, you need a very dynamic attitude with a certain level of visibility. This specification may define a set of information elements (and their scope) that can be obtained from NSF and used as monitoring information.

Essentially, this type of monitoring information can be utilized to support continuous visibility into multiple levels of granularity and can be consumed by that function.

Hereinafter, a basic information model for all monitoring data will be described.

Basic Information Model for All Monitoring Data

-message_version: It indicates the version of the data type, a 2-digit decimal number starting at 01.

-message_type: event, warning, alarm, log, counter, etc.

-time_stamp: indicates the time the message was created.

-vendor_name: The name of the NSF vendor.

-NSF_name: The name (or IP) of the NSF generating the message.

-Module_name: The name of the module that displays the message

-Severity: Indicates the level of the log. There are a total of 8 levels (from 0 to 7), and the smaller the number, the higher the severity.

Extended Information Model for Monitoring Data

The extended information model is only used for structured data such as alarms. Unstructured data is specified only as a basic information model.

System Alarm

Memory Alarm

The following information should be included in the memory alarm.

-event_name:'MEM_USAGE_ALARM'

-module_name: indicates the NSF module responsible for generating the alarm.

-usage: Specifies the amount of used memory.

-Threshold: threshold to trigger an alarm

-Severity: Risk level (e.g.: risk level, high, medium, low)

-Message: A message such as'Memory usage exceeded the threshold value' is displayed.

CPU Alarm

The following information can be included in the CPU alarm.

-event_name:'CPU_USAGE_ALARM'

-usage: Specify the amount of CPU used.

-threshold: threshold to trigger the event

-Severity: Risk level (e.g.: risk level, high, medium, low)

-Message:'CPU usage exceeded the threshold.' Prints a message such as.

Disk Alarm

The following information can be included in the disk alarm.

-event_name:'DISK_USAGE_ALARM'

-usage: Specify the amount of used disk space.

-threshold: threshold to trigger the event

-Severity: Risk level (e.g.: risk level, high, medium, low)

-Message:'Disk usage exceeded threshold.' Prints a message such as.

Hardware Alarm

The following information can be included in the hardware alarm.

-event_name:'HW_FAILURE_ALARM'

-component_name: indicates the HW component that generates this alarm.

-Threshold: threshold to trigger an alarm

-Severity: Risk level (e.g.: risk level, high, medium, low)

-Message: A message such as'Hardware component has failed or performance is degraded.' is displayed.

Interface Alarm

The following information may be included in the interface alarm.

-event_name:'IFNET_STATE_ALARM'

-interface_Name: interface name

-interface_state:'UP','DOWN','CONGESTED'

-threshold: threshold to trigger the event

-Severity: Risk level (e.g.: risk level, high, medium, low)

-Message:'Current interface status' is displayed.

System Events

Access Violation

The following information may be included in the event.

-event_name:'ACCESS_DENIED'

-user: user name

-group: the group to which the user belongs

-login_ip_address: User's login IP address

-authentication_mode: user authentication mode. For example: local authentication, third party server authentication, authentication exemption, SSO authentication

-Message:'Access is denied.' Prints a message such as.

Configuration Change

The following information may be included in the event.

-event_name:'CONFIG_CHANGE'

-user: user name

-group: the group to which the user belongs

-login_ip_address: User's login IP address

-authentication_mode: user authentication mode. For example: local authentication, third party server authentication, authentication exemption, SSO authentication

-Message: A message such as'The configuration has been modified' is displayed.

System Log

Access Logs

The access log records the administrator's login, logout, and device operation, and analyzes it to identify security vulnerabilities. Operational reports may include information such as:

-Manager: The manager who works on the device

-login_ip_address: IP address used by the administrator to log in

-login_mode: Specifies the administrator login mode (e.g.: root, user)

-operation_type: The type of operation performed by the administrator (eg: login, logout, configuration, etc.)

-Result: Result of command execution

-content: actions performed by the administrator after logging in.

Resource Utilization Logs

Running reports record the running status of the device system, which is useful for device monitoring. Implementation reports may include information such as:

-system_status: current system execution status

-CPU_usage: Specify the CPU usage.

-memory_usage: Specify the memory usage.

-disk_usage: Specifies the disk usage.

-disk_left: Specifies the available disk space.

-session_number: Specifies the total number of concurrent sessions.

-process_number: Specifies the total number of system processes.

-in_traffic_rate: Total inbound traffic rate (pps)

-out_traffic_rate: Total outbound traffic rate (pps)

-in_traffic_speed: Total inbound traffic speed (bps)

-out_traffic_speed: Total outbound traffic speed (bps)

User Activity Logs

User activity records provide visibility into the user's online history (login time, online/lockout period, and login IP address) and the actions the user is performing. User activity reports are useful for identifying exceptions during user login and network access activities.

-group: the group to which the user belongs

-login_ip_address: User's login IP address

-authentication_mode: user authentication mode. For example: local authentication, third party server authentication, authentication exemption, SSO authentication

-access_mode: user access mode. For example: PPP, SVN, LOCAL

-online_duration: online period

-lockout_duration: lockout period

-Type: User activity. Successful User Login, Failed Login Attempt, User Logout, Successful User Password Change, Failed User Password Change, User Lock, User Unlock, Unknown

-Cause: User action failed.

System Counter

Interface counters

Interface counters provide visibility into traffic to and from NSF and bandwidth usage.

-interface_name: Network interface name configured in NSF

-in_total_traffic_pkts: All inbound packets

-out_total_traffic_pkts: Total outbound packets

-in_total_traffic_bytes: Total inbound bytes

-out_total_traffic_bytes: total outbound bytes

-in_drop_traffic_pkts: Total inbound drop packets

-out_drop_traffic_pkts: Total outbound drop packets

-in_drop_traffic_bytes: Total inbound drop bytes

-out_drop_traffic_bytes: total outbound drop bytes

-in_traffic_ave_rate: Average inbound traffic rate (pps)

-in_traffic_peak_rate: Peak rate of inbound traffic (pps)

-in_traffic_ave_speed: Average speed of inbound traffic (bps)

-in_traffic_peak_speed: Maximum speed of inbound traffic (bps)

-out_traffic_ave_rate: Outbound traffic average rate (pps)

-out_traffic_peak_rate: Outbound traffic peak rate (pps)

-out_traffic_ave_speed: Outbound traffic average speed (bps)

-out_traffic_peak_speed: Maximum outbound traffic speed (bps)

NSF Events

The DDos event may include the following information.

-event_name:'SEC_EVENT_DDoS'

-sub_attack_type: Syn flood, ACK flood, SYN-ACK flood, FIN / RST flood, TCP connection flood, UDP flood, Icmp flood, HTTPS flood, HTTP flood, DNS query flood, DNS reply flood, SIP flood, etc.

-dst_ip: IP address of the victum being attacked

-dst_port: The port number targeting traffic.

-start_time: A time stamp indicating the start time of the attack

-end_time: A timestamp indicating the time when the attack ended. If the attack still occurs when sending an alert, this field may be blank.

-attack_rate: PPS of attack traffic

-attack_speed: bps of attack traffic

-rule_id: The ID of the rule being triggered.

-rule_name: the name of the triggered rule

-Profile: The security profile to which the traffic is matched.

Session table event

The following information may be included in the session table event.

-event_name:'SESSION_USAGE_HIGH'

-current: number of concurrent sessions

-max: the maximum number of sessions the session table can support

-threshold: threshold to trigger the event

-Message:'The number of session tables exceeded the threshold.'

Virus Event

The following information can be included in the virus event.

-event_Name:'SEC_EVENT_VIRUS'

-virus_type: Virus type (eg Trojan horse, worm, macro) Virus type, virus name

-dst_ip: Destination IP address of the packet where a virus was found

-src_ip: Source IP address of the packet where the virus was found

-src_port: Source port of packet where virus was found

-dst_port: Destination port of the packet where virus was found

-src_zone: Source security area of the packet in which the virus was found

-dst_zone: Target security area of the packet in which a virus is found

-file_type: The type of file where the virus is hidden

-file_name: The name of the file where the virus is hidden

-virus_info: Brief introduction of virus

-raw_info: Information describing the packet that triggers the event.

-rule_id: ID of the triggered rule.

-rule_name: The name of the triggered rule

-Profile: This is a security profile with matching traffic.

Intrusion Event

-The Intrustion Event must contain the following information:

-event_name: Event name:'SEC_EVENT_Intrusion'

-sub_attack_type: type of attack, e.g. brutal force, buffer overflow

-src_ip: the source IP address of the packet

-dst_ip: destination IP address of the packet

-src_port: the source port number of the packet

-dst_port: The destination port number of the packet

-src_zone: The source security zone of the packet

-dst_zone: the target security zone of the packet

-Protocol: Transport layer protocol used, e.g. TCP, UDP

-app: adopted application layer protocol (eg: HTTP, FTP)

-rule_id: ID of the triggered rule.

-rule_name: the name of the triggered rule

-Profile: Security profile with matching traffic

-intrusion_info: Brief description of the intrusion

-raw_info: Information describing the packet that triggers the event.

Botnet Event

The following information can be included in the botnet event.

-event_name: Event name:'SEC_EVENT_Botnet'

-botnet_name: The name of the detected botnet

-src_ip: Source IP address of the packet

-dst_ip: destination IP address of the packet

-src_port: The packet's source port number

-dst_port: The destination port number of the packet

-src_zone: The source security area of the packet

-dst_zone: The target security zone of the packet

-Protocol: Transport layer protocol used, e.g. TCP, UDP

-app: adopted application layer protocol (e.g. HTTP, FTP)

-Role: The role of the communication party in the botnet:

1. Packets from zombie host to attacker

2. Packets from the attacker to the zombie host

3. Packet from IRC / WEB server to zombie host

4. Packet sent from zombie host to IRC / WEB server

5. Packet sent from attacker to IRC / WEB server

6. Packet from IRC / WEB server to attacker

7. Packets from zombie host to victim

-botnet_info: Brief description of Botnet

-rule_id: ID of the triggered rule.

-rule_name: The name of the triggered rule

-Profile: Security profile with matching traffic

-raw_info: Information describing the packet that triggers the event

Web Attack Event

The following information can be included in the web attack event.

-event_name: Event name:'SEC_EVENT_WebAttack'

-sub_attack_type: specific web attack type (e.g. sql injection, command injection, XSS, CSRF)

-src_ip: Source IP address of the packet

-dst_ip: destination IP address of the packet

-src_port: The packet's source port number

-dst_port: The destination port number of the packet

-src_zone: The source security area of the packet

-dst_zone: The target security zone of the packet

-req_method: The method of the requirement. For example'PUT' or'GET' in HTTP

-req_url: requested URL

-url_category: Matching URL category

-filtering_type: blacklist, whitelist, user-defined, predefined, malicious category, unknown URL filtering type

-rule_id: ID of the triggered rule.

-rule_name: The name of the triggered rule

-Profile: This is a security profile with matching traffic.

NSF Logs

DDoS Logs

In addition to the fields of the DDoS alert, the following information can be included in the DDoS log in addition to the fields.

-Attack type: DDoS

-attack_ave_rate: average pps of attack traffic within the recorded time

-attack_ave_speed: average bps of attack traffic within the recorded time

-attack_pkt_num: number of attack packets within the recorded time

-attack_src_ip: This is the source IP address of attack traffic. If you have a large amount of IP addresses, choose a certain number of resources according to different rules.

-Action: Actions on DDoS attacks (eg: allow, warning, block, discard, declare, block IP, block service).

Virus Logs

In addition to the fields of the virus alert, the following information may be included in the virus log,

-Attack type: Virus

-Protocol: Transport layer protocol

-app: The name of the application layer protocol

-times: Virus detection time

-Action: Action to deal with viruses (e.g. warning, block)

-os: OS affected by the virus (eg all, android, ios, unix, windows).

Intrusion Logs

In addition to the intrusion alert fields, the following information may be included in the intrusion log.

-Attack type: Intrusion

-Time: An intrusion time occurred at the recorded time.

-os: OS that affects intrusion (eg: all, android, ios, unix, windows).

-Action: Actions dealing with intrusion, such as allow, warning, block, discard, declare, block IP, block service

-attack_rate: pps NUM of attack traffic

-attack_speed: bps of NUM attack traffic

Botnet Logs

In addition to the fields of Botnet Alarm, the following information can be included in the botnet log.

-attack_type: botnet

-botnet_pkt_num: Number of packets sent or received by the detected botnet

-Action: Action to process detected packet (e.g. allow, warning, block, discard, declare, block IP, block service, etc.

-os: All OSs targeted for attack, e.g. android, ios, unix, windows, etc.

DPI Logs

DPI logs provide statistics on uploaded and downloaded files and data, emails sent and received, and can alert and block records on websites.

-Type: DPI task type. Example: file blocking, data filtering, application behavior control

-file_name: file name

-file_type: file type

-src_zone: Traffic source security zone

-dst_zone: Target security zone for traffic

-src_region: Traffic source area

-dst_region: Target area of traffic

-src_ip: Traffic source IP address

-src_user: User who generated the traffic

-dst_ip: Target IP address of traffic

-src_port: Traffic source port

-dst_port: Destination port of traffic

-Protocol: Protocol type of traffic

-app: The name of the application layer protocol

-policy_id: Security policy ID to which traffic matches

-policy_name: Security policy name to which traffic matches

-Action: This is an action defined in the file blocking rule, data filtering rule, or application program action control rule with matching traffic.

Vulnerabillity search log

The victim host and related vulnerability information should be recorded in the vulnerability search log. The following information should be included in the report.

-victim_ip: IP address of victim host with vulnerability

-Vulnerability ID: Vulnerability ID

-vulnerability_level: vulnerability level. Example: high, low, low

-Operating system: Operating system of target host

-Service: Service that is vulnerable to victim host

-protocol: Protocol type. Example: TCP, UDP

-port: port number

-vulnerability_info: Information on vulnerability

-fix_suggestion: Suggestion to fix vulnerability.

-8.6.7. Web attack log

-In addition to the fields of the web attack alert, the following information should be included in the web attack report.

-attack_type: web attack

-rsp_code: Response code

-req_clientapp: Client application

-req_cookies: cookies

-req_host: domain name of the requested host

-raw_info: Information describing the packet that triggers the event.

NSF Counter

Firewall Counters

Firewall counters provide visibility into traffic signatures, bandwidth usage, and how configured security and bandwidth policies have been applied.

-src_zone: Traffic source security zone

-dst_zone: Target security zone for traffic

-src_region: Traffic source area

-dst_region: Target area of traffic

-src_ip: Traffic source IP address

-src_user: User who generated the traffic

-dst_ip: Target IP address of traffic

-src_port: Traffic source port

-dst_port: Destination port of traffic

-Protocol: Protocol type of traffic

-app: The name of the application layer protocol

-policy_id: Security policy ID to which traffic matches

-policy_name: Security policy name to which traffic matches

-in_interface: Inbound interface of traffic

-out_interface: Outbound interface of traffic

-total_traffic: Total traffic volume

-in_traffic_ave_rate: Average inbound traffic rate (pps)

-in_traffic_peak_rate: Peak rate of inbound traffic (pps)

-in_traffic_ave_speed: Average speed of inbound traffic (bps)

-in_traffic_peak_speed: Maximum speed of inbound traffic (bps)

-out_traffic_ave_rate: Outbound traffic average rate (pps)

-out_traffic_peak_rate: Outbound traffic peak rate (pps)

-out_traffic_ave_speed: Outbound traffic average speed (bps)

Policy Hit Counters

The policy hit counter records the number of hits and the security policy that traffic matches. You can verify that the policy configuration is correct.

-src_zone: Traffic source security zone

-dst_zone: Target security zone for traffic

-src_region: Traffic source area

-dst_region: Target area of traffic

-src_ip: Traffic source IP address

-src_user: User who generated the traffic

-dst_ip: Target IP address of traffic

-src_port: Traffic source port

-dst_port: Destination port of traffic

-Protocol: Protocol type of traffic

-app: The name of the application layer protocol

-policy_id: Security policy ID to which traffic matches

-policy_name: Security policy name to which traffic matches

-hit_times: The number of times the security policy matches the specified traffic.

19A to 19F illustrate Extensible Markup Language (XML) configuration of low-level security policy rules according to an embodiment of the present specification.

19A to 19F, as security requirements, NSF may include a general firewall, a time-based firewall, a URL filter, a VoIP/VoLTE filter, and a function of mitigating floods of http and https.

As an example of a security policy rule, the following security requirements may be included.

(I) Blocking access to SNS during business hours, (ii) Blocking malicious VoIP/VoLTE packets entering the company, (iii) Mitigating http and https floods to the company's web server

Security Requirement 1: Block SNS Access during Business Hours

19A and 19B illustrate configuration XML of a time-based firewall and web filter for blocking SNS access during business hours.

Two NSFs (i.e., time-based firewall and a web filter) can be used as the security requirements cannot be met by one NSF.

A time-based firewall can do the following:

1) The name of the system policy is sns_access.

2) The name of the rule is block_sns_access_stiming_operation_time.

3) Rules may be in effect during business hours (eg, 9 am to 6 pm).

4) This rule can check the source IPv4 address (ie 221.159.112.1~221.159.112.90) to check the packets sent by employees.

5) If the transmitted packet matches the above rule, the time-based firewall cannot inspect the contents of the packet for the SNS URL, and thus can transmit the packets to the Web Filter for additional inspection.

Web Filter can follow:

1. The name of the system policy is sns_access.

2. The name of the rule is block_facebook_and_instagram.

3. This rule can block access packets to Facebook or Instagram by examining the URL address.

4. If the transmitted packet matches the above rules, the packet is blocked.

Security Requirement 2: Block Malicious VoIP/VoLTE Packets Coming to a Company

19C and 19D illustrate a configuration for blocking malicious VoIP/VoLTE packets entering a company.

Two NSFs (ie, a general firewall and a VoIP/VoLTE filter) can be used as the security requirement cannot be met by one NSF.

General Firewall can:

1) The name of the system policy is voip_volte_inspection.

2) The name of the rule is block_malicious_voip_volte_packets.

3) This rule can check the originating IPv4 address (ie 221.12.12.1 ~ 221.12.12.10.90) to check the packets coming into the company.

4) This rule can check port numbers (ie 5060 and 5061) to check VoIP/VoLTE packets.

5) If the incoming packet matches the above rule, the General Firewall cannot inspect the contents of the VoIP/VoLTE packet, so it can send the packet to the VoIP/VoLTE filter for additional inspection.

VoIP/VoLTE Filter can follow the following.

1. The name of the system policy is malicious_voice_id.

2. The name of the rule is block_malicious_voice_id.

3. This rule can block malicious VoIP/VoLTE packets (ie 11111@voip.black.com and 22222@voip.black.com ) by examining the voice ID of VoIP/VoLTE packets.

4. If the incoming packet matches the above rule, the packet can be blocked.

Security Requirement 3: Mitigate HTTP and HTTPS Flood Attacks on a Company Web Server

19E and 19F illustrate a configuration for mitigating malicious http and https flood attacks with a company web server to which the present specification can be applied.

Two NSFs (i.e., a general firewall and a http and https flood attack mitigation) can be used as the security requirement cannot be satisfied by one NSF.

General Firewall can:

1) The name of the system policy is flood_attack_mitigation.

2) The name of the rule is mitigate_http_and_https_flood_attack.

3) This rule can check the starting IPv4 address (ie 221.159.112.95) to check the access packet coming into the company web server.

4) This rule can check port numbers (ie, 80 and 443) to check http and https packets.

5) If the incoming packet matches the above rule, the General Firewall cannot control the amount of http and https packets, so it can forward the packet to http and https flood attack mitigation for additional inspection.

HTTP and HTTPS Flood Attack Mitigation can follow:

1. The name of the system policy is http_and_https_flood_attack_mitigation.

2. The name of the rule is 100_per_second.

3. This rule can control http and https packets corresponding to the amount of incoming packets.

4. If the incoming packet matches the above rule, the packet can be blocked.

The information model, the data model, and the YANG data model described in FIGS. 1 to 19F may be selectively combined and used.

20 is an embodiment to which the present specification may be applied.

Referring to FIG. 20, the network operation management system receives a high-level first security policy from an Interface to Network Security Functions (I2NSF) user (S2010).

The network operation management system receives an available security service from the developer management system (S2020).

The network operation management system generates a second security policy of a low-level corresponding to the first security policy based on the security service (S2030). For example, the second security policy may include a policy rule to be applied, and basic operation information indicating an operation for a general security function. In addition, the policy information and the rule information include an event clause indicating a system change, a condition clause indicating an application condition of the policy rule, and a security performed when the event clause and the condition clause are satisfied. It may contain an Action Clause that represents the function. In addition, the policy rule may further include information related to a range of IP addresses to be matched.

The network operation management system transmits a packet including the second security policy for setting the generated second security policy to each of a plurality of Network Security Functions (NSFs) to the NSF instance (S2040). In more detail, the network operation management system and each of the plurality of NSFs are connected through an I2NSF NSF-facing interface, and the second security policy includes at least one of 1) blocking access to SNS during business hours, and 2) malicious Voice over Internet (VoIP). Protocol) or malicious Voice over LTE (VoLTE) packets, or 3) for mitigating the flood of http and https to the corporate web server.

For example, if the second security policy is for blocking access to SNS during the business hours, the policy rule is time information for applying the policy rule only to the business hours and source IP for checking the transmission packet. It may further include an address, and when a transmission packet matches the time information and the source IP address, if the URL (Uniform Resource Locator) address of the transmission packet is a preset URL address of a specific SNS, the transmission of the transmission packet Can be blocked.

In addition, when the second security policy is for blocking the malicious VoIP or the malicious VoLTE packet, the policy rule further includes 1) an IP address and 2) a port number to which the malicious VoIP or malicious VoLTE packet is received. Can include. When a packet received by 1) the IP address and 2) the port number are matched, reception of a packet matching the voice ID of the malicious VoIP or the malicious VoLTE packet may be blocked.

In addition, when the second security policy is to mitigate the flood of http and https to the company web server, the policy rule is 1) IP address and 2) of the packet received by the company web server. You can include more port numbers. 1) When the IP address and 2) the packet received by the port number are matched, when the packet received by the company web server exceeds an allowable reception rate per hour, the packet received by the company web server is It can be blocked.

The embodiments described above are those in which components and features of the present specification are combined in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented in a form that is not combined with other components or features. In addition, it is possible to configure the embodiments of the present specification by combining some components and/or features. The order of operations described in the embodiments of the present specification may be changed. Some configurations or features of one embodiment may be included in other embodiments, or may be replaced with corresponding configurations or features of other embodiments. It is apparent that claims that do not have an explicit citation relationship in the claims may be combined to constitute an embodiment or may be included as a new claim by amendment after filing.

The embodiments according to the present specification may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of implementation by hardware, an embodiment of the present specification includes one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), and FPGAs ( field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, etc.

In the case of implementation by firmware or software, an embodiment of the present specification may be implemented in the form of a module, procedure, function, etc. that perform the capabilities or operations described above. The software code can be stored in a memory and driven by a processor. The memory may be located inside or outside the processor, and may exchange data with the processor through various known means.

It is obvious to those skilled in the art that the present specification may be embodied in other specific forms without departing from the essential features of the present specification. Therefore, the above detailed description should not be construed as restrictive in all respects, but should be considered as illustrative. The scope of this specification should be determined by reasonable interpretation of the appended claims, and all changes within the equivalent scope of this specification are included in the scope of this specification.

The present specification can be applied to various security management systems.

Claims (20)

In a method for a network operation management system to provide a security service in a security management system,
Receiving a high-level first security policy from an Interface to Network Security Functions (I2NSF) user;
Receiving, from a developer management system, available security services;
Generating a second low-level security policy corresponding to the first security policy based on the security service; And
Transmitting a packet including the second security policy for setting the generated second security policy to each of a plurality of Network Security Functions (NSFs) to an NSF instance; Including,
Each of the network operation management system and the plurality of NSFs is connected by an I2NSF NSF-facing interface, and the second security policy includes at least one or more 1) blocking SNS access during business hours, 2) malicious Voice over Internet Protocol (VoIP) or Blocking malicious Voice over LTE (VoLTE) packets or 3) mitigating the flood of http and https to corporate web servers. The method of claim 1,
The second security policy includes a policy rule to be applied, and basic operation information indicating an operation for a general security function. The method of claim 2,
The policy rule includes policy information and rule information,
The policy information and the rule information include an event clause indicating a system change, a condition clause indicating an application condition of the policy rule, and a security function performed when the event clause and the condition clause are satisfied. How to include an Action Clause to indicate. The method of claim 3,
Based on the second security policy for blocking SNS access during the business hours,
The policy rule further includes time information for applying the policy rule only to the business hours and a source IP address for inspecting a transmission packet. The method of claim 4,
Based on the time information and the source IP address,
When the URL (Uniform Resource Locator) address of the transmission packet is a predetermined URL address of a specific SNS, the transmission of the transmission packet is blocked. The method of claim 3,
Based on the second security policy for blocking the malicious VoIP or the malicious VoLTE packet, the policy rule further includes 1) an IP address and 2) a port number to which the malicious VoIP or malicious VoLTE packet is received. , Way. The method of claim 6,
1) based on the IP address and 2) the port number,
Blocking a packet matching the voice ID of the malicious VoIP or the malicious VoLTE packet. The method of claim 3,
Based on the second security policy to mitigate the flood of http and https to the company web server,
The policy rule further includes 1) an IP address and 2) a port number of a packet received by the company web server.
The method of claim 8,
1) based on the IP address and 2) the port number,
When the packet received by the company web server exceeds an allowable reception rate per hour, the method of blocking the packet received by the company web server.
The method of claim 3,
The policy rule further includes information related to a range of IP addresses to be matched. In a security management system for providing a security service,
An Interface to Network Security Functions (I2NSF) user who creates a high-level first security policy;
A developer management system that provides security services;
Receiving the first security policy from the I2NSF user, receiving the security service from the developer management system, based on the security service, a second low-level corresponding to the first security policy A network operation management system for generating a security policy and transmitting a packet including the second security policy for setting the generated second security policy to each of a plurality of Network Security Functions (NSFs) to an NSF instance; And
Including a plurality of NSF (Network Security Function) for receiving the second security policy from the security management system,
Each of the network operation management system and the plurality of NSFs is connected by an I2NSF NSF-facing interface, and the second security policy includes at least one or more 1) blocking SNS access during business hours, 2) malicious Voice over Internet Protocol (VoIP) or A security management system, including blocking malicious Voice over LTE (VoLTE) packets or 3) mitigating the flood of http and https to corporate web servers. The method of claim 11,
The second security policy is a security management system including a policy rule to be applied, and basic operation information indicating an operation for a general security function. The method of claim 12,
The policy rule includes policy information and rule information,
The policy information and the rule information include an event clause indicating a system change, a condition clause indicating an application condition of the policy rule, and a security function performed when the event clause and the condition clause are satisfied. A security management system that includes an Action Clause to indicate. The method of claim 13,
Based on the second security policy for blocking access to SNS during the business hours, the policy rule further includes time information for applying the policy rule only to the business hours and a source IP address for inspecting a transmission packet. That, the security management system. The method of claim 14,
Based on the time information and the source IP address,
When the URL (Uniform Resource Locator) address of the transmission packet is a predetermined URL address of a specific SNS, the transmission of the transmission packet is blocked. The method of claim 13,
Based on the second security policy for blocking the malicious VoIP or the malicious VoLTE packet, the policy rule further includes 1) an IP address and 2) a port number to which the malicious VoIP or malicious VoLTE packet is received. , Security management system. The method of claim 16,
1) based on the IP address and 2) the port number,
Blocking packets matching the voice ID of the malicious VoIP or the malicious VoLTE packet. The method of claim 13,
Based on the second security policy for mitigating the flood of http and https to the company web server, the policy rule is 1) IP address and 2) port number of the packet received by the company web server. Further comprising a, security management system. The method of claim 18,
1) based on the IP address and 2) the port number,
When a packet received by the company web server exceeds an allowable reception rate per hour, a packet received by the company web server is blocked. The method of claim 13,
The policy rule further includes information related to a range of IP addresses to be matched.

Images