224 KiB
224 KiB
| hide | |
|---|---|
|
Security Scan
Helm-Chart
Scan Results
Chart Object: unifi/templates/common.yaml
| Type | Misconfiguration ID | Check | Severity | Explaination | Links |
|---|---|---|---|---|---|
| Kubernetes Security Check | KSV003 | Default capabilities not dropped | LOW | Expand...The container should drop all default capabilities and add only those that are needed for its execution.Container 'RELEASE-NAME-unifi' of Deployment 'RELEASE-NAME-unifi' should add 'ALL' to 'securityContext.capabilities.drop' |
|
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | Expand...'runAsNonRoot' forces the running image to run as a non-root user to ensure least privileges.Container 'RELEASE-NAME-unifi' of Deployment 'RELEASE-NAME-unifi' should set 'securityContext.runAsNonRoot' to true |
|
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | Expand...'runAsNonRoot' forces the running image to run as a non-root user to ensure least privileges.Container 'autopermissions' of Deployment 'RELEASE-NAME-unifi' should set 'securityContext.runAsNonRoot' to true |
|
| Kubernetes Security Check | KSV013 | Image tag ':latest' used | LOW | Expand...It is best to avoid using the ':latest' image tag when deploying containers in production. Doing so makes it hard to track which version of the image is running, and hard to roll back the version.Container 'RELEASE-NAME-unifi' of Deployment 'RELEASE-NAME-unifi' should specify an image tag |
|
| Kubernetes Security Check | KSV013 | Image tag ':latest' used | LOW | Expand...It is best to avoid using the ':latest' image tag when deploying containers in production. Doing so makes it hard to track which version of the image is running, and hard to roll back the version.Container 'autopermissions' of Deployment 'RELEASE-NAME-unifi' should specify an image tag |
|
| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW | Expand...An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk.Container 'RELEASE-NAME-unifi' of Deployment 'RELEASE-NAME-unifi' should set 'securityContext.readOnlyRootFilesystem' to true |
|
| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW | Expand...An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk.Container 'autopermissions' of Deployment 'RELEASE-NAME-unifi' should set 'securityContext.readOnlyRootFilesystem' to true |
|
| Kubernetes Security Check | KSV019 | Seccomp policies disabled | MEDIUM | Expand...A program inside the container can bypass Seccomp protection policies.Container 'RELEASE-NAME-unifi' of Deployment 'RELEASE-NAME-unifi' should specify a seccomp profile |
|
| Kubernetes Security Check | KSV019 | Seccomp policies disabled | MEDIUM | Expand...A program inside the container can bypass Seccomp protection policies.Container 'autopermissions' of Deployment 'RELEASE-NAME-unifi' should specify a seccomp profile |
|
| Kubernetes Security Check | KSV020 | Runs with low user ID | MEDIUM | Expand...Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.Container 'RELEASE-NAME-unifi' of Deployment 'RELEASE-NAME-unifi' should set 'securityContext.runAsUser' > 10000 |
|
| Kubernetes Security Check | KSV020 | Runs with low user ID | MEDIUM | Expand...Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.Container 'autopermissions' of Deployment 'RELEASE-NAME-unifi' should set 'securityContext.runAsUser' > 10000 |
|
| Kubernetes Security Check | KSV021 | Runs with low group ID | MEDIUM | Expand...Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.Container 'RELEASE-NAME-unifi' of Deployment 'RELEASE-NAME-unifi' should set 'securityContext.runAsGroup' > 10000 |
|
| Kubernetes Security Check | KSV021 | Runs with low group ID | MEDIUM | Expand...Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.Container 'autopermissions' of Deployment 'RELEASE-NAME-unifi' should set 'securityContext.runAsGroup' > 10000 |
|
| Kubernetes Security Check | KSV029 | A root primary or supplementary GID set | LOW | Expand...Containers should be forbidden from running with a root primary or supplementary GID.Deployment 'RELEASE-NAME-unifi' should set 'spec.securityContext.runAsGroup', 'spec.securityContext.supplementalGroups[*]' and 'spec.securityContext.fsGroup' to integer greater than 0 |
Containers
Detected Containers
tccr.io/truecharts/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c
tccr.io/truecharts/unifi:v6.5.53@sha256:c6cf26dcd8e73e95503a9a8fb5ab36458c05c724b33add8dc1a6152648f33d3d
Scan Results
Container: tccr.io/truecharts/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c (alpine 3.14.2)
alpine
Container: tccr.io/truecharts/unifi:v6.5.53@sha256:c6cf26dcd8e73e95503a9a8fb5ab36458c05c724b33add8dc1a6152648f33d3d (ubuntu 18.04)
ubuntu