Skip to content

KICS

KICS #289

Triggered via schedule November 15, 2023 00:38
Status Success
Total duration 1m 1s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

kics.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
[MEDIUM] Container Running With Low UID: charts/puris/charts/frontend/templates/deployment.yaml#L1
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/puris/charts/backend/templates/deployment.yaml#L1
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L45
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L240
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L26
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L176
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L45
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L176
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: backend/docker-compose.yaml#L26
Incoming container traffic should be bound to a specific host interface
[MEDIUM] Container Traffic Not Bound To Host Interface: frontend/docker-compose.yaml#L26
Incoming container traffic should be bound to a specific host interface