ISO 27002:2022, Control 8.14 – Redundancy of Information Processing Facilities

ISO 27002:2022 Revised Controls

Book a demo

bottom,view,of,modern,skyscrapers,in,business,district,against,blue

Purpose of Control 8.14

An ‘information processing facility’ (IPF) is a broad term used to describe any piece of ICT infrastructure that’s involved in processing data, such as IT equipment, software and physical facilities and locations.

IPFs play a key role in maintaining business continuity and ensuring the smooth operation of an organisation’s ICT network(s). To increase resilience, organisations need to implement measures that increase the redundancy of their IPFs – i.e. fail safe methodologies and processes that mitigate risk to systems and data in the event of failure, misuse or intrusion.

Attributes Table

Control 8.14 is a preventive control that maintains risk by implementing plans and procedures that maintain the continuous operations of information processing facilities, and by proxy, an organisation’s entire ICT network.

Control TypeInformation Security PropertiesCybersecurity ConceptsOperational CapabilitiesSecurity Domains
#Preventive#Availability#Protect #Continuity
#Asset Management
#Protection
#Resilience
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.14

Control 8.14 addresses an organisation’s ability to carry on doing business in the event of critical or minor failures that have the potential to impact resiliency. As such, ownership of 8.14 should reside with the Chief Operating Officer, or organisational equivalent.

General Guidance on Compliance

The overriding goal of Control 8.14 is to increase the availability of what ISO deems to be business services and information systems, which can be interpreted as any aspect of a network that allows the organisation to conduct business.

Control 8.14 advocates for duplication as the primary methods of achieving redundancy across its various IPFs, primarily through maintaining an inventory of spare parts, duplicate components (hardware and software) and additional peripheral devices.

A redundant system is only as good as its alerting facility. As such, organisations should ensure that failed IPFs are detected quickly, and remedial action is taken to either fail over to standby hardware, or to repair the malfunctioning IPF in as quick a time as possible.

When designing and installing redundancy measures, organisations should consider the following:

  1. Entering into a commercial relationship with two separate service providers, to reduce the risk of blanket downtime in the event of a critical event (e.g. an Internet service provider or VoIP provider).
  2. Adhering to redundancy principles when designing data networks (secondary DCs, redundant BUDR systems etc).
  3. Making use of geographically separate locations when contracting out data services, especially in the case of file storage and/or data centre facilities.
  4. Purchasing power systems that have the ability to achieve redundancy either in whole, or in part, as is necessary.
  5. Using load balancing and automatic fail over between two identical, redundant software components or systems, to improve both real time performance and resilience following a critical event. This is of particular importance when considering an operational model that encompasses both public cloud services and on-premise services. Redundant systems should be regularly tested (where possible) whilst in production mode to ensure that fail over systems are operating correctly.
  6. Duplicating physical ICT components both within servers and file storage locations (RAID arrays, CPUs), and any that act as a network device (firewalls, redundant switches). Firmware updates should be performed on all linked and redundant devices, to ensure continuity.

Get a Headstart
on ISO 27002

The only compliance
solution you need
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.14

Control 8.14 acknowledges the inherent link between robust, redundant systems and business continuity planning (see Control 5.30), and asks organisations to consider both as part of the solution to the same set of challenges.

It’s important to note that where business applications are concerned, it is extremely difficult to cater for critical errors in the application itself (particularly in the case of managed applications).

Supporting Controls

  • 5.30

Changes and Differences from ISO 27002:2013

ISO 27002:2022-8.14 replaces ISO 27002:2003-17.2.1 (Availability of information processing facilities).

27002:2022-8.14 is an enormous operational leap from 27002:2003-17.2.1, with the difference between the two controls representing the largest change throughout the entire ISO 27002:2022 update.

27002:2003-17.2.1 contains just a few cursory paragraphs on the need to achieve redundancy, whereas 27002:2022-8.14 contains extensive guidance on precisely how to achieve this across on-premise, cloud-based, logical and physical components.

How ISMS.online Helps

At ISMS.online, we’ve built a comprehensive and easy to use system that can help you to implement ISO 27002 controls and manage your entire ISMS.

ISMS.online makes implementing ISO 27002 easier by providing a set of tools to help you manage information security in your organisation. It will help you identify risks and develop controls to mitigate those risks, and then show you how to implement them within the organisation.

Contact us today to schedule 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
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