Major vs minor nonconformity: what the grading really means

A major nonconformity says a required part of your management system is missing or has broken down, and it must be closed before certification. A minor says a working system lapsed once, and it follows you to the next audit with an agreed plan; the grade matters less than the quality of your response.

By Alan Hutson, Certified ISO 27001 Lead Implementer, Certified ISO 27001 Lead Auditor, Certified Information Systems Security Professional (CISSP) · Reviewed November 2026

What is the difference between a major and a minor nonconformity?

MajorMinor
MeaningAbsence or systemic breakdown of a required elementSingle lapse within a system that otherwise works
Effect on certificationBlocks it until corrected and verifiedCertificate can be issued with an accepted plan
ClosureRoot cause, action and verification, commonly 30–90 daysPlan agreed now; evidence checked at next surveillance
ExamplesNo internal audit performed; SoA exclusions unjustified; risk methodology absentOne access review missed; one policy past its review date; one supplier file incomplete

Observations sit below both: no requirement breached, but a weakness worth fixing. Treat them seriously anyway, because at the next visit the auditor will look, and an ignored observation is how minors are born.

How do you respond to a nonconformity?

  1. Correct the instance. Do the missed review, update the document, complete the record.
  2. Find the root cause. Why did it happen: no owner, no diary trigger, a process nobody understood? Keep asking why until the answer points to a system weakness.
  3. Check for siblings. Does the same cause affect other controls, sites or suppliers? Look, and record that you looked.
  4. Fix the cause and verify. Change the process, assign the owner, set the trigger, then check later, with evidence, that it worked.

Clause 10.2 requires exactly this shape of response wherever a nonconformity arises: from audits, incidents, monitoring or complaints. It applies to your internal audit findings in exactly the same way as to external ones.

Where do findings come from at each audit stage?

At Stage 1, problems usually surface as areas of concern to resolve before Stage 2 rather than graded findings. At Stage 2 and at surveillance, grading applies in full.

At surveillance the common majors are unglamorous: no internal audit since certification, no management review, corrective actions from last year still open. All three are prevented by the rhythm in my maintenance guide.

What should you do if you have just received a major nonconformity?

Understand the finding before you dispute the grade, and resist rushing a cosmetic fix into the response window. Agree the timescale with the certification body and put a named owner on the root-cause work.

Submit evidence that shows the system now operating, because records over time beat a single heroic document. If the finding exposes something structural (the ISMS has no owner, the risk process never ran), say so and fix that: auditors respond well to honesty backed by action.

Frequently asked questions about major and minor nonconformities

Related ISO 27001 guides

ISO 27001 Stage 1 vs Stage 2 audits: what to expect

What each stage of the certification audit examines, what auditors ask for, how findings are graded and how to prepare for both.

Read the guide

Preparing for an ISO 27001 surveillance audit

What a surveillance audit covers, what auditors typically ask for and how to prepare without a last-minute scramble.

Read the guide

ISO 27001 internal audit: programme, checklist and report

Planning an impartial internal audit that covers the whole system, what to sample, and what the report must contain.

Read the guide

How much does ISO 27001 certification cost in the UK?

The three costs that make up the total (implementation support, certification-body fees and your own team's time), with published UK market fees and my indicative fees.

Read the guide

Findings to close, and a deadline on them?

Arrange a readiness discussion. Send me the findings in advance, and I will help you build responses that deal with the underlying causes.

Or email info@isosecurity.co.uk