O3 Security Image Scanner
o3.security
- Free plan
- Web
What O3 Security Image Scanner is
O3 Security Image Scanner checks container images for operating-system vulnerabilities, malicious layers, embedded secrets, and permission misconfigurations before registry push. It supports Docker, OCI, and distroless images and inspects every layer for packages, application code, credentials, and changes. Malware checks compare added binaries with known-good hashes and detect malicious signatures, unexpected cron jobs, startup scripts, and obfuscated shell scripts. Secret detection can find API keys, database credentials, and private keys left in earlier layers after later deletion. Scans can run on push, on pull through a scanning proxy, or on a recurring schedule. Integrations include Amazon ECR, Google GCR and Artifact Registry, Azure ACR, Docker Hub, and private registries using Docker Registry API v2. Each scan creates CycloneDX and SPDX SBOM output. Findings include CVSS, exploitability, fix version, and introducing layer. Promotion to production can be blocked for critical findings. O3 states that self-hosted deployment supports customer VPC or air-gapped environments.
Who it suits
It suits security and platform teams scanning container images in CI pipelines or registries. Self-hosted deployment fits organizations requiring VPC or air-gapped operation.
Good to know, and what to watch
- Inspects every image layer
- Detects secrets retained in earlier layers
- Produces CycloneDX and SPDX SBOMs
- Can block critical production promotions
- Supports self-hosted air-gapped deployment
- Pricing is available only on request
- Critical-finding blocking depends on registry integration
- Private registries require Docker Registry API v2
Plans
Every plan and pricePaid
Pricing on request
The verdict
O3 combines layer inspection, vulnerability intelligence, secret detection, SBOM generation, and registry controls. Its deployment and integration model should be matched to your image pipeline.
What the maker publishes
- Data protection
- O3 states that data in transit uses TLS 1.3, data at rest uses AES-256, and production access is restricted, logged, and reviewed. source
- Deployment
- O3 states that it offers self-hosted deployment inside a customer VPC or air-gapped environment with no outbound telemetry required. source
- Image formats
- The scanner works with Docker, OCI, and distroless images. source
- Integrations
- O3 lists more than 30 native integrations across CI/CD, code editors, package managers, cloud, ticketing, and registries. source
- Layer inspection
- O3 decomposes and inspects every image layer, including OS packages, application code, credentials, and layer changes. source
- Malware detection
- O3 compares added binaries against known-good hashes and detects malicious signatures, unexpected cron jobs, startup scripts, and obfuscated shell scripts. source
- Promotion blocking
- The registry integration can block promotion to a production registry when critical findings are present. source
- Purpose
- O3 scans container images for OS vulnerabilities, malicious layers, embedded secrets, and misconfigured permissions before registry push. source
- Registry integrations
- The image scanner integrates with Amazon ECR, Google GCR and Artifact Registry, Azure ACR, Docker Hub, and private registries using Docker Registry API v2. source
- Registry scanning
- Images can be scanned on push, on pull through a scanning proxy, or on a recurring schedule. source
- SBOM output
- Each scan generates SBOM output in CycloneDX and SPDX formats. source
- Secret detection
- O3 detects secrets that remain in earlier layers even after later deletion, including API keys, database credentials, and private keys. source
- Security certifications
- O3 states that it is SOC 2 Type II and ISO 27001 certified, with audit reports available on request under NDA. source
- Vulnerability intelligence
- O3 matches packages against NVD, OSV, and distribution-specific advisories and reports CVSS, exploitability, fix version, and introducing layer. source
Checked against the maker's pages on 1 Oct 2026.