ISO 27001
ISO 27001 Recertification Audit: What Changes in Year 3?
What gets audited across the entire scope in year three, which deadlines apply before an ISO 27001 certificate expires, and what happens if your scope changes or you switch certification body.
By KaitoSec Team · Published 5 November 2026 · 19 min read
The recertification audit in year three again evaluates your ISMS's effectiveness for the entire scope, and, unlike in the initial audit, major nonconformities must be closed before the certificate's expiry date. If it expires, the certification body can restore it within six months; after that, at least a new stage 2 is required. The KaitoSec team therefore advises planning backwards from the expiry date.
What does a recertification audit mean in ISO 27001?
With the recertification audit, a certification body confirms in year three of the cycle, before the ISO 27001 certificate expires, that your ISMS is still conformant and effective. It supports the renewal decision, which starts the next three-year cycle under ISO/IEC 17021-1.
The cycle follows ISO/IEC 17021-1, 9.1.3.2: initial audit, surveillance audits in the first and second year after the decision, recertification audit in the third year before expiry. The first cycle begins with the certification decision, each further cycle with the recertification decision. The short definition in our glossary pins down the term. For how stage 1 and stage 2 work in the initial audit, see our guide to the certification audit.
Audit and decision are separate steps: the audit provides the basis, the decision comes afterwards. This matters because the deadline hangs on the expiry date. Under 9.6.3.1.1, the audit must take place early enough to allow renewal before expiry.
The recertification process in brief:
- Report changes and plan the audit.
- Conduct the audit.
- Close nonconformities.
- The certification body decides and issues the new certificate.
Two other things called recertification are not meant here: the regular review of access rights, or access recertification, and the renewal of personal auditor certificates.
KaitoSec is not a certification body; this guide explains the rules that apply to certification bodies.
What sets recertification apart from initial certification and the surveillance audit?
The surveillance audit need not cover the entire ISMS; the recertification audit again evaluates its effectiveness for the entire scope. It differs from the initial audit by looking at three years of operation and by its deadline: the expiry date. Significant changes can make a stage 1 necessary.
The three audit types compared. Compiled by the KaitoSec team from ISO/IEC 17021-1 and published certification body rules.
| Feature | Initial certification | Surveillance audit | Recertification |
|---|---|---|---|
| Timing | Before the first certificate | In the first and second year after the decision, at least once per calendar year, except in the year of recertification | In the third year, before the certificate expires |
| Key question | Is the ISMS ready and effective? | Is it still running, and have nonconformities been addressed? | Is it still conformant and effective, including after changes? |
| Coverage | Entire ISMS within the scope | Not necessarily the entire system | Effectiveness for the entire scope |
| Stages | Stage 1 and stage 2 | No stages | Stage 1 only if needed, methodology as in stage 2 (according to TÜV NORD CERT) |
| Look back | State at the time of the audit | Previous audit | Reports of the surveillance audits in the cycle |
| Major nonconformity | Verified within six months of the last day of stage 2, otherwise another stage 2 | Deadline set by the certification body | Closed before the certificate expires |
| Result | Certification decision, cycle begins | Certificate maintained | Recertification decision, next cycle |
| Reference | 17021-1, 9.3, 9.5.3.2 (EA FAQ 36.14) | 17021-1, 9.1.3.3, 9.6.2.2 | 17021-1, 9.6.3 |
A surveillance audit is not a substitute, because its audit program is narrower. Under ISO/IEC 17021-1, 9.6.2.2, it includes internal audit and management review, actions on nonconformities, complaints, effectiveness, improvement and changes, among others. A passed surveillance audit says nothing about areas that were not covered during the cycle.
It maintains the certificate; renewal rests only on the recertification audit and subsequent decision. The six-month limit for a major nonconformity also applies only in the initial audit; in year three, the expiry date is what counts.
Individual bodies disclose their practice. TÜV NORD CERT writes in its procedure description for ISO 27001, Rev. 07/03.22: “Es werden alle Normanforderungen auditiert.” (“All requirements of the standard are audited”, our translation.) And: “Die Audit-Methodik im Re-Zertifizierungsaudit entspricht der eines Audits Stufe 2.” (“The audit methodology in the recertification audit corresponds to that of a stage 2 audit”, our translation.)
The DQS rules in 5.2 require all nonconformities to be resolved before issue, for recertification too. Your body can demand more than the minimum.
What does the auditor check differently in year three compared with the initial audit?
In year three, the auditor checks whether your ISMS works across the cycle; the initial audit asked whether it was implemented and effective at audit time. ISO/IEC 17021-1 therefore requires an audit of the management system's effectiveness, the commitment to maintaining and improving it, and the achievement of objectives, plus a review of previous surveillance reports.
The initial audit evaluates the state at audit time. In year three, records cover the entire cycle: the internal audit and the management review have run several times, plus the surveillance audit reports and corrective actions. So the auditor can compare trends. Whatever the first surveillance audit flagged can be traced to the current state.
Under ISO/IEC 17021-1, 9.6.3.2.1 and 9.6.3.1.2, attention points in four directions:
- Effectiveness for the entire scope.
- The organization's demonstrated commitment to maintaining and improving the ISMS.
- Achievement of the ISMS's objectives and intended results.
- The reports of previous surveillance audits, which feed into recertification.
The last point puts recurring findings on the agenda. A minor nonconformity that was closed during the cycle and reappears in year three should be dealt with before the audit, because under ISO/IEC 17021-1, 3.12 (EA FAQ 35.10), several minor nonconformities against the same requirement can together show a systemic failure and thus a major nonconformity. That is our assessment, not a consequence of the standard: whether the auditor rates the specific case that way remains open.
A fictional example, modeled on the one in our certification audit guide: at the first surveillance audit, the access recertification was missing, and the correction made up for it. In year three, it is missing again. Making it up a second time does not answer the obvious question of why it failed again. So clarify the cause before the audit and record the corrective action.
The certification audit guide covers the evidence expected for each clause. For the controls in the current cycle: track status and evidence for each control.
Which deadlines apply before the ISO 27001 certificate expires?
The expiry date is the decisive date: the recertification audit must take place early enough to allow renewal before it, and major nonconformities must be closed before it. At least one audit per calendar year also applies. The freely available excerpts of ISO/IEC 17021-1 contain no lead time in months; your certification body sets specific deadlines.
In the initial audit, major nonconformities have a six-month limit after the last day of stage 2. In year three, the clock runs against the expiry date: under ISO/IEC 17021-1, 9.6.3.2.2, the certification body sets the deadline so that closure falls before expiry. The later the audit takes place, the less time remains for corrective actions and verification.
Finishing early does not have to cost validity. If you pass the recertification audit before expiry, the new expiry date can build on the existing one (9.6.3.2.3). The issue date falls on or after the day of the decision.
What the standard specifies and what individual bodies add:
| Deadline | Rule | Source | Applies to |
|---|---|---|---|
| Recertification audit | Early enough for renewal before expiry | ISO/IEC 17021-1, 9.6.3.1.1 | Accredited bodies |
| Major nonconformity | Closed before expiry | ISO/IEC 17021-1, 9.6.3.2.2 | Accredited bodies |
| Earliest start | No earlier than four months before expiry | BSI certification scheme V2.2, 2.9.3 | Only ISO 27001 on the basis of IT-Grundschutz |
| Audit report | With the certification body no later than two months before expiry | BSI certification scheme V2.2, 2.9.3 | Only ISO 27001 on the basis of IT-Grundschutz |
Outside the BSI scheme, the four and two months do not apply.
The earliest date has been debated too: on a submission dated 31 August 2015, the certification sector committee of the Swiss Accreditation Service (SAS) recorded that the standard contains “keine Vorgaben” (“no requirements”, our translation) on this. The consensus reached there: an audit should take place “nicht früher als 6 Monate vor Ablauf des alten Zertifizierungszyklus” (“no earlier than 6 months before the end of the old certification cycle”, our translation). That is the Swiss state of discussion from 2015, not a German rule.
The calendar-year rule (9.1.3.3) has a side effect. If a certificate expires early in the year, the recertification audit may fall in the previous year, which then contains two audits. Clarify with your body whether an audit drops out the following year: the SAS submission from 2015 assumed so, while the EA requires at least one audit in every calendar year in FAQ 37.12.
European Accreditation (EA) addresses the reverse case in FAQ 37.12: a recertification planned for 1 December slips to 15 January for unforeseen reasons, so no audit takes place in the originally planned year. The EA treats this as an exception (“shall be considered as exceptional”). The reason should be documented and presented to the accreditation body on request. Possible measures it names include suspension or another form of surveillance until the on-site audit.
What happens if the ISO 27001 certificate expires?
If the certificate expires before recertification is completed, it is not extended. The certification body can restore it within six months, provided the outstanding activities are completed; otherwise at least a stage 2 is required. The expiry date stays tied to the old cycle, so you gain no time.
“Following expiration of certification, the certification body can restore certification within 6 months if the outstanding recertification activities are completed, otherwise at least a stage 2 shall be conducted.”
European Accreditation, FAQ 36.14
According to EA FAQ 47.5, the recertification decision is part of what must be completed within the six months; otherwise the body treats you as a new client.
Restoration does not apply retroactively. Under ISO/IEC 17021-1, 9.6.3.2.5, the effective date falls on or after the decision, and the expiry date is based on the previous cycle. So no valid certificate exists between expiry and the decision.
Individual bodies set their own rules for the period after expiry. At TÜV AUSTRIA, the right to use the certificate ends “mit sofortiger Wirkung” (“with immediate effect”, our translation) once its validity has expired. Under the DQS rules, the client must then “jede Werbung mit der Zertifizierung einstellen” (“stop all advertising with the certification”, our translation). The BSI scheme for ISO 27001 on the basis of IT-Grundschutz makes it clear: “Ein Antrag auf Re-Zertifizierung oder ein laufendes Re-Zertifizierungsverfahren verlängert die Gültigkeit des Erstzertifikats nicht.” (“An application for recertification or an ongoing recertification procedure does not extend the validity of the initial certificate”, our translation.)
If you state to customers or in tenders that the certificate is valid, you must explain the gap. Check your contracts for clauses on this.
When is a stage 1 needed for recertification?
A stage 1 can be necessary if the management system has changed significantly or legislation has changed. ISO/IEC 17021-1 does not prescribe it across the board; the certification body decides. So report changes, including to the scope, early, not during the audit.
The basis is clause 9.6.3.1.3. TÜV NORD CERT also mentions significant changes “im Zusammenhang mit den Tätigkeiten des Unternehmens” (“in connection with the company's activities”, our translation). Such changes can occur anytime in the cycle; a special audit is then also possible under 9.6.4, in one or two stages.
Bodies decide themselves what you must report. Three published examples:
- DQS names the purchase or sale of parts of the company, change of ownership, change of location, major changes in the field of activity, and fundamental process changes.
- TÜV NORD CERT (Rev. 07/03.22) names significant changes in organizational structure and processes.
- The BSI scheme, which applies only to ISO 27001 on the basis of IT-Grundschutz, also names “Änderungen im Outsourcing” (“changes in outsourcing”, our translation). There, the BSI decides on early recertification.
The body reviews a scope extension on application; under 9.6.4.1, it can be combined with a surveillance audit. TÜV NORD CERT also names the recertification audit for this, and the “Gültigkeitsdauer eines Zertifikates ändert sich dadurch nicht” (“validity period of a certificate does not change as a result”, our translation). Before applying, clarify how you define the scope.
The body also derives the audit time from current information. Report changed headcounts and sites early and ask for the calculation in writing. For budget planning, read how audit days affect the cost.
A fictional case: in year two of the cycle, a municipal utility brings a subsidiary's IT operations into the scope. The question for the certification body: is an extension enough, or is a stage 1 necessary? The body gives the answer, not this article.
What applies if you switch certification body before recertification?
A switch is possible as long as the certificate is valid and accredited. Under IAF MD 2, the new certification body reviews the existing reports, verifies open major nonconformities and takes over the current cycle. If problems arise, it treats you as a new client and the cycle restarts.
The conditions are set out in IAF MD 2:2023:
- Only valid accredited certificates can be transferred, not those known to be suspended (2.1.2).
- The new body reviews the documents and, where major nonconformities are open, can also do so through a visit, which is not an audit (2.2.2).
- If reports are missing or a due audit was not conducted, the organization counts as a new client (2.2.4).
- Open major nonconformities must be verified, and plans for minor nonconformities accepted (2.3.1).
- The certification cycle continues, and the new body plans for the remainder of the cycle (2.3.4).
For year three, the expiry date stays. Switching shortly before expiry does not move the deadline, and it follows from 2.1.2 that an expired certificate cannot be transferred.
New client status carries weight. In that case, “geht das Verfahren in eine Erstzertifizierung über” (“the procedure turns into an initial certification”, our translation), as section 5.4 of the DQS rules puts it.
The procedure description from TÜV NORD CERT (Rev. 20/01.26, by its title not applicable to ISO 27001) shows the process at one body: first the pre-transfer review, then the transfer. “Der Zertifizierungszyklus des übertragenen Zertifikates basiert auf dem vorherigen.” (“The certification cycle of the transferred certificate is based on the previous one”, our translation.)
KaitoSec does not recommend any body. To check whether a body is accredited, use the DAkkS search.
What applies to recertification under ISO/IEC 27001:2022?
Since 30 April 2024 at the latest, recertifications have run only against ISO/IEC 27001:2022, and certificates to the 2013 edition have been expired or withdrawn since 31 October 2025. If you moved over through a transition audit, you kept your expiry date. If you did so outside a recertification, the first recertification afterwards audits you against the 2022 edition.
Under IAF MD 26:2023, the transition audit could run together with a surveillance audit, a recertification audit or separately. A successful transition on its own does not change the expiry date: “the expiration of its current certification cycle will not be changed”. The minimum content included a gap analysis, the Statement of Applicability, the risk treatment plan where applicable, and new or changed controls.
IAF MD 26 sets minimum content for the transition audit, not an audit of all requirements. So if you transitioned outside a recertification, do not tick off new and changed controls as done in year three just because the transition is complete. That is our assessment, not a consequence of the standard. The Statement of Applicability and the evidence must reflect current operations.
According to the IAF decision on the IAF-ISO Joint Communiqué, the climate change amendment Amd 1:2024 to 4.1 and 4.2 has been part of the audit since its publication; a full transition program is not planned. More on this in the certification audit guide.
The body itself also has a new rule. Under IAF MD 29:2024, it uses ISO/IEC 27006-1:2024 for initial and recertification audits from its accreditation transition onward, and by 31 March 2026 at the latest for all clients. The rules on audit time have changed, and contracts with existing clients may need to be adjusted.
The customer information from TÜV NORD CERT makes two points on this: the ISMS does not have to be adapted, and the previous limit of 30% remote share no longer applies, as the share follows a risk analysis. So check your contract and audit time before the recertification audit.
How do you plan recertification backwards from the expiry date?
Plan recertification backwards from the expiry date of your certificate: decision, verification of major nonconformities, audit report, audit, change notification and scheduling. How much lead time each step needs depends on the rules of your certification body. So clarify this with them early, in writing.
The anchor is ISO/IEC 17021-1, 9.6.3.1.1: the audit must take place early enough to allow renewal before expiry.
Each step comes before the previous one. So you work from step 7 upward.
- Take the expiry date from the certificate and keep it in the ISMS as a fixed date.
- Before that comes the certification body's decision: ask them for its date.
- Before this decision: plan a buffer for corrective actions and for verifying any major nonconformities.
- Before that, set the audit report and audit date, and request the body's submission deadlines in writing.
- Before the audit date, complete the internal audit and management review; this is a recommendation, not a deadline in the standard.
- Before that, go through open findings from the surveillance reports of the cycle and look for repeats.
- At the very start: report changes, coordinate dates, clarify whether a stage 1 will be necessary, and check audit time and contract.
Software replaces neither the conversation with the body nor the decision on the scope or on risk acceptance. Only the accredited certification body decides on recertification.
Three steps of the plan can be reflected in KaitoSec. For step 6: The work list shows audit readiness and underneath the most urgent tasks from risks, findings and improvements, with their age.
For step 5, from Reporting for audit and management review: Management reviews, statements of applicability and vendor reports come from the current state and stay saved with author and time. Later it is clear what was shared when.
For the handover to the body around the audit date (step 4), from ISO 27001 in KaitoSec: Your Statement of Applicability brings applicability, justification, implementation and evidence together. Changes are versioned and your certification body can receive controlled read access to the approved state when required.
Enter the expiry date first and ask your certification body for the decision date. To see this for your own scope, walk through it with KaitoSec in a demo call.
Frequently asked questions about the ISO 27001 recertification audit
How many months before expiry should the recertification audit take place?
The freely available excerpts of ISO/IEC 17021-1 contain no number of months; renewal must be possible before expiry. Your certification body's rules are what count. In the BSI scheme for ISO 27001 on the basis of IT-Grundschutz, the audit begins no earlier than four months before expiry, and the report is in no later than two months before.
What determines how long the recertification audit takes?
The certification body derives the audit time under ISO/IEC 27006-1 from your current information, such as the headcount within the scope. So report changed figures early and request the calculation in writing. For budget planning, find the cost of surveillance audits and recertification in our cost article.
Does the recertification audit have to take place on site?
Not necessarily in full; your certification body decides. ISO/IEC 17021-1 refers to an on-site audit in 9.6.3.2.1. In its customer information, TÜV NORD CERT mentions a remote share based on risk analysis under ISO/IEC 27006-1:2024. The BSI auditing scheme for IT-Grundschutz allows remote work only under certain conditions.
Does a new three-year cycle start after recertification?
Yes. Each subsequent cycle begins with the recertification decision (ISO/IEC 17021-1, 9.1.3.2). If you finish before expiry, the new expiry date can be based on the previous one, so no validity has to be lost (9.6.3.2.3). Surveillance audits then follow again, at least once per calendar year, except in the year of recertification.
Is passing a surveillance audit enough to renew the certificate?
No. The surveillance audit maintains the certificate but does not renew it. Renewal requires a recertification audit in year three and the recertification decision (ISO/IEC 17021-1, 9.6.3). The certification regulations of TÜV AUSTRIA name the surveillance audit as a prerequisite for validity to be maintained.
Which deadlines apply to recertification in the BSI scheme for IT-Grundschutz?
The BSI certification scheme sets the audit no earlier than four months before expiry, and the audit report must arrive no later than two months before. A new application is required, and it does not extend validity. The audit activities “unterscheiden sich grundsätzlich nicht von denen eines Erstzertifizierungsaudits” (“do not fundamentally differ from those of an initial certification audit”, our translation; BSI auditing scheme).
Sources
- IAS, ISO/IEC 17021-1:2015 Section 9 (excerpts from the standard)
- European Accreditation (EA), FAQ 36.14
- European Accreditation (EA), FAQ 37.12
- European Accreditation (EA), FAQ 47.5
- European Accreditation (EA), FAQ 35.10
- TÜV NORD CERT, description of the certification procedure MS ISO 27001, ISO 22301, ISO 20000-1 (A50F300, Rev. 07/03.22)
- TÜV NORD CERT, description of the certification procedure ISO 9001 and others (A00F300, Rev. 20/01.26)
- TÜV NORD CERT, customer information on the transition to ISO/IEC 27006-1:2024
- DQS, auditing and certification rules CF10 (2026-06-01, 007/05.2026)
- TÜV AUSTRIA, certification regulations (VB-TAGMBH-MSZ-219, Rev. 16, 08.09.2026)
- BSI, certification scheme for ISO 27001 on the basis of IT-Grundschutz, version 2.2
- BSI, auditing scheme, version 2.5
- SAS (Swiss Accreditation Service), certification sector committee: discussion topic “Zeitpunkt Re-Zertifizierungsaudit”, 31 August 2015 (archived version)
- IAF MD 26:2023
- IAF MD 29:2024
- IAF-ISO Joint Communiqué, February 2024
- IAF MD 2:2023, Issue 2, Version 2
- DAkkS, search for accredited bodies
- ISO/IEC 17021-1:2015, ISO/IEC 27006-1:2024, ISO/IEC 27001:2022 with Amd 1:2024. Paid standards; only paraphrased in this article, on the basis of the accreditation documents listed above.
- ISO 27001
- ISMS
- Zertifizierung
- Audit
- Mittelstand