ISO 27002:2022, Control 8.31 – Separation of Development, Test and Production Environments

ISO 27002:2022 Revised Controls

Book a demo

office,building.,skyscraper.,exterior,of,building

Failure to properly segregate development, test, and production environments may result in loss of availability, confidentiality, and integrity of information assets.

For example, Uber accidentally published a code repository on Github that contained passwords of users from the production environment, resulting in the loss of confidentiality of sensitive information.

Therefore, organisations should implement appropriate procedures and controls to securely segregate development, test, and production environments to eliminate security risks.

Purpose of Control 8.31

Control 8.31 enables organisations to maintain the confidentiality, integrity, and availability of sensitive information assets by segregating developing, testing, and production environments through appropriate procedures, controls, and policies.

Attributes Table

Control 8.31 is preventive in nature and it requires organisations to preemptively establish and apply processes and technical controls to securely separate the development, testing, and production environments.

Control Type Information Security PropertiesCybersecurity Concepts Operational CapabilitiesSecurity Domains
#Preventive #Confidentiality
#Integrity
#Availability
#Protect #Application Security
#System and Network Security
#Protection
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

Ownership of Control 8.31

Considering that Control 8.31 entails the establishment and implementation of organisation-wide processes and controls to segregate different software environments, chief information security officer, with help of the development team, shall be ultimately responsible for compliance.

General Guidance on Compliance

Organisations should take into account the potential production problems that should be prevented when determining the required level of separation between the three environments.

In particular, Control 8.31 recommends organisations consider the following seven criteria:

  1. Segregation and operation of development and production systems to an adequate degree. For example, the use of separate virtual and physical environments for production could be an effective method.
  2. Appropriate rules and authorisation procedures should be established, documented, and applied for the use of software in the production environment after going through the development environment.
  3. Organisations should review and test changes made to applications and production systems in a test environment separate from the production environment before these changes are used in the production environment.
  4. Testing in production environments should not be allowed unless such testing is defined and approved prior to testing.
  5. Development tools such as compilers and editors should not be accessible from the production environments unless this access is absolutely necessary.
  6. To minimise errors, proper environment identification labels should be prominently displayed in menus.
  7. Sensitive information assets should not be transferred into development and testing environments unless equivalent security measures are applied in the development and testing systems.

Supplementary Guidance on Protection of Development and Testing Environments

Organisations should protect development and testing environments against security risks taking into account the following:

  • All development, integration, and testing tools such as builders, integrators, and libraries should be regularly patched and updated.
  • All systems and software should be configured securely.
  • Access to environments should be subject to appropriate controls.
  • Changes to environments and code stored in it should be monitored and reviewed.
  • Environments should be securely monitored and reviewed.
  • Environments should be backed-up.

Furthermore, no single individual should be given the privilege to make changes in both development and production environments without obtaining approval first. To prevent this, organisations can segregate access rights or establish and implement access controls.

In addition, organisations can also consider extra technical controls such as logging of all access activities and real-time monitoring of all access to these environments.

Are you ready for
the new ISO 27002

We’ll give you an 81% headstart
from the moment you log in
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

Supplementary Guidance on Control 8.31

If organisations fail to implement necessary measures, their information systems can face significant security risks.

For instance, developers and testers with access to the production environment may make unwanted changes to files or system environments, execute unauthorised code, or accidentally disclose sensitive information.

Therefore, organisations need a stable environment to perform robust testing on the code and to prevent developers from accessing the production environments where sensitive real-world data is hosted and processed.

Organisations should also apply measures such as designated roles together with separation of duty requirements.

Another threat to the confidentiality of production data is the development and testing personnel. When the development and testing teams perform their activities using the same computing devices, they may accidentally make changes to sensitive information or software programs.

Organisations are advised to establish supporting processes for the use of the production data in testing and development systems in compliance with Control 8.33.

Moreover, organisations should take into account the measures addressed in this Control when they perform end-user training in training environments.

Last but not the least, organisations may deliberately blur the lines between development, testing, and production environments. For instance, testing can be performed in a development environment or product testing can be carried out by actual use of the product by staff in the organisation.

Changes and Differences from ISO 27002:2013

27002:2022/8.31 replaces 27002:2013/(12.1.4 and 14.2.6)

While the two versions are similar to a great extent, there are two differences that should be highlighted.

Control 14.2.6 in the 2013 Version Provided More Detailed Guidance on Secure Development Environments

Control 14.2.6 in the 2013 version addresses secure development environments and lists 10 recommendations that organisations should take into account when building a development environment.

The 2022 version, in contrast, did not contain some of these recommendations such as back-up at an off-site location and restrictions on the transfer of data.

Control 8.31 Addresses Product Testing and the Use of Production Data

In contrast to the 2013 version, Control 8.31 in the 2022 Version provides guidance on how product testing should be carried out and on the use of production data in accordance with Control 8.33.

How ISMS.online Helps

The ISMS.Online platform helps with all aspects of implementing ISO 27002, from managing risk assessment activities through to developing policies, procedures and guidelines for complying with the standard’s requirements.

It provides a way to document your findings and communicate them with your team members online. ISMS.Online also allows you to create and save checklists for all of the tasks involved in implementing ISO 27002, so that you can easily track the progress of your organisation’s security program.

With its automated toolset, ISMS.Online makes it easy for organisations to demonstrate compliance with the ISO 27002 standard.

Contact us today to schedule a demo.

Get a Headstart
on ISO 27002

The only compliance
solution you need
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
Simple. Secure. Sustainable.

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

Book your demo
img

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