Major vs Minor Nonconformity: How Are Audit Findings Classified?

The difference between major and minor nonconformities, observations and opportunities for improvement: ISO/IEC 17021-1 criteria, sample findings, impact on the certification decision and how to appeal a finding.
Technical summary
Technology
ISO/IEC 27001:2022, ISO/IEC 17021-1, ISO/IEC 27006, TISAX
Topic
Classifying audit findings
Level
Beginner–intermediate
Prerequisites
  • General familiarity with the certification audit process
In this article7 sections

When the word “major” appears in the list of findings read out at the closing meeting, the certification timeline slips, sometimes along with the date promised to a customer. Yet a finding’s classification isn’t a judgment left to the auditor’s whim; it rests on the ISO/IEC 17021-1 definitions certification bodies must follow and on the nature of the evidence collected. How major nonconformities, minor nonconformities, observations and opportunities for improvement are distinguished in information security audits, how each class affects the certification decision, and which route to take when you disagree with a finding — in that order below.

Finding classes: major, minor, observation, opportunity for improvement

ISO/IEC 17021-1 defines two classes of nonconformity for certification bodies. A major nonconformity is one that affects the capability of the management system to achieve its intended results. A minor nonconformity is one that doesn’t affect this capability. Both show that a requirement isn’t met. The difference lies in the effect of the unmet requirement on the system as a whole.

Two further categories that don’t count as nonconformities are often used; their names and use vary by certification body:

  • Observation: There isn’t enough evidence to show a requirement isn’t met, but the situation could become a nonconformity if it continues. Some bodies don’t use this term at all.
  • Opportunity for improvement: The requirement is met, but the effectiveness or efficiency of the practice could be increased. A certification auditor can’t provide consulting; so these statements don’t impose a specific solution.

Read before the audit which terms appear in your audit contract and the certification body’s rules, and what kind of response each requires. Finding out at the closing meeting is too late. TISAX assessments also distinguish major and minor, but the relationship of results to the label process is different; this is explained separately in the article TISAX corrective action plan and temporary label.

Criteria that determine a major nonconformity

In a note to its definition, ISO/IEC 17021-1 lists two typical situations for a major classification: significant doubt that effective process control is in place, and a number of minor nonconformities associated with the same requirement or issue that point to a systemic failure. At the audit table, these criteria usually turn into these questions:

  1. Is the requirement not met at all, or partly? Never having carried out an internal audit is not the same as skipping one process in the internal audit program.
  2. Is the problem in a single sample or across the whole process? A missing approval in one of five changes reviewed is classified differently from no approvals in any of them.
  3. Is a core element of the ISMS cycle missing? Risk assessment, the SoA, internal audit, management review and the corrective action process are the backbone of this cycle. If one isn’t working, the system’s capability to produce results is directly affected.
  4. Is there an actual effect on information security? A critical in-scope system never being backed up doesn’t carry the same risk as a field left incomplete on a record form.
  5. Is a previous finding recurring? A problem previously reported as minor and not closed with effective corrective action may be classified more severely at the next audit.

A common source of majors isn’t technical controls but the management system cycle. A single missing firewall rule is usually written up as minor. An internal audit that was never done is usually major.

Classification table with sample findings

The examples below show typical situations you may come across in ISO/IEC 27001:2022 audits and their possible classes. The final class depends on the extent of the evidence the auditor collects and the organization’s circumstances; the table is an example of reasoning, not a decision rule.

Status Related requirement Possible class
No internal audit at all in the certification cycle Clause 9.2 Major
Management review held, some mandatory inputs not discussed Clause 9.3 Minor
No risk assessment, or it doesn’t cover the whole scope Clauses 6.1.2, 8.2 Major
One of the leavers reviewed had their account closed late Annex A 5.18 Minor
A large share of leaver accounts are open, no review done Annex A 5.18, 8.2 Major
Restore testing deviated once from the planned frequency Annex A 8.13 Minor or observation
Training records exist, effectiveness evaluation is weak Clause 7.2 Opportunity for improvement or minor

The fourth and fifth rows show that the same control can get two different classes. What decides the class isn’t the control’s name but how widespread the nonconformity is and its effect on the system’s capability to produce results. One account closed late is an accident. Dozens of open accounts are a system failure. Knowing how a finding statement is constructed makes it easier to assess the class; the elements of criterion, condition, cause and effect are explained in the guide to writing audit findings.

