Aqua Security has been building cloud native security tools since 2015, back when "cloud native security" was not a market category. Their platform spans the full lifecycle from build-time scanning through runtime protection, and they maintain some of the most widely used open source security tools in the ecosystem (Trivy, Tracee, and others). This review covers the commercial platform, not the open source tools.
Platform Architecture
Aqua's platform is built around the concept of securing workloads across their lifecycle. The major components are:
Aqua Image Scanner handles vulnerability detection in container images, serverless functions, and VM images. It supports scanning in CI/CD pipelines, registries, and at runtime.
Aqua Enforcer is the runtime agent that deploys as a DaemonSet in Kubernetes or a sidecar alongside workloads. It enforces policies, monitors system calls, and detects anomalous behavior.
Aqua Console is the centralized management interface where you define policies, review findings, and manage your security posture.
Aqua Cloud Connector extends visibility to cloud infrastructure, covering misconfigurations in AWS, Azure, and GCP resources.
The architecture is agent-based for runtime protection and agentless for scanning. This hybrid approach is pragmatic. You need an agent to monitor runtime behavior, but you do not need one to scan images in a registry.
Image Scanning
Aqua's image scanning is built on top of their own vulnerability intelligence feed, which aggregates data from NVD, vendor advisories, and Aqua's own research team. The scanner checks for OS package vulnerabilities, application dependency vulnerabilities, malware, embedded secrets, and IaC misconfigurations in Dockerfiles.
The scanning accuracy is strong. In our testing across a representative set of container images, Aqua's findings were comparable to Snyk Container in terms of coverage, with slightly better performance on Alpine and distroless images.
What sets Aqua apart is the DTA (Dynamic Threat Analysis) feature. DTA runs suspicious images in a sandboxed environment to detect runtime behaviors that static analysis misses. This catches things like malware that only activates when the container starts, cryptocurrency miners embedded in base images, and reverse shells triggered by environment variables.
DTA is not fast. A full dynamic analysis takes 2-5 minutes per image, which is too slow for every image in CI. But for base images and third-party images entering your environment for the first time, it adds a layer of detection that purely static tools cannot match.
Runtime Protection
This is where Aqua truly differentiates. The Enforcer agent provides several runtime security capabilities.
Drift prevention stops containers from deviating from their original image. If a process tries to execute a binary that was not in the original image, the Enforcer blocks it. This is devastatingly effective against post-exploitation techniques that rely on downloading and executing additional tooling.
Runtime policies let you define allowed behaviors at a granular level. You can restrict network connections, file system writes, process execution, and system calls on a per-image or per-workload basis. Creating these policies manually would be tedious, so Aqua provides a learning mode that observes normal behavior and auto-generates a baseline policy.
The behavioral profiling works well in practice. After a 24-48 hour learning period, the generated profiles accurately capture normal workload behavior. Anomaly detection against these profiles catches lateral movement, data exfiltration attempts, and supply chain attacks that modify runtime behavior.
Kubernetes Security
Aqua provides Kubernetes-specific security features beyond what generic container security offers. It scans Kubernetes manifests for misconfigurations (privileged containers, host networking, missing resource limits), monitors RBAC policies for overly permissive roles, and tracks admission control policies.
The Aqua KubeEnforcer acts as a Kubernetes admission controller, blocking workloads that violate security policies before they are scheduled. This shift-left approach prevents vulnerable or misconfigured containers from reaching the cluster in the first place.
Aqua's Kubernetes risk assessment provides a prioritized view of security issues across namespaces, workloads, and clusters. The prioritization considers vulnerability severity, network exposure, and workload criticality, which is more useful than a flat list of CVEs.
Supply Chain Security
Aqua has invested in supply chain security features including image signing and verification, SBOM generation, and pipeline integrity monitoring. They support Sigstore/cosign for image signing and can verify signatures at admission time.
The SBOM capabilities leverage Trivy (which Aqua maintains) for generation and provide a management layer on top for storage, querying, and continuous monitoring against new vulnerabilities.
Pricing and Deployment
Aqua is enterprise-priced. Expect six-figure annual contracts for a meaningful deployment. Pricing is based on the number of protected workloads, with different tiers for scanning-only versus full runtime protection.
Deployment complexity is moderate. The console can run as a SaaS offering or self-hosted. The Enforcer requires a DaemonSet deployment, which means coordinating with infrastructure teams and testing for performance impact on workloads. In our experience, the Enforcer's resource overhead is modest (50-100MB RAM per node) but non-zero.
Strengths and Weaknesses
Strengths: DTA for dynamic analysis, runtime drift prevention, behavioral profiling, comprehensive Kubernetes security, strong open source pedigree through Trivy and Tracee.
Weaknesses: Enterprise pricing excludes smaller organizations, agent deployment adds operational complexity, the console UI can be overwhelming for teams new to container security, and the breadth of features means a long time-to-value without dedicated security engineering resources.
How Safeguard.sh Helps
Safeguard.sh complements Aqua's deep container and runtime security with broader supply chain visibility. While Aqua focuses on workload-level protection, Safeguard.sh tracks the software supply chain across your entire portfolio including components that do not run in containers. The two platforms together give you depth (Aqua) and breadth (Safeguard.sh) in your security program. Safeguard.sh also ingests SBOM and vulnerability data from Aqua, providing a unified view alongside data from other tools in your security stack.