Skip to content

KICS

KICS #515

Triggered via schedule July 10, 2024 01:16
Status Success
Total duration 37s
Artifacts

kics.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
Analyze
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
[MEDIUM] Container Running With Low UID: charts/data-exchange/templates/deployment.yaml#L51
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Readiness Probe Is Not Configured: charts/data-exchange/templates/deployment.yaml#L51
Check if Readiness Probe is not configured.
[MEDIUM] Seccomp Profile Is Not Configured: charts/data-exchange/templates/deployment.yaml#L51
Containers should be configured with a secure Seccomp profile to restrict potentially dangerous syscalls
[MEDIUM] Service Account Token Automount Not Disabled: charts/data-exchange/templates/deployment.yaml#L43
Service Account Tokens are automatically mounted even if not necessary
[MEDIUM] Using Unrecommended Namespace: charts/data-exchange/templates/serviceaccount.yaml#L26
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
[MEDIUM] Using Unrecommended Namespace: charts/data-exchange/templates/service.yaml#L23
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
[MEDIUM] Using Unrecommended Namespace: charts/data-exchange/templates/secret.yaml#L24
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
[MEDIUM] Using Unrecommended Namespace: charts/data-exchange/templates/deployment.yaml#L23
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
[LOW] Image Without Digest: charts/data-exchange/templates/deployment.yaml#L51
Images should be specified together with their digests to ensure integrity
[LOW] Missing AppArmor Profile: charts/data-exchange/templates/deployment.yaml#L36
Containers should be configured with an AppArmor profile to enforce fine-grained access control over low-level system resources