Skip to content

Multi-Tenant Cloud Ingress & API Gateway (AWS / K8s Ingress)

Density:

Cloud-native ingress gateway routing public API requests to backend container microservices.

ProtocolPortService DescriptionAuth RequirementAssociated CVEs
TCP443HTTPS Envoy / NGINX Ingress ControllerBearer Token / JWTCVE-2026-64456
TCP8443Kubernetes API Health & Metrics EndpointMutual TLS (mTLS)None

  1. Path Traversal & HTTP Smuggling Canary (CHK-INGRESS-01 โ€” Frequency: every_6_hours)

    • Safe Probe Action: Inject benign duplicate Content-Length and Transfer-Encoding header to detect proxy discrepancies.
    • Expected Baseline State: Immediate HTTP 400 Bad Request rejection by edge WAF.
  2. TLS Certificate SAN & Cipher Suite Weakness Audit (CHK-INGRESS-02 โ€” Frequency: daily)

    • Safe Probe Action: Enumerate TLS 1.3/1.2 ciphers and verify validity of wildcard domain certificates.
    • Expected Baseline State: All legacy ciphers (CBC, RC4, 3DES) disabled; HSTS enabled with max-age >= 31536000.

Threat actors actively weaponizing this attack surface: