SUSE Security (NeuVector)

Open-source Kubernetes security platform with documented customer-operated deployment on AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud and OCI.

  • AWS
  • Azure
  • Google Cloud
  • Oracle Cloud
  • Alibaba Cloud
  • IBM Cloud
Customer-operated Servers / containers Open Source / Open Core

4 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

NeuVector scanner restart required for critical-severity results

SUSE requires existing scanner pods to restart or redeploy when upgrading from before 5.6.0 to 5.6.4 or later, so cached capabilities recognize critical CVE severity.

Scope: Upgrades from pre-5.6.0 controllers with existing scanner pods; not a claim of a new exploitable vulnerability in every NeuVector installation.

Older scanners cache the controller capability response. SUSE also calls for current scanner/CVE database content for PHP vulnerability checks.

Action: Follow the 5.6.4 scanner restart and database-update instructions, including the transfer process in isolated environments.

Primary source · Reviewed 2026-11-18

What lands where

  1. Supplied by

    Vendor or project

    SUSE Security Helm chart or manifests on public-cloud Kubernetes

  2. Operated by

    Your team

    Customer manages Kubernetes, registry access, Helm values, storage, certificates, policies, upgrades, monitoring and cluster privileges.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodSUSE Security Helm chart or manifests on public-cloud Kubernetes
InfrastructureServers / containers
SUSE Security runs controller, scanner and enforcement workloads on customer Kubernetes nodes.
Licensing modelOpen Source / Open Core
NeuVector is Apache-2.0 licensed. SUSE subscriptions can add entitled delivery, integrations and support.
LicenseApache License 2.0 for NeuVector; Rancher Prime delivery and commercial support have separate subscription terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

12 of 12 fields researched (100%) · 9 documented · 3 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Edition-dependentEvidence and scope for Marketplace delivery

SUSE’s security guide routes AWS procurement through its multi-product Rancher/SUSE subscription offer. The current offer is a private-offer commercial contract labelled SaaS delivery; it is not a standalone upstream OSS AMI or proof of included NeuVector support. Confirm the Security entitlement in the order.

SUSE Security (NeuVector): selected customer-operated edition · Source ↗ · Actual SUSE Cloud Marketplace Program offer ↗ · Offer prodview-b6es6ar6n4siw ↗ — SUSE; SaaS-labelled multi-product private-offer subscription · Reviewed 2026-11-18

Edition-dependent · Editor reviewed.

Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility

The multi-product private-offer route does not settle the buyer’s commitment eligibility or whether SUSE Security is included in the selected contract. Confirm exact entitlement, billable dimensions and cloud agreement.

SUSE Security (NeuVector): selected customer-operated edition · Source ↗ · AWS commitment qualification is product/agreement-specific ↗ · Reviewed 2026-11-18

Sources checked — unresolved · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

The v5.6 guide documents SAML 2.0 SSO, including Okta and group-to-role mapping. Signed assertions are required; encrypted assertions are not supported by this documented configuration. Set a deliberate default role rather than assuming group import grants appropriate access.

SUSE Security (NeuVector): selected customer-operated edition · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning

SAML group-to-role mapping does not establish a SCIM server or provisioning/deprovisioning operations. Confirm a current endpoint and user-removal behavior for the selected OSS or subscription-delivered edition.

SUSE Security (NeuVector): selected customer-operated edition · Source ↗ · Reviewed 2026-11-18

Sources checked — unresolved · Editor reviewed.

Compliance attestations
DocumentedEvidence and scope for Compliance attestations

LRQA certificate 10726335 covers SUSE’s ISO/IEC 27001:2022 ISMS and ISO/IEC 27701:2019 PIMS; schedule page 28 explicitly includes NeuVector, LLC. Issued November 4, 2025, it expires November 3, 2028. This is organisational information/privacy management assurance, not certification of a customer’s NeuVector cluster, protected workloads, configuration or operations.

SUSE organisational management systems including the scheduled NeuVector entity; not a customer-deployment attestation · Source ↗ · Official SUSE certificate index ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

NeuVector documents SAML role mapping and signed-assertion requirements. Enforcers run on cluster nodes and controllers coordinate security policy, so deployment needs the documented privileged access and network visibility. Scope cluster roles and protect console/controller access.

SUSE Security (NeuVector): selected customer-operated edition · Source ↗ · Runtime and component requirements ↗ · Cloud network and topology requirements ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Air-gapped operation
AvailableEvidence and scope for Air-gapped operation

The air-gap guide mirrors charts and images using Skopeo/zstd, transfers them and deploys from an internal registry. Its example versions are older than the current 5.6 line; resolve matching current application/chart/scanner versions and arrange offline vulnerability-database updates.

