Skip to main content

Identity resilience glossary

Identity resilience glossary

Clear explanations of the identity, backup and recovery terms used in resilience planning.

A

Active Directory (AD DS)
Active Directory Domain Services (AD DS) is Microsoft's directory service for managing users, computers, and other network resources in domains. It stores identity information and supports authentication and access control. Organizations use AD DS to manage access to domain resources and apply administrative policies across Windows environments, including through Group Policy.
Active Directory forest
An Active Directory forest is the top-level structure in Active Directory Domain Services, containing one or more domains. Its domains share a schema, configuration information, and a global catalog, with automatic two-way, transitive trusts between them. A forest is also a security boundary, which makes it an important unit for identity administration and recovery planning.
Active Directory forest recovery
Active Directory forest recovery is the coordinated process of restoring a functioning AD DS forest after a forest-wide failure. Microsoft's documented approach restores at least one writable domain controller in each domain from trusted backups. It is broader than recovering individual objects and requires decisions about the recovery state, isolation, and the directory infrastructure needed to resume service.
Auth0
Auth0 is an identity platform from Okta that developers use to add authentication and authorization to applications and APIs. An Auth0 tenant is the environment where teams manage application registrations, connections, user profiles, and configuration. Auth0 focuses on developers and customer identity, but an Auth0 tenant is not the same environment as an Okta org.

C

Configuration drift
Configuration drift is a difference between a system's actual configuration and its intended or approved baseline. In identity environments, this can affect access policies, group assignments, application settings, or other configurations that shape access. The baseline might be an approved configuration record or a definition managed through code. HashiCorp's drift guidance describes the same distinction between actual infrastructure and intended configuration.
Customer identity and access management (CIAM)
Customer identity and access management (CIAM) is the set of practices and technologies used to register customers, authenticate them, and control their access to digital services. It includes the identity lifecycle behind customer-facing websites, applications, and portals. CIAM is a branch of identity management focused on customer access, not the name of a single product.

D

Dependency-aware recovery
Dependency-aware recovery is a descriptive term for recovery that considers the relationships needed for restored objects to work as intended. It includes identifying dependencies, accounting for recovery order where necessary, and validating the resulting connections. The term does not by itself establish a universal standard, certification or fixed set of capabilities.
Domain controller
A domain controller (DC) is a server that runs Active Directory Domain Services and hosts directory data for a domain. It provides authentication and supplies information used in access decisions. Multiple domain controllers can hold replicated directory data for the same domain, so directory operation is not necessarily tied to one server.

G

Granular recovery
Granular recovery restores a selected part of an environment instead of rolling back the whole environment. The recovery unit might be an individual object, a group of objects, or a particular attribute or relationship where the recovery method supports that level of selection. Microsoft's Entra recovery documentation, for example, distinguishes recovery of all supported objects from selection by object type or object ID. Microsoft recovery scope
Group Policy Object (GPO)
A Group Policy Object (GPO) is a collection of policy settings used to configure Windows users and computers. In Active Directory, administrators link GPOs to sites, domains, or organizational units to define where they can apply. A domain-based GPO includes data in both the directory and the SYSVOL file share on domain controllers.

H

Hybrid identity
Hybrid identity is an approach that connects on-premises identity systems with cloud identity services so people can use related identities across both environments. It commonly involves provisioning, synchronization, or federation, with different responsibilities for account data and authentication. Active Directory connected to Microsoft Entra ID is one example; the concept also applies to integrations with providers such as Okta.

I

Identity backup
Identity backup is the practice of preserving copies of identity data and configuration so teams have a previous state available for investigation or recovery. Depending on the platform and backup method, that scope can include users, groups, application settings, access policies, and relationships between objects. Coverage must be stated explicitly; the word “backup” does not mean every identity object, attribute, or secret is included.
Identity failover
Identity failover is the transfer of authentication service to a prepared alternative when the primary identity service cannot support the required sign-ins. It aims to keep selected applications accessible during a disruption. It requires compatible application trust, identity data, and access controls; having a second identity tenant or a backup alone does not provide working failover.
Identity provider (IdP)
An identity provider (IdP) is a service that authenticates a user and provides an application with evidence of that authentication. In a federated sign-in, the application relies on an assertion or token from the IdP instead of verifying the user's authenticator itself. The application is called a relying party. NIST's federation guidance defines these roles and their trust relationship.
Identity resilience
Identity resilience is an organization's ability to prepare for identity-related disruption, limit its impact, and restore trusted access and identity operations. It applies to the systems, people, and procedures that support authentication and access. NIST's cyber-resilient systems guidance provides the broader foundation.

K

Known-good state
A known-good state is a previously recorded configuration that a team has checked against its security and operational requirements and considers suitable for recovery. In identity systems, this can include account settings, group memberships, access policies, and application relationships. A backup timestamp alone does not establish that the state is correct or free of unauthorized changes.

M

Microsoft Entra Conditional Access
Microsoft Entra Conditional Access evaluates identity and access signals against policies to determine whether access should be blocked or subject to requirements. Policies can consider the user, application, device, location, and risk signals, depending on configuration and licensing. They can require controls such as multifactor authentication or a compliant device before access is granted.
Microsoft Entra External ID
Microsoft Entra External ID is Microsoft's offering for managing access by people outside an organization, including partners and customers. It includes B2B collaboration in workforce tenants and customer identity and access management, or CIAM, in separate external tenants. External ID is therefore broader than CIAM alone, and Microsoft does not describe it as a simple rename of Azure AD B2C.
Microsoft Entra ID
Microsoft Entra ID is Microsoft's cloud identity and access management service, formerly called Azure Active Directory. Organizations use it to authenticate identities and manage access to applications and resources. Its identity objects and settings include users, groups, application configurations, and access policies; it is a different service from Windows Server Active Directory.

O

Okta
Okta is a cloud identity platform used to manage authentication and access to applications, particularly for workforce users. Its administrative environment, called an Okta organization or org, contains users, groups, application integrations, policies, and related configuration. Those settings help determine who can sign in and under which conditions.

P

Point-in-time recovery
Point-in-time recovery returns data or configuration to a selected earlier state. The available times depend on how the system captures and retains recovery data. Some systems use stored snapshots; others reconstruct a state from a backup and recorded changes. PostgreSQL, for example, can replay archived transaction logs to a chosen recovery target. PostgreSQL point-in-time recovery

R

Recovery point objective (RPO)
A recovery point objective, or RPO, is the maximum acceptable data loss measured in time. It defines how far back the organization can tolerate returning when recovering after a disruption. For identity configuration, the potential loss includes changes made after the last usable recovery point. NIST RPO definition, AWS recovery objectives
Recovery time objective (RTO)
A recovery time objective, or RTO, is the target maximum time for restoring a defined service after a disruption. It expresses how much downtime the organization is prepared to tolerate for that service. Business needs set the objective; the recovery approach must then be tested against it. NIST RTO definition, Google Cloud disaster recovery planning

T

Tier 0 identity infrastructure
Tier 0 identity infrastructure refers to systems, administrative identities, and dependencies that can control the identity foundation on which other access decisions rely. In Microsoft's Active Directory Domain Services tier model, examples include domain controllers and the accounts and supporting systems able to control them. The classification follows effective control, not simply an asset's name or business importance. Microsoft's AD DS tier guidance.