TMAegis

Pregledač pravila

Pregledajte svako pravilo za ojačavanje bezbednosti u katalogu. Filtrirajte po platformi, ozbiljnosti, nivou profila i tome da li se provera može automatizovati.

Pronađena 43 pravilaod 11.219Stranica 1 od 2

IDNaslovOzbiljnost
TMA-OKE-3.2.1Ensure kubelet anonymous authentication is disabledoke · Nivo 1Kritična
TMA-OKE-4.1.1Ensure that the cluster-admin role is only used where requiredoke · Nivo 1Kritična
TMA-OKE-4.2.1Minimize the admission of privileged containersoke · Nivo 1Kritična
TMA-OKE-2.1.1Use OCI IAM or OIDC tokens instead of user client certificatesoke · Nivo 1Visoka
TMA-OKE-2.2.1Ensure authorized access to OCI Audit logs for OKE activityoke · Nivo 1Visoka
TMA-OKE-3.2.2Ensure kubelet authorization mode is set to Webhookoke · Nivo 1Visoka
TMA-OKE-3.2.3Ensure the kubelet X.509 client CA file is configuredoke · Nivo 1Visoka
TMA-OKE-3.2.4Ensure the kubelet read-only port is disabledoke · Nivo 1Visoka
TMA-OKE-3.2.7Ensure kubelet tlsCertFile and tlsPrivateKeyFile are configured appropriatelyoke · Nivo 1Visoka
TMA-OKE-3.2.8Ensure the kubelet client certificate rotation is enabledoke · Nivo 1Visoka
TMA-OKE-4.1.2Ensure access to Secrets is minimized and granted only where requiredoke · Nivo 1Visoka
TMA-OKE-4.1.5Ensure that default service accounts are not actively used.oke · Nivo 1Visoka
TMA-OKE-4.1.6Ensure that Service Account Tokens are only mounted where necessaryoke · Nivo 1Visoka
TMA-OKE-4.2.2Minimize the admission of containers wishing to share the host process ID namespaceoke · Nivo 1Visoka
TMA-OKE-4.2.3Minimize the admission of containers wishing to share the host IPC namespaceoke · Nivo 1Visoka
TMA-OKE-4.2.4Minimize the admission of containers wishing to share the host network namespaceoke · Nivo 1Visoka
TMA-OKE-4.2.5Minimize the admission of containers with allowPrivilegeEscalationoke · Nivo 1Visoka
TMA-OKE-4.4.1Prefer exposing secrets as mounted files rather than environment variablesoke · Nivo 1Visoka
TMA-OKE-4.4.2Consider external secret storageoke · Nivo 1Visoka
TMA-OKE-5.2.1Use dedicated Kubernetes service accounts for OKE workloadsoke · Nivo 1Visoka
TMA-OKE-5.3.1Use customer managed KMS keys for OKE envelope encryption of Kubernetes secretsoke · Nivo 1Visoka
TMA-OKE-5.4.1Restrict OKE control plane endpoint access using private endpoints or approved CIDRsoke · Nivo 1Visoka
TMA-OKE-5.4.2Enable private OKE control plane access and disable public IP accessoke · Nivo 1Visoka
TMA-OKE-5.4.3Ensure clusters are created with Private Nodesoke · Nivo 1Visoka
TMA-OKE-5.4.5Use TLS certificates on OKE load balancer listeners for encrypted client connectionsoke · Nivo 1Visoka