Skip to content

Every read and every write is authorization-checked.

Pensieve LabsSecurity

Governanceis thearchitecture.

Governed by construction

One governed recordpensievelabs.org

The floor every tool stands on

Move past security as a layer laid over a finished application. In Pensieve the core systems sit underneath every tool: one path to the database, one identity and session system, one authorization decision on every read and write, one audit trail, and one outbound path to anything beyond the hospital. An automated check fails the build when a tool tries to go around them.

That leaves a reviewer with a short list of properties to test. A user cannot query records they hold no entitlement to, because the restriction lives in the read path. Every action reaches the audit trail in the same transaction as the change. Consent is a modelled object the authorization system reads on each access.

Read this page against your deployment model

A security claim that holds for one deployment model can fail for another, and Pensieve is defined across four: a dedicated hosted project, a shared hosted one, the hospital’s own cloud account, and hardware in the hospital’s own building. Where a statement here depends on which one you run, the whitepapers carry the per-model table. The deployment paper holds the definitions, and every other document links back to it.

Deployment Models Explained: DM-1 to DM-4

The strongest control

The lens filters the read, and it sits below the interface

WHAT OPENS THE RECORDConsentAdmissionRolePurposeEmergency pathCirith checks the actionThe lens filters the readAccess log, written in the same transaction as the changeATLAS
What opens a record is checked before the query runs, and the lens narrows the read before any row is assembled. Records outside a user’s entitlement never leave the store. The emergency lane is drawn broken because it bypasses the ordinary gate, and it lands on the same log as everything else.

The mechanisms

Six things that hold, and where each one runs

Authorization, on every action

Cirith decides every action in the platform against the relationship between the person and the record: the role they hold, the unit they work in, the patient’s consent, and the admission that put that patient in front of them. The check runs on each read and each write, and a permission that has not been granted is denied. What a user can see is a projection of what Cirith would allow, so hiding a control and refusing an action are one decision made once.

Cirith, the authorization system

The patient lens, at the read path

The lens is applied where rows are assembled. A query for records a user holds no entitlement to comes back empty, because the restriction is built into the query itself. Minimum-necessary access under HIPAA and purpose limitation under the DPDPA are enforced by the read.

The patient lens

Consent, modelled as an object

Consent is a first-class entity on a two-plane model: the patient owns the record, and admission opens a scoped gate onto it. Grant, refusal and withdrawal are each first-class actions and each audited, so the lawful basis for an access is provable after the fact. Categories a hospital designates as restricted, psychiatric records, HIV status, substance use, reproductive health and medico-legal cases, are separately controlled and separately logged, with redisclosure limited by the consent that released them.

Data Protection & Privacy Whitepaper

Audit written inside the transaction

Every action is written to the audit trail in the same transaction as the change it records, so the two cannot come apart, and audit records are archived to write-once storage. Administrator actions are written to the hospital’s own trail as well as ours: creating a user, changing a role, resetting a credential, amending a master.

One identity, one place to revoke

Identity and sessions belong to the Pensieve backend, so one sign-in covers the platform and one revocation ends it. A corridor terminal that ten people touch across three shifts is the hardest place in a hospital to keep identity honest, so individual sign-in is built to be faster than sharing one: fast switching, device-bound second factors, and session lifetimes set per role. A shared login is refused for any role that can view or amend a record. Where the hospital runs its own identity provider, SAML 2.0 and OpenID Connect hand it password policy, multi-factor and de-provisioning.

One way out of the hospital network

orophin runs as one binary inside the building and holds a single outbound, mutually authenticated connection. It exposes no inbound listener, so a network team approves egress and closes the review. It keeps a durable outbox, so machine traffic queues through a link outage and delivers on reconnect. The staff application is served over the internet and still needs connectivity, and we say so on the page that describes it.

The orophin bridge

What your network team approves

One binary inside the building, one connection out

HOSPITAL NETWORKPERIMETERPENSIEVEONE CONNECTION, OPENED FROM INSIDE. NO INBOUND LISTENER.HL7 v2 over MLLPDICOMASTM, CSV, DB pollingPensieve backend, the only path to the recordOROPHIN
The bridge speaks the protocols the machines already speak, and it holds the only line that crosses the perimeter. The hospital owns the boundary, the line is opened from inside it, and both ends authenticate each other.

Requirement, and the mechanism that carries it

Residency and hosting below describe the managed deployment. The other three models move parts of this to the hospital, and the deployment paper states which parts.

