Access to clinical systems, with evidence for the safeguards DPDP asks for.
Hospitals and clinics give clinicians, staff and equipment vendors access to systems that hold health records. Pramaan publishes those systems one application at a time and decides each request with your access rules. It writes refusals by its access checks to an audit log, as set out below. Sector rules are yours to map; here is the evidence the product produces.
The statute this page names
Of the statutes we follow, this page names one. The Digital Personal Data Protection Rules were published in the Gazette of India on 13 November 2025, and their phased compliance period ends on 13 May 2027. The Act's highest penalty, up to ₹250 crore, is for a Data Fiduciary's failure to maintain reasonable security safeguards, the category access control sits in. The sources, and which Pramaan evidence fits each safeguard.
Access problems, and what Pramaan offers
| Access problem | What Pramaan offers | From tier |
|---|---|---|
| Clinicians sign in many times a shift, on workstations they share. | Each person signs in as themselves: with passkeys and security keys from the browser, without the mobile app, or with a number-matched push approval in Pramaan's mobile app, which is Android only. Pramaan is its own MFA provider. | Every tier |
| Clinical web applications sit on the hospital network and are needed from outside it. | Publish each application through a connector. When a browser asks for it, the web edge checks the person's sign-in, their groups and your access rules, then relays the request over that app's connector. | Pramaan Zero Trust |
| Equipment and software vendors need remote desktop sessions for support. | Remote desktop in the browser: the browser talks to the broker, which relays to a remote-desktop gateway; the gateway holds the connection to the machine, and the connection's secrets never reach the browser. | Pramaan Sovereign |
| Visiting doctors use laptops and phones the hospital does not manage. | With agent posture reports switched on, a laptop running the Pramaan desktop agent reports its posture checks, and an access rule can name posture labels, such as unmanaged, and step up or deny a request from a device that carries such a label, or require a minimum score. | Pramaan Zero Trust |
| Evidence of access control has to hold up when it is questioned. | Audit events, each entered in a transparency log, set out below. | Every tier |
What the product produces as evidence
- Audit log. When the web edge refuses a request, because of the person's groups or your access rules, the refusal is written as an audit event. The broker keeps its audit events in its PostgreSQL database, on servers you run.
- Receipts. When an AI agent acts through the broker, the broker can hand back a signed action receipt, which an auditor can verify offline against the public key.
- Transparency log. Each audit event is added to a transparency log, whose signed summary you can check without asking us.
Not claimed
- Compliance with a health-sector rule. Mapping it to your controls stays with you.
- Integration with a named clinical system. This page names none.
- Customers or references. This page names none.
- A certification or a third-party audit. Pramaan was internally audited on 13 June 2026; no third-party penetration test yet.
- Recording of privileged sessions. Pramaan itself does not record what is shown or typed in a privileged session.
For your engineers
Technical detail: the evidence chain
On direct connections, the raw-TCP listener writes an audit event when its access checks refuse a connection after the person's token has been read. The transparency log follows RFC 6962; each audit event is a leaf. The browser remote-desktop gateway is guacd. Run the broker with PostgreSQL: without DATABASE_URL, the broker keeps all its state in memory and loses it on restart.
Questions
Does Pramaan make a hospital compliant with the DPDP Rules?
No. It does not make your organisation compliant. It produces evidence for some safeguards, and our page on the DPDP Rules sets out which.
Which health-sector rules does this page cover?
None. Rules written for health records are not covered here, so this page names only the DPDP Rules. Mapping sector rules to your controls stays with you.
Can a vendor support a machine without being given its password?
Through browser remote desktop, yes: the browser talks to the broker, which relays to a remote-desktop gateway; the gateway holds the connection to the machine, and the connection's secrets never reach the browser; the gateway signs in to the machine with the secrets stored in Pramaan's settings for that machine.
Where are the audit events kept?
On your servers: the broker keeps its audit events in its PostgreSQL database.
Talk to us, or try it first
-
Book a walkthrough
Against your own apps, not slides.
-
Run the lab
It uses a demonstration account; none of your data is involved.
-
See pricing
Published floors, named-user bands and what every tier includes.