Auditors should look for proof that access was granted only when needed, expired automatically, and required appropriate approval for high-risk actions. Event logs, policy-as-code, and time-bound records usually provide stronger evidence than spreadsheet-based recertification alone. The key is demonstrating that control happens before risk materialises.
How auditors judge identity governance when recertification is no longer the centrepiece
Auditors are usually looking for a control model that proves access is granted, reviewed, changed, and removed through enforceable rules rather than periodic spreadsheet attestations. That means they will focus on whether approvals are traceable, whether exceptions are bounded, and whether high-risk access is governed continuously enough to prevent entitlement drift.
A strong audit position starts with the idea that governance is an operating control, not a campaign. If access decisions are driven by workflow, policy, and expiry logic, auditors can test the process directly instead of relying on a point-in-time review that may miss short-lived but material risk.
That is why evidence quality matters. Event logs, policy-as-code, approval records, and time-bound entitlements are easier to defend than a recertification spreadsheet that only shows someone signed off after the fact. NHIMG’s IAM and IGA Basics is useful here because it frames access review, least privilege, and lifecycle governance as related but distinct controls.
What evidence auditors expect when reviews are event-driven
When recertification is not the primary control, auditors normally want proof that the organisation can explain who approved access, why it was approved, how long it remained valid, and what triggered its removal or renewal. The question is not whether every access grant was manually rechecked on a calendar cycle, but whether the governing mechanism was effective before the risk window became unacceptable.
That shifts the evidence burden toward system-generated records. A decision trail should show the request, approver, policy condition, expiry date, and any subsequent extension or revocation. If access can be reactivated without a fresh justification, or if emergency access is left open without review, the control may exist on paper but fail in practice.
Auditors also tend to value exception handling. Where business need justifies longer-lived or higher-privilege access, there should be explicit ownership and documented rationale rather than an informal habit of renewing everything. The Audit, Assurance and Compliance Guide and the Access Reviews and Certification Guide both align well with this evidence-first approach, especially where the control objective is to remove access, not just confirm it.
Why continuous governance often beats periodic recertification
Periodic recertification is weakest when access changes faster than the review cycle. If entitlements are created, modified, or inherited between review dates, the organisation can look compliant while still carrying excessive access for weeks or months. Continuous governance reduces that gap by tying access to policy conditions, role boundaries, and expiry logic that act immediately.
That does not mean reviews disappear. It means the auditor will look for a layered model: preventive controls for standard access, detective controls for anomalies or drift, and targeted reviews for high-risk privileges, unusual exceptions, or sensitive systems. The most convincing programs treat recertification as one signal among several, not as the only evidence of governance.
For environments with machine or service access, the same logic applies to non-human identities. The Lifecycle Processes for Managing NHIs section is relevant because it shows how provisioning, rotation, and offboarding create stronger control evidence than a late review of static entitlements alone.
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 CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | Continuous access governance depends on lifecycle-controlled account issuance, review, and removal. |
| IA-5 — Authenticator Management | Time-bound records and rotation logic support stronger evidence over static review artifacts. | |
| AU-2 — Event Logging | Auditors need system logs showing access decisions, changes, and removals over time. | |
| Recommendation — Use AC-2 to enforce approval, review, and timely deprovisioning for access grants. Use IA-5 to manage credential issuance, expiry, and rotation with auditable records. Use AU-2 to record access events that prove governance happened before risk materialised. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Access governance here is fundamentally about enforcing and evidencing access control decisions. |
| A.8.15 — Logging | Event logs are central evidence when recertification is no longer the primary control. | |
| Recommendation — Define and operate access control rules that are enforced, traceable, and reviewable. Retain logs that show access approvals, changes, and revocations with clear timestamps. | ||
| CIS Controls v8 | CIS-5 — Account Management | The topic turns on granting, expiring, and revoking access under operational control. |
| Recommendation — Operate account management so access is approved, time-bounded, and removed when no longer needed. | ||
Practitioner Guidance
What to verify: Test whether every high-risk access path has an owner, a policy basis, an expiry condition, and an auditable removal path. If any of those elements are missing, the organisation is still depending on recertification to compensate for weak upstream control.
Decision rule: If an access grant can materially affect production, sensitive data, or privileged administration, require stronger pre-approval and time-bound enforcement than a routine review can provide. If it cannot be bounded that way, treat it as a governance exception, not a normal entitlement.
Practitioner takeaway: Auditors are increasingly persuaded by controls that prevent risky access from persisting, not by reports that merely prove someone looked at it later.
Related resources from NHI Mgmt Group
- How should regulated teams evaluate cloud-private identity governance platforms?
- What is the difference between periodic access reviews and continuous identity governance?
- Who should own the decision when identity governance is central to GRC?
- How should teams use DSPM findings in identity governance reviews?
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 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org