Enforcement
PQ sessions, everywhere people work.
Browser, endpoint and mobile PQ-hybrid session protection for apps that can't be changed, a PQC channel for legacy estates, delivered without touching the application.
Built for
Overview
A closer look at Halo.
Browser, endpoint and mobile PQ-hybrid session protection for apps that can't be changed, a PQC channel for legacy estates, delivered without touching the application.
Dhiti Halo lives in the Enforcement of the platform, whose job is simple: make it actually stop. It ships as part of Dhiti Secure, software platform, the saas that funds the company, so it carries the same sovereignty posture as everything else Dhiti runs: region pinning, keys that stay inside the HSM, and an air gapped deployment for estates that need it.
Nothing here works in isolation. Every product on the platform reads and writes to one shared cryptographic asset graph, so what Halo produces becomes usable everywhere else: a finding here becomes a prioritised task there, and a change becomes a line of audit evidence a regulator will accept. You can adopt Halo on its own, fold it into an edition, or grow into it as your estate matures. It is built to sit above the tools you already bought rather than replace them.
At a glance
- Plane
- Enforcement
- Line
- Dhiti Secure
- Status
- Y3+· Roadmap
- Capabilities
- 3
- Pricing
- Connect for pricing
Why it matters
The problem it solves.
Most teams cannot answer a basic question about their own cryptography: where is it, what algorithms are in use, and what breaks when one of them is deprecated. That gap is not a tooling failure so much as an ownership failure. The SIEM, the EDR, the scanner and the GRC spreadsheet each see a slice, and none of them owns the cryptographic picture.
Halo closes its part of that gap in a way you can measure. Instead of a point in time report that is stale the day it ships, you get a living view that updates as your estate changes, ranked by real risk rather than raw volume, and expressed in the language your auditors and your board already use.
Capabilities
What Halo does.
PQC channel
For legacy apps you can't modify.
Endpoint reach
Browser, endpoint and mobile session protection.
No app changes
Delivered without touching the application code.
Strengths
Why teams choose Halo.
PQC channel
For legacy apps you can't modify.
Endpoint reach
Browser, endpoint and mobile session protection.
Runs on what you already own
It operates inside your existing Splunk, Sentinel, QRadar, CrowdStrike, cloud and CI/CD rather than asking you to rip anything out. Adoption is additive, not a migration in itself.
Sovereign by architecture
Data is region pinned to Mumbai, Singapore or Frankfurt at the schema level, keys are handled by reference and never leave the HSM, and a dedicated air gapped edition exists for critical infrastructure.
Honest about what ships
Every capability carries a status token. Nothing is dressed up as available today when it is on the roadmap, which is exactly what a compliance buyer needs to hear.
Priced to the Indian enterprise
The cost structure is built for regulated Indian buyers first, and pricing is quoted against your actual estate rather than a Western enterprise list price.
How it works
Four steps, one asset graph.
Connect
Halo wires into your sources, clouds and tools through the Dhiti connector fabric, read only wherever it can be, so it starts from the estate you actually run.
See
PQC channel: For legacy apps you can't modify. Everything it finds flows into the shared cryptographic asset graph.
Act
Endpoint reach: Browser, endpoint and mobile session protection. Work is ranked by blast radius and confidentiality lifetime, not by raw count.
Prove
Posture rolls up to Dhiti Command and evidence to Dhiti Comply, region pinned and audit ready, so the work you do is the work you can show a regulator.
Works with
It compounds.
Discover finds it. Orchestrate fixes it. Comply proves it.
Where it applies
Built for the estates that carry the risk.
The sectors where this product does the most work, and the regulation that forces the timeline in each:
Healthcare
DPDP + HIPAA, EHR at rest, connected medical devices
Government & Public Sector
CERT-In empanelment, Sovereign edition, air-gapped, DPDP
Education
DPDP, credential and degree signing that must verify for decades
EdTech & Online Learning
DPDP Act 2023 children's provisions, verifiable parental consent, no behavioural tracking
Media & Entertainment
Content signing, DRM key management, archive integrity
Real Estate & Smart Buildings
BMS and access-control crypto, 30-year document integrity
What we measure
We don't invent metrics. This product is measured by the outcomes customers track, exposure reduced, evidence produced, migration rate. Ask us for the current baseline.
Frequently asked
Questions a buyer actually asks.
- Does Halo replace the tools we already have?
- No. It runs alongside your existing security stack and adds the cryptographic layer none of those tools cover. You keep your SIEM, EDR and scanners; Halo makes them part of one picture.
- Where does our data live, and who can see the keys?
- Data is pinned to your chosen region at the schema level, tenants are isolated row by row, and keys are handled by reference so they never leave the HSM. For government, defence and critical infrastructure there is an air gapped Sovereign deployment.
- Is Halo available today?
- Halo carries the status token Y3+, which means it is on the roadmap rather than generally available today. We will always tell you plainly where a capability sits before you plan around it.
- What does it work with?
- It compounds with Aegis, Orchestrate and the rest of the suite through the shared asset graph. Discover finds it, Orchestrate fixes it, Comply proves it.
- How is it priced?
- Pricing is quoted per estate rather than published as a list price. Tell us your sector and scale and we will put a number to it. Every edition includes cryptographic discovery, so even at the entry tier you leave with a CBOM.
Related reading
Quantum threat research
Harvest now, decrypt later, explained for people who own the risk
PQC standards & compliance