Are HIPAA Physical Safeguards Required? Required vs. Addressable Controls and How to Prove Compliance

Check out the new compliance progress tracker


Product Pricing Demo Video Free HIPAA Training
LATEST
video thumbnail
Admin Dashboard Walkthrough Jake guides you step-by-step through the process of achieving HIPAA compliance
Ready to get started? Book a demo with our team
Talk to an expert

Are HIPAA Physical Safeguards Required? Required vs. Addressable Controls and How to Prove Compliance

Kevin Henry

HIPAA

February 04, 2024

8 minutes read
Share this article
Are HIPAA Physical Safeguards Required? Required vs. Addressable Controls and How to Prove Compliance

Overview of HIPAA Physical Safeguards

HIPAA’s Security Rule requires you to protect electronic protected health information (ePHI) through administrative, physical, and technical safeguards. Physical safeguards focus on the real-world places and hardware where ePHI is created, received, maintained, or transmitted.

In practice, this means controlling facility access, guiding how workstations are used and secured, and governing device and media handling. These measures reduce risks from theft, unauthorized entry, tampering, and environmental hazards that could compromise availability, integrity, or confidentiality.

The physical safeguard standards you must address are: Facility Access Controls, Workstation Use, Workstation Security, and Device and Media Controls. Each standard contains implementation specifications that are either required or addressable, which determines how you must implement and document them for security rule compliance.

Differentiating Required and Addressable Controls

HIPAA labels implementation specifications as required or addressable. Required specifications must be implemented as written. Addressable specifications still must be considered; you must implement them if reasonable and appropriate, implement an equivalent alternative, or document why they are not reasonable and how you mitigate the risk.

Physical safeguard standards and implementation specifications

  • Facility Access Controls (all implementation specifications are addressable)
  • Workstation Use (standard without specific implementation specs; you must define and enforce appropriate policies and procedures)
  • Workstation Security (standard without specific implementation specs; you must implement physical protections for workstations that access ePHI)
  • Device and Media Controls
    • Disposal — required
    • Media Re-use — required
    • Accountability — addressable
    • Data Backup and Storage — addressable

Think in terms of outcomes: for required items, you must do exactly what HIPAA prescribes. For addressable items, you must make and record a reasoned decision based on risk analysis, cost, and your environment, and implement compensating controls if you choose alternatives.

Conducting Risk Analysis for ePHI

Risk analysis, an administrative safeguard, is the foundation for selecting physical controls. It identifies where ePHI resides, what could go wrong, and how likely and severe those events could be, guiding reasonable and appropriate protections.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Step-by-step approach

  • Define scope: list all locations, facilities, rooms, and work areas where ePHI exists, including data centers, clinics, storage rooms, and remote sites.
  • Inventory assets: servers, endpoints, removable media, network gear, badge systems, cameras, and any device that stores or transmits ePHI.
  • Map data flows: how ePHI moves between systems and sites, including offsite backups and vendor locations.
  • Identify threats and vulnerabilities: physical intrusion controls gaps (e.g., tailgating), theft, vandalism, power loss, fire, water damage, extreme temperatures, and supply-chain risks.
  • Assess likelihood and impact: rate risks using a consistent method; prioritize high-risk scenarios that threaten ePHI confidentiality, integrity, or availability.
  • Select controls: map risks to implementation specifications and choose measures that fit your environment and budget while achieving security rule compliance.
  • Document decisions: record the rationale for each control, including addressable alternatives and residual risks.
  • Plan and track remediation: create a timeline, owners, and acceptance criteria; reassess at least annually or upon significant changes.

Implementing Physical Security Measures

Facility access controls

  • Define security zones with badge readers or biometrics; enforce visitor escort and tailgating prevention.
  • Maintain a facility security plan that covers normal operations, after-hours access, and emergency procedures.
  • Keep maintenance records for locks, door hardware, alarms, and cameras; verify corrective actions are closed.
  • Use visitor logs and identity verification procedures at all entrances where ePHI can be accessed.

Workstation use and security

  • Publish workstation use rules: permitted functions, secure locations, screen positioning, and privacy screen requirements.
  • Physically secure devices with cable locks, locked offices, or cabinets; restrict public areas for ePHI access.
  • Apply automatic screen locks and enforce clean-desk practices to limit casual viewing and device theft.

Device and media controls

  • Disposal (required): render media unreadable before disposal (e.g., shredding, degaussing, cryptographic erasure when appropriate).
  • Media re-use (required): sanitize devices before reassignment to remove ePHI.
  • Accountability (addressable): track media custody with check-in/out logs, barcodes, or asset management tools.
  • Data Backup and Storage (addressable): ensure retrievable, tested backups before moving or disposing of devices.

