The technical safeguards in 45 CFR §164.312 are where HIPAA meets your identity provider, EHR configuration, database settings, VPN and email gateway. They are written in technology-neutral language, which means the regulation tells you what outcome to achieve, not which product to buy. Translating that into concrete configuration decisions is the work of this assessment.
Our HIPAA technical safeguards assessment examines the systems that store, process or transmit ePHI and tests whether controls exist, are configured as intended and are documented. It is narrower and deeper than an enterprise HIPAA security risk assessment: we look at screens, settings and logs rather than relying on questionnaires.
Key points
- Five standards: access control, audit controls, integrity, person or entity authentication, transmission security.
- Some implementation specifications are required, others addressable — addressable is not optional.
- MFA, EDR and penetration testing are strong practices but are not explicitly mandated by the current rule.
- An assessment is not a government audit and does not certify compliance.
Service overview
We assess each in-scope system against the five §164.312 standards and their implementation specifications, collecting evidence such as configuration screenshots, user access exports, log samples and encryption settings. Findings describe what we observed, why it matters for ePHI and a practical fix.
Typical in-scope systems include the EHR or core clinical platform, practice management and billing systems, cloud workloads and databases, identity and access management, endpoints, email and file sharing, and integrations or APIs that move ePHI between systems.
Because the standards are outcome-based, the same requirement looks different in each system. Audit controls in an EHR mean user-level access logs and someone reviewing reports of unusual chart access; in a cloud database they mean query logging, administrative activity logs and alerting. Unique user identification in a clinic may hinge on shared workstation practices; in a SaaS platform it often hinges on support staff using individual, not shared, admin accounts. We assess each system on its own terms rather than applying a one-size checklist, and we note where a system relies on a vendor to provide the control — in which case we look at what the vendor documents and what your configuration enables. Our technical safeguards resource gives a plain-language overview of each standard.
Who needs this assessment
- Organizations whose risk analysis flagged technical gaps but lacked the detail to act on them.
- Healthcare SaaS and health IT vendors preparing for customer security reviews — see HIPAA consulting for healthcare IT vendors.
- Providers implementing or migrating an EHR, or consolidating systems after an acquisition.
- IT teams that want an independent check on access reviews, logging and encryption before an audit or investigation.
Regulatory considerations
The Security Rule distinguishes required implementation specifications, which must be implemented, from addressable ones. For an addressable specification, §164.306(d)(3) requires the entity to assess whether it is reasonable and appropriate; implement it if so; otherwise implement an equivalent alternative measure if reasonable and appropriate, and document why. Simply skipping it is not an option.
| Standard | Implementation specification | Required / Addressable |
|---|---|---|
| Access control §164.312(a) | Unique user identification | Required |
| Access control §164.312(a) | Emergency access procedure | Required |
| Access control §164.312(a) | Automatic logoff | Addressable |
| Access control §164.312(a) | Encryption and decryption | Addressable |
| Audit controls §164.312(b) | (Standard only) Mechanisms to record and examine activity | Required |
| Integrity §164.312(c) | Mechanism to authenticate ePHI | Addressable |
| Person or entity authentication §164.312(d) | (Standard only) Verify identity of those seeking access | Required |
| Transmission security §164.312(e) | Integrity controls | Addressable |
| Transmission security §164.312(e) | Encryption | Addressable |
Common technical safeguard gaps
- Shared or generic accounts in clinical areas, undermining unique user identification and audit trails.
- Audit logging turned on but never reviewed, or retained for too short a period to support an investigation.
- No tested emergency access (“break glass”) procedure for when normal authentication fails.
- Encryption decisions for laptops, backups and databases made informally with no documented rationale.
- Terminated users and former contractors still active in secondary systems not connected to single sign-on.
- ePHI sent through unencrypted email, SFTP replaced by ad-hoc file sharing, or APIs without transport encryption.
- Service accounts and API keys with broad privileges and no rotation.
How we assess technical safeguards
Scoping by ePHI flow
We begin with a data flow review to identify every system where ePHI is created, stored or transmitted, including integrations and backups. Scope follows the data, not the org chart.
Evidence-based testing
For each control we request evidence: user lists compared to HR rosters, role definitions, sample audit log extracts and review records, session timeout settings, disk and database encryption status, TLS configuration on external endpoints. Where useful we observe a control working, such as a logoff or an MFA prompt.
Recommended practices, clearly labeled
We note where widely adopted practices — MFA, endpoint detection and response, centralized log monitoring, vulnerability scanning, penetration testing — would strengthen your posture. We label these as recommendations, distinct from what §164.312 requires today. HHS 405(d) Health Industry Cybersecurity Practices (HICP) is a useful reference for prioritizing them.
Typical deliverables
- System inventory and ePHI data flow summary for in-scope systems.
- Control-by-control findings matrix mapped to §164.312, with evidence references.
- Addressable specification decision records — documented reasoning for each implementation choice.
- Prioritized technical remediation plan, ready for HIPAA compliance remediation or your own IT team.
- Executive summary of key risks for leadership.
Engagement process
- 1
Scope and access
Agree in-scope systems and arrange read-only access or screen-share sessions with administrators.
- 2
Data flow review
Map how ePHI moves between systems, users and vendors.
- 3
Control testing
Review configurations and evidence for each §164.312 standard on each system.
- 4
Findings validation
Walk through draft findings with system owners to correct misunderstandings before the report is final.
- 5
Report and roadmap
Deliver the findings matrix, decision records and a prioritized remediation plan.
Cost factors
The main drivers are the number of in-scope systems and environments, how many are self-hosted versus SaaS (where you rely on vendor evidence), the availability of administrators for evidence sessions, and whether technical testing such as vulnerability scanning is included. A single-EHR clinic is a short engagement; a SaaS platform with multiple cloud environments and integrations is larger. See HIPAA compliance cost for broader context.
Frequently asked questions
Does HIPAA require encryption?
Under the current Security Rule, encryption of data at rest and in transit are addressable implementation specifications. You must assess whether encryption is reasonable and appropriate and, if you decide not to implement it, document why and implement an equivalent alternative if reasonable. In practice, few organizations can justify leaving portable devices or internet-facing transmissions unencrypted.
Is multi-factor authentication a HIPAA requirement?
The current rule requires person or entity authentication but does not name MFA specifically. MFA is a strongly recommended practice, especially for remote and privileged access. The January 2025 proposed rule would make it explicit, but that is a proposal; check its current status.
Is this the same as a penetration test?
No. This assessment reviews whether safeguards required by §164.312 are in place and documented. A penetration test simulates an attacker. Penetration testing is a good practice but is not explicitly required by the current Security Rule; it can complement this assessment.
Does this cover physical and administrative safeguards?
No, it focuses on §164.312. Administrative (§164.308) and physical (§164.310) safeguards are covered in a full security risk assessment or gap analysis.
Authoritative sources
This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.