• CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES (REQ-xxx) 
• COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11) (REQ-xxx) 
• COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8) (REQ-xxx)
• LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA (REQ-xxx)
• CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL (REQ-xxx)

CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES (REQ-xxx) 

R9 PRESENTATION:

Key Contacts - Paweł Pawlak Amy Zwarico

Executive Summary -  All ONAP projects shall continue their efforts to reduce the risks associated with software vulnerabilities in the ONAP code base by upgrading all outdated, vulnerable direct dependencies in their code bases following the recommendations of SECCOM. The project and repo specific recommendations are provided in the Security Vulnerability space for Honolulu release.

Business Impact - Improves the security posture of ONAP. 

Business Markets - All operators and service providers can leverage the of fewer vulnerabilities in the open source dependencies in ONAP

Funding/Financial Impacts - N/A

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11) (REQ-xxx) 

R9 PRESENTATION:

Key Contacts -  Amy Zwarico Paweł Pawlak 

Executive Summary - All remaining ONAP projects that received exception approval in Honolulu release for using java v8 shall reduce the risks associated with no regular support for java v8 software as it causes increase of usage risk, as recommended by SECCOM. Continuation of REQ-351. and REQ-438

Business Impact - Improves the security posture of ONAP. 

Business Markets - All operators, service providers and entities using ONAP.  

Funding/Financial Impacts - N/A

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 

COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8) (REQ-xxx)

R9 PRESENTATION:

Key Contacts -  Amy Zwarico Paweł Pawlak 

Executive Summary - All remaining ONAP projectsthat received exception approval in Honolulu release using Python shall reduce the risks associated with no community support for Python 2.7 software as it causes increase of usage risk, as recommended by SECCOM. Continuation of REQ-373 and REQ-437.

Business Impact - Improves the security posture of ONAP. 

Business Markets - All operators, service providers and entities using ONAP.  

Funding/Financial Impacts - N/A

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 

LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA (REQ-441)

R8 PRESENTATION:

Key Contacts -  rouzaut Amy Zwarico Paweł Pawlak 

Executive Summary - All ONAP applications should generate logs that can be collected by Kubernetes. 

Business Impact - Improves the security posture of ONAP. 

Business Markets - All operators, service providers and entities using ONAP.  

Funding/Financial Impacts - N/A

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 

CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL (REQ-xxx)

Key Contacts - Tony Hansen Amy Zwarico Paweł Pawlak  

Executive Summary - ONAP project will provide their feedback for the Application Security questions:

1. Crypto Credentials Agility – ½ od apps in met and almost half not yet answered
2. Implement Secure Design – 1/3 of projects did not answer 
3. Crypto Weaknesses – tests to be applied (3 including Morgan)

Projects that have already answered this question positively, should verify that the answer is still correct.

Continuation of REQ-350. and REQ-443.

Business Impact - Improves the security posture of ONAP by lessening the risk. 

Business Markets - All operators and service provider.

Funding/Financial Impacts - N/A

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

SUPPORT FOR IPv4/IPv6 DUAL STACK DEPLOYMENTS IN R9 (REQ-718) 

R9 PRESENTATION:

Key Contacts - damian.nowak

Executive Summary 

Majority of LTE and 5G RAN networks today are running exclusively on IPv6. IPv4/IPv6 dual stack solution for ONAP is needed to enable integration.
In Istanbul release the scope is so far:

• An update of OOM Helm charts, using the K8S 1.20 IPv4/IPv6 DS model ("PreferDualStack"), at least for DCAEGEN2-Services
• An update of OOM Helm charts for EJBCA server to version 7.x. EJBCA 7.x is meant to support requesting certificates using IPv6 addresses.

Business Impact

Improves ONAP integration capabilities, mainly in 5G use-cases and E2E Network Slicing. Future-proofs ONAP for years to come. Aligns with ORAN standards.

Business Markets

All operators, service providers and entities using ONAP.

Funding/Financial Impacts

None. RKE is already supporting K8S 1.20 as one of recommended K8S solutions, thus no additional costs here.

Organization Mgmt, Sales Strategies

There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider