Skip to main content

v2.22.0

Date of release: 02/10/2026

Engine version: 16.12.1

Conform version: 1.3.0

Foresight version: 1.6.0

Genesis version: 0.2.0

Pulsar version: 0.2.0

New features​

ICAP server managed from the Portal​

You now start, stop and configure the ICAP server from the Portal, instead of through Helm values.

  • Start and stop the server in the Portal: open Protection settings, select the ICAP tab, then use the control under ICAP configuration. Stopping it keeps your settings, so you can start it again without reconfiguring.
  • The ICAP tab appears only when your licence includes the ICAP entitlement.
  • Mutual TLS is now a setting, settings.ICAP.MutualTlsEnabled, which replaces the old configuration.ENABLE_MTLS Helm value.
  • With mutual TLS off, the server no longer opens the TLS port. Earlier releases opened it but refused every connection, so an appliance without certificates no longer shows that port as open.
  • When autoscaling controls the number of ICAP servers (the Prometheus scaling chart with keda.icap.enabled=true), the Portal control is inactive.

Read the ICAP Server Upgrade Notice below before you upgrade an existing ICAP install. For more information, see Enable ICAP and ICAP deployment.

Prompt Injection Detection API (Pulsar)​

Halo can now detect prompt injection in text, with a new API based on Glasswall's Pulsar detection service. Use it to check text before an application sends it to a large language model (LLM).

  • Send text to POST /api/v1/detect/prompt-injection. The endpoint accepts up to 512 tokens and returns an immediate verdict.
  • The verdict has three levels: No Threat Detected, Suspicious or Malicious.
  • Text over 512 tokens is rejected with a clear error.
  • The Pulsar service runs inside the Halo Kubernetes deployment. It needs no GPU, works in air-gapped networks, and returns a result in under a second.
  • The endpoint uses your existing Halo API authentication (organisationId:token basic auth or OIDC).
  • This first release supports English text only.

Prompt injection detection needs a licence with the Pulsar entitlement, like Foresight. Without it, the endpoint returns a clear licensing error.

To install it, see Deploying the Prompt Injection Detection API. For more information, see the Halo API documentation.

New content management policy switches (Engine 16.12)​

This release upgrades the Glasswall Embedded Engine to 16.12 and adds content-management policy switches. You set each switch per organisation, in the Halo policy API or the Portal. Each new switch defaults to sanitise.

New switches:

  • write_reservation — DOCX, XLSX and PPTX
  • embedded_fonts — DOCX and PPTX
  • field_codes — DOCX
  • footnotes_endnotes — DOCX
  • custom_markup — OOXML
  • printer_information — DOCX, XLSX and PPTX
  • scenarios — XLSX

Extended switches:

  • digital_signatures now applies to OOXML Word, Excel and PowerPoint. It applied to PDF only before.
  • headers_footers now applies to XLSX. It applied to DOCX only before.

Halo now reports an encrypted OOXML file with its own outcome, instead of the previous "unknown file type" result.

For more information, see Define content management policies.

We appreciate your continued support and value your feedback. If you encounter any issues or have any questions, please don't hesitate to contact our support team.

Fixes and improvements​

  • Large uploads and small compressed files no longer run the sync and async APIs out of memory.
  • The sync and async APIs now report the same errors for over-limit archives and for members that fail to unpack. Async base64 results now include the fileId and processingId fields.
  • A semicolon in the X-Session-Id header no longer returns HTTP 500. The API now handles burst load without crashing.
  • The policy Status field now has a default on create and update. Policy edits now apply straight away, without waiting for the cache to expire.
  • The Halo OVA image is smaller.
  • Re-uploading a licence now updates the stored licence fields.

Deploying the Prompt Injection Detection API​

The Prompt Injection Detection API is optional. Follow these steps to add it to a Halo 2.22.0 install on AKS, EKS, GKE or OKE.

Before you start:

  • Your Halo licence must include the Pulsar entitlement. Pulsar reads the licence already installed for Halo.
  • Allow room for one more pod. It requests 1.5 CPUs and 2 GiB of memory, with limits of 2 CPUs and 3 GiB.

  1. Pull the chart:

    helm pull oci://glasswallhub.azurecr.io/helm/cdrplatform-pulsar --version 0.1.0 --untar --untardir .

  2. Install Pulsar. Always set the image tag, because the chart's default tag is not in the Glasswall registry.

    helm upgrade --install cdrplatform-pulsar cdrplatform-pulsar -n cdrplatform --atomic --timeout 15m \
      --set image.registry=glasswallhub.azurecr.io \
      --set image.tag=2.22.0-212371

    The first start pulls a 630 MB image and loads the detection model. The 15-minute timeout gives it time to start, so Helm does not undo the install too early.

  3. Connect API Access to Pulsar. Add this setting to the command you use to install cdrplatform-api-access, then run that command again:

    --set configuration.PULSAR__Endpoint="dns:///pulsar.cdrplatform.svc.cluster.local:50051"

    If Halo runs in a namespace other than cdrplatform, use that namespace in the address. Until you set this, the endpoint returns 503 Service Unavailable.

  4. Send a short text to POST /api/v1/detect/prompt-injection to check the install. A licensed install returns a verdict.

