One complete record of everything that happens across your environment, with a mature, accredited body of detection and compliance content on top and machine learning and constrained generative AI that never leave your boundary. Software on certified hardware or in your accredited private cloud.
The order is deliberate. The data plane comes first, so every layer above it reads the same complete record: the detection, correlation and compliance content, then machine learning, then generative AI. All of it runs inside your boundary; nothing is sent out to be analysed.
Every capability reads the same complete data on infrastructure you control.
Everything lands once, complete, in open formats.
Logs, endpoint, network, identity, file activity, OT protocol events, IoT device events and AI traces land in one store on hardware you control, queryable in seconds from hot storage. A streaming backbone, a columnar analytical store and an open-table lake for retention. You set retention; the vendor does not meter it.
A mature body of content, running on complete data.
Real-time rule evaluation on the stream, with detection content expressed in the open Sigma standard alongside native rules. Correlation runs on entities, not on log lines, so the same actor touching an identity, a model and a data store is seen as one story.
Whether a control fired, not whether it is documented.
Control-level measurement of regulatory obligations from the same telemetry: government control baselines, operational-resilience rules and critical-infrastructure regimes. Continuous, evidenced, and mapped to the obligations a board is accountable for.
Ask any question of any data, then act inside your boundary.
Sub-second investigation over billions of events from one query surface. Response workflows run as data through an embedded orchestration engine: an action runs automatically where your environment profile allows it and waits for a human where it does not, and every action is recorded against the evidence that justified it.
Every alert taken to a verdict, with the reasoning attached.
Each alert, from Withstand's own detection or from the tools you already run, is ingested, enriched, correlated against the complete record and reasoned to a verdict: closed, escalated, or contained where the gating policy allows. The first two tiers of the SOC run without a human queue; a person steps in where judgement belongs, with the timeline and the evidence already assembled. Every step of the reasoning is written to the evidence tier and exportable, so an analyst, an assessor or a board can read why.
Behavioural detection at millions of events per second.
Baselining, anomaly scoring and classification per entity and per protocol, against the analytical store. CPU-class work, trained in Withstand's build environment and shipped as signed artefacts through the same offline channel as software.
Explains, drafts and ranks, and is never the lead detection claim.
An open-weight model served on your own GPU tier, restricted to natural-language query, obligation-mapped incident narrative for boards, and response-playbook drafting. Nothing model-related leaves your environment, and your data never trains anyone's models.
What happens to one alert, and what is left behind for the person who looks later.
Alerts from
Ingest
Normalised and deduplicated against the record.
Enrich
Resolved to assets, users, data and models.
Correlate
Joined to what the same actor touched.
Reason
Explanations weighed, benign ones included.
Verdict
Decision trail
1Ingest
Alert from the identity source: a third-party application granted mailbox read and offline access for a finance user. Deduplicated against two near-identical events in the same minute.
2Enrich
User resolved in the entity model: finance, no prior consent grants. Application first seen today; publisher unverified.
3Correlate
The same user authenticated from a new location shortly before, with no matching change request. Two signals from one actor inside the hour.
4Reason
Consistent with consent phishing followed by mailbox access. Benign explanation considered: a sanctioned rollout. No record of one.
5Verdict
Escalated, high confidence. Proposed actions: revoke the grant, expire the session. Environment profile: enterprise IT. Revoking the grant runs automatically; expiring the session waits for a person.
6Recorded
Trail written to the evidence tier and exportable. A responder receives the timeline, the entities and the proposed actions.
Collection is where most platforms quietly narrow their claims. A sovereign environment contains all five, and the platforms you already run are sources too.
Endpoint process, file, registry and network events; server and application logs; identity, privileged access and MFA; network flow and DNS; firewall, proxy and email gateway; hypervisor and storage events. Collected by agent, event forwarding, syslog, agentless pulls and network sensor.
Asset inventory and protocol-level events from PLCs, RTUs, SCADA servers, HMIs and historians; control commands, set-point changes, firmware and logic changes. Observed passively on SPAN or TAP, crossing into the enterprise side through a data diode. Active scanning of OT assets is never performed.
Device discovery and fingerprinting; camera, sensor, building-management, access-control and medical-device traffic; broker and gateway events. Most devices cannot host an agent, so the value is behavioural baselining against each device's own normal.
Prompts, responses and tool calls through AI gateways; agent actions and privilege use; model registry and deployment events; vector store and retrieval access; guardrail outcomes. Captured as OpenTelemetry-compatible traces and joined to the identity that initiated them and the data they touched.
File and share access audit; database audit logs; classification and sensitivity labels; DLP and rights-management events; removable-media and cross-boundary transfer events. Lineage from source to model to output.
Cloud security platforms and specialist OT monitoring tools are consumed as sources, not replaced, and their alerts are taken to a verdict here. Withstand is the sovereign layer beside what you already run, for the networks those platforms cannot serve.
| Test | What it requires | Why it matters |
|---|---|---|
| Operational | The platform runs inside your boundary; nothing phones home; updates arrive by controlled media. | Any external dependency is an unassessed path into the most sensitive system on the network. |
| Jurisdictional | The vendor is owned, controlled and answerable inside your jurisdiction. | Foreign ownership, foreign capital and foreign legal obligations survive on-premises deployment. Running the software yourself does not change who the vendor answers to. |
| Supply chain | Documented provenance of every component; imaging and hardening performed in-country; no excluded-vendor parts. | Accreditation attaches to specific bills of materials. Supply chain is now a primary attack surface. |
| AI data governance | Your data never leaves your environment and never trains anyone's models, the vendor's or a third party's. | Digital sovereignty has moved past privacy to control over national-interest data and AI training material. |
Operational sovereignty means you run the software. Jurisdictional sovereignty means the vendor answers to your law. Only the second is a matter of law rather than trust. Withstand is independently owned, carries no intelligence-community capital, is delivered and hardened in your jurisdiction, and is designed so that inference happens inside your accreditation boundary. It is built to clear all four tests.
Withstand will never lead with an 'AI-powered detection' claim. Its detection credibility comes from proven content augmented by classical machine learning; generative capability is applied only where it is the right tool. Models are open-weight with published provenance and a model bill of materials, signed alongside each release.
A signed image on certified hardware or in your accredited private cloud. Single site, clustered, hub and spoke, or one instance per classification domain. Nothing leaves the boundary.
Your own servers from Withstand's hardware compatibility list, imaged and enrolled with a signed operating-system image, measured boot and drive binding. For agencies bound to hardware panels and estates that already own the metal.
The same signed image as a virtual machine in your already-accredited private cloud. The trust posture is reduced and stated as such: the hypervisor is in the trust base.
A core instance plus edge collectors and passive sensors at remote sites and OT zones, joined by diodes or constrained links. Collectors hold local evidence if the link is lost and reconcile on reconnection.
One instance per classification domain, with one-way flows through cross-domain guards where policy permits. Updates, content and models arrive on signed media and are verified against the trust root before use.
Withstand is engineered on the assumption that it will be targeted. An attacker who reaches the monitoring layer can blind the organisation, alter evidence and hide.
A signed, immutable operating-system image on certified hardware, with measured boot from firmware to container images. The system refuses to run altered software and can prove what it is running.
Retained telemetry and audit logs are written to write-once storage tiers with cryptographic chaining, so an intruder who reaches the platform cannot silently alter history.
Services run isolated with per-service identities. Administrative access is role-based, multi-factor and fully audited. No shared credentials, no vendor back door.
FIPS-validated encryption at rest with keys bound to the TPM or an external HSM where mandated. Crypto-erase supports classified decommissioning.
The platform monitors itself with the same detection engine and raises alerts on its own integrity, configuration and access events to a separate, minimal channel.
Offline, signed backups of configuration, detection content and models, and documented bare-metal recovery to a known-good state without any external service.
The next-generation Withstand platform is being built with design partners whose constraints are the specification. If your networks cannot leave, you are who this is for.
Become a design partner