I2NSF NSF monitoring YANG data model

1. A processor-implemented method for a security controller comprising a processor to monitor in an Interface to Network Security Functions (I2NSF) system, the method comprising:

receiving, by the processor, a first security policy of a high-level from an I2NSF user via a consumer-facing interface, the first security policy including a policy triggered in a specific event occurring in the I2NSF;

translating, by the processor, the first security policy into a second security policy of a low-level;

transmitting, by the processor, to a Network Security Function (NSF), a packet including the second security policy, for configuring the second security policy to the NSF; and

receiving, by the processor, monitoring data from the NSF via an NSF monitoring interface,

wherein an information model of the monitoring data for the NSF specifies a list of events that can trigger event-condition-action (ECA) policy,

wherein the ECA policy represents a model for designing a policy rule of the I2NSF system,

wherein the policy rule of the I2NSF system includes an event clause related to a change in a system, a condition clause for determining whether the policy rule of the I2NSF system can be executed or not, and an action clause being used to control and monitor aspects of the NSF to handle packets or flows when the event clause and the condition clause are satisfied, and

wherein the monitoring data includes time stamp information, a vendor name, an NSF name, and severity indicating a level of a log.

2. The method of claim 1 , wherein the monitoring data includes an alarm, an alert, an event, a log, or a counter.

3. The method of claim 2 , wherein the monitoring data further includes alarm information related to a component of the I2NSF system, and

wherein the component includes a memory, a CPU, a disk, a hardware, and an interface.

4. The method of claim 2 , wherein the monitoring data further includes event information related to the I2NSF system or event information detected in the NSF.

5. The method of claim 2 , wherein the monitoring data further includes log information related to the I2NSF system or log information of the NSF.

6. The method of claim 2 , wherein the monitoring data further includes counter information related to the I2NSF system or counter information related to the NSF.

7. The method of claim 4 , wherein the event information detected in the NSF is generated based on the first security policy.

8. The method of claim 2 , further comprising transmitting the monitoring data to the I2NSF user.

9. The method of claim 8 , further comprising transmitting the monitoring data to a developer's management system.

10. A security controller for monitoring in an Interface to Network Security Functions (I2NSF) system, the security controller comprising:

a transceiver; and

a processor configured to functionally control the transceiver,

wherein the processor is configured to:

receive a first security policy of a high-level from an I2NSF user via a consumer-facing interface, the first security policy including a policy triggered in a specific event occurring in the I2NSF system;

translate the first security policy to a second security policy of a low-level;

transmit, to a Network Security Function (NSF), a packet, including the second security policy, for configuring the second security policy to the NSF; and

receive monitoring data from the NSF via an NSF monitoring interface,

wherein an information model of the monitoring data for the NSF specifies a list of events that can trigger event-condition-action (ECA) policy,

wherein the ECA policy represents a model for designing a policy rule of the I2NSF system,

wherein the policy rule of the I2NSF system includes an event clause related to a change in a system, a condition clause for determining whether the policy rule of the I2NSF system can be executed or not, and an action clause being used to control and monitor aspects of the NSF to handle packets or flows when the event clause and the condition clause are satisfied, and

wherein the monitoring data includes time stamp information, a vendor name, an NSF name and severity indicating a level of a log.

11. The security controller of claim 10 , wherein the monitoring data includes an alarm, an alert, an event, a log, or a counter.

12. The security controller of claim 11 , wherein the monitoring data further includes alarm information related to a component of the I2NSF system, and

wherein the component includes a memory, a CPU, a disk, a hardware, and an interface.

13. The security controller of claim 11 , wherein the monitoring data further includes event information related to the I2NSF system or event information detected in the NSF.

14. The security controller of claim 11 , wherein the monitoring data further includes log information related to the I2NSF system or log information of the NSF.

15. The security controller of claim 11 , wherein the monitoring data further includes counter information related to the I2NSF system or counter information related to the NSF.

16. The security controller of claim 13 , wherein the event information detected in the NSF is generated based on the first security policy.

17. The security controller of claim 11 , wherein the processor is configured to transmit the monitoring data to the I2NSF user.

18. The security controller of claim 17 , wherein the processor is configured to transmit the monitoring data to a developer's management system.