MongoDB operator upgrade notice​

Starting Halo v2.22.0, in-cluster MongoDB is managed by MongoDB Controllers for Kubernetes (MCK, the mongodb-kubernetes chart) in place of the deprecated MongoDB Community Operator (community-operator). This applies only if you run MongoDB inside the cluster. Deployments backed by DocumentDB, Cosmos DB or another external MongoDB are unaffected and need no action.

If you run MongoDB inside the cluster, uninstall the Community Operator first, then install MCK. Your data is preserved if the MongoDBCommunity CRD carries the retain annotation before the uninstall.

Add the MongoDB Helm repository if you have not already:

helm repo add mongodb https://mongodb.github.io/helm-charts
helm repo update

Then, on a cluster running in-cluster MongoDB:

# Protect the data: this annotation stops the uninstall cascading to the CRD, replica set and volumes
kubectl annotate crd mongodbcommunity.mongodbcommunity.mongodb.com helm.sh/resource-policy=keep --overwrite

# Remove the old Community Operator
helm uninstall community-operator -n cdrplatform

# Install MongoDB Controllers for Kubernetes
helm install mongodb-kubernetes-operator mongodb/mongodb-kubernetes -n cdrplatform --version 1.12.0

# Redeploy the MongoDB chart (use the same cloud_provider you deployed with)
helm upgrade -i cdrplatform-mongodb cdrplatform-mongodb -n cdrplatform --atomic --set cloud_provider=<provider>

MCK adopts the existing replica set in place and rolls the MongoDB pod once. Confirm the pod is Ready and the data is intact before continuing the upgrade.

Rabbitmq Upgrade Notice​

Starting Halo v2.9.0, the RabbitMQ version is upgraded from 3.13 to 4.x. When upgrading from an older version of Halo to any version above 2.9.0 all stable RabbitMQ feature flags should be enabled before performing the usual upgrade process using below command -

rabbitmqctl enable_feature_flag all

ICAP server upgrade notice​

The ICAP server is now operated from the portal: mutual TLS moved out of the chart's configuration block and became a setting an administrator can change, and starting and stopping the server moved there too. Four things need attention when upgrading an existing ICAP install.

configuration.ENABLE_MTLS was replaced by settings.ICAP.MutualTlsEnabled. The chart fails the render on the old key, naming the replacement, rather than accepting it and ignoring it. Update any values overlay or saved helm upgrade command before upgrading:

--set settings.ICAP.MutualTlsEnabled=true

The certificate volume is now always mounted, so enabling mutual TLS no longer changes the pod specification. It still takes effect on the next ICAP server restart, because the listener binds its port at startup. While mutual TLS is off the server does not bind the TLS port at all, where earlier versions bound it and refused every connection, so a port scan of an appliance without certificates no longer reports that port as open.

The ICAP server pod now runs as its own service account, so that it can write its settings to its own ConfigMap, where it previously ran as default. Anything in the namespace bound to default—a workload-identity annotation, an image-pull secret, a NetworkPolicy or an RBAC rule naming it—has to be reapplied to the new account. Set the annotations on the new account:

--set serviceAccount.annotations.<key>=<value>

Or keep the account the install already uses:

--set serviceAccount.name=<existing-account>

The ICAP server is now started and stopped from the Portal. Open Protection settings, select the ICAP tab and use the control under ICAP configuration. The appliance ships with the ICAP server installed but not running, and nothing answers on the ICAP ports until an administrator turns it on. The ICAP settings on that tab can be changed only while the server is on.

Stop the ICAP server once after your first upgrade if you were not running it. The chart no longer fixes the number of ICAP servers, so that the Portal control keeps whatever you set across later upgrades. Upgrading a release installed from an earlier chart starts the server once as part of that change, whatever state it was in beforehand:

kubectl scale deploy icap-server -n cdrplatform --replicas=0

Only the first upgrade needs this. A freshly imaged appliance is unaffected.

Deprecation notice​

