Home NIST Guidelines PE-2(3)
PE-2(3) Physical Protection

Restrict Unescorted Access

High Risk Moderate Medium Cost

PE-2(3) (Restrict Unescorted Access) enhances base PE-2 within the NIST Physical and Environmental Protection family. Base PE-2 sets the foundational expectation; this enhancement adds specificity: Restrict unescorted access to the facility where the system resides to personnel with [organization-defined]. Individuals without required security clearances, access approvals, or need to know are escorted by individuals with appropriate physical access authorizations to ensure . Covered entities and business associates apply it to data centers, clinic rooms, media handling areas, and environmental safeguards protecting systems that store ePHI.

Control Objective

Implement Restrict Unescorted Access so organization-defined physical and environmental protection safeguards operate consistently on systems and networks that handle ePHI, with measurable evidence for HIPAA and NIST assessments.

Implementation Guidance

  1. Map PE-2(3) to systems in scope (EHR, imaging, lab, pharmacy, billing, identity, backups, and BA connections).\n2. Translate “Restrict Unescorted Access” into technical settings, procedures, or architecture patterns owned by named roles.\n3. Prefer enforceable controls (config, automation, mediation) over awareness-only measures where feasible.\n4. Integrate with change, incident, and downtime processes so clinical operations are not surprised.\n5. Log and retain evidence of operation (tickets, configs, test results) aligned to audit needs.\n6. Include vendors/BAs in contracts and connection standards when they touch the control surface.\n7. Test after major EHR, network, or cloud changes — upgrades often reset protections.\n8. Review exceptions at least quarterly; expire “temporary” holes that expose ePHI paths.

Real-World Use Cases

How this control shows up in healthcare and HIPAA-covered environments.

Real-world scenario

Badge access by clinical role (PE-2(3))\nOnly authorized nursing and biomed roles receive unescorted access to the EHR computer room. Evidence labeled for PE-2(3).\n\n### Two-form visitor ID (PE-2(3))\nVendors entering the data center present two forms of ID logged against the work order. Evidence labeled for PE-2(3).\n\n### Escort for contractors (PE-2(3))\nCable vendors in clinic IDFs are escorted; unescorted exceptions require PE-2 approval. Evidence labeled for PE-2(3).

Best Practices

  • Name an owner for PE-2(3) in the SSP control matrix.\n- Favor system enforcement on ePHI paths over informal email approval.\n- Measure coverage: percent of in-scope clinical systems where the enhancement operates.\n- Review exceptions quarterly with security and clinical informatics.\n- Feed relevant events to SIEM with a named use case.\n- Keep a one-page evidence pack (config + sample log + last test) ready for assessors.

Common Gaps & Violations

  • Policy cites PE-2(3) but production EHR/network paths show no enforcement of restrict unescorted access.\n- Permanent exceptions with no expiry for vendors or “special” clinics.\n- Control implemented only on corporate IT — clinical devices and interfaces omitted.\n- No logs or test records; reliance on tribal knowledge.\n- Major upgrade silently disabled the enhancement.

Required Documentation

  • Procedure/standard for Restrict Unescorted Access (PE-2(3))\n- Architecture or configuration baselines showing enforcement points\n- Exception register with owners and expiry\n- Sample logs, alerts, or test results\n- Training or runbook references for clinical/IT operators

How to Test & Validate

  1. Attempt a prohibited or out-of-policy action related to restrict unescorted access; confirm block, alert, or required workflow.\n2. Complete an authorized clinical/IT path; confirm success and logging.\n3. Sample open exceptions for approval and expiry.\n4. Verify at least one EHR-adjacent and one BA/vendor path are in scope.\n5. Confirm evidence retained for the last 90 days (or per policy).

Audit Considerations

Assessors look for operating evidence of Restrict Unescorted Access on systems touching ePHI — configs, logs, restore/DR artifacts, or failed-test results — not only a policy paragraph referencing PE-2(3).

HIPAA Mapping

How this NIST control supports HIPAA Security Rule expectations.

  • 164.310(a)(1) Facility Access Controls — limit physical access to facilities with ePHI systems.\n- 164.310(b) Workstation Use — policies for workstations that access ePHI.\n- 164.310(c) Workstation Security — physical safeguards for workstations that access ePHI.\n- 164.310(d)(1) Device and Media Controls — control receipt and removal of hardware/media with ePHI.

Compliance Tips

  • List PE-2(3) explicitly in the system security plan with system inventory references.\n- Prioritize emergency department, inpatient EHR, and remote access paths first.\n- Bundle evidence with related HIPAA evaluation, integrity, or workforce-security narratives where they overlap.

References & Resources

  • NIST SP 800-53 Rev. 5 — PE-2(3)\n- Related controls: PE-2, PS-2, PS-6

Related Guidelines

Related controls that commonly accompany PE-2(3).

PE-2 Medium

Physical Access Authorizations

PE-2 requires developing, approving, and maintaining a list of individuals with authorized access to the facility where the system resides…
PS-2 High

Position Risk Designation

PS-2 requires assigning a risk designation to all organizational positions, establishing screening criteria for individuals filling those…
PS-6 Medium

Access Agreements

PS-6 requires developing and documenting access agreements for organizational systems, reviewing/updating them periodically, and ensuring…

Need Help Implementing PE-2(3)?

Our auditors map NIST SP 800-53 controls to your HIPAA Security Rule program — policies, technical evidence, and audit readiness.

Contact Our Experts View All Guidelines