Free HIPAA policy template · v1.0 · Applies to covered entities & business associates · Companion: Procedures →
Adopting this document means committing to these HIPAA controls, the 45 CFR §164 requirements it helps satisfy, by area:
Common threats (NIST SP 800-30 classes) that the controls behind this document defend against:
Exploits: Endpoint not encrypted · 164.312(a)(2)(iv) Encryption; 164.310(d) Device Controls
Exploits: No disposal/sanitization procedure · 164.310(d)(2)(i) Disposal
Exploits: No contingency operations · 164.310(a)(2)(i) Contingency Ops
Template. Replace every
[bracketed]item with your organization's specifics. A name in[Title Case]is your organization, a role, or a person; a phrase in[lower case]is a category of tool. Substitute the actual product you use (e.g.,[cloud infrastructure provider]→ your chosen vendor). Have this reviewed by counsel or your compliance advisor before adoption.
This Policy establishes how [Organization] limits physical access to the facilities, workspaces, and systems that house or are used to access electronic protected health information (ePHI), so that only authorized persons can reach those resources and the equipment and media holding ePHI are protected from tampering, theft, and improper disposal. It satisfies the physical-safeguard requirements of the HIPAA Security Rule at 45 CFR §§ 164.310(a)(1), 164.310(a)(2)(i)–(iv), and 164.310(d)(2)(i).
[Organization] is [remote-first / hybrid / office-based]. Production systems and the primary stores of ePHI are hosted by a contracted [cloud infrastructure provider] and a under a Business Associate Agreement (BAA); the physical security of those datacenters is the provider's responsibility and is inherited through the BAA (see §2). This Policy therefore governs two environments: any physical office or facility under 's control where ePHI systems, devices, or media are present, and the remote and home-office workspaces from which workforce members access ePHI.
See where your organization stands on the controls this template cites.
Join Us[cloud productivity & storage suite][Organization]This Policy applies to all workforce members (employees, contractors, interns, and volunteers), to visitors and vendors who enter a controlled space, and to every location and physical asset that creates, receives, maintains, or transmits ePHI, including controlled offices, equipment rooms, approved home work areas, workstations and laptops, and any removable or paper media. Workforce members must acknowledge this Policy in writing before access is granted and at least annually thereafter.
[Organization] limits physical access to facilities and to the systems and media that house ePHI to authorized workforce members, while ensuring that properly authorized access is allowed. For any controlled office or equipment room, entry is restricted by a physical control (locked door, badge reader, or keyed lock), access is granted by role on a least-privilege basis, and the set of people holding keys or badges is documented and kept current. Where production systems and ePHI are cloud-hosted, the corresponding datacenter facility controls are provided by the [cloud infrastructure provider] and inherited under the BAA (§2); [Organization]'s own facility controls focus on the offices, devices, and media within its custody. Workforce members must report any suspected unauthorized physical access promptly per the Security Incident Response Policy. (164.310(a)(1))
Production services and the primary ePHI stores run on a contracted [cloud infrastructure provider] and [cloud productivity & storage suite] operating under a BAA. Under the shared-responsibility model:
[Organization] responsibilities: configure and administer its tenants securely, restrict and review access, and maintain physical safeguards for the offices, workstations, and media within its control. [Organization] does not operate production datacenters of its own.The provider's current attestations are obtained and reviewed under the Vendor & Third-Party Management Policy, which is the control of record for confirming that these inherited physical safeguards remain in force.
[Organization] maintains a facility security plan that protects its facilities and the equipment therein from unauthorized physical access, tampering, and theft. The plan identifies each location where ePHI systems, devices, or media may be present (controlled offices and approved home work areas alike) and the safeguards applied to each:
The plan is reviewed at least annually and upon any material change to the ePHI environment. (164.310(a)(2)(ii))
[Organization] controls and validates a person's physical access to facilities and workspaces based on their role and, for software/program testing and revision, their function:
[endpoint protection], host firewall, automatic updates, and screen-lock).(164.310(a)(2)(iii))
[Organization] establishes procedures that allow facility access in support of restoring lost data under the disaster-recovery and emergency-mode plans during an emergency. Because production systems and backups are cloud-hosted, emergency restoration depends on continued access to the [cloud infrastructure provider] rather than on entry to a company datacenter; [Organization] therefore maintains multiple administrators with MFA and documented break-glass access so that recovery can proceed even if a key individual is unavailable. Where a controlled office holds equipment or media needed for recovery, designated personnel are pre-authorized to enter during an emergency, and such access is logged and reviewed afterward. This control operates together with the Contingency Planning Policy (data backup, disaster recovery, and emergency-mode operations). (164.310(a)(2)(i))
[Organization] documents repairs and modifications to the physical components of a facility and to equipment that are related to security: for example, changes to locks, doors, badge readers, alarms, or the hardware of devices authorized to access ePHI. Each record captures the date, the component or device, the nature of the work, who performed it, and, for a device that has held ePHI, whether ePHI was present and how it was protected while the device was out of [Organization]'s control. Routine facility maintenance with no bearing on security need not be logged. Maintenance records are retained for six years. The operational steps live in the companion Physical & Facility Security Procedures. (164.310(a)(2)(iv))
[Organization] addresses the final disposition of ePHI and of the hardware or electronic media on which it is stored so that ePHI cannot be readily recovered or reconstructed:
[cloud infrastructure provider] / [cloud productivity & storage suite]; the provider performs media-level sanitization at end of life under the BAA (§2).Disposal aligns with the six-year HIPAA retention requirement: records are destroyed only after their retention period has elapsed. Media re-use sanitization and broader device/media handling are governed by the Device & Workstation Security Policy. (164.310(d)(2)(i))
[Security Official]: owns this Policy; approves the facility security plan, physical-access authorizations, and exceptions; ensures maintenance and disposal records are kept; reviews emergency facility access.[Security Official] if none): administers keys, badges, and visitor control for controlled spaces and records maintenance affecting security.[Privacy Officer]: advises on safeguards for any ePHI handled in paper form.Physical & Facility Security Procedures · Access Control Policy · Device & Workstation Security Policy · Contingency Planning Policy · Vendor & Third-Party Management Policy · Security Incident Response Policy.
| Citation | Requirement | Addressed in |
|---|---|---|
| 164.310(a)(1) | Facility Access Controls | §1 |
| 164.310(a)(2)(ii) | Facility Security Plan | §3 |
| 164.310(a)(2)(iii) | Access Control and Validation Procedures | §4 |
| 164.310(a)(2)(i) | Contingency Operations | §5 |
| 164.310(a)(2)(iv) | Maintenance Records | §6 |
| 164.310(d)(2)(i) | Disposal | §7 |
Reviewed at least annually by the [Security Official] and after any significant change to the ePHI environment or to [Organization]'s facilities. v1.0.