A Network Security Function (NSF) is a function that makes sure of the integrity, confidentiality and availability of network communications, to detect unnecessary network activity, or to stop or at least reduce the efficiencies of unusual activities. NSF’s are offered and consumed in rapidly varied environments. Users can utilise network security services given by NSF hosted by one or more providers that may be their own enterprise, service providers, or a combination of both. In a similar way, service providers might provide network security services, which are given by multiple security products, functions from various vendors, or open source technologies. NSF’s might be offered by physical or virtualised infrastructure. Without standard interfaces to look after the behavior of NSF’s, it has become almost impossible for the providers of security services to automate service that provides different security functions against different vendors.
The main aim of 12NSF in looking to describe a set of software interfaces and data models for controlling and monitoring characteristics of physical and non-physical NSF is to enable clients to specify rule sets. In case a working group comes across the work on an information model prior to the data models, to offer guidance, and find out the data models, it might do so. The working group can decide later if the information model has to be published as an RFC. Other characteristics of NSF’s like device or network provisioning and configuration, are out of scope. As there are various vendors or open source technologies to support many features and functions on their devices, 12 NSF will have to concentrate on flow based NSF’s, which offer cure to packets/flows like Intrusion protection or Detection system (IPS or IDS), web filtering, flow filtering, deep packet checking, or pattern matching as well as remediation. Controlling and monitoring characteristics of NSF’s involve the capability to tell rules, (via a single controller on the first phase), query, and monitor NSF’s through one or more management entities. The starting phase of I2NSF will only see to the one single controller, which can specify or alter rules to NSFs, as multiple headed controls need the co-ordination to prevent potential conflict of rules. The NSFs might be monitored via variety of the entities; however, the database update and synchronization among multiple management entities are not in the scope of I2NSF. I2NSF can specify interfaces at the two different levels of control and monitoring of network security functions.
0 Comments
Leave a Reply. |
|