Our Aquasec Services

Aquasec is a CNAPP that combines image scanning, Kubernetes security posture management (KSPM) and runtime protection into a single console. We ensure that this console aligns with how your teams build and deploy, without requiring developers to change their workflow.

01

Security Assessment


With a Cloud Security Health Check, we assess your containers, clusters, and pipelines and provide you with a prioritized roadmap.

02

Implementation & integration


We install Aquasec Enforcers and scanners in your Kubernetes clusters (EKS, AKS, GKE, OpenShift, or Rancher) and integrate them with GitLab, GitHub, Terraform, your SIEM, and Jira.

03

Supply Chain & DevSecOps


We integrate image scanning, SBOMs, and policy gates into your CI/CD pipeline to ensure that vulnerable images don't end up in the registry.

04

Managed Services


Through Managed Kubernetes, we maintain Aquasec policies, agents, and runtime alerts, with proactive monitoring and support based on an SLA.

05

Support

Need Aquasec support right now?


Is a policy blocking your build, or are you seeing a runtime alert that you can't resolve? Please contact us, and a SUE engineer will help you troubleshoot the issue.

Request support
We are happy to share knowledge

Expert Aquasec Content

Read what Aquasec and the Dutch government have published about supply chain attacks, runtime security, and the Cyber Resilience Act.

Contact
Three people are sitting next to each other
Aquasec
"We partner with SUE to help organizations innovate with confidence by securing their cloud native journey."

Aquasec Use Cases

01

Software Supply Chain Security in Your CI/CD Pipeline


Common Supply Chain Challenges

Teams rely on hundreds of open-source packages and base images without a clear overview of what’s running in production. The attack on the open-source project Trivy in March 2026 demonstrated that even a scanner in your pipeline can serve as an entry point if GitHub Actions run on version tags and secrets are widely accessible.

 

Take Control of Your Pipeline

We integrate Aquasec with GitLab or GitHub and scan every build for CVEs, secrets, malware, and misconfigurations in Dockerfiles, Helm charts, and Terraform. Images are assigned an SBOM and a policy gate: anything that doesn’t meet the standard isn’t allowed into the registry. In addition, we pin GitHub Actions to commit SHAs and restrict which secrets a pipeline can access.

 

Advantages

For each image, you’ll know which components it contains and which images are affected by a new CVE. Your SBOMs and scan results will be ready for the Cyber Resilience Act, under which the reporting requirement takes effect on September 11, 2026.

02

Kubernetes Runtime Security with Aquasec CNAPP


Common Kubernetes Security Challenges

A clean image at deployment says little about what a container is doing a week later. Security teams see thousands of vulnerabilities in dashboards, but don't know which ones are actually exploitable in a running pod.

 

From Alert to Intervention in the Cluster

We’ll roll out Aquasec Enforcers (eBPF-based) in your clusters and enable drift prevention, KSPM checks, and runtime policies on a per-namespace basis. Alerts are sent to your SIEM or SOC, where your team decides how to respond.

 

Advantages

Prioritization based on what is currently in production. A documented incident response process for the Dutch Cybersecurity Act (NIS2), which took effect on August 15, 2026.

The IT challenges

Containers and Kubernetes enable you to deliver software faster. Images, pipelines, and clusters therefore also represent a potential attack surface. With the Cybersecurity Act (NIS2) taking effect on August 15, 2026, and the reporting requirement under the Cyber Resilience Act taking effect on September 11, 2026, you must be able to demonstrate which components you use and how quickly you address an actively exploited vulnerability. Added to this are AI workloads, for which the AI Act sets its own requirements.

How Aquasec Helps

  • A single platform from code to runtime: Aquasec combines image scanning, supply chain security, Kubernetes security posture management (KSPM) and runtime protection in a single CNAPP console.
  • Runtime as a starting point: Aquasec’s eBPF agents monitor what containers are doing in production and intervene in the event of drift or malware, using Aquasec Compass for human-in-the-loop agentic response.
  • Recognized for container and supply chain security: In 2025, GigaOm named Aquasec a Leader in the Container Security Radar and the Software Supply Chain Security Radar.
Start Your Aquasec Partnership

Partner with SUE for your Aquasec implementation

  • Assessment first: With a Cloud Security Health Check, you’ll know where the biggest risks lie in your clusters and pipelines before you purchase licenses.
  • In-house Kubernetes expertise: We build and manage Kubernetes platforms and landing zones ourselves, so Aquasec policies align with how you actually run your clusters.
  • Developers continue to build: We enable policies step by step—first in audit mode and then in blocking mode—so that builds don't suddenly come to a halt.
  • Managed Services: With Managed Kubernetes, we keep Aquasec agents, policies, and alerts up to date, and you remain in control of what gets blocked.

Frequently asked questions

All frequently asked questions
Trivy is Aquasec’s open-source scanner for images, IaC, and SBOMs. The commercial Aquasec Platform adds runtime protection, KSPM, centralized policies, and reporting, and uses a custom build of Trivy with separate pipelines. According to Aquasec, that build was not affected by the Trivy attack in March 2026.
This is possible if your pipeline ran Trivy v0.69.4, Docker tags 0.69.5 or 0.69.6, or a compromised tag from trivy-action or setup-trivy on March 19 or 20, 2026. Aquasec recommends rotating all secrets that the pipeline could access and pinning GitHub Actions to a full commit SHA. We can help you perform that check and clean up your pipelines.
Both are CNAPPs, but they take different approaches. Wiz starts agentlessly with your cloud accounts and establishes connections between configuration, identities, and vulnerabilities. Aquasec starts with containers and Kubernetes, using eBPF agents that intervene in production in the event of drift or malware, along with scans integrated into your pipeline. If you run a lot of Kubernetes in production, runtime protection is more important; if your risk lies primarily in cloud configuration, then Wiz is a better fit. SUE works with both and provides recommendations based on your environment.
Generate an SBOM for each build—for example, in CycloneDX or SPDX format—and store it alongside the image in your registry. Trivy and the Aquasec Platform automatically generate these SBOMs in your CI/CD pipeline and link any new CVEs back to the images containing the affected component. This allows you to see which products are affected within the CRA’s reporting window: 24 hours for an early warning.
Start in audit mode. Policies will then indicate what they would block, without actually stopping builds or deployments. After a few weeks, you’ll know which rules are triggered correctly and which exceptions are needed, and you can set them to block on a per-team or per-namespace basis. This helps developers maintain confidence in the pipeline.

Choose an experienced Aquasec partner

Jan van der Torn

Let’s talk


Choose an experienced Aquasec partner

* required

By submitting this form, you confirm that you have read and understood our privacy statement.
SUE Cloud Native Solutions
Privacy overview
This website uses cookies. We use cookies to ensure that our website and services function properly, to gain insight into the use of our website, and to improve our products and marketing. For more information, please read our privacy and cookie policy.