Third-Party ISO Certification Body in UK, Europe, UAE, MENA & Globally. (MENA HO: UAE)
SCS KNOWLEDGE CENTRE

ISO 27001 Stage 1 and Stage 2 Audits and Nonconformities

Understand ISO 27001 Stage 1 and Stage 2 audits, readiness concerns and nonconformity responses through worked examples and practical certification guidance.

  1. Home
  2. Knowledge Centre
  3. ISO 27001 Stage 1 and Stage 2 Audits and Nonconformities

ISO 27001 Certification Audits — Stage 1, Stage 2 and Responding to Nonconformities

ISO 27001 Certification Audits — Stage 1, Stage 2 and Responding to Nonconformities
Understand ISO 27001 Stage 1 and Stage 2 audits, readiness concerns and nonconformity responses through worked examples and practical certification guidance.

ISO 27001 Certification Audits — Stage 1, Stage 2 and Responding to Nonconformities

A company books its Stage 2 audit while its risk-treatment actions are still being implemented. The calendar looks settled, but the records needed to demonstrate operation do not yet exist. Another company completes the audit and assumes the closing meeting itself authorises use of a certification mark.

Both situations need a clearer understanding of the certification process. Stage 1, Stage 2, finding follow-up and the certification decision perform different functions.

This guide explains the handoffs between them and how to prepare a useful response when requirements have not been met. The existing ISO 27001 evidence article remains the broader records guide. For applications, audit planning and ongoing certification, see the SCS certification-process page.

Understand the basis of the independent assessment

An ISO 27001 certification audit assesses the defined ISMS against applicable requirements. ISO/IEC 17021-1 sets requirements for management-system certification bodies, complemented by ISO/IEC 27006-1 for ISMS certification. These are requirements for certification bodies, not additional management-system certificates that every ISO 27001 applicant must obtain.

The practical audit plan depends on the organisation and proposed coverage. Establish the legal entity, activities, locations, significant outsourced functions and current implementation position before making a commitment about completion dates.

Stage 1 evaluates readiness for Stage 2

Stage 1 considers the ISMS documented arrangements and the organisation's preparedness for the next stage. It also helps the certification body understand the scope, relevant conditions and planning needs. Internal-audit and management-review arrangements form part of the readiness considerations.

It should not be described as a consultancy exercise in which the certification auditor designs the applicant's system. The organisation remains responsible for addressing its gaps and operating the ISMS.

Record the concerns communicated by the body and clarify their meaning where necessary. Explain the work needed, responsible owners and realistic completion position before confirming progression. The body's terminology for Stage 1 outcomes and the follow-up required should be established from its actual report and process.

Use the interval between stages to resolve the identified concerns

Translate each concern into an understandable action and evidence route. An updated procedure can be part of the response, but an intended operating process may also need to be implemented and evaluated.

Stage 1 concern in a fictional application

Useful response before progression

Question to resolve with the body

The scope omits an overseas support function

Clarify the support activity, access and relationship to the ISMS

Does the proposed audit coverage or plan need revision?

Treatment actions have no implementation evidence

Establish the actual delivery status and relevant operating records

What further evaluation is needed before Stage 2 can proceed?

Internal audit did not examine an important interface

Reconsider programme coverage and evaluate the omitted activity

How does the completed work affect the readiness assessment?

Management review has no recorded decisions

Complete the required evaluation and retain the resulting decisions

What evidence is needed to address the reported concern?

 

Do not backdate records to make a planned audit appear achievable. Discuss unresolved work honestly. Significant changes or readiness issues can affect the schedule and may require further Stage 1 activity; the body determines the applicable arrangements.

Stage 2 evaluates implementation and effectiveness

Stage 2 examines how the ISMS operates. Interviews, observations, documents and records can be used to evaluate conformity and effectiveness within the audit scope.

A fictional SaaS company presents an approved release procedure. The auditor follows a deployment through review, authorisation, release and exception handling. A procedure describes the expected process; the selected operating records help show whether it was followed.

The same principle applies to a colocation operator's visitor access or a professional-services firm's information handling. The controls and evidence depend on the operation. Use the SaaS operating-evidence guide for software examples and the data-centre scope guide for operator and tenant boundaries.

An audit uses sampling. Avoid interpreting an unexamined area as specifically approved or describing certification as a guarantee that incidents cannot occur.

Read the finding before proposing the remedy

A nonconformity concerns failure to fulfil a requirement. Understand the requirement cited, the objective evidence and the identified gap. Clarify factual misunderstandings through the body's process while retaining the original report and communication trail.

Do not assume every issue has the same significance. Major and minor classifications have different implications under the applicable certification rules. Ask the body to explain the classification, response requirements and follow-up arrangements for the actual finding.

ISO's conformity-assessment toolbox explains the wider sequence of audit evidence, findings, cause analysis, action evaluation and certification decisions. A closing-meeting recommendation and a certification decision remain separate steps.

Worked example of a nonconformity response

In this fictional example, an organisation's approved procedure requires application owners to remove departed contractors' access through a documented exit workflow. Audit sampling finds that the workflow did not reach a separately administered support platform and that several former contractors still had active accounts. Assume the body has raised a finding against the applicable requirement; this example does not assign a universal severity classification.

Response element

Illustrative response

Evidence that could support evaluation

Correction and consequence review