Environmental hazard protections

  • Provide fire detection and suppression appropriate to equipment; add water-leak sensors where needed.
  • Stabilize power with UPS and generators; monitor temperature and humidity in server and telecom rooms.
  • Test alarms and environmental monitors; maintain calibration and maintenance documentation.

Remote and hybrid workforce considerations

  • Define approved home-office setups, including locked rooms, device storage, and prohibition on shared family use.
  • Require privacy screens for ePHI access in non-dedicated spaces; prohibit printing ePHI without secure storage and shredding.
  • Ship devices with tamper-evident seals; verify custody and return processes for offboarding.

Documenting Compliance Decisions

Documentation turns good intentions into provable compliance. For each implementation specification, maintain a decision record that shows how you met the requirement and why your approach is reasonable and appropriate for your risks and resources.

What to capture

  • Control description linked to the relevant implementation specification.
  • Risk analysis reference, selected option (implement, alternative, or not implement), and justification.
  • Procedures, responsible roles, dates of approval, and effective dates.
  • Evidence references: SOPs, diagrams, photos, purchase orders, test results, and training materials.
  • Exceptions and compensating controls with expiration and review dates.

Maintaining Security Records

HIPAA requires you to retain policies, procedures, and related documentation for at least six years from the date of creation or last effective date. Establish a retention schedule and centralized repository so you can retrieve records quickly.

Key records to retain

  • Risk analyses, risk registers, and remediation plans.
  • Facility security plans, visitor logs, badge records, and access reviews.
  • Maintenance records for doors, cameras, alarms, and environmental systems.
  • Asset inventories, chain-of-custody logs, and media tracking.
  • Certificates of destruction, sanitization logs, and backup/restore test results.
  • Workstation use and security policies, training rosters, and acknowledgments.
  • Vendor agreements and onsite assessments where business associates access facilities or ePHI.

Proving Compliance during Audits

Auditors look for alignment between what you say, what you do, and what you can prove. Prepare to demonstrate your controls through policies, procedures, and objective evidence that maps to the physical safeguard implementation specifications.

Audit-readiness evidence bundle

  • Security Rule mapping that ties each implementation specification to your controls and evidence.
  • Most recent risk analysis covering physical threats and environmental hazard protections.
  • Facility access artifacts: visitor logs, access approval workflows, and badge audits.
  • Workstation use and security procedures with spot-check results and photos of control placement.
  • Device/media artifacts: sanitization logs, certificates of destruction, and custody records.
  • Environmental records: UPS tests, generator run logs, sensor alerts, and maintenance tickets.
  • Training records for workforce members with physical access to ePHI locations.
  • Sampling package: a small, curated set of records (e.g., three months) that demonstrates consistent operation.

Conclusion

HIPAA physical safeguards are mandatory standards supported by a mix of required and addressable implementation specifications. Use risk analysis to select reasonable and appropriate controls, document every decision, maintain security records for six years, and compile evidence that shows your controls operate effectively. This approach strengthens security rule compliance and equips you to prove it during audits.

FAQs.

What are required physical safeguards under HIPAA?

All physical safeguard standards are mandatory: Facility Access Controls, Workstation Use, Workstation Security, and Device and Media Controls. Within Device and Media Controls, Disposal and Media Re-use are required implementation specifications. Other specifications may be addressable but must still be evaluated and documented to protect electronic protected health information.

How do addressable controls differ from required controls?

Required controls must be implemented as specified. Addressable controls require a documented decision: implement as written if reasonable and appropriate, implement an equivalent alternative that achieves the same purpose, or document why implementation is not reasonable and how risks are otherwise mitigated. The decision must be based on risk analysis and retained as part of your compliance record.

How can covered entities prove compliance with physical safeguard requirements?

Provide a clear map from implementation specifications to your policies, procedures, and evidence. Typical proof includes risk analyses, facility security plans, visitor and maintenance logs, badge audits, workstation security checks, media sanitization and destruction records, environmental system tests, training rosters, and a sampling set that shows consistent, ongoing operation.

What steps are involved in conducting a HIPAA risk analysis for physical safeguards?

Define scope and ePHI locations; inventory facilities, devices, and media; map data flows; identify threats such as physical intrusion and environmental hazards; assess likelihood and impact; prioritize risks; select controls aligned to HIPAA implementation specifications; document decisions and compensating controls; and track remediation, with periodic reassessment and updates.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Related Articles