Rule explorer
Browse every hardening rule in the catalog. Filter by platform, severity, profile level and whether the check can be automated.
34 rules foundof 8,597Page 1 of 2
| ID | Title | Platform | Severity | Level | Check |
|---|---|---|---|---|---|
| TMA-EKS-AUTO-4.2.1 | Prevent workloads from running privileged containerseks-auto · Level 1 | eks-auto | Critical | 1 | Automated |
| TMA-EKS-AUTO-4.1.2 | Ensure access to Secrets is minimized and granted only where requiredeks-auto · Level 1 | eks-auto | High | 1 | Manual review |
| TMA-EKS-AUTO-4.1.5 | Ensure that default service accounts are not actively usedeks-auto · Level 1 | eks-auto | High | 1 | Automated |
| TMA-EKS-AUTO-4.1.6 | Ensure that Service Account Tokens are only mounted where necessaryeks-auto · Level 1 | eks-auto | High | 1 | Automated |
| TMA-EKS-AUTO-4.1.7 | Standardize EKS cluster access by using access entries, policies, and permissionseks-auto · Level 1 | eks-auto | High | 1 | Automated |
| TMA-EKS-AUTO-4.1.8 | Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes clustereks-auto · Level 1 | eks-auto | High | 1 | Manual review |
| TMA-EKS-AUTO-4.1.11 | Restrict webhook configuration access to approved identitieseks-auto · Level 1 | eks-auto | High | 1 | Manual review |
| TMA-EKS-AUTO-4.1.12 | Minimize access to the service account token creationeks-auto · Level 1 | eks-auto | High | 1 | Manual review |
| TMA-EKS-AUTO-4.2.2 | Prevent pods from sharing the host process ID namespaceeks-auto · Level 1 | eks-auto | High | 1 | Automated |
| TMA-EKS-AUTO-4.2.4 | Require workload pods to run with hostNetwork set to falseeks-auto · Level 1 | eks-auto | High | 1 | Automated |
| TMA-EKS-AUTO-4.2.5 | Require workload containers to set allowPrivilegeEscalation to falseeks-auto · Level 1 | eks-auto | High | 1 | Automated |
| TMA-EKS-AUTO-4.4.1 | Mount secrets as files instead of environment variableseks-auto · Level 1 | eks-auto | High | 1 | Manual review |
| TMA-EKS-AUTO-4.4.2 | Use external secret storage for sensitive valueseks-auto · Level 1 | eks-auto | High | 1 | Manual review |
| TMA-EKS-AUTO-5.1.2 | Enforce least privilege for ECR repositories storing EKS Auto Mode workload imageseks-auto · Level 1 | eks-auto | High | 1 | Manual review |
| TMA-EKS-AUTO-5.1.3 | Restrict EKS Auto Mode Node IAM role to ECR pull-only permissionseks-auto · Level 1 | eks-auto | High | 1 | Manual review |
| TMA-EKS-AUTO-5.2.1 | Use dedicated service accounts for EKS Auto Mode workload identitieseks-auto · Level 1 | eks-auto | High | 1 | Automated |
| TMA-EKS-AUTO-5.3.1 | Encrypt EKS API data with customer managed KMS keyseks-auto · Level 1 | eks-auto | High | 1 | Manual review |
| TMA-EKS-AUTO-5.4.1 | Enable private EKS API access and restrict public access to approved CIDRseks-auto · Level 1 | eks-auto | High | 1 | Automated |
| TMA-EKS-AUTO-5.4.2 | Enable private only EKS API access and disable public endpoint accesseks-auto · Level 1 | eks-auto | High | 1 | Automated |
| TMA-EKS-AUTO-5.4.3 | Deploy EKS Auto Mode nodes only in private subnetseks-auto · Level 1 | eks-auto | High | 1 | Manual review |
| TMA-EKS-AUTO-5.4.4 | Use TLS certificates for EKS Auto Mode load balancer listenerseks-auto · Level 1 | eks-auto | High | 1 | Manual review |
| TMA-EKS-AUTO-5.5.1 | Use EKS access entries for IAM principal Kubernetes accesseks-auto · Level 1 | eks-auto | High | 1 | Automated |
| TMA-EKS-AUTO-4.1.1 | Grant AmazonEKSClusterAdminPolicy only where full cluster administration is requiredeks-auto · Level 1 | eks-auto | Medium | 1 | Manual review |
| TMA-EKS-AUTO-4.1.3 | Minimize wildcard use in Roles and ClusterRoleseks-auto · Level 1 | eks-auto | Medium | 1 | Manual review |
| TMA-EKS-AUTO-4.1.4 | Minimize access to create podseks-auto · Level 1 | eks-auto | Medium | 1 | Manual review |