Facility Access Controls¶
Last 1 Enterprises LLC / LastVet Safeguard category: Physical HIPAA Security Rule citation: 45 CFR §164.310(a) Status: Scaffold (Bucket 1c). Not approved for enforcement until Ryan review.
Document metadata¶
| Field | Value |
|---|---|
| Policy owner | TODO (Ryan) |
| Version | 0.1-scaffold |
| Effective date | TODO (Ryan) |
| Review cadence | Annual (TODO: Ryan confirm) |
| Approver | TODO (Ryan) |
| Last reviewed | 2026-08-26 (scaffold only) |
1. Purpose¶
Limit physical access to facilities and systems that house ePHI.
2. Scope¶
On-prem R940, NAS, network gear, and any colocation facility if used.
3. Policy statements¶
- Contingency operations, facility security plan, access control and validation, maintenance records shall be documented.
- Physical access to R940 and NAS shall be restricted to authorized personnel.
- TODO (Ryan): Document facility security plan for current operator site and Feb 2027 colo move [Depends on 1a §4 TODO 8].
4. Roles and responsibilities¶
| Role | Responsibility |
|---|---|
| Security Officer (Ryan) | TODO (Ryan): assign formal Security Rule responsible person per §164.308(a)(2) |
| Workforce members | TODO (Ryan): acknowledge policy when hired / annually |
| Contractors / BAs | TODO (Ryan): flow-down via BAA and agreements |
5. LastVet-specific context (from existing docs)¶
R940 on operator-controlled LAN (192.168.1.0/24). iDRAC on dedicated port. Muster tracks colo BAA question and hardware relocation.
6. Related documents¶
../HIPAA_ARCHITECTURE.md— asset inventory and data flows (Bucket 1a)../HIPAA_RISK_ANALYSIS.md— risk register (Bucket 1b)../../security/POSTURE.md— canonical security posture../../architecture/R940_PLATFORM_ARCHITECTURE.md
7. Ryan TODO (substantive content deferred)¶
- Facility access log or badge policy if colo.
- Visitor escort procedures.
- iDRAC physical port access controls.