TMAegis

Rule explorer

Browse every hardening rule in the catalog. Filter by platform, severity, profile level and whether the check can be automated.

50 rules foundof 11,219Page 1 of 2

IDTitleSeverity
TMA-AKS-3.2.1Ensure that the --anonymous-auth argument is set to falseaks · Level 1Critical
TMA-AKS-3.2.2Ensure that the --authorization-mode argument is not set to AlwaysAllowaks · Level 1Critical
TMA-AKS-4.1.1Ensure that the cluster-admin role is only used where requiredaks · Level 1Critical
TMA-AKS-4.2.1Minimize the admission of privileged containersaks · Level 1Critical
TMA-AKS-3.2.3Ensure that the --client-ca-file argument is set as appropriateaks · Level 1High
TMA-AKS-3.2.4Ensure that the --read-only-port is set to 0aks · Level 1High
TMA-AKS-4.1.2Ensure access to Secrets is minimized and granted only where requiredaks · Level 1High
TMA-AKS-4.1.5Ensure that default service accounts are not actively usedaks · Level 1High
TMA-AKS-4.1.6Ensure that Service Account Tokens are only mounted where necessaryaks · Level 1High
TMA-AKS-4.1.7Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes clusteraks · Level 1High
TMA-AKS-4.1.9Minimize access to the proxy sub-resource of nodesaks · Level 1High
TMA-AKS-4.1.11Minimize access to webhook configuration objectsaks · Level 1High
TMA-AKS-4.1.12Minimize access to the service account token creationaks · Level 1High
TMA-AKS-4.2.2Minimize the admission of containers wishing to share the host process ID namespaceaks · Level 1High
TMA-AKS-4.2.3Minimize the admission of containers wishing to share the host IPC namespaceaks · Level 1High
TMA-AKS-4.2.4Minimize the admission of containers wishing to share the host network namespaceaks · Level 1High
TMA-AKS-4.2.5Minimize the admission of containers with allowPrivilegeEscalationaks · Level 1High
TMA-AKS-5.2.1Prefer using dedicated AKS Service Accountsaks · Level 1High
TMA-AKS-5.3.1Encrypt Kubernetes Secrets at rest with AKS KMS protectionaks · Level 1High
TMA-AKS-5.4.2Use private AKS clusters and disable public control plane DNSaks · Level 2High
TMA-AKS-5.4.3Ensure clusters are created with Private Nodesaks · Level 1High
TMA-AKS-2.1.1Enable Diagnostic Platform Logs and Metricsaks · Level 1Medium
TMA-AKS-3.1.1Ensure that the kubeconfig file permissions are set to 644 or more restrictiveaks · Level 1Medium
TMA-AKS-3.1.2Ensure that the kubelet kubeconfig file ownership is set to root:rootaks · Level 1Medium
TMA-AKS-3.1.3Ensure that the azure.json file has permissions set to 644 or more restrictiveaks · Level 1Medium