What a framework asks a system for, the Pensieve mechanism that answers it, and where that mechanism runs
RequirementPensieve mechanismWhere it runs
Minimum-necessary access (HIPAA) and purpose limitation (DPDPA)The patient lens at the database read path, with an authorization decision on every read and write.Cirith
Lawful, withdrawable consent (DPDPA)Consent is a first-class object on a two-plane model; the authorization system reads it on every access.two-plane consent
A complete, tamper-evident access record (NABH, DPDPA)Every action is audited in the same transaction as the change and archived to write-once storage.audit trail
Every record entry attributable to a named person (NABH)A shared login is refused for any role that can view or amend a record, and individual sign-in is built to be faster than sharing one.Nexus
Data residency (DPDPA)In the managed deployment, Pensieve runs on Google Cloud in region asia-south1 (India), co-located with the database.asia-south1
The attack surface a hosted system usually addsThe orophin bridge is outbound-only over mTLS, with no inbound port and no listener on the hospital network.orophin

Who is reading this

Four people arrive here, and each wants a different answer

The IT head: what do I run, and what do you want from my network?

One binary, on a Windows PC or a Linux server inside the building, holding one connection out. There is no inbound rule to write, no listener to expose and no tunnel into your estate. The bridge speaks the protocols your machines already speak and queues their traffic through an outage. Everything else is served over the internet.

What is deployed, and where

The CISO: where is the decision made, and what can Pensieve decrypt?

The decision is made below the interface, once, on every read and write. Encryption, the key hierarchy, key custody, and the precise answer to what Pensieve can decrypt are stated per deployment model in the security whitepaper, alongside network security, the development lifecycle, vulnerability management, detection, incident response and continuity.

Pensieve Security Whitepaper

The security reviewer: what can I read before the call?

The assurance overview is public: what Pensieve holds today, what is in progress, and what it does not hold. The four whitepapers behind it open on the Trust Center after one access request, each carrying a document id, a version, a last-modified date and a SHA-256 you can verify. Read them and most of a questionnaire answers itself.

Trust & Assurance Overview: What Pensieve Has, What Is Coming, What It Does Not Have

The medical superintendent: can I prove who opened a record?

Yes, and the proof is a property of the write. Every access and every change carries the name of the person who made it, whichever terminal they used, written in the same transaction as the change, and archived. An administrator can ask it either way round: who currently holds access to this patient’s record, and everything one member of staff can reach. A permission change can be simulated before it is made.

Governance, written down once

Every legal, security and privacy text Pensieve publishes is authored once in the Trust Center. The notices this website renders are fetched from it at render time, and this site keeps no copy of any of it. There is one text, one version, one last-modified date and one SHA-256 for that text at any moment, so a reviewer quoting this page and a reviewer quoting the Trust Center are quoting the same bytes. Each document page prints its hash and the link that resolves it.

The document register

What governance means on this page

Access is governed because the decision is made in one place and recorded as it is made. Documents are governed because each carries an owner, a version, a review date, and a published notice once that date passes. Where a control belongs to the hospital, the boundary statements name the hospital as its owner. A shared control then has someone who answers for it.

What leaving looks like

Because Pensieve reads open standards it can write them, so your data leaves on HL7 v2, FHIR R4 and DICOM. The bridge lets Pensieve run alongside the systems you already have, so there is no rip and replace to reverse. Pensieve commits to that exit in writing.

Exit and Data Portability Commitment

What Pensieve does not hold

There is no ISO 27001 certificate, no SOC 2 report and no completed external penetration test to point at today. The assurance overview lists each one, says whether it is planned, and gives the date and the owner where it is. It is the register, it is more current than any other page here, and it is public.

Trust & Assurance Overview: What Pensieve Has, What Is Coming, What It Does Not Have

The published record

The documents behind this page

This page states the argument. The documents below state the detail, and where the two differ the documents win: each is authored once in the Trust Center, versioned, hashed and reviewed on a schedule. The assurance overview is public there, and the Trust Center releases the four whitepapers on request.

Security

WPR-GL-001. Twenty one sections, written for a hospital’s IT head and its security reviewer at once, qualified per deployment model throughout because a claim that holds for a dedicated deployment can fail for an on-premise one.

Pensieve Security Whitepaper

Architecture

WPR-GL-002. What the platform is technically: its layers, its tenancy model, how a hospital sets it up through configuration, how it integrates, how it is released and observed, and where its limits are.

Pensieve Architecture & Technical Overview

Privacy and data protection

WPR-GL-003. Who is answerable for what under the DPDPA, how consent is divided between the hospital and Pensieve, how a data principal’s rights are routed and answered, and what residency means in each market.

Data Protection & Privacy Whitepaper

Deployment

WPR-GL-004. The single source of truth for the four deployment models, from a dedicated hosted project to hardware in your own building, and what each one moves from Pensieve to the hospital.

Deployment Models Explained: DM-1 to DM-4

Assurance

WPR-GL-005. The register of what Pensieve holds today, what is in progress with dates and owners, and what it does not hold. It is reviewed quarterly and re-dated in public when a target moves.

Trust & Assurance Overview: What Pensieve Has, What Is Coming, What It Does Not Have

Powerful. Responsible. Pensieve.

Get started