Subscribe to the Non-Human & AI Identity Journal
Home Glossary Governance, Ownership & Risk Recertification Audit
Governance, Ownership & Risk

Recertification Audit

← Back to Glossary
By NHI Mgmt Group Updated June 11, 2026 Domain: Governance, Ownership & Risk

A recertification audit is the periodic reassessment that renews ISO 27001 certification after the certificate expires. It tests whether the management system still reflects current operations, which means organisations must keep controls, evidence, and ownership aligned over time.

Expanded Definition

Recertification audit is often used in a broader governance sense than its strict ISO 27001 meaning. In ISO practice, it is the full reassessment that occurs at the end of the certification cycle to confirm the management system still meets requirements and still matches real operations. That makes it different from surveillance audits, which are narrower checkpoints during the cycle. For NHI and IAM programmes, the term is useful as a governance analogue: it describes the moment when controls, evidence, ownership, and exception handling must be proven current, not merely documented.

The practical value of the concept is alignment. If access reviews, secret rotation, service account ownership, and logging have drifted from policy, recertification exposes that drift. This is closely related to the control logic in NIST Cybersecurity Framework 2.0, where governance and continuous risk management depend on operational evidence. The most common misapplication is treating recertification as a paperwork renewal, which occurs when teams prepare evidence only at audit time and ignore whether controls still work day to day.

Examples and Use Cases

Implementing recertification rigorously often introduces documentation and evidence-collection overhead, requiring organisations to weigh audit readiness against the operational cost of continuous upkeep.

  • A cloud platform team revalidates service account ownership, rotation cadence, and privileged access paths before an ISO 27001 recertification review.
  • A security office uses Ultimate Guide to NHIs — Lifecycle Processes for Managing NHIs to map which machine identities still have active business purpose.
  • An internal audit function samples API keys, certificates, and secrets stored outside approved vaults, then compares the results with the evidence trail described in Ultimate Guide to NHIs — Regulatory and Audit Perspectives.
  • A platform engineering team proves that offboarding controls actually revoke credentials after workload decommissioning, rather than relying on ticket closure alone.
  • A compliance lead checks whether exceptions granted during incident response were reviewed, time-boxed, and formally accepted before renewal of certification.

In practice, the concept aligns with the broader expectation that governance evidence should reflect operational reality, not just policy intent.

Why It Matters in NHI Security

Recertification matters because NHI risk compounds when controls are not re-tested against live environments. A certificate renewal can fail for reasons that are invisible in static policy documents: orphaned service accounts, undocumented secrets, excessive privilege, or ownership gaps after team changes. Those failures are especially dangerous in NHI environments because machine identities scale faster than human oversight. NHIMG reports that NHIs outnumber human identities by 25x to 50x in modern enterprises, which means a small review gap can become a major exposure surface quickly.

This is why recertification should be read as an assurance event, not an administrative milestone. The operational question is whether the organisation can still demonstrate control integrity across lifecycle, access, and evidence management. That concern is reinforced by the fact that the Ultimate Guide to NHIs shows only 5.7% of organisations have full visibility into their service accounts. When visibility is weak, recertification becomes the first hard test of whether the programme actually knows what it is certifying. Organisations typically encounter the need to rebuild ownership and revoke stale access only after an audit exception or certificate lapse, at which point recertification becomes operationally unavoidable to address.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP Non-Human Identity Top 10 address the attack and risk surface, while NIST CSF 2.0 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP Non-Human Identity Top 10NHI-10Recertification exposes stale ownership, access drift, and weak lifecycle governance for NHIs.
NIST CSF 2.0GV.OV-01Recertification is a governance assurance activity that checks whether controls still operate as intended.
NIST Zero Trust (SP 800-207)SC-3Recertification validates that access and trust assumptions still match least-privilege and zero-trust design.

Revalidate NHI ownership, privileges, and evidence on a fixed cycle and remediate drift before renewal.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on June 11, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org