Skip to content
Work smarter with our new enhanced navigation!
See how IO makes compliance easier.
Read the blog

What Is Control 6.4?

ISO 27002:2022, Control 6.4. Disciplinary Process talks about the need for organisations to put in place some form of disciplinary process to serve as a deterrent so that personnel will not commit information security violations.

This process should be formally communicated and a suitable penalty designed for employees and other relevant interested parties who commit an information security policy violation.

Information Security Violation Explained

Information security policy violation is a breach of the rules or laws governing the proper handling of information. Information security policies are established by organisations to protect confidential, proprietary and personal data, such as customer records and credit card numbers. Information security policies also include computer security policies that help ensure the safety and integrity of data stored on computers.

For example, if you don’t have permission from your supervisor to use company email to send personal emails, doing so may result in a violation of company policy. In addition, if you make a mistake while using company equipment or software and cause damage to it or the data stored on it, that could also be considered an information security policy violation.

If an employee violates an organisation’s information security policy, he or she could be subject to disciplinary action or termination from employment. In some cases, a company may choose not to terminate an employee who breaks its computer usage policy, but instead take other appropriate measures to prevent future violations of company policy.

Attributes Table

Controls can be grouped using attributes. When you look at the control’s attributes, you can more easily relate it to established industry requirements and terminology. The following attributes are in control 6.4.

Control Type Information Security Properties Cybersecurity Concepts Operational Capabilities Security Domains
#Preventive #Confidentiality #Protect #Human Resource Security #Governance and Ecosystem
#Corrective #Integrity #Respond
#Availability



ISMS.online gives you an 81% Headstart from the moment you log on

ISO 27001 made easy

We’ve done the hard work for you, giving you an 81% Headstart from the moment you log on. All you have to do is fill in the blanks.




What Is the Purpose of Control 6.4?

The purpose of the disciplinary process is to ensure personnel and other relevant interested parties understand the consequences of an information security policy violation.

Apart from ensuring that employees and other relevant interested parties understand the consequences of information security policy violations, control 6.4 is designed to deter and help deal with those that violate these policies.

A key element of an effective information security programme is the ability to implement appropriate disciplinary actions for employees who violate information security policies and procedures. This way, employees are aware of the consequences of violating established policies and procedures, thus reducing the potential for intentional or accidental data breaches.

The following are examples of activities that may be included when implementing this control:

  • Conduct periodic training sessions on policy changes;
  • Design disciplinary actions for non-compliance with information security policies;
  • Provide a copy of the organisation’s disciplinary procedures to each employee;
  • Ensure that disciplinary procedures are followed consistently in similar situations.

The disciplinary actions spelled out in the framework/document should be taken promptly following an incident, to discourage others who may want to violate organisational policies.

What Is Involved and How to Meet the Requirements

To meet the requirements of control 6.4, disciplinary action must be taken when there is evidence of non-compliance with the policies, procedures, or regulations of the organisation. This includes non-compliance with legislation and regulations that apply to the organisation.

According to control 6.4, the formal disciplinary process should provide for a graduated response that takes into consideration the following factors:

  1. The nature (who, what, when, how), gravity, and consequences of the breach;
  2. Whether the offence was malicious (intentional) or unintentional (accidental);
  3. Whether this is the first or second offence;
  4. Whether or not the violator received adequate training.

The action should take into account all pertinent legal, legislative, regulatory, contractual, and corporate obligations, as well as any other pertinent circumstances.




climbing

Embed, expand and scale your compliance, without the mess. IO gives you the resilience and confidence to grow securely.




Changes and Differences from ISO 27002:2013

If you are familiar with ISO 27002:2013, you will know that even though the control identity/ number has been changed, control 6.4 in ISO 27002:2022 is not exactly a new control. Rather, it is a modified version of control 7.2.3 in ISO 27002:2013.

That said, there are no significant differences between the two controls in both versions of ISO 27002. The little difference you will notice is that the control number has been changed from 7.23 to 6.4. Also, in the 2022 version of the standard, the attributes table and statement of purpose have been included. These two features are not in the 2013 version.

Aside from their different wording, these controls are basically identical in terms of their content and context. User-friendly terminology was used in ISO 27002:2022 to make sure that the standard’s users could better understand its content.

Who Is in Charge of This Process?

In most cases, the disciplinary process is handled by the department manager or human resources representative. It is not uncommon for the HR representative to delegate the responsibility of disciplinary action to someone else in the organisation, such as an information security specialist.

