Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Have a formal, communicated disciplinary process for people who break security rules.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
A disciplinary process helps the organization respond consistently when security rules are broken, but it must be fair, documented, and coordinated with HR, line management, and legal requirements. If staff only hear about sanctions after an incident, the process can feel arbitrary and may fail to deter repeated misuse of systems, data, or credentials. Clear steps also protect investigations by separating fact finding from disciplinary decisions.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Security breaches are handled informally by managers, so similar misconduct receives inconsistent treatment and the rationale for outcomes is not recorded.
The process mentions sanctions but does not explain investigation steps, evidence handling, or employee response rights, creating procedural gaps before discipline is imposed.
Acceptable use rules reference discipline, yet staff cannot find the actual procedure or escalation path, weakening notice and consistency across teams.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Publish a disciplinary procedure that sets out stages for allegation intake, fact finding, temporary safeguards, decision making, appeal, and closure. Keep HR as process owner, with line managers and ISMS leads accountable for timely reporting and evidence preservation. Define a fair threshold for immediate containment, such as suspension of access, while making clear that access changes do not replace the disciplinary review.
Map common security violations to graduated responses, such as coaching, written warning, retraining, restricted access, or dismissal, depending on intent, impact, and repetition. Use decision criteria that consider negligence, maliciousness, prior history, and whether the person cooperated. Link the process to legal, contractual, and privacy obligations so investigations remain proportionate and confidential.
Train managers on what they can and cannot do during a case: preserve logs, avoid informal interrogation, record dates and witnesses, and avoid tampering with evidence. Ensure the individual has a chance to respond before final sanction unless urgent containment is necessary. For serious or repeated violations, require a second-level review or HR sign-off to reduce bias and uneven outcomes.
Keep records of allegations, interview notes, evidence reviewed, decisions, approvals, sanctions, appeals, and remediation actions. Trend repeat issues by team or process to identify whether poor controls, weak training, or unrealistic procedures are driving misconduct. Feed lessons into policy updates, awareness material, and access review changes so discipline supports improvement rather than only punishment.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.