They should connect lifecycle events from the authoritative HR source to badge issuance, badge modification, and badge revocation. Physical access must be governed with the same joiner, mover, and leaver logic used for applications so the person’s employment status and facility authority never diverge.
How to make physical access follow the same lifecycle as logical access
Extend joiner-mover-leaver by treating badge access as another governed entitlement, not as a separate facilities exception process. The authoritative HR record should trigger badge issuance for joiners, scope changes for movers, and immediate badge revocation for leavers, with the same ownership, approval, and audit trail discipline used for application access.
The practical shift is to align the physical access workflow to the same authoritative source, timing, and exception handling you already expect in identity governance. That usually means the HR event is the system of record, facilities or security operations enforce the change, and the access decision is recorded in a way that can be reviewed later.
Where organisations already have an identity governance layer, the cleanest approach is to apply the joiner-mover-leaver model consistently across doors, sites, and secure rooms so the person’s employment status and physical authority never drift apart.
What changes when physical access becomes part of identity governance
Physical access is not just a facilities control, because it governs who can enter spaces where sensitive systems, paperwork, hardware, or people are exposed. When the lifecycle is extended properly, a change in department, location, manager, contractor status, or termination date should automatically drive badge changes just as it would drive a role change in an application.
This matters most for movers, because a transfer often leaves the old access in place unless someone explicitly removes it. That creates privilege creep in the real world: a person may no longer need access to a floor, lab, data centre, or branch, but their badge still works there unless the move event is translated into a physical entitlement review.
A useful operating model is to treat badge issuance, door-group changes, temporary access, and revocation as governed entitlements that are linked to role, location, or sponsor rules. Identity governance for boards becomes relevant here because it shows how leaver gaps and access recertification failures turn into measurable control weaknesses, not one-off administrative misses.
Design the handoff between HR, facilities, and security operations
The strongest design is one where HR creates the lifecycle event, identity governance determines the entitlement change, and the physical access system enforces it without manual interpretation. That keeps the decision consistent across badges, readers, and sites, and it reduces the chance that a local site manager quietly preserves access after the business no longer needs it.
For multi-site organisations, the handoff should distinguish between global employment status and local physical authority. A mover may need access to one building but lose access to another; a leaver should usually lose all standard access immediately, with any retained access handled as an explicit exception and time bound approval.
That is why a physical access control system needs identity integration, because the control only works if it can consume lifecycle events and enforce them across doors, readers, and badge credentials rather than relying on manual desk processes.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | PE-3 — Physical Access Control | Physical badge lifecycle is governed through controlled facility entry |
| AC-2 — Account Management | Lifecycle-driven access changes mirror joiner-mover-leaver governance | |
| IA-3 — Device Identification and Authentication | Badge systems rely on authenticated credentials or devices at access points | |
| Recommendation — Map badge issuance and revocation to PE-3 and enforce lifecycle-based facility access changes. Use AC-2 to drive timely provisioning, modification, and removal of physical access rights. Apply IA-3 to ensure physical access credentials are uniquely bound to an authorised holder. | ||
| CIS Controls v8 | CIS-5 — Account Management | Badge access should be inventoried, modified, and revoked with the same lifecycle rigor as accounts |
| Recommendation — Extend account lifecycle controls to physical access grants and revocation. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Physical access permissions need controlled assignment and removal as part of access control |
| Recommendation — Include physical access entitlements within the organisation’s access control rules. | ||
Practitioner Guidance
What to verify: Confirm that every physical access grant has an owner, a source event, and a revocation path. If a site still issues or extends badges outside the HR driven workflow, treat that as a lifecycle control gap, not as a facilities preference.
Implementation sequence: Start with joiners and leavers at your highest risk sites, then extend to movers, temporary access, and contractor populations. Tie badge changes to the same joiner-mover-leaver rules you already use for application access, then test whether revocation actually lands at the reader level and not just in a ticket queue.
Practitioner takeaway: Physical access becomes governable when it is managed as an entitlement with lifecycle ownership, not as a standalone badge administration task.
Related resources from NHI Mgmt Group
- How should organisations govern physical badge access across joiner-mover-leaver events?
- What breaks when physical access is not tied to joiner-mover-leaver events?
- How can organisations use access profiles in joiner-mover-leaver workflows?
- How should teams govern Jira access through joiner-mover-leaver workflows?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 19, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org