This is a wiki page that captures the intent and planned/ongoing actions for the support of security coordination in ONAP.
...
The ONAP security work is split into two parts. The management of identified vulnerabilities, which is handled by the vulnerability management sub-committee and the coordination and identification of necessary security related activities which is handled by the security sub-committee.
Vulnerability management
...
Vulnerability management covers how to handle the reception of an identified vulnerability through to solution and communication of the vulnerability. The process is initiated by the reception of an email to onap-security@lists.onap.org. The vulnerability management procedures can be found here: ONAP Vulnerability Management.The vulnerability management procedures are executed on by the vulnerability management sub-committee
Release Vulnerabilities
This lists the vulnerabilities reported for each Release.
ONAP security sub-committee
...
The ONAP security sub-committee meeting logistics are:
- Time: Wednesday 15:00 - 16:00 Central European time [ 6AM - 7AM PST]Tuesdays 1 PM UTC time
- Zoom details:793296315
- Or iPhone one-tap (US Toll): +16465588656,793296315# or +14086380968,793296315#
- Or Telephone:
- Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
- Meeting ID: 793 296 315924 1503 6769
International numbers available: https://zoom.us/zoomconference?m=Meh_TwQwIDnJKy9MU9R_A8hFaAUbegBa
...
Security sub-committee recommendations can be found here: Security Sub-Committee Recommendations
Backlog
...
Creation of a Vulnerability Management Procedures and Team.
...
Done. Activity Closed.
...
Nexus IQ/Sonatype LCM has the ability to identify and display known vulnerabilities of used components. These used components are in the end part of the ONAP release and it is not desirable to release with known vulnerabilities.
A proposal needs to be created to bring to the TSC to address how to work-through the known vulnerabilities and relate it to the project release plan.
...
Nexus IQ/Sonatype LCM is ready for use and the results can be made available.
Status: Proposing to TSC
...
https://github.com/linuxfoundation/cii-best-practices-badge
This may identify good practices, which could include guidelines. consider, Ensure least privilege by design), consider how to look at code scaning into the integration processes.
Also look at:
- https://wiki.opnfv.org/display/security/Security+Home
- https://wiki.opnfv.org/display/security/Opnfv-security-guide
...
Done.
The security subcommittee recommends a gold level.
Included in the S3P recommendations.
...
JIRA project for issue prioritization: https://jira.onap.org/projects/SECCOM/
...
Identify and propose a process for static vulnerability scans
Information can be found on: https://wiki.onap.org/display/DW/ONAP+security+Recomendation+Development
...
Recommendation: Coverity is used, and included as part of the CI/CD tool chain with weekly mails to the PTLs, with seccom support in analysis.
Status: proposing to TSC
...
Proposed architecture and proposal for handling credentials in ONAP
Information can be found on: https://wiki.onap.org/display/DW/ONAP+security+Recomendation+Development
...
Completed. Credential management and secret storage service will be part of the AAF project scope..
...
wondering if the Security subcommittee would find it helpful to the community to document the various attack surfaces that ONAP has and to identify what, if any tooling, counter-measures, etc exist for each, what has been covered, what is a continued gap, etc. Such attack surfaces are:
- South-bound interfaces - communication with controllers, EMSs, VIMs, VNFs, etc. What authentication, authorization, and encryption are or can be put in place for these interfaces?
- East/West interfaces - communication with other orchestrators, VNFCs, etc. ""
- North-bound interfaces - Portal access, External API access, etc.
- Component/Upgrade Security. How to ensure each ONAP component is an authentic part of the ONAP system? How to allow, but secure component upgrades?
... etc. Those are in addition to what we know we are already focused on such as:
- ONAP code vulnerabilities
- 3rd Party component published vulnerabilities (CVEs)
Given the broad scope of "ONAP Security", would we find it helpful to spell out all the different types of security that we can imagine when dealing with this system, prioritizing what are most important, identifying where we have good/medium/poor coverage of a particular attack-surface and long range plans/aspirations on improving them?
...
If you want to be involved, please contact Stephen.terrill@ericsson.com Pawel Pawlak or Amy Zwarico
Note: if you would like to change the contents of this site, please contact Stephen Terrillcontact Pawel Pawlak or Amy Zwarico.