The main purpose of disciplinary action is to protect the organisation against any further violations by the employee. It also aims to prevent similar incidents from reoccurring by ensuring that all employees understand the significance of information security violations.

In order to make sure that disciplinary action is taken against an employee who has violated an organisation’s policies or procedures, it is important that there are clear guidelines for handling such situations. These guidelines should include specific instructions about how to conduct investigations and the actions that should be taken after investigations have been completed.

What Do These Changes Mean for You?

If you are wondering what these changes mean for you, here is a brief breakdown of the most important points:

  • It is not a significant change, so you don’t need to re-certify.
  • You can keep your existing certification until it expires (if it is still valid).
  • There are no major changes in the content of ISO 27002.
  • The focus is more on updating the standard to align with current best practices and standards.

The structure of the standard remains unchanged. Some controls have been amended, though, to clarify their meaning or improve consistency with other parts of the standard.

However, if you are intending on obtaining ISMS certification, you may need to examine your security procedures to verify they are in compliance with the revised standard.

To learn more about how the new ISO 27002 may affect your information security operations and ISO 27001 certification, please check out our free ISO 27002:2022 guide.




ISMS.online supports over 100 standards and regulations, giving you a single platform for all your compliance needs.

ISMS.online supports over 100 standards and regulations, giving you a single platform for all your compliance needs.




New ISO 27002 Controls

New Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
5.7 NEW Threat intelligence
5.23 NEW Information security for use of cloud services
5.30 NEW ICT readiness for business continuity
7.4 NEW Physical security monitoring
8.9 NEW Configuration management
8.10 NEW Information deletion
8.11 NEW Data masking
8.12 NEW Data leakage prevention
8.16 NEW Monitoring activities
8.23 NEW Web filtering
8.28 NEW Secure coding
Organisational Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
5.1 05.1.1, 05.1.2 Policies for information security
5.2 06.1.1 Information security roles and responsibilities
5.3 06.1.2 Segregation of duties
5.4 07.2.1 Management responsibilities
5.5 06.1.3 Contact with authorities
5.6 06.1.4 Contact with special interest groups
5.7 NEW Threat intelligence
5.8 06.1.5, 14.1.1 Information security in project management
5.9 08.1.1, 08.1.2 Inventory of information and other associated assets
5.10 08.1.3, 08.2.3 Acceptable use of information and other associated assets
5.11 08.1.4 Return of assets
5.12 08.2.1 Classification of information
5.13 08.2.2 Labelling of information
5.14 13.2.1, 13.2.2, 13.2.3 Information transfer
5.15 09.1.1, 09.1.2 Access control
5.16 09.2.1 Identity management
5.17 09.2.4, 09.3.1, 09.4.3 Authentication information
5.18 09.2.2, 09.2.5, 09.2.6 Access rights
5.19 15.1.1 Information security in supplier relationships
5.20 15.1.2 Addressing information security within supplier agreements
5.21 15.1.3 Managing information security in the ICT supply chain
5.22 15.2.1, 15.2.2 Monitoring, review and change management of supplier services
5.23 NEW Information security for use of cloud services
5.24 16.1.1 Information security incident management planning and preparation
5.25 16.1.4 Assessment and decision on information security events
5.26 16.1.5 Response to information security incidents
5.27 16.1.6 Learning from information security incidents
5.28 16.1.7 Collection of evidence
5.29 17.1.1, 17.1.2, 17.1.3 Information security during disruption
5.30 5.30 ICT readiness for business continuity
5.31 18.1.1, 18.1.5 Legal, statutory, regulatory and contractual requirements
5.32 18.1.2 Intellectual property rights
5.33 18.1.3 Protection of records
5.34 18.1.4 Privacy and protection of PII
5.35 18.2.1 Independent review of information security
5.36 18.2.2, 18.2.3 Compliance with policies, rules and standards for information security
5.37 12.1.1 Documented operating procedures
People Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
6.1 07.1.1 Screening
6.2 07.1.2 Terms and conditions of employment
6.3 07.2.2 Information security awareness, education and training
6.4 07.2.3 Disciplinary process
6.5 07.3.1 Responsibilities after termination or change of employment
6.6 13.2.4 Confidentiality or non-disclosure agreements
6.7 06.2.2 Remote working
6.8 16.1.2, 16.1.3 Information security event reporting
Physical Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
7.1 11.1.1 Physical security perimeters
7.2 11.1.2, 11.1.6 Physical entry
7.3 11.1.3 Securing offices, rooms and facilities
7.4 NEW Physical security monitoring
7.5 11.1.4 Protecting against physical and environmental threats
7.6 11.1.5 Working in secure areas
7.7 11.2.9 Clear desk and clear screen
7.8 11.2.1 Equipment siting and protection
7.9 11.2.6 Security of assets off-premises
7.10 08.3.1, 08.3.2, 08.3.3, 11.2.5 Storage media
7.11 11.2.2 Supporting utilities
7.12 11.2.3 Cabling security
7.13 11.2.4 Equipment maintenance
7.14 11.2.7 Secure disposal or re-use of equipment
Technological Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
8.1 06.2.1, 11.2.8 User endpoint devices
8.2 09.2.3 Privileged access rights
8.3 09.4.1 Information access restriction
8.4 09.4.5 Access to source code
8.5 09.4.2 Secure authentication
8.6 12.1.3 Capacity management
8.7 12.2.1 Protection against malware
8.8 12.6.1, 18.2.3 Management of technical vulnerabilities
8.9 NEW Configuration management
8.10 NEW Information deletion
8.11 NEW Data masking
8.12 NEW Data leakage prevention
8.13 12.3.1 Information backup
8.14 17.2.1 Redundancy of information processing facilities
8.15 12.4.1, 12.4.2, 12.4.3 Logging
8.16 NEW Monitoring activities
8.17 12.4.4 Clock synchronization
8.18 09.4.4 Use of privileged utility programs
8.19 12.5.1, 12.6.2 Installation of software on operational systems
8.20 13.1.1 Networks security
8.21 13.1.2 Security of network services
8.22 13.1.3 Segregation of networks
8.23 NEW Web filtering
8.24 10.1.1, 10.1.2 Use of cryptography
8.25 14.2.1 Secure development life cycle
8.26 14.1.2, 14.1.3 Application security requirements
8.27 14.2.5 Secure system architecture and engineering principles
8.28 NEW Secure coding
8.29 14.2.8, 14.2.9 Security testing in development and acceptance
8.30 14.2.7 Outsourced development
8.31 12.1.4, 14.2.6 Separation of development, test and production environments
8.32 12.1.2, 14.2.2, 14.2.3, 14.2.4 Change management
8.33 14.3.1 Test information
8.34 12.7.1 Protection of information systems during audit testing

