Rule explorer
Browse every hardening rule in the catalog. Filter by platform, severity, profile level and whether the check can be automated.
16,927 rules foundPage 13 of 678
| ID | Title | Platform | Severity | Level | Check |
|---|---|---|---|---|---|
| TMA-AKS-AUTOMATIC-4.1.8 | Minimize access to create persistent storageaks-automatic · Level 1 | aks-automatic | Medium | 1 | Manual review |
| TMA-AKS-AUTOMATIC-4.1.9 | Minimize access to the nodes/proxy subresourceaks-automatic · Level 1 | aks-automatic | Medium | 1 | Manual review |
| TMA-AKS-AUTOMATIC-4.1.10 | Minimize access to the approval subresource of CertificateSigningRequests objectsaks-automatic · Level 1 | aks-automatic | Medium | 1 | Manual review |
| TMA-AKS-AUTOMATIC-4.4.1 | Prefer exposing secrets as mounted files rather than environment variablesaks-automatic · Level 2 | aks-automatic | Medium | 2 | Automated |
| TMA-AKS-AUTOMATIC-4.4.2 | Consider external secret storageaks-automatic · Level 2 | aks-automatic | Medium | 2 | Manual review |
| TMA-AKS-AUTOMATIC-5.1.1 | Ensure container image vulnerability scanning with Defender for Containers or a third-party provideraks-automatic · Level 1 | aks-automatic | Medium | 1 | Manual review |
| TMA-AKS-AUTOMATIC-5.1.2 | Minimize and scope access to Azure Container Registry (ACR)aks-automatic · Level 1 | aks-automatic | Medium | 1 | Manual review |
| TMA-AKS-AUTOMATIC-5.1.3 | Limit AKS access to pull images from Azure Container Registry (ACR)aks-automatic · Level 1 | aks-automatic | Medium | 1 | Manual review |
| TMA-AKS-AUTOMATIC-5.1.4 | Restrict AKS workloads to approved container registries onlyaks-automatic · Level 2 | aks-automatic | Medium | 2 | Manual review |
| TMA-AKS-AUTOMATIC-5.4.1 | Restrict Access to the Control Plane Endpointaks-automatic · Level 1 | aks-automatic | Medium | 1 | Automated |
| TMA-AKS-AUTOMATIC-5.4.4 | Use HTTPS with valid TLS certificates for externally exposed workloadsaks-automatic · Level 2 | aks-automatic | Medium | 2 | Manual review |
| TMA-AKS-AUTOMATIC-5.5.1 | Use Microsoft Entra ID authorization for the Kubernetes APIaks-automatic · Level 2 | aks-automatic | Medium | 2 | Manual review |
| TMA-AKS-AUTOMATIC-4.5.1 | Create administrative boundaries between resources using namespacesaks-automatic · Level 1 | aks-automatic | Low | 1 | Manual review |
| TMA-AKS-AUTOMATIC-4.5.2 | Apply Security Context to Your Pods and Containersaks-automatic · Level 2 | aks-automatic | Low | 2 | Manual review |
| TMA-AKS-AUTOMATIC-4.5.3 | The default namespace should not be usedaks-automatic · Level 2 | aks-automatic | Low | 2 | Automated |
| TMA-ALIBABA-1.1 | Avoid the use of the "root" accountalibaba · Level 1 | alibaba | High | 1 | Manual review |
| TMA-ALIBABA-1.2 | Ensure no root account access key existsalibaba · Level 1 | alibaba | High | 1 | Manual review |
| TMA-ALIBABA-1.3 | Ensure MFA is enabled for the "root" accountalibaba · Level 1 | alibaba | High | 1 | Manual review |
| TMA-ALIBABA-1.4 | Ensure that multi-factor authentication is enabled for all RAM users that have a console passwordalibaba · Level 1 | alibaba | High | 1 | Automated |
| TMA-ALIBABA-1.7 | Ensure RAM password policy requires at least one uppercase letteralibaba · Level 1 | alibaba | High | 1 | Automated |
| TMA-ALIBABA-1.8 | Ensure RAM password policy requires at least one lowercase letteralibaba · Level 1 | alibaba | High | 1 | Automated |
| TMA-ALIBABA-1.9 | Ensure RAM password policy require at least one symbolalibaba · Level 1 | alibaba | High | 1 | Automated |
| TMA-ALIBABA-1.10 | Ensure RAM password policy require at least one numberalibaba · Level 1 | alibaba | High | 1 | Automated |
| TMA-ALIBABA-1.11 | Ensure RAM password policy requires minimum length of 14 or greateralibaba · Level 1 | alibaba | High | 1 | Automated |
| TMA-ALIBABA-1.12 | Ensure RAM password policy prevents password reusealibaba · Level 1 | alibaba | High | 1 | Automated |