...
| Jira No | Summary | Description | Status | Solution | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CMPv2 status update – Pawel/Hampus | Issue with lack of support from AAF for CMPv2 implementation. CMPv2 client implementation connected with AAF CertMan as goal for Frankfurt release. | Issue with lack of support from AAF for CMPv2 implementation. El Alto code does not build, some contradiction in the code. Testing with 2 DCAE components (nokia) and SDNC (E///). | Meeting with Jonathan to be done today. | VNF security requirements | Leftovers from El Alto to be collected. Special focus on ensuring that the language is clear and definition allows for an automatic tests - fitting OVP process. | 2 tickets were created from last week's call. Dealine before early spring. | We focus on testable requirements. | OOM password generation update | Passwords in ONAP should be randomly generated but it generates issues related to update of components. That is an alternative idea is considered - person deploying ONAP must provide master password- based on HMAC. If we provide the same password for deployments, the passwords generated inside ONAP will gonna be the same. For upgrade with Master passrod, ONAP passwords will not change. | Change of password done with a reliable way. | Consequences of using m,aster password - if it is compromised . See Master Password attached file. | CII Badging update – Tony | To discuss with David McBride his role in supporting CII Badging | David to be invited for the next SECCOM meeting | E-mail was sent to David. David confirm his availability on 17th of December. | ONAP access management - Natacha | User has an access to all services which is not ok | Service Mesh POC could be a solution to further investigate, amount of work with AAF could be high as an alternative. | SECCOM proposed release assessment for TSC at 12/5 meeting -KPIs
-Define the passing criteria for security | Define the KPIs for the Frankfurt release Define the SECCOM passing criteria Owners of each KPI asked to update the KPI and passing criteria in Frankfurt security assessment | |
Code Coverage:
CII badging:
| Frankfurt security assessment (https://wiki.onap.org/display/DW/Frankfurt+Security+Assessment+Proposal) | Percentage values are proposed for each KPI. | Wiki with proposals is ready for comments | We have to book a slot at the next PTL call to present those proposals and then at the TSC call to present recommendation for approval. | Topics identified for next week's SECCOM agenda | None response still coming from some projects. Some of the CII editors moved and we need to have somebody who has an access to all . For silver level for some questions we have completely no answers. | Tony will send a summary of answers to David, so ONAP wide answers could be unified accross projects. | ||||||||||||||
ONAP and SOL004 VNF signature update – Samuli |
| View file | ||||
|---|---|---|---|---|
|
| View file | ||||
|---|---|---|---|---|
|
| View file | ||||
|---|---|---|---|---|
|
...
ONAP SECCOM Priority 2: Integrity Verification at Instantiation ONAP SECCOM P.riority 3: Service Provider Ability to Sign the Artifacts - no exact mechanism specified yet. | it is not yet an operational requirement. Package signature is valiated at the onboarding, in the instantiation individual signatures. | Explot occured operationally already via lack of signatures in operators networks. |