How the finding class affects the certification decision

The certification body must assess the responses to nonconformities before making a decision. The effect varies by class and audit type:

Class Initial certification Surveillance / recertification
Major No certification decision is made until the implementation of the correction and corrective action has been verified; verification can be done by an extra visit or document review Can lead to suspension of the certificate; at recertification it must be verified before the certificate’s expiry date
Minor The organization’s correction and corrective action plan is accepted; implementation is verified at the next audit The plan is accepted, closure is reviewed at the next surveillance
Observation / opportunity for improvement A formal response may not be needed You may be asked at the next audit what was done

ISO/IEC 17021-1 requires that, in initial certification, if the certification body can’t verify the implementation of corrections and corrective actions for major nonconformities within six months of the last day of Stage 2, a new Stage 2 audit is carried out before recommending certification. Response times (for example how many days the plan must be sent within) are set by each body under its own rules; these times are stated in the audit report or the contract. Find out the timeline on day one.

What to do when you disagree with a finding

The most productive time to discuss a finding is during the audit, not after closing. Auditors usually share findings at the daily wrap-up or before the closing meeting; that moment should be used to present evidence. The order is:

  1. Separate the fact from the class. First clarify whether you dispute the factual basis of the finding. If the fact is correct, the discussion is about the class; if it’s wrong, you need evidence that refutes the fact.
  2. Explain with evidence. Saying “we actually do this” isn’t enough; show the related record, its date and its scope. If the auditor accepts the evidence, the finding can be changed or withdrawn.
  3. Ask for the criterion. Ask for the text of the requirement the finding is based on. A practice the standard doesn’t require may have become a finding as the auditor’s preferred method.
  4. Put it on record at the closing meeting. For findings where no agreement is reached, ask for your view to be noted in the report.
  5. Use the formal appeal route. ISO/IEC 17021-1 requires certification bodies to define complaint and appeal processes and keep them publicly available. The appeal is made in writing, based on evidence and in line with this procedure.

Don’t miss response deadlines while an appeal is in progress. Preparing the correction plan for the finding anyway prevents the certification decision from being delayed. If you’re proven right, the plan is withdrawn; if not, you haven’t lost time.

Minor findings adding up to a major

Several minor findings gathered around the same requirement or issue point to a systemic weakness and may be classified as major. Think of access management: in the same audit, accounts closed late, privileged accounts not reviewed and permission changes with no record may each look minor. Read together, they show the access control process isn’t working.

The way to prevent this is to close minor findings at their root causes. Fixing only the example in the finding (closing the one account closed late) carries the problem to the next audit. The symptom closes, the cause remains. For effective root cause analysis, see the 5 Whys and fishbone applications in the article root cause analysis in corrective action. How closure of previous findings is reviewed at surveillance is explained in the surveillance audit preparation guide.

If you use the same classification logic in your own internal audits, you’ll see systemic weaknesses before the certification auditor does. To set up the internal audit program this way, see our ISO 27001 internal audit and corrective action management service, and to close open findings after certification, our post-audit nonconformity closure and corrective action service. The official text of the requirements for certification bodies is on the ISO/IEC 17021-1 page.

Frequently asked questions

If we get a major nonconformity, can’t we get certified?

In initial certification, no certification decision is made while a major nonconformity is open; the process continues once the certification body has verified that the correction and corrective action have been implemented. If verification can’t be done within six months of the last day of Stage 2, a new Stage 2 audit is required.

How quickly do we need to respond to a minor nonconformity?

The time isn’t set as a fixed number of days in ISO/IEC 17021-1 but by the certification body’s rules. It’s usually stated in the audit report or the contract; for minor findings, the correction and corrective action plan is expected to be sent within this time.

Is it mandatory to open a corrective action for an observation or opportunity for improvement?

A formal response usually isn’t mandatory, but you may be asked at the next audit what was done. Assessing the observation and creating a decision record is good practice that stops the topic turning into a nonconformity.

Can we appeal the classification the auditor gave a finding?

Yes. First explain with evidence during the audit; if you can’t agree, ask for your view to be noted in the report. Afterwards, a written, evidence-based appeal can be made under the certification body’s publicly available appeals procedure.

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