Disable unauthorised accounts and investigate whether they were used

Account history, removal records and the documented impact review

Cause analysis

Establish why the platform was absent from the exit workflow and why earlier checks missed it

Interviews, workflow ownership and the relevant application inventory

Check for similar conditions

Examine other separately administered systems and supplier-access routes

Defined review population, results and additional actions

Corrective action

Connect the application inventory and owners to the exit process and verify removal completion

Revised responsibilities, implemented workflow and subsequent cases

Effectiveness evaluation

Check later departures and relevant reconciliation results against the intended outcome

Dated evaluation with results, exceptions and follow-up decisions

 

“Staff reminded” may be part of a response, but it does not explain an inventory or ownership problem by itself. Determine the actual cause before deciding that training is the appropriate corrective action.

Keep correction and corrective action distinguishable

Correction addresses the detected problem. Corrective action addresses its cause to reduce the likelihood of recurrence. The organisation also needs to consider consequences and whether similar nonconformities exist or could occur elsewhere.

Retain the original evidence, actions and evaluation results. Do not delete an earlier failed check after a later successful one. If an action has not yet been completed or its effectiveness has not yet been established, describe that position accurately.

Submit responses in the format and timescale agreed with the body. Do not apply a universal 30-day or 90-day deadline from another provider's website. Required review, evidence verification or further audit activity depends on the actual finding and certification process.

Understand what happens before certification is granted

The certification body evaluates the required audit and follow-up information through its decision process. Major nonconformities require verified correction and corrective action before initial certification can be granted; minor findings require the applicable acceptance of correction and corrective-action plans. European Accreditation's certification FAQs, under response to nonconformities, explain this distinction. Confirm the exact evidence and follow-up obligations with the body rather than treating every finding as requiring the same route.

Do not promise a customer a certificate merely because Stage 2 has finished or a response has been submitted. Confirm the granted scope, certificate details and authorised use of marks after the decision and issue process.

For a data-centre operator responding to a contract requirement, the existing customer-request article explains how to assemble the enquiry and deadline information. Keep that commercial requirement separate from the independent audit outcome.

Audit arrangements for UAE Malaysia and international operations

For a UAE entity supported by a Malaysian team, explain the work performed in each location, the systems accessed and who can provide evidence. An office address alone does not establish whether a site or function belongs in the proposed certification coverage.

Use the UAE and Malaysia certification guides for local enquiry context. The Saudi Arabia, Oman, Qatar, Kuwait, Bahrain, India, Canada and Singapore articles provide the respective country routes. Confirm available assessment arrangements for the actual application.

After the initial certification decision

Continue operating, evaluating and improving the ISMS. Later business changes and unresolved actions remain relevant to ongoing certification. Use the recertification-planning article for expiry-based planning and the transfer guide if you are considering another certification body; neither process is simply a repeat of an initial application.

For your next assessment discussion, provide the scope, locations, current audit stage and a truthful summary of outstanding work. Visit the SCS ISO 27001 service page or contact SCS to clarify the applicable route. Do not attach unrestricted confidential audit material to an initial public enquiry.

Share this article

Need ISO 27001 Certification for Your Business?

Speak with our certification specialists to understand certification requirements, audit process, implementation timelines and accredited certification services.

Frequently Asked Questions

No. Stage 1 is part of the initial certification audit process. Stage 2 and the applicable follow-up and certification-decision requirements still need to be completed.
Yes. Clarify the actual activities, locations and interfaces when they are questioned. The body may need to revise its planning or seek further information.
No. Read the body's report and process. A concern identifies something requiring attention; do not invent a classification or assume it can be ignored before progression.
No universal interval applies to every applicant. The certification body considers readiness, the time needed to address concerns and relevant changes when determining arrangements.
Yes. Unresolved concerns, significant changes or other planning factors can affect the agreed date. Discuss the position with the body before making customer commitments.
It establishes the approval at its actual date. Earlier operation needs its own evidence; do not backdate the policy or present a later record as historical proof.
Certification audits use sampling and other appropriate assessment methods. The applicant should still provide accurate information about the relevant populations and arrangements.
Tell the body early and identify suitable authorised evidence access or another knowledgeable person. The body determines whether the proposed arrangement supports the audit.
Explain the specific factual concern and provide supporting information through the body's process. Distinguish a factual clarification from disagreement with an applicable requirement.
No. The certification body classifies its findings under the applicable requirements. The organisation can seek clarification or use the relevant appeal process where appropriate.
It may correct the detected issue but leave its cause or similar conditions elsewhere unchanged. Evaluate the required cause analysis, wider extent and corrective action.
A label alone rarely explains why the process allowed the issue. Examine the circumstances, responsibilities and safeguards sufficiently to determine an appropriate response.
No. Select an action appropriate to the actual cause. Changes to responsibilities, interfaces, verification or other arrangements may be relevant without a software purchase.
Only claim what the evaluation supports. A completed design change does not by itself demonstrate later operating effectiveness; explain any evaluation that remains outstanding.
No. The body must review the response and determine the applicable acceptance or verification outcome. Retain that communication separately from the submission itself.
A closing-meeting conclusion or recommendation is not the same as the certification body's decision. Follow the body's decision and certificate-issue process.
Do not guarantee an independent outcome before the applicable process is completed. Communicate the current stage and proposed schedule accurately, including unresolved dependencies.