Skip to content
HIPAA ComplianceConsulting

HIPAA Resource

HIPAA Technical Safeguards: §164.312 Explained with Implementation Examples

The five technical safeguard standards in §164.312, what each requires, how organizations typically implement them, and which common controls are recommended practice rather than mandates.

5 min read Reviewed

Technical safeguards are defined in §164.304 as the technology, and the policies and procedures for its use, that protect electronic PHI and control access to it. §164.312 contains five standards: access control, audit controls, integrity, person or entity authentication, and transmission security.

The rule is deliberately technology-neutral. It tells you what outcome to achieve, not which product to buy. That makes it durable, but it also means organizations have to translate each standard into concrete controls. Below, each standard is broken into what the rule says, how it is commonly implemented, and recommended practices that go beyond the explicit text. A technical safeguards assessment tests whether those controls are actually configured and working.

Key points

  • Unique user IDs, emergency access, audit controls and authentication are required.
  • Automatic logoff, encryption, integrity mechanisms and transmission controls are addressable.
  • MFA, EDR, SIEM and pen testing are recommended practices, not explicit current mandates.
  • Decisions must trace back to your risk analysis under §164.308(a)(1)(ii)(A).

The five standards at a glance

StandardSpecificationR/ATypical implementation
Access control §164.312(a)(1)Unique user identificationRNamed accounts in EHR, cloud and OS; no shared logins
Emergency access procedureRDocumented break-glass accounts with logging and post-use review
Automatic logoffASession timeouts and screen locks sized to the setting
Encryption and decryptionAFull-disk encryption; database or storage encryption
Audit controls §164.312(b)—RLogging of access to ePHI systems and a review process
Integrity §164.312(c)(1)Mechanism to authenticate ePHIAChecksums, database constraints, immutable backups, change logs
Person or entity authentication §164.312(d)—RPasswords plus additional factors; certificate-based service auth
Transmission security §164.312(e)(1)Integrity controlsATLS, message authentication, secure file transfer
EncryptionATLS 1.2+ for web and APIs; encrypted email or portals

Access control — §164.312(a)

The standard requires technical policies and procedures that allow access only to persons or software programs granted access rights under §164.308(a)(4). In other words, the technical controls enforce the access decisions your administrative processes make.

Required: unique user identification and emergency access

  • Assign a unique identifier to every user so activity can be traced to a person. Shared front-desk or nursing-station logins are a frequent finding.
  • Service accounts and API keys should also be individually identifiable and owned.
  • Document how ePHI will be accessed during an emergency — for example, sealed break-glass credentials, with every use logged and reviewed afterward.

Addressable: automatic logoff and encryption

  • Automatic logoff: shorter timeouts on shared clinical workstations, possibly paired with tap-badge re-authentication; longer on single-user devices in secured offices. Document the reasoning.
  • Encryption at rest: full-disk encryption on laptops and mobile devices; encryption on databases, object storage and backups. Lost unencrypted laptops have been the basis of many OCR settlements.

Audit controls — §164.312(b)

You must implement hardware, software and/or procedural mechanisms that record and examine activity in information systems that contain or use ePHI. This is a required standard with no sub-specifications, and it pairs with the administrative requirement for information system activity review in §164.308(a)(1)(ii)(D).

  • Decide which events to log: logins, failed logins, record views, exports, privilege changes, configuration changes
  • Protect logs from alteration and retain them long enough to investigate incidents
  • Assign someone to review logs and define what triggers escalation
  • Recommended practice: centralize logs in a SIEM and alert on anomalies such as bulk record access or after-hours exports

Integrity — §164.312(c)

The standard requires policies and procedures to protect ePHI from improper alteration or destruction. The addressable specification asks for electronic mechanisms to corroborate that ePHI has not been altered or destroyed in an unauthorized manner.

  • Application-level audit trails showing who changed what and when
  • Database integrity constraints and controlled change management
  • Hashing or checksums for files and interfaces
  • Immutable or write-once backups as a defense against ransomware (recommended practice)

Person or entity authentication — §164.312(d)

You must verify that a person or entity seeking access to ePHI is the one claimed. The current rule does not name a method. Passwords alone can satisfy the text, but your risk analysis will almost certainly identify credential theft as a high risk for remote access, email and cloud administration.

  • Recommended practice: multi-factor authentication for remote access, email, cloud consoles, privileged accounts and EHR access from outside the network
  • Recommended practice: phishing-resistant methods (FIDO2/WebAuthn) for administrators
  • Mutual TLS or signed tokens for system-to-system authentication
  • Password management procedures under §164.308(a)(5)(ii)(D) should match the technical settings

Transmission security — §164.312(e)

The standard requires technical measures to guard against unauthorized access to ePHI transmitted over an electronic communications network. Both specifications — integrity controls and encryption — are addressable, but for transmission over the public internet it is hard to justify not encrypting.

  • TLS for web applications, patient portals, APIs and EHR interfaces; disable outdated protocol versions
  • Encrypted email, secure messaging or portal delivery for PHI sent outside the organization
  • VPN or zero-trust access for remote administration
  • Document your approach to unencrypted email when a patient requests it after being warned of the risks

Evidence auditors and assessors ask for

For a full assessment of these items against your environment, see HIPAA security consulting.

  • User account listings showing unique IDs and recent access reviews
  • Break-glass procedure and log of its use
  • Encryption status reports for endpoints and storage, or documented alternatives
  • Sample audit logs and records of log review
  • Authentication configuration (MFA policies, password settings)
  • TLS configuration and secure transmission procedures

Frequently asked questions

Is MFA required by HIPAA?

Not explicitly under the current rule. §164.312(d) requires authentication without naming a method. MFA is a recommended practice and is often the most reasonable way to address credential-theft risk identified in a risk analysis.

Can we skip encryption because it is addressable?

Only if your risk analysis supports that decision and you document why it is not reasonable and appropriate and what equivalent measure you use instead. For laptops, mobile devices and internet transmission, that justification is rarely credible.

How long should audit logs be kept?

The Security Rule does not set a log retention period. The six-year rule in §164.316 applies to required documentation such as policies and assessments. Set log retention based on your risk analysis, investigation needs and any state or contractual requirements.

Do technical safeguards apply to SaaS vendors?

Yes. Business associates must comply with the Security Rule directly, including §164.312. Customers are also responsible for how they configure and use the service.

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.

Talk through your HIPAA obligations with a consultant

Tell us about your organization, how you handle patient information, and what’s prompting the review. We’ll suggest a practical scope — and tell you if you don’t need us.