ISO 27002:2022, Control 6.4 – Disciplinary Process

ISO 27002:2022 Revised Controls

Book a demo

modern,office,building,on,a,clear,sky,background

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 TypeInformation Security Properties Cybersecurity Concepts Operational Capabilities Security Domains
#Preventive
#Corrective
#Confidentiality
#Integrity
#Availability
#Protect
#Respond
#Human Resource Security#Governance and Ecosystem
Get a Headstart on ISO 27001
  • All updated with the 2022 control set
  • Make 81% progress from the minute you log in
  • Simple and easy to use
Book your demo
img

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.

Get a Headstart
on ISO 27002

The only compliance
solution you need
Book your demo

Simple. Secure. Sustainable.

See our platform in action with a tailored hands-on session based on your needs and goals.

Book your demo
img

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.

Discover our platform

Book a tailored hands-on session
based on your needs and goals
Book your demo

Updated for ISO 27001 2022
  • 81% of the work done for you
  • Assured Results Method for certification success
  • Save time, money and hassle
Book your demo
img

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.

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.

Are you ready for
the new ISO 27002

We’ll give you an 81% headstart
from the moment you log in
Book your demo

New Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
5.7NewThreat intelligence
5.23NewInformation security for use of cloud services
5.30NewICT readiness for business continuity
7.4NewPhysical security monitoring
8.9NewConfiguration management
8.10NewInformation deletion
8.11NewData masking
8.12NewData leakage prevention
8.16NewMonitoring activities
8.23NewWeb filtering
8.28NewSecure coding

Organisational Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
5.105.1.1, 05.1.2Policies for information security
5.206.1.1Information security roles and responsibilities
5.306.1.2Segregation of duties
5.407.2.1Management responsibilities
5.506.1.3Contact with authorities
5.606.1.4Contact with special interest groups
5.7NewThreat intelligence
5.806.1.5, 14.1.1Information security in project management
5.908.1.1, 08.1.2Inventory of information and other associated assets
5.1008.1.3, 08.2.3Acceptable use of information and other associated assets
5.1108.1.4Return of assets
5.12 08.2.1Classification of information
5.1308.2.2Labelling of information
5.1413.2.1, 13.2.2, 13.2.3Information transfer
5.1509.1.1, 09.1.2Access control
5.1609.2.1Identity management
5.17 09.2.4, 09.3.1, 09.4.3Authentication information
5.1809.2.2, 09.2.5, 09.2.6Access rights
5.1915.1.1Information security in supplier relationships
5.2015.1.2Addressing information security within supplier agreements
5.2115.1.3Managing information security in the ICT supply chain
5.2215.2.1, 15.2.2Monitoring, review and change management of supplier services
5.23NewInformation security for use of cloud services
5.2416.1.1Information security incident management planning and preparation
5.2516.1.4Assessment and decision on information security events
5.2616.1.5Response to information security incidents
5.2716.1.6Learning from information security incidents
5.2816.1.7Collection of evidence
5.2917.1.1, 17.1.2, 17.1.3Information security during disruption
5.30NewICT readiness for business continuity
5.3118.1.1, 18.1.5Legal, statutory, regulatory and contractual requirements
5.3218.1.2Intellectual property rights
5.3318.1.3Protection of records
5.3418.1.4Privacy and protection of PII
5.3518.2.1Independent review of information security
5.3618.2.2, 18.2.3Compliance with policies, rules and standards for information security
5.3712.1.1Documented operating procedures

People Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
6.107.1.1Screening
6.207.1.2Terms and conditions of employment
6.307.2.2Information security awareness, education and training
6.407.2.3Disciplinary process
6.507.3.1Responsibilities after termination or change of employment
6.613.2.4Confidentiality or non-disclosure agreements
6.706.2.2Remote working
6.816.1.2, 16.1.3Information security event reporting

Physical Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
7.111.1.1Physical security perimeters
7.211.1.2, 11.1.6Physical entry
7.311.1.3Securing offices, rooms and facilities
7.4NewPhysical security monitoring
7.511.1.4Protecting against physical and environmental threats
7.611.1.5Working in secure areas
7.711.2.9Clear desk and clear screen
7.811.2.1Equipment siting and protection
7.911.2.6Security of assets off-premises
7.1008.3.1, 08.3.2, 08.3.3, 11.2.5Storage media
7.1111.2.2Supporting utilities
7.1211.2.3Cabling security
7.1311.2.4Equipment maintenance
7.1411.2.7Secure disposal or re-use of equipment

Technological Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
8.106.2.1, 11.2.8User endpoint devices
8.209.2.3Privileged access rights
8.309.4.1Information access restriction
8.409.4.5Access to source code
8.509.4.2Secure authentication
8.612.1.3Capacity management
8.712.2.1Protection against malware
8.812.6.1, 18.2.3Management of technical vulnerabilities
8.9NewConfiguration management
8.10NewInformation deletion
8.11NewData masking
8.12NewData leakage prevention
8.1312.3.1Information backup
8.1417.2.1Redundancy of information processing facilities
8.1512.4.1, 12.4.2, 12.4.3Logging
8.16NewMonitoring activities
8.1712.4.4Clock synchronization
8.1809.4.4Use of privileged utility programs
8.1912.5.1, 12.6.2Installation of software on operational systems
8.2013.1.1Networks security
8.2113.1.2Security of network services
8.2213.1.3Segregation of networks
8.23NewWeb filtering
8.2410.1.1, 10.1.2Use of cryptography
8.2514.2.1Secure development life cycle
8.2614.1.2, 14.1.3Application security requirements
8.2714.2.5Secure system architecture and engineering principles
8.28NewSecure coding
8.2914.2.8, 14.2.9Security testing in development and acceptance
8.3014.2.7Outsourced development
8.3112.1.4, 14.2.6Separation of development, test and production environments
8.3212.1.2, 14.2.2, 14.2.3, 14.2.4Change management
8.3314.3.1Test information
8.3412.7.1Protection of information systems during audit testing
Say hello to ISO 27001 success

Get 81% of the work done for you and get certified faster with ISMS.online

Book your demo
img

Explore ISMS.online's platform with a self-guided tour - Start Now