Multi-Tenant Cloud Ingress & API Gateway (AWS / K8s Ingress)
Description & Perimeter Architecture
Section titled โDescription & Perimeter ArchitectureโCloud-native ingress gateway routing public API requests to backend container microservices.
Entry Points & Service Interfaces
Section titled โEntry Points & Service Interfacesโ| Protocol | Port | Service Description | Auth Requirement | Associated CVEs |
|---|---|---|---|---|
TCP | 443 | HTTPS Envoy / NGINX Ingress Controller | Bearer Token / JWT | CVE-2026-64456 |
TCP | 8443 | Kubernetes API Health & Metrics Endpoint | Mutual TLS (mTLS) | None |
Continuous Probing Routines
Section titled โContinuous Probing Routinesโ-
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.
- Safe Probe Action:
-
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.
- Safe Probe Action:
Threat Actor Targeting Context
Section titled โThreat Actor Targeting ContextโThreat actors actively weaponizing this attack surface: