Start by mapping badges, facility rights, contractor credentials, and application entitlements to a single identity record. Then apply the same joiner-mover-leaver, certification, and revocation processes across both domains so access can be approved, reviewed, and removed consistently rather than through separate physical and digital evidence chains.
One identity model for buildings and systems
The practical goal is not to merge every control, it is to make one authoritative identity record govern both physical and digital access decisions. That lets you treat a badge, a door right, a contractor status, an application entitlement, and a revoked account as different expressions of the same access relationship. The benefit is consistency: one identity, one owner, one lifecycle, one evidence trail.
That model works best when the identity record becomes the source of truth for approval, review, and removal, rather than a downstream reporting layer. If a person changes role, site, vendor status, or employment status, the change should flow through both PACS and IAM controls so access does not drift into separate approval chains.
For teams building the operating model, the important design choice is whether physical and digital access are governed by the same policy decision and review process. If the answer is yes, the identity record needs enough context to drive both domains, including affiliation, location, sponsor, and access scope. Identity Security Programme Guide is useful here because it frames how a single governance model can span human, non-human, and AI agent identities without fragmenting ownership.
Why joiner-mover-leaver and certification must span both domains
The joiner-mover-leaver process only works when the same event changes both the badge and the account. A joiner should receive the minimum physical and digital access needed for day one, a mover should trigger a fresh entitlement decision rather than a partial update, and a leaver should lose all access paths together. Otherwise, one domain can be closed while the other remains open, which is how orphaned access persists.
Certification should also be unified. If the business asks managers or sponsors to attest to access, they should be attesting to the whole access footprint, not just one half of it. That matters because a badge that still opens a site after a contractor role ends is the same governance failure as an application entitlement that was never removed.
When the operating model already separates physical and digital tooling, Access Governance vs Access Management helps clarify the split between deciding access and enforcing it, which is exactly the distinction teams need when they are trying to unify review and revocation across both channels. IAM and IGA Basics is also directly relevant because joiner-mover-leaver and access review only become reliable when the governance layer treats entitlements as a lifecycle problem, not a one-time provisioning task.
For organisations that want a physical-security lens on the same problem, Physical Security Guide for Security Teams is a practical companion because it covers badge security, access control, and the convergence of physical and cyber security around one operating model.
What a converged identity model changes in day-to-day operations
The biggest change is that evidence has to be consistent. Facilities teams should not approve access from one record while IAM teams approve system access from another, because that creates mismatched ownership and weakens revocation. A converged model also makes exception handling clearer: temporary access, contractor access, and emergency access should all be time bound, reviewable, and attributable to the same identity.
It also changes how teams investigate anomalies. If someone has a valid badge but no valid employment or contractor status, or an active application account with no current site access need, the mismatch becomes a control signal rather than a normal exception. That is why the identity model should not stop at login credentials. It should include the people, places, and privileges that define whether access is still justified.
For practitioners focused on the physical side of the control loop, D3-PAM Physical Access Mediation is a useful reference because it translates physical access approval and revocation into an enforceable mediation model, which aligns well with a single identity record.
Risk and Threat Considerations
Converging physical and digital access reduces fragmentation, but it also concentrates failure. If the identity record is wrong, stale, or incompletely deprovisioned, the error can propagate into both the building and the application stack. That increases the blast radius of a missed mover event, an unrevoked contractor, or an improperly sponsored badge.
Failure mechanism: Separate approval chains let one access path survive after the other is removed, so a person can retain either site entry or digital access even when the business relationship has ended. That creates persistence through governance gaps rather than through a technical exploit.
Impact: The result can be unauthorized site entry, unauthorized system access, weak auditability, and delayed detection of insider misuse or orphaned access. The longer the gap persists, the harder it becomes to prove whether access was still justified at the time it was used.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CSA Cloud Controls Matrix, 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 |
|---|---|---|
| CSA Cloud Controls Matrix | IAM — Identity & Access Management | Unified physical and digital access depends on centralized identity governance and lifecycle control. |
| Recommendation — Centralize identity lifecycle decisions so badge and system access change together. | ||
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | Joiner-mover-leaver and revocation across access paths are account lifecycle controls. |
| IA-5 — Authenticator Management | Badges, credentials, and tokens are all access-bearing material that needs lifecycle control. | |
| Recommendation — Link account and badge lifecycle events to approved provisioning and timely revocation. Manage all authenticators with issuance, rotation, and revocation rules. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | A single model for site and system access aligns with access control policy governance. |
| Recommendation — Define one access policy that covers both physical and digital access decisions. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | Converged access governance needs consistent provisioning, review, and removal of access. |
| Recommendation — Standardize access provisioning and removal across physical and digital systems. | ||
Practitioner Guidance
What to verify: Confirm that one authoritative identity record drives both PACS and IAM decisions, and that leaver actions revoke badges, accounts, and temporary access within a defined service window. If the two systems can be reconciled only manually, the model is not yet converged enough to trust.
Decision rule: If a person’s business relationship changes, process the change once and propagate it to every access mechanism the role can use. Do not allow “physical only” or “digital only” exceptions unless there is a documented business case, an expiry date, and a named owner.
Practitioner takeaway: The safest converged model is not the one with the most controls, it is the one where every access path is governed by the same identity state and the same revocation trigger.
Related resources from NHI Mgmt Group
- How should organisations govern identity when digital access and physical access are split across different systems?
- How should security teams govern identity and access in a decentralized operating model?
- How should security teams govern access when they test a new frontier model through a shared AI gateway?
- Why does combining digital identity, payments, and service access in one app increase the need for strong security controls?
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