Annex A Controls Explained
ISO 27001 Control 6.4: Disciplinary Process
ISO 27001 Control 6.4 asks for a disciplinary process that covers security breaches. Most businesses already have one. The skill is using it without destroying the reporting culture.
Last Updated: 3 November 2026

Alan Parker, ISO 27001 Consultant & Internal Auditor,
Helping UK SMEs hit ISO 27001 in 90 days.
B.Sc (Hons) Information Systems · Certified ISO 27001 Lead Auditor · CISMP · ITIL Expert · 30+ years in IT governance and security.
Read full bio →
ISO 27001 Control 6.4: Disciplinary Process
https://www.iso.org/standard/27001
A disciplinary process shall be formalized and communicated to take actions against personnel and other relevant interested parties who have committed an information security policy violation.
Key Takeaways
- Control 6.4 asks for a formal, communicated disciplinary process covering information security breaches.
- Most businesses already have one in the handbook or an HR procedure. Check it covers security.
- Intent matters most: was it a mistake, negligence or deliberate?
- Most security events are honest mistakes, and those call for support, not discipline.
- Punishing honest reporting kills the reporting culture, and incidents get worse.
- Keep the formal process for deliberate breaches and persistent negligence.
- For contractors, use contract terms rather than HR procedures.

Table of Contents
Introduction
In short: ISO 27001 control 6.4, disciplinary process, requires a formal, communicated process for dealing with people who breach information security policy. Most small businesses already have one in their HR policies; the control asks you to make sure it covers security and distinguishes honest mistakes from negligence and deliberate acts.
This is one of the controls that is almost always already in place. Every business knows it needs a legal route for dealing with misconduct, so a disciplinary process exists, usually in the employee handbook or as a separate HR procedure.
What is often missing is the connection to information security. Does the process cover security policy breaches? Do staff know it does? And, just as importantly, does the way you use it encourage people to report their mistakes, or frighten them into hiding them?
Control 6.4 is the stick. But in my experience the carrot matters more, and the two have to be balanced. This page covers what the control requires, how to tell a mistake from misconduct, and how to keep a positive, no-blame culture while still having a route for the cases that need it.
What control 6.4 actually asks for
The control requires a disciplinary process to be formalised and communicated, so that action can be taken against personnel and other relevant interested parties who have committed an information security policy violation. In practice:
- A formal process exists. Usually your existing HR disciplinary procedure.
- It covers information security. Security policy breaches are named, or clearly fall within what it covers.
- It is communicated. Staff know that breaching security policies can lead to disciplinary action.
- It is proportionate and fair. Responses take account of intent, impact and whether it has happened before.
- It covers others where relevant. Contractors and suppliers usually through their contracts rather than HR.
In the 2013 edition this was control A.7.2.3. ISO/IEC 27002, the guidance that accompanies the standard, stresses that the process should not start without verification that a breach occurred, and that the response should be graduated.
The process is usually already there
For most small businesses, meeting this control does not mean writing anything new. It means checking three things in the process you already have:
- That information security policy breaches are within its scope. A line listing “serious breaches of the company’s information security or acceptable use policies” among examples of misconduct is enough.
- That it follows the Acas Code of Practice on disciplinary and grievance procedures, which employment tribunals take into account.
- That staff have been told. The information security policy and induction should both mention that breaches can lead to disciplinary action.
For contractors and suppliers, the equivalent is a contract term allowing you to remove their access or end the agreement for security breaches, under control 5.20.
Mistake, negligence or deliberate?
The intent behind an incident matters most. Before deciding how to respond, ask what the person meant to do. Broadly, security breaches by staff fall into three groups, and each calls for a different response.
| What happened | Typical example | Proportionate response |
|---|---|---|
| An honest mistake | Clicked a convincing phishing link and reported it straight away; sent an email to the wrong recipient. | Support, not discipline. Thank them for reporting, fix the issue, and look at whether training or a technical control would prevent a repeat. |
| Negligence | Repeatedly ignoring a known rule, such as leaving devices unlocked in public, after reminders and training. | A conversation, then the informal and formal stages of the disciplinary process if it continues. Check whether the rule is practical first. |
| Deliberate action | Copying client data to a personal account before leaving; sharing credentials knowingly; disabling security controls on purpose. | The formal disciplinary process, following the Acas Code, and possibly legal action. Preserve evidence under control 5.28. |
The overwhelming majority of security events caused by people are honest mistakes. They clicked a link that looked real. They sent an attachment to the wrong Sarah. They forgot to lock a screen. Treating those as disciplinary matters is unfair, and it is also counter-productive, because of what it does to reporting.
Carrot and stick: protecting the reporting culture
My general view is that a positive, no-blame culture of support and assistance works far better than one where people expect to be beaten up for mistakes. The reason is simple: the most valuable thing staff can do in an incident is report it quickly. If people believe reporting a mistake will get them into trouble, they will hide it, and a small problem caught in five minutes becomes a large one discovered in five weeks.
So be explicit about it. Your incident reporting guidance under control 6.8 should say that people who report their own mistakes promptly will be supported, not disciplined. Then make sure that is what happens. One example of someone being punished for honest reporting will undo years of encouragement.
The disciplinary process is still needed. It is the route for deliberate breaches, and for persistent negligence after support and training have failed. Having it, and having it clearly reserved for those cases, is part of what makes the no-blame message credible.
Before you use it
A few practical points for the rare occasions the process is needed for a security breach:
- Establish the facts first. Logs, emails and records, gathered properly. If there is any chance of legal action, follow the evidence handling approach in control 5.28.
- Check the rule was known and practical. If the person was never trained, or the rule could not be followed, the problem is the system.
- Take HR advice before accessing someone’s accounts or devices. Monitoring and investigating employees has its own legal requirements.
- Be consistent. Similar breaches should get similar responses, whoever was involved.
- Fix the cause too. Even a deliberate breach usually reveals a control that should have stopped it.
What auditors will look for
I rarely see this process used, so I test whether it exists and whether people know about it.
- The process. Where is it, and does it cover information security breaches?
- Communication. How do staff know? I will look in the security policy, the handbook and the induction material.
- Proportionality. Does it take account of intent and severity, or is every breach treated the same?
- Contractors. What happens if a contractor breaches a policy?
- Use in practice. If it has been used for a security matter, I may ask how. If it has not, I will ask how recent incidents caused by people were handled instead.
Common issues
- A disciplinary process that does not mention information security at all.
- Staff unaware that security breaches can be a disciplinary matter.
- Honest mistakes treated as misconduct, so people stop reporting.
- No route for dealing with contractors who breach policies.
- Inconsistent treatment, with senior staff held to different standards.
- Investigations that access employees’ accounts without HR or legal advice.
The self-check
Imagine someone has just reported their own mistake.
- Does your disciplinary process cover information security breaches?
- Would your staff say that reporting their own mistake is safe?
- How was the last security incident caused by a person handled?
- What would you do if a contractor deliberately breached a policy?
- Is the line between mistake and misconduct written down anywhere?
The second is the one to sit with. The answer tells you more about your security culture than any policy.
What I see in audits
Almost none of the disciplinary policies I see mention information security specifically. Of the roughly 30 organisations I have audited or implemented ISO 27001 for since 2024, I would put it at around one in ten, and that is being generous (see my findings).
That is not automatically a finding. Often the link is made from the other direction: the information security policy says that failing to follow it may lead to disciplinary action, or the staff handbook covers it somewhere. That is fine, provided something clearly traces the consequences of a security breach back to the individual. What I usually find is that the link exists but is flimsy at best: a single generic line in one document, never referenced anywhere else, and unknown to most staff.
The fix takes an afternoon. Add a sentence to the disciplinary policy that names information security breaches, reference it from the security policy, and make sure it distinguishes honest mistakes from negligence and deliberate acts, as described above.
How control 6.4 links to other clauses and controls
- Control 6.2, Terms and conditions of employment. The contract tells staff that breaches can have consequences.
- Control 6.3, Information security awareness, education and training. The first response to most people problems.
- Control 6.8, Information security event reporting. The reporting culture that disciplinary practice can make or break.
- Control 5.28, Collection of evidence. Evidence for a disciplinary case needs to be handled properly.
- Control 5.36, Compliance with policies, rules and standards. When compliance checks find deliberate non-compliance, this is the route.
Frequently asked questions
Do we need a separate disciplinary process for information security?
No. Your existing HR disciplinary process is usually enough, provided it covers information security breaches and staff know it does.
Should staff be disciplined for clicking a phishing link?
Generally not, if it was an honest mistake and they reported it. Disciplining people for mistakes discourages reporting, which makes incidents worse. Reserve discipline for deliberate breaches and persistent negligence.
Does control 6.4 apply to contractors?
It applies to relevant interested parties as well as staff. For contractors and suppliers, that usually means contract terms allowing you to remove access or end the agreement.
What should we check before starting disciplinary action for a security breach?
That a breach actually occurred, that the person knew the rule and could reasonably follow it, and that evidence has been gathered properly. Follow the Acas Code and take HR advice.
Sources and further reading
Official legislation, standards and guidance referred to on this page.
- ISO/IEC 27002:2022. The implementation guidance that accompanies the controls.
- Acas Code of Practice on disciplinary and grievance procedures. The statutory code employment tribunals take into account.
- Phishing attacks: defending your organisation. NCSC guidance, including why punishing people who click is counter-productive.
- Employment information. ICO guidance on monitoring and handling workers’ personal data during investigations.
- ISO/IEC 27001:2022, Information security management systems. The standard itself, published by ISO.
Internal Audit Service
Get an independent view of your ISO 27001 ISMS before you go into an audit.
“Alan from Iseo Blue truly came to our rescue. His support ahead of our internal audit was outstanding, and he helped us get our ISMS 100% ready for the Phase 2 audit.“
– Quartile.
✓ Gain confidence
✓ Audit plan
✓ Independent view
✓ An ISO 27001 requirement
✓ Audit findings report
✓ Recommendations
✓ Review meeting
✓ Fixed price
