Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Please find below the Minutes of Meetings and recording for the SECCOM meeting that was held on 9th of August 2022.

Jira No
SummaryDescriptionStatusSolution

Update on Unmaintained Projects task group



Update on the Security Logging Fields and Global Requirement  


ongoing

Byung to re-gain access to O-RAN.


SBOM creation 


ongoing

Superblueprint

Use cases to be added, limited resources to go with E2E solution integration.

Weekly meetings: https://wiki.lfnetworking.org/pages/viewpage.action?pageId=50528282

Architecture: https://wiki.lfnetworking.org/pages/viewpage.action?pageId=53609061

Roadmap: https://wiki.lfnetworking.org/display/LN/5G+Super+Blueprint+Roadmap

Requirements and Use case Advisory Group: https://wiki.lfnetworking.org/display/LN/Requirements+and+Use+Case+Advisory+Group

Use cases: https://wiki.lfnetworking.org/pages/viewpage.action?pageId=68792322

Use cases to be added, limited resources to go with E2E solution integration.

ØNext meeting later today, resource assignment needs to be done

Secure slicing needs to be better defined.

Major focus on setting up 5G with open source components.

ongoingLogistic from program perspective needs to be improved.

PTL meeting – August 15th

Meeting cancelled - bank holiday in part of Europe




TSC meeting – August 11th

-Confluence injection attack – plugin disabled

-DTF submissions, no deadline yet




Pawel and Amy submitted proposal: ONAP’s Recipe for Managing CVEs and Securing Open Source Software

Byung will present service descriptor and potentially new ONAP security architecture with service mesh.




LFN Developer & Testing Forum NA 

Productization of Assured Opensource Software - Muddasar

SBOM implementation and challenges in ONAP - Muddasar

5G orchestration with ONAP, AI and ML. - Maggie


Brian to be asked by Muddasar as co-presenter for SBOM.

Node.js recommended upgrades

We start this topic.

The even-numbered versions of Node.js roll through “current” status, “Active LTS” status, and “Maintenance LTS” status. New releases come out every 6 months. So a current release becomes LTS 1 year later, then Maintenance LTS 1 year after that for an additional 1.5 years.

The current version is v18, the active LTS is v16, and maintenance LTS is v14. V14 is active through Apr 2023.

We should make sure that we are using Containers with Node.js v14, v16 or v20.

This MIGHT be automatic if we are using current node.js containers.

stratedto be further explored the number of java script containers and recommended releases.

SECCOM MEETING CALL WILL BE HELD ON 23th OF August'22. 






Recording: 


SECCOM presentation:





  • No labels