translate

src/pentesting-cloud/kubernetes-security/README.md

@@ -82,4 +82,3 @@ kubernetes-pivoting-to-clouds.md
 
 
 
-

src/pentesting-cloud/kubernetes-security/abusing-roles-clusterroles-in-kubernetes/README.md

@@ -700,4 +700,3 @@ https://github.com/aquasecurity/kube-bench
 
 
 
-

src/pentesting-cloud/kubernetes-security/abusing-roles-clusterroles-in-kubernetes/kubernetes-roles-abuse-lab.md

@@ -614,4 +614,3 @@ kubectl delete serviceaccount test-sa
 
 
 
-

src/pentesting-cloud/kubernetes-security/abusing-roles-clusterroles-in-kubernetes/pod-escape-privileges.md

@@ -51,4 +51,3 @@ spec:
 
 
 
-

src/pentesting-cloud/kubernetes-security/attacking-kubernetes-from-inside-a-pod.md

@@ -397,4 +397,3 @@ Off-Menu         +
 
 
 
-

src/pentesting-cloud/kubernetes-security/exposing-services-in-kubernetes.md

@@ -217,4 +217,3 @@ kubectl get ingresses --all-namespaces -o=yaml
 
 
 
-

src/pentesting-cloud/kubernetes-security/kubernetes-basics.md

@@ -571,4 +571,3 @@ https://www.youtube.com/watch?v=X48VuDVv0do
 
 
 
-

src/pentesting-cloud/kubernetes-security/kubernetes-enumeration.md

@@ -614,4 +614,3 @@ https://www.cyberark.com/resources/threat-research-blog/kubernetes-pentest-metho
 
 
 
-

src/pentesting-cloud/kubernetes-security/kubernetes-external-secrets-operator.md

@@ -120,4 +120,3 @@ https://github.com/external-secrets/external-secrets
 
 
 
-

src/pentesting-cloud/kubernetes-security/kubernetes-hardening/README.md

@@ -176,4 +176,3 @@ You should update your Kubernetes environment as frequently as necessary to have
 
 
 
-

src/pentesting-cloud/kubernetes-security/kubernetes-hardening/kubernetes-securitycontext-s.md

@@ -64,4 +64,3 @@ Note that the attributes set in **both SecurityContext and PodSecurityContext**,
 
 
 
-

src/pentesting-cloud/kubernetes-security/kubernetes-kyverno/README.md

@@ -58,4 +58,3 @@ When a pod is created in the `default` namespace without the label `app: myapp`,
 
 
 
-

src/pentesting-cloud/kubernetes-security/kubernetes-kyverno/kubernetes-kyverno-bypass.md

@@ -62,4 +62,3 @@ Another way to bypass policies is to focus on the ValidatingWebhookConfiguration
 
 
 
-

src/pentesting-cloud/kubernetes-security/kubernetes-namespace-escalation.md

@@ -35,4 +35,3 @@ attacking-kubernetes-from-inside-a-pod.md
 
 
 
-

src/pentesting-cloud/kubernetes-security/kubernetes-network-attacks.md

@@ -292,4 +292,3 @@ It will install agents in the selected pods and gather their traffic information
 
 
 
-

src/pentesting-cloud/kubernetes-security/kubernetes-opa-gatekeeper/README.md

@@ -78,4 +78,3 @@ When Gatekeeper is deployed in the Kubernetes cluster, it will enforce this poli
 
 
 
-

src/pentesting-cloud/kubernetes-security/kubernetes-opa-gatekeeper/kubernetes-opa-gatekeeper-bypass.md

@@ -65,4 +65,3 @@ Another way to bypass constraints is to focus on the ValidatingWebhookConfigurat
 
 
 
-

src/pentesting-cloud/kubernetes-security/kubernetes-pivoting-to-clouds.md

@@ -325,4 +325,3 @@ fi
 
 
 
-

src/pentesting-cloud/kubernetes-security/kubernetes-role-based-access-control-rbac.md

@@ -167,4 +167,3 @@ abusing-roles-clusterroles-in-kubernetes/
 
 
 
-

src/pentesting-cloud/kubernetes-security/kubernetes-validatingwebhookconfiguration.md

@@ -104,4 +104,3 @@ abusing-roles-clusterroles-in-kubernetes/
 
 
 
-

src/pentesting-cloud/kubernetes-security/pentesting-kubernetes-services/README.md

@@ -216,4 +216,3 @@ https://labs.f-secure.com/blog/attacking-kubernetes-through-kubelet
 
 
 
-

src/pentesting-cloud/kubernetes-security/pentesting-kubernetes-services/kubelet-authentication-and-authorization.md

@@ -111,4 +111,3 @@ Forbidden (user=system:node:ip-172-31-28-172.ec2.internal, verb=get, resource=no
 
 
 
-