How ISMS.Online Helps

ISMS.Online is the leading ISO 27002 management system software that supports compliance with ISO 27002, and helps companies to align their security policies and procedures with the standard.

The cloud-based platform provides a complete set of tools to assist organisations in setting up an information security management system (ISMS) according to ISO 27002.

These tools include:

  • A library of templates for common corporate documents;
  • A set of predefined policies and procedures;
  • An audit tool to support internal audits;
  • An interface for customising ISMS policies and procedures;
  • An approval workflow for all changes made to policies and procedures;
  • A checklist for making sure that your policies and information security processes follow the approved international standards.

ISMS.Online also allows users to:

ISMS.Online also provides guidance on how to best implement your ISMS by providing tips on how to create policies and procedures related to aspects such as risk management, personnel security awareness training, and incident response planning.

Our platform has been designed from scratch with the help of information security experts from around the world, and we have developed it in a way that makes it easy for people without any technical knowledge about information security management systems (ISMS) to use it.

Want to see it in action?

Get in touch today to book a demo.


Sam Peters

Sam is Chief Product Officer at ISMS.online and leads the development on all product features and functionality. Sam is an expert in many areas of compliance and works with clients on any bespoke or large-scale projects.

Take a virtual tour

Start your free 2-minute interactive demo now and see
ISMS.online in action!

platform dashboard full on mint

We’re a Leader in our Field

4/5 Stars
Users Love Us
Leader - Winter 2026
Regional Leader - Winter 2026 UK
Regional Leader - Winter 2026 EU
Regional Leader- Winter 2026 Mid-market EU
Regional Leader - Winter 2026 EMEA
Regional Leader - Winter 2026 Mid-market EMEA

"ISMS.Online, Outstanding tool for Regulatory Compliance"

— Jim M.

"Makes external audits a breeze and links all aspects of your ISMS together seamlessly"

— Karen C.

"Innovative solution to managing ISO and other accreditations"

— Ben H.