-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Knowledge Agent Release 23.12 Security Acceptance Criteria #91
Comments
Hi All, knowledge-agents-edc/agentplane-hashicorp SCA Did not pass due to high finding knowledge-agents-edc/agentplane-azure-vault SCA Did not pass due to high findings knowledge-agents/remoting-agent SCA Did not pass due to high findings knowledge-agents/conforming-agent https://analysiscenter.veracode.com/auth/index.jsp#HomeAppProfile:47240:1821743 SCA Passed knowledge-agents/provisioning-agent SCA Did not pass due to high findings |
Hi All, SCA Passed for knowledge-agents-edc/agentplane-hashicorp |
Hi All and @drcgjung Everything is on green now SCA Passed https://analysiscenter.veracode.com/auth/index.jsp#HomeAppProfile:47240:1821743 |
|
Here are the trivy findings for knowledge-agents. Since the release PR is pending on an IP check (eclipse-tractusx/knowledge-agents#66), we show a locally-built preview results on 1.10.15. Shows that only high findings of the base images are left (see the DevOps discussion, OSS requirements weigh higher than security). Note that we had to derive from base images in the case of strong runtime dependencies on RDF4J SDK (remoting-agent) and Ontop VKP (provisioning-agent) "Scans removed" |
Dear Colleagues kindly check:
|
Threat Modeling approved. No major changes |
Hi All, SAST passed Just please keep in mind that we have few open medium findings. |
as @drcgjung stated. |
@kelaja @scherersebastian Container Scan for knowledge-agents (IP check through, release done) should now also be green. Aaaaah thats all a moving target, another medium for spring-boot ... feeling like sisiphos. A29078924@T000c60ad4 Applications % trivy image tractusx/remoting-agent:1.10.15 tractusx/remoting-agent:1.10.15 (ubuntu 22.04) Total: 35 (UNKNOWN: 0, LOW: 24, MEDIUM: 11, HIGH: 0, CRITICAL: 0) A29078924@T000c60ad4 Applications % trivy image tractusx/provisioning-agent:1.10.15 tractusx/provisioning-agent:1.10.15 (ubuntu 22.04) Total: 32 (UNKNOWN: 0, LOW: 22, MEDIUM: 10, HIGH: 0, CRITICAL: 0) And that one is using the official TX base image A29078924@T000c60ad4 Applications % trivy image tractusx/conforming-agent:1.10.15 tractusx/conforming-agent:1.10.15 (alpine 3.18.4) Total: 4 (UNKNOWN: 0, LOW: 0, MEDIUM: 2, HIGH: 2, CRITICAL: 0) "Scans removed" I have the idea of using the non-base images for 24.03 no more as runtime, but just as "build container" and then repackage the stuff into the official base image. Because its all JRE-based this should not be too difficult. |
If you can't remove the libraries and install the fixed ones, and there is no way around - then please commit yourself to a hot fix as soon as you can fix it. |
here is the commitment eclipse-tractusx/knowledge-agents#72 |
Trivy passed :) |
Release Security 23.12
Source in Catena-X Confluence and Expert Contacts here(Source only accessible for Catena-X Consortia members in current transition phase).
Threat Modelling Analysis results
Analysis completed (operations excluded):
Artifact Repository:
Prime Contacts:
Static Application Security Testing (SAST)
Best Practise:
Artifact Repository:
Prime Contacts:
Dynamic Application Security Testing (DAST)
incl API testing (if applicable)
Best Practise:
Artifact Repository:
Prime Contacts:
Secret scanning
Scan executed centrally by SEC team and ZERO valid findings
Artifact Repository:
Best Practise:
Prime Contact:
Software Composition Analysis (SCA)
Dependencies must be scanned with Veracode tool with regards to vulnerability
Best Practise:
Artifact Repository:
Prime Contacts:
Container Scan conducted
All containers in GitHub Packages must be scanned
Best Practise:
Artifact Repository:
Prime Contacts:
Infrastructure as Code
IaC code must be scanned.
Best Practise:
Artifact Repository:
Prime Contacts:
The text was updated successfully, but these errors were encountered: