Common warning signs include missed accounts, outdated permission records, inconsistent reviewer decisions, and reviews that feel like routine sign-off rather than real scrutiny. If audit evidence is hard to produce, if role changes are not reflected quickly, or if excessive access keeps reappearing, the process is not giving reliable governance or compliance assurance.
What failing manual reviews usually look like
Manual Concur access reviews usually fail when the review becomes a paperwork exercise instead of a real control. The strongest signal is not one missed item but a pattern: stale access stays approved, reviewers stop challenging anomalies, and the evidence trail no longer shows that access decisions were informed by current role, manager, or business need.
That is why review quality matters as much as review completion. A process can be “done” on schedule and still miss account sprawl, inherited access, contractor exceptions, and repeated approvals that no longer reflect the real operating model. For a broader control-health lens, see Measuring security control effectiveness.
In practice, Concur reviews fail fastest when the reviewer is looking at a static export rather than an authoritative entitlement view. If role changes, departures, and exception approvals are not reflected quickly, the review is validating yesterday’s state and will keep producing false confidence.
Why the review stops providing governance value
A healthy access review should surface whether access is still justified, whether privilege is excessive, and whether remediation actually happened. When the output is always the same, the same people keep approving the same access, or reviewers cannot explain why an entitlement was accepted, the control has lost discriminatory power. It is then closer to sign-off than certification.
One common failure mode is reviewer fatigue. When too many entitlements appear in one cycle, people skim, accept defaults, or rely on trust in the system owner rather than checking whether access is still needed. Another is poor data quality: duplicate identities, old job codes, missing owners, and unclear entitlement descriptions make it hard to decide anything with confidence.
Manual review also breaks down when it is disconnected from lifecycle events. If movers, leavers, and temporary exceptions are not feeding the review process, excessive access is likely to reappear even after it was removed once. That is why access-review programs work best when they are tied to lifecycle remediation, not isolated from it, as reflected in the Access Reviews and Certification Guide.
What good evidence and remediation should look like
Reliable reviews leave a clear audit trail: who reviewed what, what exception was approved, what was removed, and when the change actually took effect. If you cannot produce that trail without manual reconstruction, the review process is not trustworthy enough for audit or governance use.
Good evidence also shows that the review is shaping access outcomes, not just documenting them. You should be able to see revoked access, corrected role assignments, and follow-up on unresolved items. If excessive access keeps reappearing, that usually means the upstream provisioning or role model is still wrong, not just that reviewers are missing items.
The most useful response to a failing review is often to narrow scope and improve signal, not to demand more attention from reviewers. For example, focus the process on risky access first, use cleaner ownership data, and close the loop on remediation before expanding volume. That is the same governance logic used in IAM and IGA Basics.
Risk and Threat Considerations
When manual Concur access reviews fail, the risk is not just weak paperwork. Stale or excessive access can persist long enough for inappropriate expense creation, approval abuse, or fraud-style misuse to go unnoticed, and weak review discipline also makes audit evidence less credible.
Failure mechanism: Reviewers approve by habit, rely on outdated entitlement lists, or cannot see recent role and ownership changes, so excessive access survives multiple cycles and becomes normalized.
Impact: The organisation loses assurance over who can submit, approve, or modify sensitive Concur activity, and repeated exceptions can create avoidable compliance exposure, remediation backlog, and potential financial misuse.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-6 — Access Control Management | Manual access reviews are an access-control safeguard that must remove stale and excessive entitlements. |
| Recommendation — Review and revoke unnecessary Concur access on a defined cadence and verify removals. | ||
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | Concur review failures show account and entitlement governance breakdowns that AC-2 addresses. |
| AU-6 — Audit Review, Analysis, and Reporting | The question centers on whether review evidence is trustworthy and actionable for governance assurance. | |
| Recommendation — Ensure accounts and privileges are reviewed, approved, and removed through a controlled lifecycle. Retain review evidence that proves access decisions were examined and acted on. | ||
| ISO/IEC 27001:2022 | A.5.18 — Access rights | Access-rights review quality is directly tied to periodic validation and removal of inappropriate access. |
| A.5.15 — Access control | The issue is whether access governance remains effective, consistent, and enforceable over time. | |
| Recommendation — Periodically verify user access rights and remove access that is no longer justified. Apply consistent access-control rules and validate that they are actually enforced. | ||
Practitioner Guidance
What to verify: Check whether the review input is generated from current authoritative access data, not a stale export, and confirm that movers, leavers, and exception removals are reflected before certification begins. If reviewer notes never change and removals are rare, assume the process is not exercising real judgment.
Decision rule: If the control cannot show timely remediation and repeatable evidence of challenge, treat it as a weak governance control rather than a reliable attestation mechanism. In that case, reduce review scope, improve entitlement hygiene, and fix ownership data before increasing frequency or volume.
Practitioner takeaway: A Concur review is failing when it preserves the appearance of compliance but no longer changes access behaviour; the test is whether it still removes bad access and leaves defensible evidence behind.
Related resources from NHI Mgmt Group
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 October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org