KubernetesOverview
AI runtimes and agents should not use host networking unless there is a clear infrastructure requirement. Host networking bypasses normal service isolation and can expose model endpoints, agent tools, or metadata paths beyond the intended pod boundary.
Remediation guidance
Remediation
Remove host networking from AI workloads and expose only the required service ports through Kubernetes Services, Ingress, or a private gateway.
- Review why host networking is enabled.
- Move traffic to normal pod networking or a dedicated gateway.
- Add network policies and endpoint authentication for model and agent services.
Query logic
These are the stored checks tied to this control.
AI Kubernetes workloads should not use host networking
Connectors
Kubernetes
Covered asset types
AI ServicesCronJobDaemonSetDeploymentJobPodStatefulSet
Expected check: eq []
{
pods(where: { assetCategory: { eq: "AI Services" }, hostNetwork: { eq: true } }) { ...AssetFragment }
deployments(where: { assetCategory: { eq: "AI Services" }, podTemplate: { hostNetwork: { eq: true } } }) { ...AssetFragment }
statefulSets(where: { assetCategory: { eq: "AI Services" }, podTemplate: { hostNetwork: { eq: true } } }) { ...AssetFragment }
daemonSets(where: { assetCategory: { eq: "AI Services" }, podTemplate: { hostNetwork: { eq: true } } }) { ...AssetFragment }
jobs(where: { assetCategory: { eq: "AI Services" }, cronJobName: { eq: "" }, podTemplate: { hostNetwork: { eq: true } } }) { ...AssetFragment }
cronJobs(where: { assetCategory: { eq: "AI Services" }, podTemplate: { hostNetwork: { eq: true } } }) { ...AssetFragment }
}
