Skip to content

What is Control 5.8 – Information Security in Project Management?

Control 5.8 covers the need for organisations to ensure that information security is integrated into project management.

Information Security Explained

Information security, sometimes shortened to InfoSec, is the practice of defending information from unauthorised access, use, disclosure, disruption, modification, perusal, inspection, recording or destruction. It is a general term that can be used regardless of the form the data may take (e.g., electronic, physical).

Information security’s primary focus is the balanced protection of the confidentiality, integrity and availability of data (also known as the CIA triad) while maintaining a focus on efficient policy implementation, all without hampering organisation productivity.

The field covers all the processes and mechanisms by which digital equipment, information and services are protected from unintended or unauthorised access, change or destruction. Information security pros are employed in many different industries — from finance to government to health care to academics and from small one-person companies to large multinational organisations.

Project Management Explained

Project management is a large part of business. It’s about planning, organising and managing resources for the completion of a specific goal.

Project management focuses on a project, which is an identified piece of work that requires inputs from various people or groups to produce specific outputs.

Basically, it involves determining the goal of the project and dividing it into several subtasks. A project manager then works with the team to complete each task in time for the overall goal to be completed.

Project management may sound like something only a big corporation needs. But it’s valuable to any kind of business. After all, even small businesses have projects they need to complete.

Information Security in Project Management

As more and more businesses handle their activities online, it’s no surprise that information security in project management has become a hot topic. Project managers are dealing with an increasing number of people working outside of the office, as well as employees using their personal devices for work purposes.

By creating a security policy for your business, you’ll be able to minimise the risk of a breach or data loss and ensure that you’re able to produce accurate reports on project status and finances at any given time.

The best way to include information security in the project planning and execution process is to:

  • Define the information security requirements for the project, including business needs and legal obligations.
  • Assess the risk impacts from information security threats.
  • Manage the risk impacts by implementing appropriate controls and processes.
  • Monitor and report on the effectiveness of these controls.

To protect your business projects, you need to make sure that all project managers are aware of information security and follow it as they complete their work.




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.




Attributes Table of Control 5.8

Controls are classified using attributes. Using these, you can quickly match your control selection with commonly used industry terms and specifications. In control 5.8, the attributes are:

Control Type Information Security Properties Cybersecurity Concepts Operational Capabilities Security Domains
#Preventive #Confidentiality #Identify #Governance #Governance and Ecosystem
#Integrity #Protect #Protection
#Availability

What Is The Purpose of Control 5.8?

The purpose of this control according to ISO 27002:2022 is to ensure information security risks related to projects and deliverables are effectively addressed in project management throughout the project life cycle.

Information security is a key consideration for project management and projects.

Control 5.8 covers the control, purpose and implementation guidance for integrating information security in project management according to the framework as defined by ISO 27001.

Control 5.8 understands that project management requires the coordination of resources, including information assets, to achieve a defined business goal. This is because projects often include new business processes and systems, which have information security implications.

Projects may also span multiple departments and organisations, meaning that control 5.8 objectives, which is all about ensuring that proper information security protocols are in place, need to be coordinated across internal and external stakeholders.

This control can be viewed as a guideline that identifies information security issues in projects, and ensures these issues are addressed throughout the project lifecycle.

What Is Involved and How to Meet the Requirements

It’s important to integrate information security into project management because this provides the opportunity for organisations to ensure that information security risks are identified, evaluated, and addressed as part of the project management.

For example, if an organisation wants to implement a new product development system, they can identify the information security risks associated with a new product development system – such as unauthorised disclosure of proprietary company information – and take steps to mitigate those risks.

Therefore, to meet the requirements for the new ISO 27002:2022, the information security manager should work with the project manager to ensure that information security risk is identified, assessed, and addressed as part of the project management processes. Information security should be integrated into project management so that it is a “part of the project” rather than something that is done “to the project.”

According to control 5.8, the project management in use should require that:

  • information security risks are assessed and treated at an early stage and periodically as part of project risks throughout the project life cycle.
  • information security requirements [e.g. application security requirements (8.26), requirements for complying with intellectual property rights (5.32), etc.] are addressed in the early stages of
    projects.
  • information security risks associated with the execution of projects, such as security of internal and external communication aspects are considered and treated throughout the project life cycle.
  • progress on information security risk treatment is reviewed and effectiveness of the treatment is evaluated and tested.

The Project Manager (PM) should determine the information security requirements for all types of projects, regardless of its complexity, size, duration, discipline or application area, not only ICT development projects. PMs should be aware of the Information Security Policy and related procedures, and the importance of information security.

More details on the implementation guidelines can be found in the revised ISO 27002:2022.




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.




Differences Between ISO 27002:2013 and ISO 27002:2022

Information Security in Project Management was revised in ISO 27002:2022 to reflect more clarifications in the implementation guidance compared to that of ISO 27002:2013. For example, in ISO 27002:2013, there are 3 points that every project manager should know as it affects information security. But in the 2022 version, this was expanded to 4 points.

Also, control 5.8 in ISO 27002:2022 is not a new control, rather, it is a combination of controls 6.1.5 and 14.1.1 in ISO 27002:2013.

Control 14.1.1 in ISO 27002: 2013 talks about information security related requirements for new information systems or enhancements to existing information systems. The implementation guidelines for control 14.1.1 is similar to the section of control 5.8 that talks about ensuring that the architecture and design of information systems are protected against known threats based on the operational environment.

Control 5.8, although not a new control, brings some important changes to the standard. Plus, combining the two controls in ISO 27002:2022 makes the standard more user friendly.

Who Is In Charge Of This Process?

The Project Manager (PM) is responsible for ensuring that information security is implemented in the life cycle of every project. However, the PM may find it useful to consult an Information Security Officer (ISO) to decide what information security requirements are needed for different types of projects.




climbing

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




What Do These Changes Mean For You?

There are no changes to the ISO/IEC 27001 standard, thus existing ISMS do not need to be updated. Besides, there is a grace period of two years before organisations need to embrace the new standard.

However, because Annex A of ISO/IEC 27001 will be matched with the new ISO/IEC 27002 controls by the end of 2022, it is recommended that activities based on the information presently available on the new ISO/IEC 27002 controls be completed.

For example, organisations can:

  • Take a look at the scope of their ISMS.
  • Refresh the organisation’s information security policy and all other rules to ensure that the relevant references and controls are implemented.
  • Make sure you understand your position in relation to new controls and the standard’s new structure by doing a gap assessment.
  • Incorporate the new information security controls into your risk assessment approach.

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

A cloud-based platform for ISO 27002 implementation, ISMS.online, helps you manage your information security risk management processes easily and effectively.

With our cloud-based platform, you will have access to a library of pre-written policies, procedures, work instructions and forms ready for you.

The ISMS.online platform provides a range of powerful tools that simplify the way you can document, implement, maintain and improve your information security management system (ISMS) and achieve compliance with ISO 27002.

The comprehensive package of tools gives you one central place where you can create a bespoke set of policies and procedures that align with your organisation’s specific risks and needs. It also allows for collaboration between colleagues as well as external partners such as suppliers or third party auditors.

By using a web app specifically designed to help companies implement an Information Security Management System (ISMS) based on ISO 27001, you’ll not only save time, but also increase the security of your organisation.

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 crystal

We’re a Leader in our Field

4/5 Stars
Users Love Us
Leader - Fall 2025
High Performer, Small Business - Fall 2025 UK
Regional Leader - Fall 2025 Europe
Regional Leader - Fall 2025 EMEA
Regional Leader - Fall 2025 UK
High Performer - Fall 2025 Europe Mid-market

"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.