Independent thinking. Informed defence.

CISO Times

Intelligence for the people behind the defence.

The CISO Decision Brief

If…, then how…

If an internal audit, an incident or a complaint shows a nonconformity, then how do we correct it and stop it coming back?

5 decision pointsThe pack behind this answer: ISO 27001 Implementation & Certification Readiness

Add to board memo

The short answer

Recommendation
Log every nonconformity whatever its source, correct it, find a root cause you can change, set an owned and dated corrective action, check it worked with new samples, and close it only on that check. Treat observations separately and report the log to the management review.
Reasoning
The pack's rule is that every nonconformity gets a root cause, a correction, a corrective action and a check that it worked. A fix that treats only the symptom returns at the first surveillance audit. The pack's log covers audits, incidents and complaints. The auditor samples a finding traced end to end, and asks whether the root cause was found and the fix checked.
Considerations
  • The timings shown are the pack's defaults for internal findings. Your procedure, or your certification body for its own findings, may set others.
  • The standard's text is paywalled. The steps here come from the pack and public guides.
  • A major nonconformity raised by your certification body has its own route and deadlines, set by that body.
  • The pack's internal deadlines are shorter for majors, while certification bodies usually give different periods for their own findings. Do not apply one set to the other.

The decision, step by step

Select any step for the reasoning behind it and where the pack covers it.

  • Start
  • Step
  • Decision
  • Outcome
  • Loop back

Keyboard: Tab to a step, arrow keys move along the flow, Enter pins its explanation, + and − zoom, 0 fits the diagram, Esc closes. The text version below has the same content.

Where a step quotes a number, it is the default in the CISO Times pack. Your own standard may set a different one.

Read as text

The same flow written out: each step, its reasoning and where the pack covers it. 20 steps.
  1. Start

    Something does not meet a requirement

    It came from an internal audit, an incident or a complaint. The route is the same whatever the source, and the log should hold all three: the pack's checklist warns against logs that hold only audit findings. If a certification body raised it, its own deadlines apply and the route differs; see the linked question.

    In the pack

  2. Decision

    Is a requirement of the standard, your policy or a contract not met?

    A nonconformity is a requirement not met. A weakness that breaks no requirement, or an idea that would make a control work better, is an observation. If you are not sure which, answer yes and let the auditor or ISMS manager grade it.

    In the pack

  3. Step

    Record it as an observation and take it to the management review

    Observations are recorded and considered at the management review, but not tracked as nonconformities. Bring them as improvement opportunities with a note of the effect expected.

    In the pack

  4. Outcome

    Observation recorded: no corrective action required

    Keep the note. Do not downgrade a real nonconformity to an observation to avoid the work. The pack grades by effect, not by embarrassment.

    In the pack

  5. Step

    Log it with its source, date and owner

    One log for all sources lets you see repeats. Record what happened, the requirement, the evidence and who owns the response.

    In the pack

  6. Decision

    Is it missed altogether, or widespread enough to doubt the ISMS?

    The pack grades by effect: a major is a requirement not met at all, or a failure widespread or repeated enough to doubt the system. A minor is a partial lapse where the system still works. When in doubt between the two, take more samples.

    In the pack

  7. Step

    Tell the executive sponsor at once

    By the pack's default the sponsor hears of a major internal finding at once, and within 2 working days of the closing meeting at the latest. Treat every internal major as a blocker for the certification audit.

  8. Step

    Correct the problem now and deal with the consequences

    Fix the immediate problem: the missing record, the leaver's account, the overdue review. A correction does not stop it happening again, so do not close the finding here.

    In the pack

  9. Step

    Find the root cause: ask why until it is something you can change

    Keep asking until the answer is a process step, a responsibility, a tool or a missing reminder. 'Human error' is never a root cause on its own. The pack's default is within 10 working days of the report.

    In the pack

  10. Step

    Set an owned, dated action; widen it if the cause acts elsewhere

    The action removes the cause. Check whether the same cause could produce the same nonconformity elsewhere and extend the action if so. Enter it in the gap tracker or your own log. The pack's defaults for internal findings are 30 calendar days to complete a major and 90 for a minor. Make the action fit the size of the effects.

    In the pack

  11. Decision

    Is the action complete by its date?

    Check at each review of the log. An action past its date goes to the executive sponsor and is named in the monthly readiness review and the management review. If you are not sure it is finished, answer no.

    In the pack

  12. Step

    Escalate to the executive sponsor and name it in the review

    Ask for a decision: resource, a new date with a reason, or a change to the action. An overdue corrective action counts as a gap overdue in the readiness measures.

  13. Step

    Check it with new samples taken after the action

    After the action has had time to work, take samples from the period after it and confirm the cause is gone. The check is done by the auditor or someone else independent of the action, within 60 calendar days of the action being complete, the pack's default.

    In the pack

  14. Decision

    Does the check show the cause is gone?

    Read the new samples against the requirement. The same failure in the new period means the cause is still there. If the evidence is thin, answer no and take more samples.

    In the pack

  15. Step

    Close the finding on the check, and change the ISMS if needed

    Never close a finding on the owner's word alone. If the cause sat in a process, a control or a risk, update that document or risk entry now. Then include the item in the report to the management review.

    In the pack

  16. Step

    Reopen it with a new root cause

    The first root cause was wrong or the action did not reach it. Go back to the cause with the new evidence, and set a new action.

    In the pack

  17. Decision

    Has the check on this finding now failed twice?

    Two failures mean the process is not able to fix this by itself. The pack escalates an effectiveness check that fails twice to top management.

    In the pack

  18. Outcome

    Take it to top management for a decision

    Ask for resource, a change of design or an acceptance of the consequence. Do not tell a customer or a certification body that the problem is fixed until a check has passed.

    In the pack

  19. Step

    Report the log to the management review

    Show nonconformities opened, closed, overdue and repeated, and the effectiveness checks passed. The review reads them with the audit results and the measures, and decides what needs action.

    In the pack

  20. Outcome

    Closed on evidence: the log shows the whole route

    An auditor can now trace one finding from its source to its closed check. Do not describe a finding as fixed on the correction alone. Your certification body's own findings follow its deadlines.

    In the pack

Practical checklist

  1. Log the finding with its source: audit, incident or complaint.
  2. Correct the immediate problem and deal with its consequences.
  3. Ask why until the answer is something the organisation can change; 'human error' alone is not a root cause.
  4. Set the corrective action with an owner and date, and widen it if the cause could act elsewhere.
  5. Check the action with new samples taken after it, by someone independent of the action.
  6. Report the log, including overdue and repeat items, to the management review.

Evidence to have ready

  • A log showing each nonconformity, its correction, root cause, corrective action, owner, date and effectiveness check.
  • The effectiveness record with the new samples.
  • Management review minutes showing the log was reported and overdue items discussed.

Assumptions

  • You run, or will run, an internal audit programme, an incident process and a way to log complaints.
  • The deadlines are the pack's defaults for internal findings. Your own procedure may differ.
  • Someone independent of the fix can check it, such as the internal auditor.

Not covered here