Rule explorer
Browse every hardening rule in the catalog. Filter by platform, severity, profile level and whether the check can be automated.
43 rules foundof 16,927Page 1 of 2
| ID | Title | Platform | Severity | Level | Check |
|---|---|---|---|---|---|
| TMA-OKE-3.2.1 | Ensure kubelet anonymous authentication is disabledoke · Level 1 | oke | Critical | 1 | Automated |
| TMA-OKE-4.1.1 | Ensure that the cluster-admin role is only used where requiredoke · Level 1 | oke | Critical | 1 | Manual review |
| TMA-OKE-4.2.1 | Minimize the admission of privileged containersoke · Level 1 | oke | Critical | 1 | Automated |
| TMA-OKE-2.1.1 | Use OCI IAM or OIDC tokens instead of user client certificatesoke · Level 1 | oke | High | 1 | Manual review |
| TMA-OKE-2.2.1 | Ensure authorized access to OCI Audit logs for OKE activityoke · Level 1 | oke | High | 1 | Manual review |
| TMA-OKE-3.2.2 | Ensure kubelet authorization mode is set to Webhookoke · Level 1 | oke | High | 1 | Automated |
| TMA-OKE-3.2.3 | Ensure the kubelet X.509 client CA file is configuredoke · Level 1 | oke | High | 1 | Automated |
| TMA-OKE-3.2.4 | Ensure the kubelet read-only port is disabledoke · Level 1 | oke | High | 1 | Manual review |
| TMA-OKE-3.2.7 | Ensure kubelet tlsCertFile and tlsPrivateKeyFile are configured appropriatelyoke · Level 1 | oke | High | 1 | Automated |
| TMA-OKE-3.2.8 | Ensure the kubelet client certificate rotation is enabledoke · Level 1 | oke | High | 1 | Automated |
| TMA-OKE-4.1.2 | Ensure access to Secrets is minimized and granted only where requiredoke · Level 1 | oke | High | 1 | Manual review |
| TMA-OKE-4.1.5 | Ensure that default service accounts are not actively used.oke · Level 1 | oke | High | 1 | Automated |
| TMA-OKE-4.1.6 | Ensure that Service Account Tokens are only mounted where necessaryoke · Level 1 | oke | High | 1 | Automated |
| TMA-OKE-4.2.2 | Minimize the admission of containers wishing to share the host process ID namespaceoke · Level 1 | oke | High | 1 | Automated |
| TMA-OKE-4.2.3 | Minimize the admission of containers wishing to share the host IPC namespaceoke · Level 1 | oke | High | 1 | Automated |
| TMA-OKE-4.2.4 | Minimize the admission of containers wishing to share the host network namespaceoke · Level 1 | oke | High | 1 | Automated |
| TMA-OKE-4.2.5 | Minimize the admission of containers with allowPrivilegeEscalationoke · Level 1 | oke | High | 1 | Automated |
| TMA-OKE-4.4.1 | Prefer exposing secrets as mounted files rather than environment variablesoke · Level 1 | oke | High | 1 | Automated |
| TMA-OKE-4.4.2 | Consider external secret storageoke · Level 1 | oke | High | 1 | Manual review |
| TMA-OKE-5.2.1 | Use dedicated Kubernetes service accounts for OKE workloadsoke · Level 1 | oke | High | 1 | Automated |
| TMA-OKE-5.3.1 | Use customer managed KMS keys for OKE envelope encryption of Kubernetes secretsoke · Level 1 | oke | High | 1 | Manual review |
| TMA-OKE-5.4.1 | Restrict OKE control plane endpoint access using private endpoints or approved CIDRsoke · Level 1 | oke | High | 1 | Manual review |
| TMA-OKE-5.4.2 | Enable private OKE control plane access and disable public IP accessoke · Level 1 | oke | High | 1 | Automated |
| TMA-OKE-5.4.3 | Ensure clusters are created with Private Nodesoke · Level 1 | oke | High | 1 | Manual review |
| TMA-OKE-5.4.5 | Use TLS certificates on OKE load balancer listeners for encrypted client connectionsoke · Level 1 | oke | High | 1 | Manual review |