Aqua Security
Aqua Security provides cloud-native security for the full application lifecycle, protecting containers, serverless functions, and cloud workloads with vulnerability scanning, runtime protection, and compliance enforcement.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Aqua Security the way a machine reads it — 102 machine-readable artifacts across 8 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Aqua Security scores 66.7/100 (strong), with a separate agent-readiness read of 60/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Aqua Security
Each block below is one kind of artifact we hold for Aqua Security. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Trivy
Trivy is a comprehensive open source security scanner for containers, Kubernetes, code repositories, clouds, and more — finding vulnerabilities, misconfigurations, secrets, and ...
Tracee
Tracee is a runtime security and forensics tool for Linux that uses eBPF technology to trace system events and detect suspicious behavioral patterns.
Aqua Security Authentication API
User authentication and token management
Aqua Security Containers API
Running container monitoring and enforcement
Aqua Security Images API
Container image scanning and vulnerability management
Aqua Security Policies API
Security policy management
Aqua Security Registries API
Container registry configuration
Aqua Security Users API
User and role management
Scroll within the panel for all 8 ·
Arazzo Workflows 8
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Aqua Security Create Assurance Policy
Authenticate, create an image assurance security policy, then list policies to confirm it was registered.
ARAZZOAqua Security Image Compliance Gate
Authenticate, poll an image scan to completion, then branch on whether critical or high vulnerabilities were found to pass or fail a compliance gate.
ARAZZOAqua Security Image Vulnerability Lookup
Authenticate, list registered images filtered by registry and repository, then fetch full vulnerability detail for the first match.
ARAZZOAqua Security Onboard Registry Image
Authenticate, confirm the target registry is configured, register an image from it, then poll the scan to completion.
ARAZZOAqua Security Registry Inventory
Authenticate, list configured registries, then enumerate the images registered under the first connected registry.
ARAZZOAqua Security Rescan And Cleanup
Authenticate, re-register an image to trigger a fresh scan, poll until it completes, then delete the image when its scan failed.
ARAZZOAqua Security Running Container Inventory
Authenticate, list running containers monitored by the enforcer, then read the image detail behind the first running container.
ARAZZOAqua Security Scan Image On Demand
Authenticate, register a container image for scanning, then poll until the scan completes and read its vulnerability counts.
ARAZZOScroll within the panel for all 8 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
MCP Server
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Aqua Security Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Aqua Security Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Vulnerability Scanning
Comprehensive scanning of container images, VM workloads, and serverless functions for known CVEs and misconfigurations.
Runtime Protection
Real-time protection of running containers and cloud workloads using behavioral analysis and policy enforcement.
CSPM
Cloud Security Posture Management to identify and remediate misconfigurations across AWS, Azure, and GCP.
Supply Chain Security
Protect the software supply chain by scanning code, open source dependencies, and CI/CD pipelines.
Kubernetes Security
Native Kubernetes security including admission control, runtime policies, and compliance benchmarks.
Compliance Enforcement
Automated compliance checks against CIS, PCI-DSS, HIPAA, NIST, and other regulatory frameworks.
Secrets Detection
Detect and prevent secrets and credentials from being embedded in container images and code repositories.
Network Policy
Visualize and enforce container network connectivity and micro-segmentation policies.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Aqua Security Api Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Aqua Security API Rules
SPECTRALAqua Security API Rules
SPECTRALJSON Schema 17
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ContainerList
JSON SCHEMAContainer
JSON SCHEMAErrorResponse
JSON SCHEMAImageDetail
JSON SCHEMAImageList
JSON SCHEMAImageRequest
JSON SCHEMAImage
JSON SCHEMALoginRequest
JSON SCHEMALoginResponse
JSON SCHEMAPolicyList
JSON SCHEMAPolicyRequest
JSON SCHEMAPolicy
JSON SCHEMARegistryList
JSON SCHEMARegistry
JSON SCHEMAUserList
JSON SCHEMAUser
JSON SCHEMAVulnerabilityCounts
JSON SCHEMAScroll within the panel for all 17 ·
JSON Structure 17
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Aqua Security Api Container List Structure
JSON STRUCTUREAqua Security Api Container Structure
JSON STRUCTUREAqua Security Api Error Response Structure
JSON STRUCTUREAqua Security Api Image Detail Structure
JSON STRUCTUREAqua Security Api Image List Structure
JSON STRUCTUREAqua Security Api Image Request Structure
JSON STRUCTUREAqua Security Api Image Structure
JSON STRUCTUREAqua Security Api Login Request Structure
JSON STRUCTUREAqua Security Api Login Response Structure
JSON STRUCTUREAqua Security Api Policy List Structure
JSON STRUCTUREAqua Security Api Policy Request Structure
JSON STRUCTUREAqua Security Api Policy Structure
JSON STRUCTUREAqua Security Api Registry List Structure
JSON STRUCTUREAqua Security Api Registry Structure
JSON STRUCTUREAqua Security Api User List Structure
JSON STRUCTUREAqua Security Api User Structure
JSON STRUCTUREAqua Security Api Vulnerability Counts Structure
JSON STRUCTUREScroll within the panel for all 17 ·
Examples 17
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 17 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Container Security
Secure Docker and OCI containers throughout the build-to-runtime lifecycle.
Kubernetes Security
Enforce security policies, runtime protection, and compliance for Kubernetes clusters.
Serverless Security
Protect AWS Lambda, Azure Functions, and Google Cloud Functions from vulnerabilities and runtime attacks.
DevSecOps
Integrate security scanning into CI/CD pipelines to shift security left and prevent vulnerabilities from reaching production.
Cloud Workload Protection
Protect VMs and cloud workloads across multi-cloud environments from threats and misconfigurations.
SBOM Generation
Generate Software Bill of Materials (SBOM) for container images and code repositories to understand component risk.
Integrations 10
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
AWS
Native integrations with AWS ECS, EKS, Lambda, ECR, Security Hub, and other AWS services.
Azure
Integrations with Azure Kubernetes Service, Azure Container Registry, and Azure Security Center.
Google Cloud
Support for GKE, Google Container Registry, and Cloud Run on Google Cloud Platform.
GitHub Actions
Trivy GitHub Action for automated vulnerability scanning in CI/CD workflows.
Jenkins
Jenkins plugin for container image scanning and policy enforcement in pipelines.
Terraform
Terraform provider for declarative management of Aqua Security platform configuration.
Helm
Official Helm charts for deploying Aqua Security components on Kubernetes.
Splunk
Integration with Splunk for centralized security event logging and SIEM.
PagerDuty
Alert routing to PagerDuty for runtime security event notifications.
Slack
Security alert notifications delivered to Slack channels.
Scroll within the panel for all 10 ·
Resources
Every other property we hold for Aqua Security — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 11
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 11 ·
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/aqua-security · machine-readable index on apis.io