Skip to content

SPSH-1162: Remove kuerzel and kennung for organisation seeding data (… #19

SPSH-1162: Remove kuerzel and kennung for organisation seeding data (…

SPSH-1162: Remove kuerzel and kennung for organisation seeding data (… #19

Triggered via push October 14, 2024 11:11
Status Failure
Total duration 14m 7s
Artifacts 1
scan_helm  /  Kics Helm Chart Scan
28s
scan_helm / Kics Helm Chart Scan
CodeQL  /  Analyze CodeQL
2m 15s
CodeQL / Analyze CodeQL
Linting  /  Nest Lint
1m 11s
Linting / Nest Lint
Tests and Sonarcloud  /  Tests and Sonarcloud
11m 55s
Tests and Sonarcloud / Tests and Sonarcloud
release_helm  /  release
31s
release_helm / release
Publish image and scan with trivy  /  Publish image
1m 28s
Publish image and scan with trivy / Publish image
Publish image and scan with trivy  /  pre_scan
0s
Publish image and scan with trivy / pre_scan
Publish image and scan with trivy  /  ...  /  Trivy Scan
12s
Publish image and scan with trivy / Trivy scan for uploaded image / Trivy Scan
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 11 warnings
Publish image and scan with trivy / Trivy scan for uploaded image / Trivy Scan
Path does not exist: trivy-results.sarif
Publish image and scan with trivy / Trivy scan for uploaded image / Trivy Scan
Process completed with exit code 2.
[MEDIUM] Container Running As Root: charts/dbildungs-iam-server/templates/redis-deployment.yaml#L22
Containers should only run as non-root user. This limits the exploitability of security misconfigurations and restricts an attacker's possibilities in case of compromise
[MEDIUM] Container Running With Low UID: charts/dbildungs-iam-server/templates/backend-deployment.yaml#L22
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Running With Low UID: charts/dbildungs-iam-server/templates/backend-deployment.yaml#L53
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Running With Low UID: charts/dbildungs-iam-server/templates/backend-deployment.yaml#L22
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Running With Low UID: charts/dbildungs-iam-server/templates/redis-deployment.yaml#L34
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Running With Low UID: charts/dbildungs-iam-server/templates/redis-deployment.yaml#L38
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] NET_RAW Capabilities Not Being Dropped: charts/dbildungs-iam-server/templates/redis-deployment.yaml#L22
Containers should drop 'ALL' or at least 'NET_RAW' capabilities
[MEDIUM] Seccomp Profile Is Not Configured: charts/dbildungs-iam-server/templates/redis-deployment.yaml#L38
Containers should be configured with a secure Seccomp profile to restrict potentially dangerous syscalls
[MEDIUM] Service Account Token Automount Not Disabled: charts/dbildungs-iam-server/templates/redis-deployment.yaml#L20
Service Account Tokens are automatically mounted even if not necessary
[LOW] Container Requests Not Equal To It's Limits: charts/dbildungs-iam-server/templates/backend-deployment.yaml#L22
Containers must have the same resource requests set as limits. This is recommended to avoid resource DDoS of the node during spikes and means that 'requests.memory' and 'requests.cpu' must equal 'limits.memory' and 'limits.cpu', respectively
release_helm / release
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size Digest
test-artifacts Expired
1.37 MB
sha256:7a32d5d68497061e9ab916e84430fbb993f86c21023b8aedc4c2be9afac612a9