SUSE Security (NeuVector): selected customer-operated edition · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

NeuVector maintains a Helm chart for manager/controller/enforcer/scanner deployment. The reviewed chart release is v2.11.4, separate from application v5.6.4. Pin image tags and check values/privileges; air-gap documentation’s historical chart example is not a current version pin.

SUSE Security (NeuVector): selected customer-operated edition · Source ↗ · Deployment artifact ↗ (NeuVector Helm chart v2.11.4) · Reviewed 2026-11-18

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The requirements recommend three controllers for HA, an enforcer on each worker and separate scanner/manager resources. Controller minimum is 1 CPU/2 GB; an enforcer needs 1+ CPU/1 GB and a scanner 1 CPU/2 GB before workload growth. The public-cloud guide warns against multiple managers behind a load balancer because of session state, while requirements suggest manager redundancy; resolve that design before claiming full HA.

SUSE Security (NeuVector): selected customer-operated edition · Source ↗ · Manager scaling caveat and cloud topology ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Upstream NeuVector is Apache 2.0 licensed. SUSE subscription-delivered images, support and Rancher Prime integrations may require commercial entitlements. The multi-product AWS order is distinct from the free upstream code licence.

SUSE Security (NeuVector): selected customer-operated edition · Source ↗ · SUSE commercial procurement path ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

Size by protected Kubernetes node count, network throughput, container/image scan volume, registry retention and HA controller/scanner design, not directory users. Include per-node enforcers, scan capacity, persistent configuration and any SUSE support subscription. The manager redundancy conflict also needs resolution.

Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput · Source ↗ · Current AWS Linux EC2 rates; workload/topology still required ↗ · Storage performance and charging inputs ↗ · Reviewed 2026-11-18

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

NeuVector v5.6.4 was published October 27, 2026; chart v2.11.4 is a separate release. When upgrading from before v5.6.0, SUSE requires restarting/redeploying existing scanner pods for critical CVE severity handling. Maintenance releases on older branches are not a newer major-line snapshot.

SUSE Security (NeuVector): selected customer-operated edition · Source ↗ · 5.6.4 upgrade and scanner requirements ↗ · Separate chart release ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Scope & considerations

This entry covers upstream NeuVector/SUSE Security deployment; subscription images/support can require commercial entitlements. SUSE names six public-cloud Kubernetes targets. Resolve the conflicting manager-redundancy guidance before HA design, and apply GKE Autopilot allowlists where required. Scan-policy/compliance functions do not certify the customer installation.

Community & maintenance

NeuVector publishes contribution/governance instructions and maintained public application and Helm releases. This is sustained upstream participation rather than a star-count threshold; commercial SUSE support remains a separately purchased entitlement.

Category fit

DevOps
Adds runtime security, vulnerability scanning and policy enforcement to customer Kubernetes delivery environments.
Observability
Provides workload, network and security-event visibility for Kubernetes clusters.

Compare within DevOps

  • Argo CDGitOps continuous delivery controller and interface for deploying and reconciling applications in Kubernetes clusters.
    • AWS
    Customer-operated · Open Source / Open Core
  • Azure DevOps ServerSource control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.
    • Azure
    Customer-operated · Commercial Only
  • Bitbucket Data CenterCommercial self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • CircleCI ServerCommercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.
    • AWS
    • Google Cloud
    Customer-operated · Commercial Only
  • CloudBees CI on Modern Cloud PlatformsEnterprise continuous-integration platform installed with Helm in a Kubernetes cluster you operate.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitHub Enterprise ServerCustomer-operated GitHub software-development platform deployed as a licensed virtual appliance.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitLab Self-ManagedSource control and CI/CD on infrastructure you operate.
    • AWS
    • Azure
    • Google Cloud
    • Oracle Cloud
    • Alibaba Cloud
    Customer-operated · Open Source / Open Core
  • HarborContainer and OCI artifact registry for managing software images within customer-operated infrastructure.
    • Railway
    Customer-operated · Open Source / Open Core

Showing 8 of 27 other listings in DevOps. These products address related workflows; read their category-fit notes before comparing scope. See all of DevOps →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • SUSE Security on six named public-cloud Kubernetes services ↗ · AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud, Oracle Cloud

      Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

      SUSE explicitly names AWS EKS, Azure AKS, Google Cloud, IBM Cloud Kubernetes, Alibaba Cloud and Oracle Cloud and links full Kubernetes/Helm application deployment. Confirm tested platform versions and privileges. GKE Autopilot requires allowlists; AWS ECS is no longer supported in the requirements guide.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory