Security reviewers
What does a hospital security reviewer get from Inhold?
Twenty answers with a status each, a list of known gaps, a map to 45 CFR 164.312, and an evidence pack your own auditor exports from your own account.
Inhold is being built. No customers yet. The AWS install's Terraform passes CI checks but has not been run in a real AWS account. Repo goes public 9 Nov 2026.
Where the data sits
In your account, and nowhere else
Agent memory and outputs
Your database, on your key, inside your cloud account. Inhold the company holds nothing: no telemetry, no license server, no update check.
Who can read it
Only the agents and people named in your policy bundle, and only for the purposes each is registered for. Reads of the audit log are logged too.
PHI labels
Added locally at write time by pattern detectors and an optional local name model. The model misses 1 to 2 names in 10 on synthetic sets, and addresses and free-text dates are not detected, so items about a patient also carry a subject that makes them PHI.
What every decision leaves behind
One row, chained and anchored
Allowed and denied alike
Each policy decision writes one audit row carrying the hash of the row before it and the hash of the policy in force. Rows are never updated or deleted, purge included.
Tampering is detectable
A rewritten row breaks the chain, and anchors signed with a key the database cannot reach catch a rewrite below the newest anchor. Detectable, not impossible: an administrator who can reach both the rows and the anchors is the limit.
A failed commit
If a decision cannot be committed, it is kept and written to the log at the next commit, marked recovered; if that fails too, the log records how many decisions were lost. Verify and the pack show both counts. In the AWS and Azure installs the fallback files are task-local, so a task restart loses them.
What to ask for
The pages made for your review
The reviewer packet
One printable page with the 20 answers, the gaps and the 164.312 map.
The HIPAA map
Each safeguard, what Inhold does for it, and whether that part is built, designed or a gap.
An evidence pack
A real pack from the synthetic demo you can download and check before any install.
What is not there
No SOC 2 report (Type II planned 2027), no outside security review yet (after the first paid pilot), no certification of any kind. The gap list names each one.