Workflow

A workflow is a one time access process used for a specific user or exception case. It is typically used for unusual provisioning or deprovisioning needs that do not fit a standard role template. In identity operations, workflows handle special cases while preserving an auditable record of each step.

Expanded Definition

In identity operations, a workflow is a controlled one time process used to handle a specific access request, exception, or lifecycle action that does not fit a standard role template. It is usually temporary, auditable, and approval driven, which distinguishes it from routine provisioning or a standing access policy.

Definitions vary across vendors, but in NHI management the practical meaning is consistent: workflows are the exception path for special cases such as emergency access, unusual deprovisioning, or bespoke environment setup. They matter because they preserve evidence of who approved what, when, and why, which supports governance and incident review. For broader identity governance context, see the NIST Cybersecurity Framework 2.0 and the NHI lifecycle guidance in Ultimate Guide to NHIs.

The most common misapplication is treating a workflow like a reusable role or permanent entitlement, which occurs when teams approve the same exception repeatedly instead of redesigning the underlying access model.

Examples and Use Cases

Implementing workflows rigorously often introduces latency and review overhead, requiring organisations to weigh speed of access against auditability and risk reduction.

• Emergency access for a service account during an outage, with time bounded approval and automatic revocation after the incident closes.
• One time deprovisioning of an API key after a merger event, where the asset owner must confirm downstream dependencies before removal.
• Temporary access for a CI/CD pipeline to rotate a certificate in a nonstandard environment, with change tickets and evidence attached.
• Exception based onboarding for a third party integration that cannot use the standard template, similar to breach patterns discussed in the GitHub Action tj-actions Supply Chain Attack research.
• Manual approval of an elevated token request where the request must be validated against least privilege guidance in the NIST Cybersecurity Framework 2.0.

For NHI teams, the important distinction is that a workflow should resolve an exception, not become the normal path for everyday access operations.

Why It Matters in NHI Security

Workflows are often where weak governance becomes visible. They create a documented exception trail for access changes, but they also become a control surface if they are poorly designed, overly broad, or left unreviewed. This is especially important in NHI security because exceptions often involve secrets, tokens, certificates, and service accounts that can outlive the business need that justified them.

NHI Mgmt Group research shows that only 20% of organisations have formal processes for offboarding and revoking API keys, which means many exceptions are never fully closed out. That gap increases the chance that a temporary workflow becomes a lingering access path. The same operational risk appears in incident response, where leaked credentials can remain valid long after notification, as discussed in the Ultimate Guide to NHIs and the GitHub Action tj-actions Supply Chain Attack research.

Organisations typically encounter workflow risk only after a compromised exception, failed offboarding, or audit finding, at which point the workflow becomes operationally unavoidable to address.

Related resources from NHI Mgmt Group

• How should organisations secure workflow platforms that handle both files and secrets?
• Why do workflow engines create such a large blast radius for attackers?
• How should security teams protect NHI secrets stored in AI workflow platforms?
• Why do AI workflow platforms create a larger identity risk than a normal app server?