125 KiB
125 KiB
| hide | |
|---|---|
|
Security Overview
Helm-Chart
Scan Results
Chart Object: minio/templates/common.yaml
| Type | Misconfiguration ID | Check | Severity | Explaination | Links |
|---|---|---|---|---|---|
| Kubernetes Security Check | KSV001 | Process can elevate its own privileges | MEDIUM | Expand...A program inside the container can elevate its own privileges and run as root, which might give the program control over the container and node.Container 'hostpatch' of Deployment 'RELEASE-NAME-minio' should set 'securityContext.allowPrivilegeEscalation' to false |
|
| 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-minio' of Deployment 'RELEASE-NAME-minio' should add 'ALL' to 'securityContext.capabilities.drop' |
|
| 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 'hostpatch' of Deployment 'RELEASE-NAME-minio' should add 'ALL' to 'securityContext.capabilities.drop' |
|
| Kubernetes Security Check | KSV011 | CPU not limited | LOW | Expand...Enforcing CPU limits prevents DoS via resource exhaustion.Container 'hostpatch' of Deployment 'RELEASE-NAME-minio' should set 'resources.limits.cpu' |
|
| 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-minio' 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 'hostpatch' of Deployment 'RELEASE-NAME-minio' should set 'securityContext.runAsNonRoot' 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 'RELEASE-NAME-minio' of Deployment 'RELEASE-NAME-minio' 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-minio' 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 'hostpatch' of Deployment 'RELEASE-NAME-minio' should set 'securityContext.readOnlyRootFilesystem' to true |
|
| Kubernetes Security Check | KSV015 | CPU requests not specified | LOW | Expand...When containers have resource requests specified, the scheduler can make better decisions about which nodes to place pods on, and how to deal with resource contention.Container 'hostpatch' of Deployment 'RELEASE-NAME-minio' should set 'resources.requests.cpu' |
|
| Kubernetes Security Check | KSV016 | Memory requests not specified | LOW | Expand...When containers have memory requests specified, the scheduler can make better decisions about which nodes to place pods on, and how to deal with resource contention.Container 'hostpatch' of Deployment 'RELEASE-NAME-minio' should set 'resources.requests.memory' |
|
| Kubernetes Security Check | KSV017 | Privileged container | HIGH | Expand...Privileged containers share namespaces with the host system and do not offer any security. They should be used exclusively for system containers that require high privileges.Container 'hostpatch' of Deployment 'RELEASE-NAME-minio' should set 'securityContext.privileged' to false |
|
| Kubernetes Security Check | KSV018 | Memory not limited | LOW | Expand...Enforcing memory limits prevents DoS via resource exhaustion.Container 'hostpatch' of Deployment 'RELEASE-NAME-minio' should set 'resources.limits.memory' |
|
| 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-minio' of Deployment 'RELEASE-NAME-minio' 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-minio' 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 'hostpatch' of Deployment 'RELEASE-NAME-minio' 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-minio' of Deployment 'RELEASE-NAME-minio' 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-minio' 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 'hostpatch' of Deployment 'RELEASE-NAME-minio' should set 'securityContext.runAsGroup' > 10000 |
|
| Kubernetes Security Check | KSV023 | hostPath volumes mounted | MEDIUM | Expand...HostPath volumes must be forbidden.Deployment 'RELEASE-NAME-minio' should not set 'spec.template.volumes.hostPath' |
|
| 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-minio' 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/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c
tccr.io/truecharts/minio:latest@sha256:bd004ba41b2456f115c7f1360d7c49f4478f5d9ce20ad042c8ce2cf5aff46d24
Scan Results
Container: tccr.io/truecharts/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c (alpine 3.14.2)
alpine
Container: tccr.io/truecharts/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c (alpine 3.14.2)
alpine
Container: tccr.io/truecharts/minio:latest@sha256:bd004ba41b2456f115c7f1360d7c49f4478f5d9ce20ad042c8ce2cf5aff46d24 (redhat 8.5)
redhat