Please note cdrplatform-metrics-collation service is deprecated and removed from release 2.6.2. When upgrading to 2.6.2 and any version above, please uninstall the cdrplatform-metrics-collation helm chart using below command.

helm delete cdrplatform-metrics-collation -n cdrplatform
Service Versions (Image tags)
ServiceContainer RepositoryVersion
cdrplatform-engineglasswallhub.azurecr.io/cdrplatform-engine2.22.0-212371
cdrplatform-sync-apiglasswallhub.azurecr.io/cdrplatform-sync-api2.22.0-212371
cdrplatform-report-extractorglasswallhub.azurecr.io/cdrplatform-report-extractor2.22.0-212371
cdrplatform-portalglasswallhub.azurecr.io/cdrplatform-portal2.22.0-212371
cdrplatform-policy-apiglasswallhub.azurecr.io/cdrplatform-policy-api2.22.0-212371
cdrplatform-api-accessglasswallhub.azurecr.io/cdrplatform-api-access2.22.0-212371
cdrplatform-portal-accessglasswallhub.azurecr.io/cdrplatform-portal-access2.22.0-212371
cdrplatform-license-managementglasswallhub.azurecr.io/cdrplatform-license-management2.22.0-212371
cdrplatform-cleanupglasswallhub.azurecr.io/cdrplatform-cleanup2.22.0-212371
cdrplatform-async-apiglasswallhub.azurecr.io/cdrplatform-async-api2.22.0-212371
cdrplatform-metrics-projectionglasswallhub.azurecr.io/cdrplatform-metrics-projection2.22.0-212371
cdrplatform-tally-accumulatorglasswallhub.azurecr.io/cdrplatform-tally-accumulator2.22.0-212371
icap-serverglasswallhub.azurecr.io/icap-server2.22.0-212371
cdrplatform-rabbitmqglasswallhub.azurecr.io/cdrplatform-rabbitmq2.22.0-212371
cdrplatform-storage-monitorglasswallhub.azurecr.io/cdrplatform-storage-monitor2.22.0-212371
Prompt Injection Detection APIglasswallhub.azurecr.io/pulsar/detection2.22.0-212371
Helm Chart Versions
ChartChart RepositoryVersion
cdrplatform-rabbitmqglasswallhub.azurecr.io/helm/cdrplatform-rabbitmq0.9.4
cdrplatform-external-secretsglasswallhub.azurecr.io/helm/cdrplatform-external-secrets0.7.0
cdrplatform-storageglasswallhub.azurecr.io/helm/cdrplatform-storage0.8.1
cdrplatform-engineglasswallhub.azurecr.io/helm/cdrplatform-engine0.6.3
cdrplatform-sync-apiglasswallhub.azurecr.io/helm/cdrplatform-sync-api0.4.3
prometheus-scalingglasswallhub.azurecr.io/helm/prometheus-scaling0.3.1
cdrplatform-portalglasswallhub.azurecr.io/helm/cdrplatform-portal0.4.3
cdrplatform-policy-apiglasswallhub.azurecr.io/helm/cdrplatform-policy-api0.3.3
cdrplatform-api-accessglasswallhub.azurecr.io/helm/cdrplatform-api-access1.5.0
cdrplatform-portal-accessglasswallhub.azurecr.io/helm/cdrplatform-portal-access0.5.1
cdrplatform-license-managementglasswallhub.azurecr.io/helm/cdrplatform-license-management0.4.0
cdrplatform-cleanupglasswallhub.azurecr.io/helm/cdrplatform-cleanup0.3.4
cdrplatform-async-apiglasswallhub.azurecr.io/helm/cdrplatform-async-api0.2.4
cdrplatform-metrics-projectionglasswallhub.azurecr.io/helm/cdrplatform-metrics-projection0.2.3
cdrplatform-report-extractorglasswallhub.azurecr.io/helm/cdrplatform-report-extractor0.2.2
cdrplatform-tally-accumulatorglasswallhub.azurecr.io/helm/cdrplatform-tally-accumulator0.2.5
cdrplatform-mongodbglasswallhub.azurecr.io/helm/cdrplatform-mongodb0.3.1
icap-serverglasswallhub.azurecr.io/helm/icap-server2.2.3
cdrplatform-storage-monitorglasswallhub.azurecr.io/helm/cdrplatform-storage-monitor0.2.5
cdrplatform-pulsarglasswallhub.azurecr.io/helm/cdrplatform-pulsar0.1.0

Documentation​

Swagger Documentation Glasswall Documentation Clean a file Archive Support License Management

Last updated on