Stop customer data leaving the laptop. Keep it patched.
One agent on each endpoint decides, on the device, what may leave it and what may be installed on it — and keeps the record an auditor asks for under DPDP, RBI and ISO 27001.
- Detection and decisions run on the device
- Signed bundles and two-person approval
- Hash-chained, tamper-evident audit log
- ● Blocked
customers_Q3.xlsx
Upload to personal webmail · Aadhaar ×12
- ● Redacted
Prompt to ChatGPT
PAN masked, question sent
- ● Justified
loan_book.pdf
Copy to USB · reason recorded
- ● Installed
KB5044284
Signed bundle · approved by 2 people
Illustrative example
Data going out. Patches coming in.
Buy one or both. Each endpoint gets only the features it needs, managed from the same console.
Know where sensitive data goes. Decide what happens next.
- Aadhaar, PAN, GSTIN, IFSC, UPI and cards validated by checksum, on the laptop
- Files, USB, clipboard, print, browser uploads and AI prompts in one view
- AI prompts redacted instead of blocked outright
- Every incident scored, with the reasons shown
Approve once. Roll out in rings. Prove every install.
- Signed bundles, built offline and carried across an air gap
- Two people approve; nobody approves their own deployment
- Ring-by-ring rollout that pauses when something fails
- In doubt, the agent installs nothing and reports
Every way data leaves a laptop.
Each event carries the content's label, the channel and the destination, so you see paths, not isolated alerts.
Detectors that validate, not just match.
Indian identifiers are checked against their real checksum rules, scored from the words around them, and masked before anything is stored.
Four steps from install to evidence.
- STEP 1
Enrol the endpoint
Install one signed agent with a one-time token. It reports in and picks up its policy.
- STEP 2
Decide at the gate
Detection and the verdict happen on the laptop: allow, warn, ask for a reason, hold or stop.
- STEP 3
Approve with two people
Policy changes and patch deployments need a second person. Nobody approves their own.
- STEP 4
Prove it afterwards
Every verdict and install lands in a hash-chained log you can verify and hand to an auditor.
More choices than allow or block.
Start in monitor mode, read what each rule would have stopped, and tighten from there.
Let it through.
Record it, say nothing.
Tell the user, do not stop them.
Ask for a reason and record it.
Hold for a human approver.
Set the file aside.
Stop the operation.
One of everything an operator has to run.
One agent
Detection, the policy decision and the patch engine run on the device, online or offline.
One server
Hands out signed policy and approved patches. Never in the path of a decision.
Per-endpoint licensing
Assign DLP and patch features only to the endpoints that need them.
Hosted, private or air-gapped
The same software in our cloud or inside your own network.
Questions people ask first.
One platform from Dataspace Security with two products: Dataspace DLP, which controls sensitive data leaving the endpoint, and Patch Management, which controls what gets installed on it. Both run on the same agent and are managed from the same console.
Dataspace One produces the evidence. GovernanceOps AI turns it into compliance.
Carry DLP incidents and patch records into DPDP, SEBI CSCRF and ISO audit packs from one workspace.
See what is leaving your laptops today.
Start in monitor mode, or book a walkthrough with our team for the hosted, private or air-gapped edition.
