The ISO 27001 Certification Audit: How to Pass Stage 1 and Stage 2

How the ISO 27001 certification audit works: checking the body and its accreditation, the difference between Stage 1 and Stage 2, managing findings and a pre-audit checklist.
Technical summary
Technology
ISO/IEC 27001:2022, ISO/IEC 17021-1, ISO/IEC 27006-1, IAF
Topic
The Stage 1 and Stage 2 process of the initial certification audit
Level
Intermediate
Prerequisites
  • An ISMS with its scope, risk assessment and SoA completed
  • At least one internal audit and management review record
In this article8 sections

The procedures are written, the SoA is signed, the risk table is full. Still, on the first day the auditor asks, “Who applied this rule in the last three months, and where?” and no record turns up. An ISO 27001 certificate isn’t obtained by setting up the ISMS, but through a two-stage audit by an independent certification body and the certification decision that follows. This guide walks ISMS and IT managers preparing for initial certification through the process in order, from choosing the body to the certification decision: what’s looked at in Stage 1 and in Stage 2, how to use the time in between and what to check before audit day.

Choosing a certification body and accreditation

Certification bodies work according to ISO/IEC 17021-1 (general requirements for bodies providing audit and certification of management systems) and the ISMS-specific ISO/IEC 27006-1 rules. The mechanism that independently verifies a body complies with these rules is accreditation. In Türkiye, the accreditation body is TÜRKAK; accreditation bodies abroad may also be party to the IAF (International Accreditation Forum) mutual recognition arrangement. If your customer or a tender specification requires an “accredited certificate”, a certificate from an unaccredited body usually won’t be accepted. A cheap quote ends up costly here.

Before collecting quotes, verify the following:

  • Accreditation scope: Accreditation isn’t granted in general but for specific standards and sectors. Check for yourself on the website of TÜRKAK or the relevant accreditation body that ISO/IEC 27001 is in the annex to the accreditation certificate; don’t rely on the logo in a sales presentation.
  • Verifiability of the certificate: Ask whether the certificate will carry the accreditation logo and whether it will be searchable in public databases such as IAF CertSearch.
  • Basis for audit duration: Audit man-days start from the number of employees in scope, according to the table in ISO/IEC 27006-1, and are adjusted with complexity factors. If there’s a large difference in days between quotes, ask for the reasoning behind the calculation. Below-standard time means a shallow audit.
  • Auditor competence: Clarify from the start whether an auditor with experience in your sector (manufacturing, software, finance, etc.) will be assigned, and the language of the audit.
  • Separation of consulting and auditing: A certification body can’t provide consulting for the same ISMS. An offer of an “audit + consulting package” breaches the impartiality rule.

The Stage 1 audit: purpose and scope

Stage 1 assesses whether the ISMS is ready for Stage 2. Here the auditor looks less at sampling the effectiveness of controls than at the design of the management system and whether the documented information meets the standard. Under ISO/IEC 17021-1, Stage 1’s typical objectives are:

  • Confirming the scope, locations and processes; settling the scope statement in the form it will appear on the certificate.
  • Reviewing mandatory documented information: the information security policy, the risk assessment and risk treatment process, the risk treatment plan, the Statement of Applicability (SoA), information security objectives.
  • Seeing that the internal audit and management review have been planned and carried out.
  • Gathering information for the Stage 2 plan: shifts, remote locations, processes to be sampled, critical systems.

Stage 1 can be done partly or entirely remotely; this depends on the body’s practice and the nature of the scope. If you have a choice, ask for it on site. The auditor sees the server room, cabinets and physical entry points early; the risk of surprise findings in Stage 2 goes down.

Three problems you may come across in Stage 1: the scope statement and the SoA not matching, the risk assessment not fully covering the assets in scope, and the justification for controls excluded in the SoA being dismissed with an empty phrase such as “not applied”. All three are caught at the desk. We explained how to structure the SoA in detail in the ISO 27001 SoA preparation guide.

Managing Stage 1 findings

The Stage 1 report lists areas of concern that could become nonconformities in Stage 2. These aren’t formal nonconformities; but if the same situation persists in Stage 2, a nonconformity is expected to be raised. The order of checks should be:

  1. Record every finding: Open a tracking list with the finding, owner, target date and closure evidence; link this list to the ISMS corrective action log.
  2. Get to the root cause: Closing a finding such as “the procedure has a missing field” just by updating the document often isn’t enough. In Stage 2, the auditor looks for records showing the updated rule is applied.
  3. Produce implementation evidence: For every process you changed, let a few real records build up before Stage 2 (e.g. a review done with the new access review form).
  4. Set a realistic timeline: If the findings are serious, postponing Stage 2 is cheaper than going in unprepared and getting a major nonconformity.

The time between Stage 1 and Stage 2 isn’t a fixed number in the standard; the certification body sets it according to the nature of the findings and your readiness. This interval isn’t waiting time. It’s an implementation period in which gaps are closed and evidence is built up.

The Stage 2 audit: implementation effectiveness

Stage 2 assesses whether the ISMS is really operated according to its own rules and produces results. The auditor interviews process owners, selects sample records, reviews system screens and reports and visits locations if needed. The question isn’t “Is there a procedure?” The question is, “Is the procedure applied, and does it work?”

