Regulation

The HIPAA Security Rule, read as an engineering backlog

9 November 2026Charles TrinhRemote
The HIPAA Security Rule, read as an engineering backlog — cover card
Regulation · The HIPAA Security Rule, read as an engineering backlog

Access control is a deployment decision

Unique user identification, emergency access and automatic logoff have to exist in the architecture, not in a policy PDF. On a self-hosted estate that means named accounts, sessions that expire, and a break-glass path that is logged when used.

Audit controls need a clock you trust

A log is only evidence if it cannot be silently rewritten and its time source is consistent. Append-only files, journal forwarding and a change record per deployment turn a requirement into an artefact you can hand an auditor.

Transmission security is verifiable

TLS everywhere, no plaintext fallback, and an outbound allowlist is a configuration you can test — refused connections are the proof, not the cipher list.

HIPAAHITECHSecurityAudit
TRINH — Charles Trinh, technology architect
TRINH

Charles Trinh

Fractional CTO/CIO and Technology Architect — Healthcare Data, Identity & Regulated Infrastructure · Las Vegas, NV

Las Vegas, Nevada · US citizen · Fractional and project engagements

(702) 559-3489 Email Charles Trinh