A single HIPAA breach can cost a healthcare‑focused startup like Devin millions in fines, remediation expenses, and irreparable brand damage. Regulators expect detailed logs of who accessed protected health information (PHI), when, and why. Without that evidence, an audit can quickly turn into a costly investigation.
In many fast‑moving teams, developers reach the same PostgreSQL instance with a shared service account. The credentials sit in a config file, and any engineer can run arbitrary queries. Auditing is limited to occasional manual log reviews, and there is no way to hide PHI returned by the database. The result is a blind spot: the organization cannot prove that only authorized queries touched PHI, nor can it demonstrate that privileged access was granted only for a justified purpose.
Most organizations address the first gap by moving to identity‑aware authentication: each service or CI job gets its own OIDC token, and role‑based policies restrict which tables can be read. This reduces the blast radius of a compromised secret, but the request still travels straight to the database. There is still no central point that can enforce query‑level controls, mask sensitive fields in real time, or capture an immutable replay of the session. Without a data‑path gateway, the audit trail remains incomplete.
That missing control surface is where hoop.dev fits. By positioning a Layer 7 gateway between every identity and the underlying infrastructure, hoop.dev becomes the only place where enforcement can happen. The gateway inspects each protocol exchange, applies just‑in‑time approvals, masks PHI on the fly, and records a full session replay that can be stored for the required retention period.
Continuous audit evidence for HIPAA
HIPAA’s Security Rule demands that covered entities maintain logs of all accesses to ePHI, retain them for six years, and make them available for inspection. hoop.dev records each session from the moment a user authenticates until the connection closes. Those recordings include timestamps, the identity that initiated the request, the exact commands issued, and the responses received. Because the proxy sits in the data path, the logs cannot be altered by the client or the target system.
When a query returns a column that contains PHI, hoop.dev masks the field in real time. The original value never leaves the gateway, so downstream tools or screen recordings cannot capture it. Masking policies are defined once and enforced consistently across every connection, satisfying the HIPAA requirement to limit unnecessary exposure of ePHI.
Just‑in‑time (JIT) access is another safeguard. Before a privileged command is forwarded, hoop.dev can require a human approver. The approval workflow is logged, linking the approver’s identity to the specific operation. This creates a clear chain of responsibility, a key element of HIPAA’s accountability mandate.