Areas typically examined in Stage 2:

  • The risk management cycle: That the risk assessment is updated at planned intervals or when significant changes occur, actions in the risk treatment plan are tracked and residual risks are approved by risk owners.
  • Sampling of Annex A controls: Records for controls marked applicable in the SoA: access requests and leaver processes, backup and restore tests, patch records, supplier assessments, incident records, training records. The item that trips people up most in the field is the restore test; the backup job looks “successful” but there’s no record of a tested restore.
  • Measurement and monitoring: That objectives are measured, results evaluated and reported to management.
  • Internal audit and management review: The internal audit covering the full scope, findings being linked to corrective action and the management review addressing the inputs in the standard. You can find internal audit planning in the article ISO 27001 internal audit program and the content of the management review in the management review guide.
  • Leadership: Top management’s involvement in the ISMS; the auditor usually talks to top management at the opening meeting or in a separate interview. The general manager saying “IT knows about that” is a bad start.

At the end of Stage 2, findings are classified as nonconformities (major or minor) and observations/opportunities for improvement. A major nonconformity is a requirement not being met at all, or a situation raising serious doubt about the ISMS’s ability to achieve its intended outcome; a minor nonconformity is an isolated deviation that doesn’t affect the system as a whole. We explained the classification criteria with examples in the article the difference between major and minor nonconformities.

Stage 1 vs Stage 2

Dimension Stage 1 Stage 2
Core question Is the system design ready? Is the system implemented and effective?
Focus Documents, scope, SoA, risk method Records, interviews, system evidence
Location Remote or on site Mainly on site
Participants ISMS manager, key owners Process owners, IT, HR, top management
Output Readiness report, areas of concern, Stage 2 plan Nonconformities, certification recommendation
Effect on certification No certification decision directly The basis for the certification decision

The certification decision and after

If nonconformities were raised in Stage 2, you submit the correction and corrective action plan within the time the certification body gives. For a minor nonconformity, acceptance of the plan is usually enough; the effectiveness of implementation is verified at the next audit. For a major, implementation of the correction and corrective action must be verified before the certification decision; this can be done by reviewing evidence or with an additional on-site visit. If the deadline is missed, the body may require a new Stage 2.

The audit team doesn’t make the certification decision; a decision-maker or committee at the certification body who didn’t take part in the audit makes it. If the decision is positive, the certificate is issued valid for three years. In this cycle, a surveillance audit is held every year, followed by recertification at the end of the cycle. The first surveillance audit must be held within twelve months of the certification decision. Build your calendar backwards from there: the internal audit and management review must be finished before that date. Details of the post-certification cycle are in the article surveillance audit preparation.

A common mistake after getting the certificate is filing it without reading the scope statement on it. ISO/IEC 27006-1 expects certification documents to reference the relevant version of the SoA; check your contract to see whether you need to inform the body when you update the SoA. Scope changes such as a new location or new service should also be notified to the body and, if necessary, assessed with an additional audit.

Pre-certification checklist

Go through it separately before Stage 1 and before Stage 2:

  • The scope statement, risk assessment, SoA and organization chart describe the same scope.
  • For each control in the SoA, the implementation status and exclusion justification are written down; the evidence source for each applicable control is clear.
  • The risk treatment plan is approved; residual risks have been accepted by risk owners.
  • At least one internal audit covering the whole scope has been completed, with its findings linked to corrective action.
  • The management review has been held with the inputs in the standard; decisions and actions are in the minutes.
  • Results for at least one measurement period are available for information security objectives.
  • Awareness training records show all employees in scope, including new starters.
  • Evidence to present to the auditor is organized by control in an evidence folder; access permissions for the duration of the audit are defined. We covered how to map evidence in the article preparing an evidence matrix.
  • Process owners have been told the audit schedule; a deputy plan is ready for interview times.
  • Rules for masking confidential data and screen sharing on screens the auditor will see are set. Don’t leave a password list open on a live console.

If you want an independent view of your current state before certification, an ISO 27001 gap analysis identifies gaps before Stage 1; certification audit preparation focuses on the evidence file and the audit day plan. For accreditation bodies, see the TÜRKAK and IAF websites.

Frequently asked questions

How much time should there be between Stage 1 and Stage 2?

The standard doesn’t give a fixed period. The certification body sets the date based on the seriousness of the Stage 1 findings and your readiness. Use this interval to close areas of concern and build up real implementation records for the processes you changed.

Can you go into Stage 2 without having done an internal audit and management review?

In practice, no. ISO/IEC 17021-1 requires Stage 1 to assess whether internal audits and management reviews are being planned and performed; that’s why certification bodies want to see internal audit and management review records covering the scope before Stage 2. If these records are missing, Stage 2 is usually postponed or a nonconformity is raised.

Does a major nonconformity mean no certificate?

No certification decision is made while a major nonconformity is open; but the process doesn’t end there. A decision can be made once the correction and corrective action have been verified through evidence or an additional visit. If verification can’t be done within the time the body gives, a new Stage 2 may be needed.

How do I verify that the certificate is accredited?

Check on the accreditation body’s website that ISO/IEC 27001 appears on the certification body’s accreditation certificate and its annex. Also ask whether the certificate will be searchable in public databases such as IAF CertSearch.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles