
# Observability on Oracle Cloud

Compare documented Observability deployments on Oracle Cloud, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/oci/observability/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Tenancy and compartment
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.oracle.com/en-us/iaas/Content/Identity/Tasks/managingcompartments.htm (checked 2026-11-20).
- Network: Virtual Cloud Network (VCN)
- Identity and access: OCI IAM policies and identities
- Installation guidance: Terraform, optionally orchestrated through OCI Resource Manager stacks.
- Guidance source: https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Concepts/resourcemanager.htm
- Guidance reviewed: 2026-11-10


### Dedicated connectivity

FastConnect links a customer data center privately to OCI. Review partner/circuit availability, routing and redundancy; an OCI application guide does not automatically include that connectivity.
Source: https://docs.oracle.com/en-us/iaas/Content/Network/Concepts/fastconnect.htm (reviewed 2026-11-14).

The listings below have evidence for Oracle Cloud Infrastructure. Read each cloud evidence note for the applicable package, edition and support qualifications.

2 listings.


## Coroot Community Edition

Self-hosted application observability with service maps, logs, metrics, traces and continuous profiling.

- Listing: https://launchinyourcloud.com/directory/coroot-community/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for Coroot Community Edition. Enterprise Edition has separate subscription terms.
- Licensing model: open-source
- Installation: Install the Coroot Operator and Community Edition Helm chart on the customer's Kubernetes cluster.
- Architecture: Customer-operated Coroot server and agents. ClickHouse stores logs, traces and profiles, and metrics can use ClickHouse or Prometheus.
- Operations: The customer manages the operator, image versions, privileged node-agent permissions, storage capacity, telemetry retention, backup and recovery, and access to the UI.
- Product website: https://coroot.com/
- Source review: 2026-11-20; cloud review: 2026-11-20; licensing review: 2026-11-20; infrastructure review: 2026-11-20

### Scope and qualifications

The node agent requires privileged access for eBPF and host inspection, and upstream describes AWS Fargate support as basic. Anonymous usage statistics are enabled by default and can be disabled. The operator updates unpinned Coroot component images automatically. Native SAML/OIDC SSO is Enterprise-only. The Coroot server v1.29.4, Community chart 0.3.3 and operator chart 0.10.8 are separate version tracks; inspect and pin each required image.

Apache-2.0 applies to the published Community code. The Kubernetes guide identifies the separate licensed Enterprise chart.

Coroot and its agents run as Kubernetes workloads. Cluster node agents use eBPF and require compatible Linux kernels and privileged access.


### Category fit

- observability: Node and cluster agents collect operational telemetry for application monitoring and troubleshooting.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.coroot.com/installation/requirements/ (checked 2026-11-20). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.coroot.com/installation/requirements/ (checked 2026-11-20). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.coroot.com/installation/requirements/ (checked 2026-11-20). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.coroot.com/installation/requirements/ (checked 2026-11-20). 


### Cloud deployment evidence

- Coroot on Amazon EKS (aws): https://docs.coroot.com/installation/requirements/
  The vendor explicitly names EKS as a supported Kubernetes environment. Use the linked Community Helm instructions to deploy the operator, server and agents. The vendor specifies basic support for Fargate.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Coroot on Azure AKS (azure): https://docs.coroot.com/installation/requirements/
  The vendor explicitly names AKS among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster, subject to privileges and Linux requirements.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Coroot on Google GKE (gcp): https://docs.coroot.com/installation/requirements/
  The vendor explicitly names GKE among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Coroot on Oracle OKE (oci): https://docs.coroot.com/installation/requirements/
  The vendor explicitly names OKE among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.


### Community and maintenance

The upstream project has sustained public contributor history (including def, apetruhin, Split174) and a reviewed dated v1.29.4 release. This establishes maintenance/community participation rather than a production suitability, support or capacity guarantee.

Reviewed 2026-11-20.

- Public contributor history: https://github.com/coroot/coroot/graphs/contributors

- Reviewed dated upstream release: https://github.com/coroot/coroot/releases/tag/v1.29.4

### Sources

- Community Helm installation and operating requirements: https://docs.coroot.com/installation/kubernetes/

- Supported orchestrators and Linux requirements: https://docs.coroot.com/installation/requirements/

- Coroot assembly and telemetry flow: https://docs.coroot.com/installation/architecture/

- ClickHouse storage and retention: https://docs.coroot.com/configuration/clickhouse/

- Apache-2.0 license: https://github.com/coroot/coroot/blob/main/LICENSE

- Upstream release history: https://github.com/coroot/coroot/releases

- Usage statistics and opt-out: https://docs.coroot.com/misc/anonymous-usage-statistics/

- Operator package: https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz

- Published chart index: https://coroot.github.io/helm-charts/index.yaml

- Buyer evidence: sso: https://docs.coroot.com/configuration/authentication/

- Buyer evidence: footprint: https://github.com/coroot/helm-charts/releases/download/coroot-ce-0.3.3/coroot-ce-0.3.3.tgz

- Buyer evidence: licensePricing: https://github.com/coroot/coroot/blob/v1.29.4/LICENSE

- Buyer evidence: release: https://github.com/coroot/coroot/releases/tag/v1.29.4

- Public contributor history: https://github.com/coroot/coroot/graphs/contributors

### Licensing sources

- https://github.com/coroot/coroot/blob/main/LICENSE

- https://docs.coroot.com/installation/kubernetes/

### Infrastructure sources

- https://docs.coroot.com/installation/kubernetes/

- https://docs.coroot.com/installation/architecture/


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. The reviewed edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Cloud commitment eligibility: Sources checked — unresolved. No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Single sign-on: Explicitly unsupported. The authentication guide explicitly reserves native SAML/OIDC single sign-on for Coroot Enterprise. Community has local users with Admin, Editor and Viewer roles. An external authentication proxy would be a separate configuration, not native Community SSO. Scope: Native Coroot Community authentication; Enterprise is a separate edition. Source: https://docs.coroot.com/configuration/authentication/ (reviewed 2026-11-20).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources do not establish a SCIM endpoint and supported user/group lifecycle for this edition. SSO and just-in-time account creation are not SCIM evidence. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Compliance attestations: Sources checked — unresolved. No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Security controls: Documented. Community provides local-user authentication, three predefined roles and API-key service accounts. Set the initial admin password before exposure and review anonymous-mode settings. Node agents need privileged eBPF/host access; review the operator ClusterRole and its optional restriction on global secret access. Scope: Configured Community access controls and privileged collector/operator boundary. Source: https://docs.coroot.com/configuration/authentication/ (reviewed 2026-11-20). Supporting source: Node-agent privilege requirements — https://docs.coroot.com/installation/kubernetes/. Supporting source: Inspected operator permissions/configuration — https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz.

- Air-gapped operation: Sources checked — unresolved. The reviewed sources do not establish a complete disconnected installation, update and licensing workflow. A telemetry opt-out alone does not establish air-gapped support; review registry, package, identity and optional external-service dependencies. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Deployment artifact / IaC: Documented. The inspected coroot-ce 0.3.3 chart creates a Community custom resource and requires a separately installed operator; the reviewed operator chart is 0.10.8 (operator application 1.10.8). Neither chart version identifies the Coroot server release. Pin server, node-agent and cluster-agent images to prevent the documented automatic upgrades. Scope: Community custom resource plus separately versioned operator and component images. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20). Deployment artifact: https://github.com/coroot/helm-charts/releases/download/coroot-ce-0.3.3/coroot-ce-0.3.3.tgz. Artifact reference: coroot-ce 0.3.3; sha256:e6213b27a4e73924d2fe03c12aa815ebd8ec806436c3a5ab9bd4a8801c18e6f3; operator chart 0.10.8 / operator 1.10.8. Supporting source: Operator package — https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz. Supporting source: Published chart index — https://coroot.github.io/helm-charts/index.yaml.

- Minimum footprint / sizing: Documented. The inspected Community chart defaults to 10 GiB Coroot storage, 10 GiB Prometheus storage and 100 GiB per ClickHouse instance. Its default ClickHouse layout is one shard/replica; the installation guide overrides this to two shards and two replicas. Operator requests are 100m CPU/64 MiB. These are component defaults, not total cluster CPU/RAM minima or an HA capacity guarantee. Scope: Chart-specific storage and operator request baseline; server/agent/database sizing remains workload-dependent. Source: https://github.com/coroot/helm-charts/releases/download/coroot-ce-0.3.3/coroot-ce-0.3.3.tgz (reviewed 2026-11-20). Supporting source: Separate operator requests — https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz. Supporting source: Installation layout and replica override — https://docs.coroot.com/installation/kubernetes/. Supporting source: Kernel and orchestrator prerequisites — https://docs.coroot.com/installation/requirements/.

- License pricing: Documented. Coroot Community v1.29.4 is licensed under Apache-2.0. This establishes the software licence rather than a per-seat subscription; Enterprise features/support, dependencies and infrastructure have separate costs. Scope: Upstream Community code; excludes Enterprise subscriptions. Source: https://github.com/coroot/coroot/blob/v1.29.4/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Release snapshot / cadence: Documented. The reviewed Coroot Community server snapshot is v1.29.4, published November 18, 2026. Operator, server, agents and charts are independently versioned; this snapshot does not guarantee support or pin the complete installation. Scope: Upstream Community server release. Source: https://github.com/coroot/coroot/releases/tag/v1.29.4 (reviewed 2026-11-20).







## SUSE Security (NeuVector)

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

- Listing: https://launchinyourcloud.com/directory/suse-security-neuvector/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, ibm, alibaba, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for NeuVector; Rancher Prime delivery and commercial support have separate subscription terms.
- Licensing model: open-source
- Installation: SUSE Security Helm chart or manifests on public-cloud Kubernetes
- Architecture: Manager, controller and scanner services plus an enforcer DaemonSet inside the customer Kubernetes cluster.
- Operations: Customer manages Kubernetes, registry access, Helm values, storage, certificates, policies, upgrades, monitoring and cluster privileges.
- Product website: https://www.suse.com/products/security/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

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.

NeuVector is Apache-2.0 licensed. SUSE subscriptions can add entitled delivery, integrations and support.

SUSE Security runs controller, scanner and enforcement workloads on customer Kubernetes nodes.


### 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.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 


### Cloud deployment evidence

- SUSE Security on six named public-cloud Kubernetes services (aws, azure, gcp, ibm, alibaba, oci): https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html
  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.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector/blob/main/CONTRIBUTING.md

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector/releases/tag/v5.6.4

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4

### Sources

- Deploy SUSE Security on public-cloud Kubernetes: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html

- Deploy SUSE Security with Helm: https://documentation.suse.com/cloudnative/security/latest/en/helm.html

- SUSE Security support matrix: https://www.suse.com/suse-neuvector/support-matrix/all-supported-versions/neuvector-v-all-versions/

- NeuVector Apache 2.0 license: https://github.com/neuvector/neuvector/blob/main/LICENSE

### Licensing sources

- https://github.com/neuvector/neuvector/blob/main/LICENSE

### Infrastructure sources

- https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html


### Buyer diligence


Research coverage: 12/12 fields (100%); 9 documented, 3 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Edition-dependent. 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. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/awsmarketplace.html (reviewed 2026-11-18). Supporting source: Actual SUSE Cloud Marketplace Program offer — https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw. Offer prodview-b6es6ar6n4siw: SUSE; SaaS-labelled multi-product private-offer subscription; https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw.

- Cloud commitment eligibility: Sources checked — unresolved. 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. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. 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. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. 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. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18).

- Compliance attestations: Documented. 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. Scope: SUSE organisational management systems including the scheduled NeuVector entity; not a customer-deployment attestation. Source: https://www.suse.com/support/security/certifications/SUSE-ISO-27001-ISO-27701.pdf (reviewed 2026-11-18). Supporting source: Official SUSE certificate index — https://www.suse.com/support/security/certifications/isoiec-certification/.

- Security controls: Documented. 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. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18). Supporting source: Runtime and component requirements — https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html. Supporting source: Cloud network and topology requirements — https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html.

- Air-gapped operation: Documented. 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. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/airgap.html (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. 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. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/latest/en/helm.html (reviewed 2026-11-18). Deployment artifact: https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4. Artifact reference: NeuVector Helm chart v2.11.4.

- Minimum footprint / sizing: Documented. 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. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html (reviewed 2026-11-18). Supporting source: Manager scaling caveat and cloud topology — https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html.

- License pricing: Documented. 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. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://github.com/neuvector/neuvector/blob/main/LICENSE (reviewed 2026-11-18). Supporting source: SUSE commercial procurement path — https://documentation.suse.com/cloudnative/security/5.6/en/awsmarketplace.html.

- Operating cost estimate: Sources checked — unresolved. 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. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. 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. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://github.com/neuvector/neuvector/releases/tag/v5.6.4 (reviewed 2026-11-18). Supporting source: 5.6.4 upgrade and scanner requirements — https://documentation.suse.com/cloudnative/security/5.6/en/5x.html. Supporting source: Separate chart release — https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- NeuVector scanner restart required for critical-severity results (security-advisory): 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. Conditions: 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. Source: https://documentation.suse.com/cloudnative/security/5.6/en/5x.html; reviewed 2026-11-18.



