This is an old revision of the document!
Moon OPNFV Security Management System
Proposed name for the project: Moon OPNFV Security Management System
Proposed name for the repository: moon
Project Categories: Collaborative Development
This project proposes a security management system called Moon. NFV uses cloud computing technologies to virtualize the resources and automate the control.
The cloud infrastructure is able to provision a set of different cloud resources/services for VNFs (Virtualized Network Functions).
Management of isolation and protection of, and interaction between, these VNFs become a big challenge. In order to avoid losing control over the VNFs in the cloud, Moon aims at designing and developing a security management system for OPNFV.
We can create security managers to protect different layers of the NFV infrastructure, and choose various security project mechanisms “a la cart” to enforcement related security managers.
A security management system integrates mechanisms of different security aspects. This project will firstly propose security manager that specifies users’ security requirements.
It will also enforce the security managers through various mechanisms like authorization for access control, firewall for networking, isolation for storage, logging for tractability, etc.
No centralized control: The OpenStack platform is divided into different services, like Nova for computing, Swift for storage, etc. Each service uses a configuration file with the corresponding security policy. For SND controllers, there exists another control system. For the OPNFV platform, it lacks a synchronization mechanism between these configuration and control systems in order to build a consistent and End-to-End protection system.
No dynamic control: Currently, the authentication and authorization in OpenStack are achieved through the token mechanism, but there isn’t any token revocation mechanism. Once a user gets an authorization token, we will not have any control over the user. It lacks dynamic control at runtime in OpenStack and/or SDN controllers.
No customization and flexibility: Each user of OpenStack and/or SND controllers consumes their resource pool in their own manner, but it lacks customization for security management system integration. For example, in both OpenStack and OpenDaylight, user cannot define their own security policy for each VNF resource pool.
No fine-granularity: Finally, the granularity of authorization in OpenStack and/or SDN controllers is not enough fine. Currently, it’s at the API
-level. This means that we can authorize or deny a user from using an API
like launch VM in OpenStack. But we need the granularity to be pushed to the resource-level, authorize or deny a user from using a specific resource through the API
, e.g. allowing a user to launch a dedicated VNF VM.
This project works on a security management system to monitor, control and manage VNFs based on the OpenStack infrastructure:
The first draft code of moon is available over:
Committers and Contributors
Ruan HE (firstname.lastname@example.org)
Jamil CHAWKI (email@example.com)
Loic LAGADEC (firstname.lastname@example.org)
Ashutosh Dutta (email@example.com)
Marcel Winandy (firstname.lastname@example.org)
Test suite for continuous integration will be developped.
In the first release we will provide a light-weight security management with only authorization, log as protection mechanisms for all the created VNFs and the whole infrastructure.
Proposed Release Schedule:
Moon OPNFV Rel 2 timeframe: 2S 2015