KubernetesOverview
Encrypt traffic to HTTPS load balancers using TLS certificates.
Rationale
Encrypting traffic between users and your Kubernetes workload is fundamental to protecting data sent over the web.
Audit
Your load balancer vendor can provide details on auditing the certificates and policies required to utilize TLS.
Remediation guidance
Your load balancer vendor can provide details on configuring HTTPS with TLS.
References
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
Kubernetes
Use admission policies, baseline cluster configuration, GitOps templates, and namespace or workload guardrails so new deployments follow the control by default.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
Ingresses without TLS config
Connectors
Covered asset types
Expected check: eq []
{
EKSIngressesWithoutTLSConfig {
...AssetFragment
}
}
