They should treat those applications as lifecycle exceptions that still need full governance, not as exempt systems. The practical response is to inventory them, prioritise the highest-risk apps, and use resilient automation or controlled manual evidence for provisioning, deprovisioning, and recertification. The objective is consistent access control, not connector completeness.
Applications that lack SCIM or SAML support should still be governed as part of the access estate, because the absence of a standard connector changes the operating model, not the accountability. Treat them as exceptions with explicit ownership, documented lifecycle steps, and compensating controls so access does not drift just because automation is harder.
What matters most is establishing how those apps enter, change, and leave the environment. A complete inventory lets teams separate low-value edge cases from systems that can materially expand access risk, while a risk-ranked queue helps focus manual work on the applications most likely to create orphaned access, delayed offboarding, or inconsistent recertification.
For many organisations, the practical answer is a controlled mix of resilient automation and manual evidence. Use whatever can be automated safely for provisioning and deprovisioning, then backfill the remaining steps with auditable approvals, attestations, and periodic access review so governance remains consistent even when the application cannot participate in modern federation or lifecycle tooling.
Risk and Threat Considerations
The main risk is not the missing connector itself, but the governance gap it creates. Unsupported integration paths often lead to standing access, slower removal of leavers, weaker evidence for recertification, and more room for privilege creep when teams treat the application as “too hard to manage.”
Failure mechanism: Lifecycle actions become inconsistent across systems, so access is granted or retained outside the normal control plane. That increases the chance of orphaned accounts, delayed revocation, and inaccurate access records, especially when the application is business-critical or widely used.
Impact: Security teams lose reliable control over who can access the application and for how long, which can widen the blast radius of a compromise and weaken auditability. Over time, the exception becomes a parallel identity process rather than a governed exception.
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, CIS Controls v8 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | Covers lifecycle control over application accounts and access exceptions. |
| IA-5 — Authenticator Management | Applies where manual provisioning uses credentials, tokens, or shared secrets. | |
| AC-6 — Least Privilege | Supports limiting access when automation gaps force exception handling. | |
| Recommendation — Enforce account lifecycle approval, review, and removal for unsupported apps. Manage secrets and authenticators used for manual app access workflows. Constrain exception access to the minimum permissions required. | ||
| CIS Controls v8 | CIS-5 — Account Management | Directly addresses inventory, authorization, and removal of application access. |
| Recommendation — Maintain complete account inventory and remove unused access promptly. | ||
| NIST Zero Trust (SP 800-207) | Zero Trust Architecture | Uses continuous verification and least privilege when standard federation is absent. |
| Recommendation — Apply continuous verification and least privilege to exception applications. | ||
Practitioner Guidance
What to prioritise: Start with the applications that combine high business value, sensitive data, and frequent user movement. Those systems create the greatest governance risk when provisioning or deprovisioning is manual, because even small delays can leave active access behind after role changes or offboarding.
Decision rule: If an application cannot participate in automated lifecycle integration, require an explicit exception owner, a documented manual process, and a review cadence that is tied to the access risk of the system rather than to a generic annual schedule. If the process cannot produce evidence, it is not governing the application.
What good looks like: Every exception app has a named owner, a current inventory record, a repeatable joiner-mover-leaver path, and a clear recertification trail. The standard is consistent access control, not perfect connector coverage.
Practitioner takeaway: The right control objective is governance parity, not tooling parity, so teams should accept manual handling only when it remains controlled, reviewable, and bounded by clear exception management.
For teams building a broader identity programme, the same principle applies to lifecycle exceptions elsewhere in the estate, including Joiner-Mover-Leaver (JML) Guide and SCIM and Automated Provisioning Guide. When applications cannot use standard lifecycle integration, governance still has to deliver the same outcomes through exception handling, evidence, and review.
Related resources from NHI Mgmt Group
- Guide: Workforce Identity Security Guide
- Govern
- How should security teams extend zero trust to nonstandard applications that do not support SAML, SCIM, or OIDC?
- How should teams govern provisioning when some applications do not support SCIM?
- How should security teams extend identity lifecycle management to applications that do not support SCIM, APIs, or federation?
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 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org