GITBOOK-641: No subject

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

@@ -60,7 +60,15 @@ kube-hunter --remote some.node.com
 
 ### [**KubiScan**](https://github.com/cyberark/KubiScan)
 
-[**KubiScan**](https://github.com/cyberark/KubiScan) is a tool for scanning Kubernetes cluster for risky permissions in Kubernetes's Role-based access control (RBAC) authorization model. 
+[**KubiScan**](https://github.com/cyberark/KubiScan) is a tool for scanning Kubernetes cluster for risky permissions in Kubernetes's Role-based access control (RBAC) authorization model.
+
+### [Managed Kubernetes Auditing Toolkit](https://github.com/DataDog/managed-kubernetes-auditing-toolkit)
+
+[**Mkat**](https://github.com/DataDog/managed-kubernetes-auditing-toolkit) is a tool built to test other type of high risk checks compared with the other tools. It mainly have 3 different modes:
+
+* **`find-role-relationships`**: Which will find which AWS roles are running in which pods
+* **`find-secrets`**: Which tries to identify secrets in K8s resources such as Pods, ConfigMaps, and Secrets.
+* **`test-imds-access`**: Which will try to run pods and try to access the metadata v1 and v2. WARNING: This will run a pod in the cluster, be very careful because maybe you don't want to do this!
 
 ## **Audit IaC Code**
 
@@ -156,7 +164,6 @@ spec:
 * [https://kubernetes.io/docs/tasks/configure-pod-container/security-context/](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/)
 * [https://kubernetes.io/docs/concepts/policy/pod-security-policy/](https://kubernetes.io/docs/concepts/policy/pod-security-policy/)
 
-
 ### General Hardening
 
 You should update your Kubernetes environment as frequently as necessary to have: