daffainfo
/
nuclei-templates
mirror of https://github.com/daffainfo/nuclei-templates.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fixed lint error 🛠️

patch-4
Prince Chaddha 2024-05-26 08:58:13 +04:00
parent aedfb3905a
commit 11445ea3e4
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
cloud/kubernetes/pods/k8s-containers-share-host-ipc.yaml
View File

@ -7,7 +7,7 @@ info:
description: Checks if any containers in Kubernetes Pods are configured to share the host's IPC namespace, which can lead to security risks. description: Checks if any containers in Kubernetes Pods are configured to share the host's IPC namespace, which can lead to security risks.
impact: | impact: |
Sharing the host's IPC namespace allows containers to access data across all containers on the same host, posing potential security risks. Sharing the host's IPC namespace allows containers to access data across all containers on the same host, posing potential security risks.
remediation: Ensure that no container in Kubernetes Pods is set to share the host IPC namespace. Configure 'spec.hostIPC' to 'false' for all pods to isolate IPC namespaces. remediation: Ensure that no container in Kubernetes Pods is set to share the host IPC namespace. Configure 'spec.hostIPC' to 'false' for all pods to isolate IPC namespaces.
reference: reference:
- https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ - https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
tags: cloud,devops,kubernetes,k8s,devsecops,pods tags: cloud,devops,kubernetes,k8s,devsecops,pods

2
cloud/kubernetes/pods/k8s-readonly-fs.yaml
View File

@ -7,7 +7,7 @@ info:
description: Checks for containers that do not use a read-only filesystem, which can prevent malicious write operations at runtime description: Checks for containers that do not use a read-only filesystem, which can prevent malicious write operations at runtime
impact: | impact: |
Not using a read-only filesystem can expose containers to risks of malicious modifications at runtime, compromising the container's integrity and security. Not using a read-only filesystem can expose containers to risks of malicious modifications at runtime, compromising the container's integrity and security.
remediation: Configure containers to use read-only filesystems where possible to enhance security and minimize risk of unauthorized data modification remediation: Configure containers to use read-only filesystems where possible to enhance security and minimize risk of unauthorized data modification
reference: reference:
- https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation - https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation
tags: cloud,devops,kubernetes,k8s,devsecops,pods tags: cloud,devops,kubernetes,k8s,devsecops,pods