| Kubernetes Security Check | KSV003 | Default capabilities not dropped | LOW | The container should drop all default capabilities and add only those that are needed for its execution. | Container 'RELEASE-NAME-jackett' of Deployment 'RELEASE-NAME-jackett' should add 'ALL' to 'securityContext.capabilities.drop' | <details><summary>Click to expand!</summary><a href="https://kubesec.io/basics/containers-securitycontext-capabilities-drop-index-all/">https://kubesec.io/basics/containers-securitycontext-capabilities-drop-index-all/</a><br><a href="https://avd.aquasec.com/appshield/ksv003">https://avd.aquasec.com/appshield/ksv003</a><br></details> |
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | 'runAsNonRoot' forces the running image to run as a non-root user to ensure least privileges. | Container 'autopermissions' of Deployment 'RELEASE-NAME-jackett' should set 'securityContext.runAsNonRoot' to true | <details><summary>Click to expand!</summary><a href="https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted">https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted</a><br><a href="https://avd.aquasec.com/appshield/ksv012">https://avd.aquasec.com/appshield/ksv012</a><br></details> |
| Kubernetes Security Check | KSV013 | Image tag ':latest' used | LOW | 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-jackett' of Deployment 'RELEASE-NAME-jackett' should specify an image tag | <details><summary>Click to expand!</summary><a href="https://kubernetes.io/docs/concepts/configuration/overview/#container-images">https://kubernetes.io/docs/concepts/configuration/overview/#container-images</a><br><a href="https://avd.aquasec.com/appshield/ksv013">https://avd.aquasec.com/appshield/ksv013</a><br></details> |
| Kubernetes Security Check | KSV013 | Image tag ':latest' used | LOW | 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-jackett' should specify an image tag | <details><summary>Click to expand!</summary><a href="https://kubernetes.io/docs/concepts/configuration/overview/#container-images">https://kubernetes.io/docs/concepts/configuration/overview/#container-images</a><br><a href="https://avd.aquasec.com/appshield/ksv013">https://avd.aquasec.com/appshield/ksv013</a><br></details> |
| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW | 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-jackett' of Deployment 'RELEASE-NAME-jackett' should set 'securityContext.readOnlyRootFilesystem' to true | <details><summary>Click to expand!</summary><a href="https://kubesec.io/basics/containers-securitycontext-readonlyrootfilesystem-true/">https://kubesec.io/basics/containers-securitycontext-readonlyrootfilesystem-true/</a><br><a href="https://avd.aquasec.com/appshield/ksv014">https://avd.aquasec.com/appshield/ksv014</a><br></details> |
| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW | 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-jackett' should set 'securityContext.readOnlyRootFilesystem' to true | <details><summary>Click to expand!</summary><a href="https://kubesec.io/basics/containers-securitycontext-readonlyrootfilesystem-true/">https://kubesec.io/basics/containers-securitycontext-readonlyrootfilesystem-true/</a><br><a href="https://avd.aquasec.com/appshield/ksv014">https://avd.aquasec.com/appshield/ksv014</a><br></details> |
| Kubernetes Security Check | KSV019 | Seccomp policies disabled | MEDIUM | A program inside the container can bypass Seccomp protection policies. | Container 'RELEASE-NAME-jackett' of Deployment 'RELEASE-NAME-jackett' should specify a seccomp profile | <details><summary>Click to expand!</summary><a href="https://kubesec.io/basics/metadata-annotations-container-seccomp-security-alpha-kubernetes-io-pod/">https://kubesec.io/basics/metadata-annotations-container-seccomp-security-alpha-kubernetes-io-pod/</a><br><a href="https://avd.aquasec.com/appshield/ksv019">https://avd.aquasec.com/appshield/ksv019</a><br></details> |
| Kubernetes Security Check | KSV019 | Seccomp policies disabled | MEDIUM | A program inside the container can bypass Seccomp protection policies. | Container 'autopermissions' of Deployment 'RELEASE-NAME-jackett' should specify a seccomp profile | <details><summary>Click to expand!</summary><a href="https://kubesec.io/basics/metadata-annotations-container-seccomp-security-alpha-kubernetes-io-pod/">https://kubesec.io/basics/metadata-annotations-container-seccomp-security-alpha-kubernetes-io-pod/</a><br><a href="https://avd.aquasec.com/appshield/ksv019">https://avd.aquasec.com/appshield/ksv019</a><br></details> |
| Kubernetes Security Check | KSV020 | Runs with low user ID | MEDIUM | Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table. | Container 'RELEASE-NAME-jackett' of Deployment 'RELEASE-NAME-jackett' should set 'securityContext.runAsUser' > 10000 | <details><summary>Click to expand!</summary><a href="https://kubesec.io/basics/containers-securitycontext-runasuser/">https://kubesec.io/basics/containers-securitycontext-runasuser/</a><br><a href="https://avd.aquasec.com/appshield/ksv020">https://avd.aquasec.com/appshield/ksv020</a><br></details> |
| Kubernetes Security Check | KSV020 | Runs with low user ID | MEDIUM | Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table. | Container 'autopermissions' of Deployment 'RELEASE-NAME-jackett' should set 'securityContext.runAsUser' > 10000 | <details><summary>Click to expand!</summary><a href="https://kubesec.io/basics/containers-securitycontext-runasuser/">https://kubesec.io/basics/containers-securitycontext-runasuser/</a><br><a href="https://avd.aquasec.com/appshield/ksv020">https://avd.aquasec.com/appshield/ksv020</a><br></details> |
| Kubernetes Security Check | KSV021 | Runs with low group ID | MEDIUM | Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table. | Container 'RELEASE-NAME-jackett' of Deployment 'RELEASE-NAME-jackett' should set 'securityContext.runAsGroup' > 10000 | <details><summary>Click to expand!</summary><a href="https://kubesec.io/basics/containers-securitycontext-runasuser/">https://kubesec.io/basics/containers-securitycontext-runasuser/</a><br><a href="https://avd.aquasec.com/appshield/ksv021">https://avd.aquasec.com/appshield/ksv021</a><br></details> |
| Kubernetes Security Check | KSV021 | Runs with low group ID | MEDIUM | Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table. | Container 'autopermissions' of Deployment 'RELEASE-NAME-jackett' should set 'securityContext.runAsGroup' > 10000 | <details><summary>Click to expand!</summary><a href="https://kubesec.io/basics/containers-securitycontext-runasuser/">https://kubesec.io/basics/containers-securitycontext-runasuser/</a><br><a href="https://avd.aquasec.com/appshield/ksv021">https://avd.aquasec.com/appshield/ksv021</a><br></details> |
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
TrueCharts-Bot