About Container Security

OX gives you end-to-end container security by linking container images, runtime environments, and deployment metadata — so you see what’s built, where it runs, and whether it’s safe.

With container security in OX you cover multiple stages of the lifecycle, combining static analysis, cluster context, and live runtime visibility.

This chapter includes the following key components:

K8 integrations Connect your Kubernetes clusters (e.g. via GKE) to OX. Once connected, OX enhances visibility with cloud-native metadata: it shows which workloads are deployed, what images are running, and how services are exposed. The integration enriches your application inventory, and raises the priority of issues depending on actual deployment and reachability in the cloud.

CS policy (static analysis, images & configurations) Before deployment, OX scans container images and configurations to detect vulnerabilities, misconfigurations, and insecure dependencies. This helps catch problems early — during build or CI/CD — before artifacts ever reach your clusters or production.

Runtime (live behavior & usage context) With the OX Runtime Sensor you get runtime signals from your Kubernetes workloads. The Sensor observes which libraries and dependencies are actually loaded in memory at runtime. If a known vulnerability affects a library that’s actively loaded, OX marks that issue with higher severity, giving better insight into real, exploitable risk rather than theoretical vulnerabilities.

Inspector (cluster-level data & metadata collection) OX K8s Inspector runs inside your cluster (as a CronJob), periodically collecting configuration and metadata about deployments, images in use, and active workloads. It securely sends that data to OX for analysis. This is especially useful in environments where the Kubernetes API isn’t exposed externally; Inspector works entirely from within the cluster while still giving OX full visibility into what’s running.

Use these components together so you can:

• Understand what container images and configurations you build, store, and run.

• Know which workloads are deployed — and exposed — in your clusters.

• Detect vulnerabilities before deployment and track real runtime risk after deployment.

• Prioritize fixes and remediation based on what your environment actually uses.