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

Compare with Current View Page History

Version 1 Current »

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

Jira No
SummaryDescriptionStatusSolution

Update on the Security Logging Fields and Global Requirement  

DRAFT slides: https://wiki.onap.org/display/DW/Security+Logging+Fields+-+Global+Requirement

Bob presented the deck and collected feedback.

Implementatiojn does not require highly qualified resources to modify XML files. To be further investigated the project complexity and resources needed to implement.

ongoing

Other than CPS project shall be involved for resource estimation for requirement implementation.

Test proposal - can it be taken from CPS on how do you know it works?


SBOM creation 

Good news: It worked on DCAE VES repo.

-https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/dcaegen2-collectors-ves-maven-stage-master/1142/sbom-dcaegen2-collectors-ves-maven-stage-master

- SBOM file is generated successfully without any further manipulation after the SBOM SW upgrade

LF IT will be introducing an another parameter in the Jenkins job that will allow to define the target path for the repo.

ongoingWaiting for the feedbck on introducing and testing 

Superblueprint

They preparing some demo for ONES NA. Security aspects would be good to cover, it would require to contribute and attend their meetings (on Tuesdays and Wednesdays).

-Currently project team is seeking suggestion on Use cases:  https://wiki.lfnetworking.org/pages/viewpage.action?pageId=68792322

- Advisory group: https://wiki.lfnetworking.org/display/LN/Advisory+Group+Meeting+Minutes

- Please feel free to add what you think will add value.

- SBP FAQs: https://wiki.lfnetworking.org/display/LN/5G+Super+Blueprint+FAQ

Security slicing definition to be explored. Is it related only to confidentiality? 

It can be securing entire Ci/CD pipeline

ongoingAmy to share meeting invitation to SECCOM distribution list. 

Service Mesh for Kohn release

follow-up of the Andreas presentation - service mesh used for communication as default.

AuN and AuZ as next steps by E/// team. Connection to Keyclock is needed for user management with token. For London to be applied.

AAF removal not ready for Kohn as providing full RBAC and certificates. Target to London.

ISTIO GW configuration.We ave only one ONAP namespace.


Andreas will talk to Seshu.

Byung will have internal meeting at E/// to keep resources to support service Mesh.


PTL meeting – July 25th

Kohn M3 scheduled for Sept 1




TSC meeting – July 21st

Approved Kohn M2 under the condition that GR / Best Practice are color coded by all projects by M3.




Pawel and Amy submitted proposal, 

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


Proposal to be submitted - CFP deadline is July 29th.

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






Recording: 


SECCOM presentation:






  • No labels