Encryption that does not require rewriting the application — an agent between the application and storage, so the fifteen-year-old system nobody will refactor becomes addressable. It also lets a DBA administer a system without reading the data inside it.identity & access (least-privilege), all on the DataAI Command Graph. Now part of Veeam.
Data residency & processing — two different questions
Where data lives
Yours — deploy on-premises in India
CipherTrust Manager deploys as a virtual appliance or physical hardware in your own data centre, and Luna HSM is a box you own. Keys, ciphertext and policy stay on infrastructure you control — the strongest available answer to an Indian residency question, where the evidence is a serial number and an access log rather than a contract clause.
The constraint, stated plainly
No India SaaS region — and Noida is people, not data
CipherTrust as-a-Service runs in Europe and North America only. Thales has 2,200+ staff in India with Noida as its Cyber & Digital engineering centre, and that is a genuine commitment — but people in India and data in India are different facts. Treating an engineering presence as a residency answer is the error that surfaces during an audit.
For a residency-bound Indian buyer this pushes you to on-premises deployment, which is very likely what your regulator wanted anyway. Under the DPDP Act the sequence matters more than the product: find the personal data first, then protect it. For RBI-regulated entities the question behind the question is usually who can decrypt, and whether administrators can read production data — both answerable here with evidence rather than assurance. And note what does not exist, so its absence is not misread: Gartner publishes no Magic Quadrant for HSM or key management at all, only Market Guides, which have no Leader quadrant. No vendor in this category has a Gartner Leader placement, and any implying one is misleading you.
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
This page covers CipherTrust Transparent Encryption. The rest of the Securiti platform:
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
An agent between the application and storage that encrypts data at rest and enforces access policy — with no modification to the application itself.
What consolidation actually replaces, dimension by dimension.
| Dimension | Unprotected / signature email | Transparent Encryption |
|---|---|---|
| Where is data | Unknown / partial map | Discovery + classification everywhere |
| Shadow data | Untracked exposure | Shadow & dark data detected |
| Misconfig risk | Found late (if ever) | Data risk & misconfig, ranked |
| Who can access | Unknown | Data Access Intelligence (the edge) |
| Least-privilege | Over-broad standing access | Access governance — cut it back |
| Data + privacy + AI | Separate tools, gaps | One DataAI Command Graph |
| Vendor backing | (startup risk) | Now part of Veeam |
| Best fit | (varies) | Know, govern access, reduce risk |
Securiti DSPM tells you where your sensitive data is, who can access it, and how to reduce the risk — discover & classify, find misconfigurations, tie data risk to identity/access (least-privilege), protect at rest & in motion — on the DataAI Command Graph (same graph as privacy + AI). GigaOm ‘Highest Rated’, Gartner Customers’ Choice. Now part of Veeam. Honest: competitive field — DSPM inside cloud security? Wiz. Deep file/access heritage? Varonis. TechBag scopes modules, adds GST & the India DPDP framing.
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
Discover and classify sensitive data across clouds, SaaS, on-prem, files and databases — so you know WHAT sensitive data you have and WHERE it lives, structured and unstructured alike. You can't secure data you can't see. Find it all first.
Surface data risk and misconfigurations — public buckets, over-shared files, unencrypted or mis-permissioned data, shadow copies — and prioritise by sensitivity. See where sensitive data is actually exposed. Risk, ranked by what matters.
Data Access Intelligence & Governance maps WHO can access each store of sensitive data — identities, entitlements, effective permissions — so you don't just find sensitive data, you know who can reach it, and can enforce least-privilege. Data risk, tied to identity. The core edge.
Reduce the risk — remediate misconfigurations, cut over-broad access, protect data at rest and in motion across clouds and SaaS — and keep it reduced. Not just finding risk, but reducing it. Posture that improves, not just reports.
Everything — the data, the risk, the access, the controls — is governed by ONE DataAI Command Graph, the SAME graph that powers Securiti's privacy and AI governance, so DSPM isn't a silo but part of a unified data-command story. One graph for data, access and beyond. Governed as one.
One map of where sensitive data lives and who touches it — risk governed at the source, not at the perimeter.
Securiti finds your sensitive data, ties the risk to who can access it & reduces it — data-centric security posture from portfolio, and paired with the human firewall.
Discover sensitive data across clouds, SaaS, on-prem, files and databases — structured and unstructured — so you know what you have and where it lives. You can't secure what you can't see. Find it all.
Classify data by sensitivity and type (PII, PHI, PCI, secrets, regulated data) with high accuracy on the graph — so risk is prioritised by what actually matters. Know what each store holds. Classification you can trust.
A single catalog of your sensitive data across the whole estate — built on the DataAI Command Graph — so you have one map of where sensitive data lives. One map of your sensitive data. The single source of truth.
Surface shadow copies, forgotten stores and dark data that no one's tracking — the exposure you didn't know you had. Find the data you forgot about. No blind spots.
Detect data risk and misconfigurations — public buckets, unencrypted stores, over-permissive settings — and rank by sensitivity. See where sensitive data is exposed. Risk, prioritised.
Map WHO can access each store of sensitive data — identities, entitlements, effective permissions — so you don't just find sensitive data, you know who can reach it. The differentiator. Data risk, tied to identity.
Find data that's over-shared or over-permissioned — files anyone can open, identities with far more access than they need — so you can cut it back. Too much access is risk. Right-size it.
Score and prioritise data risk continuously, and track your data security POSTURE over time — so you fix what matters most and catch drift early. Posture you can measure. Improve, don't just report.
Data Access Governance lets you enforce least-privilege — cut over-broad access to sensitive data down to who genuinely needs it. From knowing who can reach data to reducing it. Least-privilege, enforced.
Protect sensitive data at rest and in motion across clouds and SaaS — encryption, masking, controls — so exposure is reduced, not just reported. Reduce the risk, don't just find it. Protection that follows the data.
Remediate misconfigurations and over-broad access, and continuously monitor posture so drift is caught early — posture that gets better and stays better. Fix and keep it fixed. Continuous, not one-shot.
One knowledge graph maps sensitive data, its access and its controls — the SAME graph that powers Securiti's privacy and AI governance — so DSPM is part of a unified data story, not a silo. One graph for data and access. Context is everything.
The overview, getting started, and the core workflows.
Encrypting without changing the application.
Where it sits in the platform.
Want a live, India-context walkthrough for your environment?
Book a guided demo →Here’s what genuinely sets Securiti apart (and where a point tool leads).
Every encryption programme meets the same wall: the systems most in need of protection are the ones nobody will modify. A fifteen-year-old application that the business depends on, that no current employee wrote, and whose vendor support ended years ago is not getting refactored to add encryption, whatever the policy says. An agent between the application and storage sidesteps the question entirely — the application is unchanged, the data on disk is protected, and the project can actually include the systems that mattered most. That is a deployment argument rather than a cryptographic one, and it is why this product exists.
In most estates, the permission to keep a database running and the permission to read every customer record inside it are the same permission. That is not a considered decision; it is an accident of how database privileges work. Privileged-user access control separates them, so a DBA or root account can perform its actual job without the data being readable. When an RBI or SEBI reviewer asks who has access to production data, this is the control they are probing — and "our administrators, necessarily" is a much weaker answer than a demonstrable separation.
Perimeter thinking assumes the boundary holds. Encrypting and enforcing access at the storage layer means a compromised network, a stolen backup or an over-permissioned account does not automatically yield readable data. The blast radius of any single failure shrinks, which is the practical security argument distinct from the compliance one.
There is a performance cost to encrypting and decrypting on every read and write. How much depends entirely on your workload — I/O patterns, record sizes, how much of the working set is hot — and any number a vendor or a reseller quotes you in the abstract is close to meaningless. Test on your least-modern, most business-critical system rather than a clean host, because that is the system the project must survive. If the overhead is unacceptable there, better to know during a proof of concept than after a rollout.
This is right when you need data at rest protected on infrastructure you control, especially across systems you cannot modify. It is the wrong product if your problem is documents leaving the organisation — protection here stops at the boundary of the systems you control, and a file exported by an authorised process is plaintext the moment it lands elsewhere. For that you want rights management, and TechBag sells Seclore and Microsoft Purview. It is also not a substitute for a key manager: Transparent Encryption applies protection, CipherTrust Manager decides who holds the keys, and serious deployments use both.
Software key management under your control, or keys that exist only in hardware? And on-premises or cloud — remembering CipherTrust as-a-Service has no India region. These two answers determine the architecture and most of the cost, so establish them before any demo.
Scope an encryption project against a scan rather than an asset inventory. Inventories record what was provisioned deliberately; sensitive data accumulates by accident, in the reporting replica and the forgotten file share. Those are the stores that produce breaches, and they are never in the CMDB.
Test transparent encryption and measure performance overhead against your oldest business-critical system, not a clean host. That is the system the rollout has to survive, and an unacceptable overhead is far cheaper to discover now.
Hardware key custody creates roles nobody previously had, and they must be different people. Assign them during the project rather than retrofitting separation of duties afterwards, which is considerably harder and tends to get waived under delivery pressure.
Key rotation is easy to mandate and easy to skip. Equally, back up the security domain and then actually test recovering from it — an untested HSM backup is a assumption, and it is the assumption that ends organisations rather than merely inconveniencing them.
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
“The auditor stopped asking whether the data was encrypted and started asking who held the key. This is what answered that.”
“Deploying against systems nobody would let us modify was the whole reason this got approved.”
“Budget the operational side properly. The appliance is the easy part; the separation of duties took longer than the install.”
“No India SaaS region, so we went on-premises. Honestly that is what our regulator wanted anyway.”
Analyst firms bury this view behind paywalls, and G2 retired its Grid. So here’s TechBag’s synthesis of the DSPM market — tap any vendor to see why it sits where it does.
Execution strength vs product vision — the classic market map, minus the paywall.
Key custody in hardware, with India engineering.
The grid nobody publishes — how deep the core capability is vs how broad the wider platform.
Deepest on key custody; not a document product.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
Wiz (DSPM), Varonis, Cyera, Sentra and BigID — honest lanes; the edge is DSPM tied to identity/access AND unified with privacy + AI governance on one graph (a consolidation play), backed by strong analyst recognition. DSPM inside cloud security? Wiz. Deep file/access heritage? Varonis. We say so — we sell Wiz too.
| Dimension | Thales | Entrust | Microsoft Purview | Seclore | HashiCorp Vault |
|---|---|---|---|---|---|
| What it actually is | Key management + hardware custody + encryption | The HSM and PKI peer | Document rights management | India-built EDRM | Secrets and encryption-as-a-service |
| Who holds the keys | You — in hardware if you want | You — in hardware | Microsoft, unless you use Double Key Encryption | Either — SaaS or self-hosted | You |
| Protection travels with the file | No — this protects infrastructure, not documents | No | Yes — labels travel with the file | Yes, with post-distribution revocation | No |
| Hardware key custody | Luna HSM | nShield — holds BIS certification | DKE holds one key; not an HSM product | Not an HSM vendor | Can integrate with an HSM |
| India data residency | Deploy on-premises — no India SaaS region | On-premises appliances — no India SaaS | India region via Advanced Data Residency | India-built; SaaS or self-hosted | Self-host anywhere, including India |
| Analyst standing | KuppingerCole Overall Leader 2025 ×2 | No HSM/key-management Leader placement found | Microsoft, evaluated broadly elsewhere | Specialist — no Gartner EDRM MQ exists | Widely recognised in its category |
| Published pricing | Quote-only | Quote-only | $12/user/mo Purview add-on; E5 $60 | Quote (INR) | Free community edition |
| The thing to plan around | HSM operations: firmware, backup, separation of duties | Scope: it exited public TLS in Sep 2025 | DKE breaks co-authoring, search and Copilot | Adoption — manual protection is rarely applied | Operationally heavy to run well |
| Best fit | Key custody with hardware, on your own infrastructure | Where BIS certification is a procurement requirement | Microsoft estates with E5 needing document labels | Documents shared outside, India-built vendor | Engineering-owned secrets and encryption services |
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
CipherTrust Transparent Encryption is one of 18 encryption & rights management products TechBag carries. The encryption & rights management guide narrows them to a shortlist and shows the reasoning. →
Drag the sliders (data stores; sensitive-data sources; hour cost as loaded rate). Estimates contrast blind-spot data security (unknown data map, unseen misconfigurations, no access intelligence, over-broad access) vs Securiti (discover & classify, find risk, tie to access, least-privilege) — the wins are faster risk reduction and fewer exposure/compliance incidents. Illustrative — TechBag scopes your estate.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Securiti is priced by QUOTE (annual, modular — scales with data volume, estate size and modules; enterprise license agreements), in USD; no public list. Now a Veeam company. TechBag scopes the modules you actually need (DSPM, data access governance, privacy, AI governance), adds INR/GST, and frames it against DPDP — quote current figures for your estate.
Best for data security posture
Best for a broader rollout
Best value with TechBag
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Tell us your requirements and current tools — we’ll model it against what you spend today.
Take this into your next vendor call — including ours.
Do keys need to exist only in tamper-resistant hardware, or is software key management under our control enough?
Have we accepted that CipherTrust as-a-Service is EU/NA only, and planned on-premises if residency binds us?
Are we clear that Thales's India engineering presence is people, not a data region?
Have we scanned rather than relied on an asset inventory to scope this?
Have we measured the overhead on our least-modern business-critical system?
Who administers the HSM, and who approves key use? They must not be the same person.
Do we need a second appliance at another site, and is it budgeted?
Have we backed up the security domain AND tested restoring from it?
Is our actual problem key custody, or is it documents leaving the organisation? Those are different products.
Have we priced hardware, support, resilience and operations — not just the licence?
Scope Securiti DSPM (know where your sensitive data is, who can access it, and reduce the risk — discovery & classification, data risk & misconfigurations, Data Access Intelligence & Governance for least-privilege, protection at rest & in motion, all on the DataAI Command Graph, now Veeam-backed) — and let a TechBag advisor scope the modules, compare vs Wiz/Varonis/Cyera/Sentra honestly, frame it against DPDP, and add INR/GST and local support.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.