Join our Newsletter — 33% off our NHI Course
Home› Glossary› Identity Beyond IAM› Coexistence
Identity Beyond IAM

Coexistence

← Back to Glossary
By NHI Mgmt Group Updated November 1, 2026 Domain: Identity Beyond IAM

Coexistence is the operating state where source and target directory environments remain live during a phased migration. Users, services, and dependencies may span both sides for weeks or months. This makes sequencing, visibility, and rollback planning essential, because failures affect only the active wave if the program is designed correctly.

What Coexistence Means in a Directory Migration

Coexistence is not a single product feature, but a transitional operating state. The source and target directories both remain live so authentication, lookups, account references, and application dependencies can continue while migration waves move through the estate. The value of this model is continuity, but it also means two systems must be managed as one temporary security boundary.

In practice, coexistence is where migration planning becomes a control problem. Teams need to know which users, groups, service accounts, and applications still depend on the old directory, which ones have moved, and which identities must work across both environments until cutover is complete.

Why Coexistence Exists in Staged Migrations

Coexistence reduces migration risk by avoiding a hard cutover. Instead of forcing every identity, policy, and application dependency to move at once, organisations can migrate in controlled waves and keep business services running while the remaining population is still anchored to the source directory.

This staged model is especially important when applications are tightly coupled to directory semantics such as group membership, nested delegation, legacy LDAP lookups, or directory-bound service identities. If those dependencies are not mapped in advance, coexistence can become a long-lived exception state rather than a disciplined bridge to final migration.

Done well, coexistence gives the programme room to validate synchronisation, entitlement mapping, and application compatibility before the final switchover. Done poorly, it creates ambiguity about which directory is authoritative for a given object at a given time.

Key Security and Operational Challenges

The main challenge is that coexistence expands the number of moving parts during the highest-risk phase of the migration. Errors in replication, attribute mapping, identity lookup, or dependency sequencing can break access only for the wave that is moving, which is useful for containment but still disruptive if the programme lacks clear rollback rules.

Coexistence also complicates visibility. When the same user, service, or application may be represented in both environments, administrators need strong inventory discipline to avoid drift, duplication, stale entitlements, or hidden trust paths between the two directories.

Because phased migration often involves temporary exceptions, the programme should treat coexistence as an active control state rather than a passive bridge. The question is not only whether both directories are running, but whether every dependent system still has a documented, tested, and recoverable path across them.

How Coexistence Ends

Coexistence should have a defined exit condition. The end state is reached when the remaining dependencies on the source directory have been removed, synchronised data is no longer needed, and the target directory can serve as the single source of truth for the migrated population.

That final phase usually depends on proving that the last legacy applications, scripts, integrations, and administrative workflows no longer require the old environment. Without that evidence, coexistence can linger indefinitely and preserve the very complexity the migration was meant to eliminate.

For a phased migration programme, the real measure of success is not simply that both directories can operate together, but that the organisation can retire the old one without losing access, control, or auditability.

Risk and Threat Considerations

Coexistence increases exposure when the two directories are not governed with the same discipline. The most common failure pattern is drift: stale identities, duplicate accounts, mismatched group membership, or inconsistent policy enforcement that leaves one environment more permissive than the other.

Failure mechanism: Attackers or internal mistakes can exploit the window where one directory still accepts access while the other has already been updated, creating confusion about authority, account state, or privilege boundaries. Mis-sequenced cutovers and incomplete rollback planning can also extend the blast radius of a failed wave.

Impact: The result can be unauthorised access, broken authentication for dependent applications, orphaned service relationships, or prolonged exposure from accounts and trust paths that were meant to be temporary.

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 NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5CM-3 — Configuration Change ControlDirectory coexistence depends on controlled sequencing and approved migration changes.
AC-2 — Account ManagementCoexistence centers on keeping user and service identities consistent across both directories.
AC-6 — Least PrivilegeTemporary dual-directory operation can widen access unless privileges are tightly bounded.
Recommendation — Use CM-3 to control migration changes and approve directory-state transitions. Use AC-2 to govern account lifecycle and prevent duplicate or stale directory identities. Use AC-6 to restrict access during coexistence to only the permissions required for migration.
NIST CSF 2.0ID.AM-01 — Physical Devices and Systems InventoryCoexistence requires accurate inventory of systems and dependencies spanning source and target directories.
Recommendation — Maintain an accurate inventory of all systems that still depend on either directory.

Practitioner Guidance

Why practitioners should care: Coexistence succeeds only when ownership is explicit. Every wave should have a clear authority model for which directory is primary, how identity changes are synchronised, and how rollback works if a dependency fails mid-migration.

What to watch for: Pay close attention to duplicate identities, stale entitlements, applications that still query the source directory, and manual exception handling that is no longer time-bound. Those are the signals that coexistence is turning into permanent dual operation.

Practitioner takeaway: Treat coexistence as a temporary security and operational state with an exit plan, not as an open-ended migration convenience.

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.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 1, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org