Container with Host Network
The pod shares the node's network stack, so it can bind host ports and reach services meant to stay cluster-internal.
Free to start. No card. The playground just needs your work email.
AWSAzureGoogle CloudKubernetes
Found, explained, handed over.
Exposure and fragility, security posture and single points of failure.
Detect
ZopNight checks this automatically across AWS, Azure and Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Disable host networking on deployment.
Fix
The finding opens with the change already spelled out, so the fix is one ticket, not an investigation.
- Applies to
- EKS DaemonSets on AWS, EKS Deployments on AWS, EKS StatefulSets on AWS, AKS DaemonSets on Azure, AKS Deployments on Azure, AKS StatefulSets on Azure, GKE DaemonSets on Google Cloud, GKE Deployments on Google Cloud, GKE StatefulSets on Google Cloud
- Category
- Security. Risky configurations: privileged containers, containers running as root, host networking, ingress without TLS.
- Where it appears
- The Risk tab of Recommendations, with every affected resource listed.
- Rule IDs
RC-1729RC-1730RC-1731RC-1829RC-1830RC-1831RC-1929RC-1930RC-1931- Full reference
Related checks
See the security findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.