Skip to content

fix: add default empty array value for null policy profiles (#1706) #5242

fix: add default empty array value for null policy profiles (#1706)

fix: add default empty array value for null policy profiles (#1706) #5242

Triggered via push December 4, 2024 15:11
Status Success
Total duration 1m 2s
Artifacts

kics.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
Analyze
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
[MEDIUM] Container Traffic Not Bound To Host Interface: samples/edc-dast/docker-compose.yaml#L30
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Healthcheck Not Set: samples/edc-dast/docker-compose.yaml#L24
Check containers periodically to see if they are running properly.
[MEDIUM] Host Namespace is Shared: samples/edc-dast/docker-compose.yaml#L24
The hosts process namespace should not be shared by containers
[MEDIUM] Memory Not Limited: samples/edc-dast/docker-compose.yaml#L24
Memory limits should be defined for each container. This prevents potential resource exhaustion by ensuring that containers consume not more than the designated amount of memory
[MEDIUM] Security Opt Not Set: samples/edc-dast/docker-compose.yaml#L24
Attribute 'security_opt' should be defined.
[LOW] Container Capabilities Unrestricted: samples/edc-dast/docker-compose.yaml#L24
Some capabilities are not needed in certain (or any) containers. Make sure that you only add capabilities that your container needs. Drop unnecessary capabilities as well.
[LOW] Cpus Not Limited: samples/edc-dast/docker-compose.yaml#L24
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests