Skip to main content
Migration Notice
We're migrating documentation from the old portal into this one. Some things may look a little different or out of place in the meantime — we know, and we're working to get it right. If something's unclear or doesn't look right, let us know.

Product Prerequisites

This guide covers what Superna Data Security for Dell AI Infrastructure needs before you install it and connect your first devices:

  • Compute and registry requirements.
  • Per-device connection details and credentials.
  • Least-privilege service accounts.
  • The firewall ports that must be open, with direction.
  • How audit data and the classification pipeline flow through the system.

For the task-oriented walkthrough, see the Quick Start Setup Guide.

Two ways to deploy:

  • VMware appliance (OVA): the console runs in a virtual machine, and the pipeline agents run on Linux hosts that you provide. See Install on VMware (OVA).
  • Kubernetes (Helm): the console, its databases, and the pipeline agents all run in your cluster. See Install on Kubernetes (Helm).

Compute and registry requirements​

The console is validated against Kubernetes v1.31 to v1.37. This applies to the cluster the product runs on and to any monitored cluster that you add on Settings > Clusters. The card of each monitored cluster shows its observed version and flags it if it falls outside this range.

A newer cluster still scans on a best-effort basis, and unknown fields from a later Kubernetes release are tolerated. Versions outside the validated range are not fully tested. Upgrade the console to get official support for a newer Kubernetes version.

VMware appliance (OVA)​

The requirements of the virtual machine are in Install on VMware (OVA). The pipeline agents run on Linux hosts that you provide. Their requirements are on System Operations > Fleet Management > Agent Installation. See Agent Installation.

Kubernetes (Helm)​

The sizing below is the configuration in the values file of each platform guide under Install on Kubernetes (Helm). Memory is the per-pod limit, CPU is the request, and disk is the persistent volume per pod.

ComponentPodsImageCPU (request)Memory (limit)Disk (recommended)
Console1aisec-console46 GiB40 GiB
Extraction agent1extraction-agent24 GiB10 GiB or more
Linguistic Coherence (LC) agent2lc-agent4 each12 GiB each10 GiB or more each
Classify agent2classify-agent4 each8 GiB each10 GiB or more each
PostgreSQL (metadata / OLTP)1cloudnative-pg/postgresql0.51 GiB40 GiB
ClickHouse (audit store)1clickhouse/clickhouse-server430 GiB600 GiB

Totals: about 26.5 CPU requested, 81 GiB of memory limits, and 730 GiB of persistent volumes, plus the two bundled operators. The nodes also need about 52 GiB of free ephemeral storage for the agents' scratch space, and at least one node must fit the 4 CPU / 30 GiB ClickHouse pod.

The two operator pods (CloudNativePG and Altinity) and several helper containers set no resource requests or limits. If the namespace has a ResourceQuota, add a LimitRange that gives them defaults.

The defaults of the chart, which apply when a value is not set, differ. Set the sizes in your values file: console.persistence.size: 40Gi, pipeline.stages.<stage>.persistence.size: 10Gi, postgres.storage.size: 40Gi, clickhouse.storage.size: 600Gi. The platform guides' values files already do. Size the ClickHouse disk for your audit volume and retention. Volumes can be grown later only on a storage class with allowVolumeExpansion: true; the local-path class cannot be expanded.

Pipeline agents scale by replica count. Each extra agent adds the figures of its row.

Check your cluster before you install​

These conditions in your cluster block or break the install. Check them before deployment day. Settings such as the console URL, ingress class, storage class and certificate are chosen during the install; see Install on Kubernetes (Helm).

  1. Version: the cluster runs Kubernetes v1.31 to v1.37. OpenShift and OKD need the extra steps in the platform notes of the install page.
  2. Capacity: the cluster can give the release the totals above. At least one node fits a 4 CPU / 30 GiB pod (ClickHouse), and the nodes have about 52 GiB of free ephemeral storage for agent scratch space. A ResourceQuota on the namespace must allow these totals.
  3. Operators: if CloudNativePG or the Altinity ClickHouse operator is already installed, do not install a second copy. Set operators.cnpg.install or operators.clickhouse.install to false, and make sure the existing operator watches the release namespace.
  4. Storage: a StorageClass provides ReadWriteOnce volumes with the capacity above. Choose one that allows volume expansion, so that the ClickHouse volume can grow later.
  5. Ingress: users reach an ingress controller over HTTPS on port 443. A load balancer in front of it must pass TLS through or re-encrypt; if it terminates TLS and forwards plain HTTP, login fails with 403.
  6. Images: the cluster can pull from the Superna public registry, docker.io and ghcr.io on port 443, or from a private registry that holds all the images. An air-gapped cluster needs such a registry inside the network.
  7. Network policies: if the cluster applies default-deny NetworkPolicies to new namespaces, the product's traffic must be allowed. See Cluster policies in your platform's install guide.
  8. GitOps: Argo CD and other tools that render the chart without a cluster connection can't keep the chart's generated passwords and keys. Set them in your values file, as described in your platform's install guide.
  9. Admission policies: Kyverno, OPA Gatekeeper or custom OpenShift security context constraints must allow the product's registries, user IDs 1000 and 101, emptyDir volumes, and the two operator pods, which set no CPU or memory limits.
  10. Node taints: if your nodes are tainted or reserved, set scheduling.tolerations and scheduling.nodeSelector so that the product's pods can run.

Environment details to prepare​

Have these details ready before deployment day, with exact names and versions:

  1. Node operating system: distribution and version, kernel version, SELinux or AppArmor mode, host firewall (for example firewalld), and whether FIPS mode is enabled.
  2. Kubernetes: exact version including patch level, and the container runtime and its version (containerd, CRI-O).
  3. Network: the CNI plugin and version, any service mesh that adds sidecars to new namespaces (Istio, Linkerd), and any proxy that nodes or pods use to reach the internet.
  4. Ingress: the controller and version, how it is exposed (LoadBalancer service such as MetalLB, NSX Advanced Load Balancer or F5; an external load balancer in front of node ports; or the host network), and, for an external load balancer, whether it passes TLS through, re-encrypts, or terminates TLS.
  5. Storage: the CSI driver and version behind the StorageClass, and the StorageClass definition (provisioner, parameters, reclaim policy, volume binding mode). For the Dell PowerScale CSI driver (NFS), also the NFS export options (for example root squash) and the driver's fsGroupPolicy.
  6. Policies: the Pod Security level enforced on new namespaces, and any Kyverno, OPA Gatekeeper or ValidatingAdmissionPolicy policies that apply to the product's namespace.
  7. GitOps (if used): the tool and version, and how secrets are delivered (External Secrets, Sealed Secrets, Vault).

Container image registry​

Kubernetes installs pull the product images from a registry. The VMware appliance ships with its images and needs no registry access. An air-gapped Kubernetes cluster needs a private registry inside the network that holds all the images below; without one, use the VMware appliance.

WhatValue
Image registry (server)northamerica-northeast2-docker.pkg.dev/superna-579/oci/aisecurity. Google Artifact Registry, public and anonymously pullable. No pull secret is needed for the Superna images.
aisec imagesaisec-console, extraction-agent, lc-agent, and classify-agent under the registry above. Set the image tag of the release you deploy. See Install on Kubernetes (Helm).
Helm chart (OCI)oci://northamerica-northeast2-docker.pkg.dev/superna-579/oci/aisecurity/charts/aisec, at the chart version of your release. Requires Helm 3.18.6 or newer.
Public dependenciesghcr.io/cloudnative-pg/postgresql:17.10, ghcr.io/cloudnative-pg/cloudnative-pg:1.30.0 (operator), docker.io/clickhouse/clickhouse-server:26.3.10.62, docker.io/altinity/clickhouse-operator:0.27.1, docker.io/altinity/metrics-exporter:0.27.1, docker.io/bitnami/kubectl:latest (installs the ClickHouse operator's resource definitions at install and upgrade), and docker.io/library/busybox:1.37 (init containers).
Port / protocol443 / HTTPS (outbound)
note

Private mirror: to pull from your own registry (Harbor, Artifactory, or Nexus), mirror all 11 images with the same tags: the four aisec images and the seven public dependencies above. bitnami/kubectl is published only as latest, so mirror it by digest. Then point the chart at your registry in the values file:

  • default.image.registry: the four aisec images
  • console.initImage.registry: busybox
  • postgres.image.registry and clickhouse.image.registry
  • cloudnative-pg.image.repository: the full repository path of the CloudNativePG operator
  • altinity-clickhouse-operator.operator.image.registry and altinity-clickhouse-operator.metrics.image.registry
  • altinity-clickhouse-operator.crdHook.image.repository: the full repository path of kubectl

If your registry needs credentials, configure them on the nodes (for example RKE2 registries.yaml, the containerd registry configuration, or the OpenShift global pull secret). A pull secret set in the chart values does not reach the PostgreSQL, ClickHouse or operator pods. Each platform install guide has the full steps.

The four aisec images, PostgreSQL and ClickHouse can also be pinned by digest with <component>.image.digest.

Information to prepare for onboarding​

Have this information ready for the onboarding call. For a Kubernetes (Helm) deployment, also see Check your cluster before you install and Environment details to prepare.

Deployment​

  • Deployment model: the VMware appliance (OVA) or Kubernetes (Helm). For the OVA, the Linux hosts with Docker that will run the pipeline agents. Air-gapped sites use the OVA.

Kubernetes and AI workloads​

  • The Kubernetes clusters and namespaces to monitor, their distribution and version (validated v1.31 to v1.37), container runtime, CNI and node operating system.
  • The AI workload types that run there (RAG, training, fine-tuning, inference), and whether NVIDIA Run:ai is used to submit jobs.
  • Whether the Dell PowerScale CSI driver and the ObjectScale COSI driver are installed.
  • Who can add the audit policy and audit webhook configuration on the control-plane nodes (needed for user attribution).

Storage​

  • The number of PowerScale clusters and their OneFS versions; whether ObjectScale / ECS is in use, and whether it is virtual or hardware.
  • Whether protocol auditing is enabled, and whether Superna Ransomware Defender or Easy Auditor is already deployed.
  • Whether the Dell Data Analytics Engine (Starburst / Trino) is in use.

Integrations​

  • The DNS type and the certificate authority for the console hostname.
  • The SIEM or SOAR tools in use, and the compliance requirements that apply (for example GLBA or HIPAA).

Devices, accounts, and API keys​

Each device below matches an add-device form on Settings > Clusters or Settings > Storage. Provide the endpoints and the account, and create the API key or token as shown. Optional integrations are marked.

Kubernetes cluster​

  • Add-device fields: API Endpoint https://<host>:6443 (or the Rancher proxy URL), plus Dell CSI namespace and CSI secret for PowerScale PVC discovery. The Dell PowerScale CSI driver must already be installed.
  • Account required: the read-only aisec-reader service account. See Kubernetes read-only service account.
  • API key or token: the long-lived token that the manifest creates. Paste it as the Bearer Token:
kubectl -n aisec-reader get secret aisec-reader-token -o jsonpath='{.data.token}' | base64 -d; echo
  • Kubernetes audit webhook (user attribution): requires a self-managed control plane where you can change kube-apiserver flags (root on each control-plane node to add the audit policy and webhook configuration, then restart kube-apiserver). The API server must reach the console over HTTPS (self-signed by default: skip verification or trust the console's certificate authority). See Kubernetes API Audit Ingestion.

PowerScale (OneFS)​

  • Add-device fields:
    • IP.
    • SSH host (SmartConnect FQDN) on port 22, plus user and password.
    • Audit Log Dir /ifs/.ifsvar/audit/logs.
    • OneFS Mgmt host on port 8080, plus user and password.
  • Account required: an SSH user (audit-log read) and a OneFS user with a Platform-API role.
  • API key or token: none. Use a OneFS local or AD user, and assign a platform-API read role (user and password only).

ObjectScale / Dell ECS​

  • Add-device fields:
    • Management Endpoint on port 4443.
    • S3 (data) Endpoint on port 9020 (HTTP) or 9021 (HTTPS).
    • SSH admin:22 (audit-log SFTP).
  • Account required: an ECS management user and an SSH audit user.
  • API key or token: none. You do not create S3 keys: the product creates its own per-namespace reader. The management user is the ECS management login.

RunAI (optional, GPU and workload context)​

  • Add-device fields: Base URL https://runai.<domain>, Client ID, and Client Secret.
  • Account required: a RunAI Application (OAuth client).
  • API key or token: in the RunAI UI, go to Settings > Applications > New, then copy the Client ID and Client Secret.

Trino audit (optional, event-listener plugin)​

  • Add-device fields: none. Trino audit is configured on the Trino coordinator, not in an add-device form. The plugin posts to POST /api/trino-audit/ingest on the console.
  • Account required: a Trino audit ingest token, stored AES-256 encrypted on the console.
  • API key or token: on Settings > Trino Audit, generate or rotate the token. Then run the console-provided install.sh?token=… one-liner on the coordinator and restart it.

The installer writes the listener settings to etc/event-listener.d/superna-audit.properties if that directory exists, and otherwise to etc/event-listener.properties (replacing that file):

event-listener.name=superna-clickhouse-audit
superna-audit.console-url=https://<console>
superna-audit.ingest-token=<token from Settings > Trino Audit>
superna-audit.tls-skip-verify=true # only when you chose to skip TLS verification

Minimum permissions​

Connect each integration with a dedicated, clearly named least-privilege account, svcaisec. The account grants exactly what the product's ingest, inventory, audit, and read-access code paths touch, and nothing more. Do not use root, admin, or cluster-admin.

The task-oriented walkthrough is the Quick Start Setup Guide.

IntegrationIdentityMinimum grantProvisioned by
KubernetesSA aisec-readerRead-only ClusterRole (get/list/watch); secrets only in the Dell CSI namespace. Manifest below.kubectl apply
PowerScaleUser svcaisec (role svcaisec_ro)LOGIN_SSH, LOGIN_PAPI, IFS_BACKUP; SMB/NFS/AUDIT read-onlyOneFS admin (isi CLI)
ObjectScale (mgmt)Mgmt user svcaisecSystem Monitor plus Namespace Administrator per protected namespaceECS Security Administrator
ObjectScale (SSH)Local audit userLogin plus read/list on the deployment-type log path (no sudo, write, or shell)ECS node admin
RunAI (optional)Read-only Application (OAuth client)Viewer/researcher read scopeRunAI admin
Trino audit (optional)Ingest tokenScoped to the Trino audit ingest endpoint and the plugin downloadSettings > Trino Audit

Kubernetes read-only service account​

The product only reads the cluster (get, list, watch). No cluster-admin or write access is required. The manifest below creates the aisec-reader service account, the read-only permissions, and a long-lived token. The same manifest is used for the VMware appliance (OVA) and Helm deployments.

AccessResourcesUsed for
get, list, watch (cluster-wide)nodes, namespaces, pods, persistentvolumes, persistentvolumeclaimsInventory scan, namespace list
get, list, watch (cluster-wide)replicasets, jobsFinding the Deployment or CronJob that owns each pod
get, list, watch (cluster-wide)storageclassesStorage mapping
get, list, watch (cluster-wide)COSI buckets, bucketaccessesObjectScale buckets used by pods. Harmless if COSI is not installed.
get, list (Dell CSI namespace only)secretsReading the Dell CSI driver configuration to map volumes to PowerScale paths

Before you apply it, change dell-storage (two places, marked) if the Dell CSI driver runs in a different namespace. If the cluster has no Dell CSI driver, delete the last two objects (the Role and the RoleBinding).

Save the manifest as aisec-reader.yaml:

apiVersion: v1
kind: Namespace
metadata:
name: aisec-reader
---
apiVersion: v1
kind: ServiceAccount
metadata:
name: aisec-reader
namespace: aisec-reader
---
apiVersion: v1
kind: Secret
metadata:
name: aisec-reader-token
namespace: aisec-reader
annotations:
kubernetes.io/service-account.name: aisec-reader
type: kubernetes.io/service-account-token
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: aisec-reader
rules:
- apiGroups: [""]
resources: [nodes, namespaces, pods, persistentvolumes, persistentvolumeclaims]
verbs: [get, list, watch]
- apiGroups: [apps]
resources: [replicasets]
verbs: [get, list, watch]
- apiGroups: [batch]
resources: [jobs]
verbs: [get, list, watch]
- apiGroups: [storage.k8s.io]
resources: [storageclasses]
verbs: [get, list, watch]
- apiGroups: [objectstorage.k8s.io]
resources: [buckets, bucketaccesses]
verbs: [get, list, watch]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: aisec-reader
subjects:
- kind: ServiceAccount
name: aisec-reader
namespace: aisec-reader
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: aisec-reader
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
name: aisec-reader-csi-secrets
namespace: dell-storage # Dell CSI driver namespace
rules:
- apiGroups: [""]
resources: [secrets]
verbs: [get, list]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: aisec-reader-csi-secrets
namespace: dell-storage # Dell CSI driver namespace
subjects:
- kind: ServiceAccount
name: aisec-reader
namespace: aisec-reader
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: aisec-reader-csi-secrets

Apply it, then read the token and the API endpoint for Settings > Clusters:

kubectl apply -f aisec-reader.yaml

# Bearer Token
kubectl -n aisec-reader get secret aisec-reader-token -o jsonpath='{.data.token}' | base64 -d; echo

# K8s API Endpoint
kubectl config view --minify -o jsonpath='{.clusters[0].cluster.server}'; echo

On a Helm deployment where the console runs in the cluster it monitors, https://kubernetes.default.svc also works as the API endpoint. Always enter both the endpoint and the token, including on Helm.

Check the access. Each command prints yes, except the last one, which prints no:

SA=system:serviceaccount:aisec-reader:aisec-reader
kubectl auth can-i list pods --all-namespaces --as=$SA
kubectl auth can-i list jobs.batch --all-namespaces --as=$SA
kubectl auth can-i list buckets.objectstorage.k8s.io --as=$SA
kubectl auth can-i get secrets -n dell-storage --as=$SA
kubectl auth can-i get secrets -n default --as=$SA
note
  • A 403 on the COSI buckets resource silently breaks ObjectScale bucket↔pod binding: buckets are discovered but never marked COSI-managed.
  • To rotate the token, delete the aisec-reader-token secret, apply the manifest again, and paste the new token into Settings > Clusters.
  • To remove access, run kubectl delete -f aisec-reader.yaml.

PowerScale (OneFS) read-only role and user​

Create a dedicated read-only role and user rather than using root. The role needs:

  • Login: SSH/SFTP for the audit-log pull, and PAPI to authenticate to the management API.
  • Read access to the audit directory.
  • Read on SMB/NFS shares and the auditing configuration, for the read-only OneFS management features.

The role needs no write or provisioning privileges.

isi auth roles create svcaisec_ro --description "Superna AI Security read-only service account"
isi auth roles modify svcaisec_ro --add-priv ISI_PRIV_LOGIN_SSH # SSH/SFTP audit-log pull
isi auth roles modify svcaisec_ro --add-priv ISI_PRIV_LOGIN_PAPI # authenticate to the mgmt API
isi auth roles modify svcaisec_ro --add-priv ISI_PRIV_IFS_BACKUP # read the audit dir (bypasses ACL; RESTORE omitted)
isi auth roles modify svcaisec_ro --add-priv-read ISI_PRIV_SMB # read SMB shares (read-only)
isi auth roles modify svcaisec_ro --add-priv-read ISI_PRIV_NFS # read NFS exports (read-only)
isi auth roles modify svcaisec_ro --add-priv-read ISI_PRIV_AUDIT # read auditing config (read-only)
isi auth users create svcaisec --enabled yes --set-password
isi auth roles modify svcaisec_ro --add-user svcaisec

Use these credentials as both the SSH user and the OneFS management user.

  • --add-priv grants an action or login privilege.
  • --add-priv-read grants read-only.
  • ISI_PRIV_IFS_RESTORE and all share and configuration write privileges are deliberately omitted.

ObjectScale (Dell ECS)​

ObjectScale read access is not a plain read-only account. The product creates a per-namespace reader IAM user with a read-only S3 policy. The management identity therefore needs IAM-admin within each protected namespace, plus cluster-wide read for inventory. The reader the product provisions is least-privilege, and the management identity is scoped to inventory-read plus per-namespace IAM.

Management-API account:

  • System Monitor (cluster-wide: ListNamespaces, ListBuckets).
  • Namespace Administrator on every namespace this system protects. In the ECS Portal, go to Manage > Namespace > namespace > Edit > Namespace Administrators.
  • Namespace Admin covers creating and managing the per-namespace reader. It is not full System Admin.
  • Creating the management user itself requires a Security Administrator on ECS.

Reader (auto-provisioned):

  • The product creates a per-namespace IAM user with a read-only S3 policy (s3:GetObject, s3:ListBucket).
  • You do not create it by hand.

SSH/SFTP audit account:

  • Login plus read and directory-listing only on the audit-log directory for your ECS Deployment Type.
  • No sudo, no write, no shell. The product only lists and reads files over SFTP.
  • ECS has no granular SSH RBAC through its management API, so this is a local OS user on the ECS node (no wheel or docker group, no sudo). Grant read and list on the specific directory rather than assuming default access.
ECS Deployment Type (Settings)Audit-log path
ObjectScale / Virtual ECS (default)/var/log/vipr/emcvipr-object
Hardware ECS Appliance/opt/emc/caspian/fabric/agent/services/object/main/log
CustomThe path you supply
note

The COSI driver for ObjectScale must be installed so COSI-provisioned buckets are discovered and bound to their pods. This binding also requires the Kubernetes COSI RBAC grant described in Kubernetes read-only service account.

RunAI (optional)​

Create a dedicated RunAI Application (OAuth client) with a read-only / viewer scope sufficient to list projects, workloads, and users. The console only reads workload and user context for topology attribution. Copy the Client ID and Client Secret into the cluster integration.

Trino audit (optional)​

The Trino integration uses a console-issued ingest token, not a platform account.

  • The token is scoped to the Trino audit ingest endpoint (POST /api/trino-audit/ingest) and the plugin download. It cannot reach any other API, setting, or table.
  • Rotating the token immediately invalidates the previous value.
  • On the Trino side, the account that runs the installer only needs write access to Trino's plugin/ and etc/ directories and the ability to restart the coordinator. It needs no product-side privileges.

Firewall ports and direction​

Outbound means the console initiates the connection to the device. Inbound means an external client (or a device) connects to the console.

DirectionSource → DestinationPort / protoPurpose
OutboundConsole → ObjectScale / ECS management4443 / TCP HTTPSBucket inventory, management API
OutboundConsole → ECS S3 data9020 / TCP HTTP · 9021 / TCP HTTPSS3 read (read-access verify)
OutboundConsole → ECS / ObjectScale SSH22 / TCPAudit-log SFTP
OutboundConsole → PowerScale SSH22 / TCPAudit-log SFTP
OutboundConsole → PowerScale OneFS management8080 / TCP HTTPSOneFS platform API
OutboundConsole → Kubernetes API server6443 / TCP (or 443 via Rancher)Pod / PVC / node discovery
OutboundConsole → RunAI (optional)443 / TCP HTTPSGPU / workload context
OutboundKubernetes nodes → northamerica-northeast2-docker.pkg.dev (Google Artifact Registry) + ghcr.io/docker.io (deps)443 / TCP HTTPSImage pull + Helm chart (Kubernetes installs)
OutboundConsole → support relay host set on Settings > Remote Support (optional)443 / TCP WSSRemote support
InboundOperator browser → Console UI443 / TCP HTTPS (the VMware appliance also answers on 80 and redirects to HTTPS; on Kubernetes, through the ingress)Web console
InboundTrino coordinator → Console /api/trino-audit/ingest (+ plugin.jar, install.sh)443 / TCP HTTPSStructured (Trino) audit push + plugin fetch
InboundKubernetes API server (control-plane nodes) → Console /api/k8s-audit/webhook/{clusterId}443 / TCP HTTPS (on Kubernetes, through the ingress)Kubernetes API audit webhook (Pod Creator attribution)
InboundPipeline agents → Console443 / TCP HTTPS (on Kubernetes, the cluster network)Agent enrollment, heartbeats, image download, results
Between agent hostsExtraction agent hosts → single-role LC or classify host9101 / TCPWork hand-off (VMware appliance). See Agent Installation.
Between agent hostsExtraction agent hosts → host running all three roles9101 / TCP (LC), 9102 / TCP (classify)Work hand-off (VMware appliance)
OutboundExtraction agents → PowerScale (data interface)22 / TCP (the SSH port of the cluster)Read the files to classify (SFTP)
OutboundExtraction agents → ECS / ObjectScale S3 endpoint9020 / TCP HTTP · 9021 / TCP HTTPS (or 443)Read the objects to classify (S3)
InternalHealth checks inside the appliance or podNot applicableNo firewall rule needed

Data flow diagrams​

Audit ingestion and management-API calls​

  • The console pulls file audit logs over SSH/SFTP (PowerScale and ObjectScale).
  • Object management data uses the ECS management API (4443) and the S3 API (9020/9021).
  • OneFS configuration is read over the platform API (8080).
  • Trino pushes query audit to the console over REST (HTTPS, 443).
  • All audit records land in ClickHouse.

Audit ingestion and management API data flow

Classification pipeline​

Discovered files and objects are enqueued as work items. They then flow through extraction → linguistic coherence (LC) → classification. LC is on in every edition; it can be switched off on Settings > Pipeline Discovery. Results (PII, coherence verdict, classification) are written to ClickHouse and surfaced in K8 Data Security.

Classification pipeline data flow

Install sequence​

  1. Install the product. Follow Install on VMware (OVA) or Install on Kubernetes (Helm).
  2. Install the license on Settings > Licensing.
  3. Add a Kubernetes cluster on Settings > Clusters: API endpoint, bearer token, and Dell CSI namespace and secret. Use the read-only service account described in Kubernetes read-only service account.
  4. Connect storage on Settings > Storage: PowerScale (SSH and OneFS management) and/or ObjectScale (management, S3, and SSH). Use the least-privilege accounts described in PowerScale (OneFS) read-only role and user and ObjectScale (Dell ECS).
  5. (Optional) Add RunAI on the cluster.
  6. (Optional) Enable Trino audit on Settings > Trino Audit: generate the token, then run install.sh on the coordinator.
  7. Open the firewall ports listed in Firewall ports and direction: outbound to devices and the registry, inbound for the console UI and the Trino push, and between agent hosts.

Once the devices are connected, audit data ingests automatically (see Audit ingestion and management-API calls). Discovered files and objects flow through the classification pipeline (see Classification pipeline).

For a guided walk-through of searching the audit data, see the File, Object and Trino auditing overview Quick Start tour (Help > Quick Start).