ONOS Security proposal

SRI International/KAIST security proposal for ONOS- targeted for Cardinal release

Transcript

1. ONOS Security: Conservative-mode Phillip Porras (porras@csl.sri.com) Martin Fong (mwfong@csl.sri.com) Seungwon Shin (claude@kaist.ac.kr) Changhoon Yoon (chyoon87@kaist.ac.kr) SRI International KAIST Feature proposal
2. Motivation ONOS applications are granted a powerful authority Can perform any network operations desired Install flow rules! Read flow statistics! … Modify network topology!? ONOS Network View App 2 control plane data plane Northbound API Southbound API IntentService .submit(A,B) DeviceProviderService .deviceDisconnected(SW1) A B SW1 SW2 A B SW1 SW2 Mission-critical applications may be affected App 1
3. Offer a new option for granting the true minimum required capability to ONOS applications (Least-privileged) Let the network operators know what each ONOS application is capable of Conservative-mode ONOS: The Objectives
4. Conservative-mode ONOS: Permission model (1) Bundle-level Role-based Access Control (2) Application-level Role-based Access Control (3) API-level Permission-based Access Control ONOS applications must ONLY access the NB APIs and other necessary utilities Non-administrative ONOS applications must NOT access the Administrative NB APIs (Admin Services) ONOS application must be granted a permission to make each API call
5. Conservative-mode ONOS: Policy file (example) (1) Bundle-level Role-based Access Control (2) Application-level Role-based Access Control (3) API-level Permission-based Access Control (1) (2) (3) <type> : a bundle is an ONOS application or NOT <role> : an ONOS application is administrative app or NOT <uses-permission> : a list of permissions to be granted to an ONOS app bundle
6. Thank you!
7. Backup