Purpose of Control 8.13
An organisation’s backup operation should encompass a broad range of efforts that improve resilience and protect against loss of business by establishing a robust and tightly managed set of backup jobs, using dedicated software and utilities, with adequate retention levels and agreed upon recovery times.
Control 8.13 advocates for a topic-specific approach to backups that includes bespoke processes for each individual topic, and takes into account the different types of data (and associated risk levels) that organisations process and access throughout their operation.
Attributes Table of Control 8.13
Control 8.13 is a corrective control that maintains risk by implementing policies which enable timely recovery from data and/or system loss or interruption.
Control Type | Information Security Properties | Cybersecurity Concepts | Operational Capabilities | Security Domains |
---|---|---|---|---|
#Corrective | #Integrity | #Recover | #Continuity | #Protection |
#Availability |
Ownership of Control 8.13
Control 8.13 deals with daily backup operations that should be handled by technical support staff with responsibility for the maintenance of the organisation’s network.
As such, ownership of Control 8.13 should reside with the individual responsible for the organisation’s day-to-day ICT operation, or the person who oversees an outsourced ICT contract.
Get an 81% headstart
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.
General Guidance on Control 8.13
Organisations should draft topic-specific policies that directly address how the organisation backs up the relevant areas of its network.
Backup facilities should be implemented with the primary aim of ensuring that all business critical data, software and systems are able to be recovered following the below events:
- Data loss
- Intrusion
- Business interruption
- Failure of systems, applications or storage media
Any backup plan created in accordance with Control 8.13 should aim to:
- Outline clear and concise restoration procedures that cover all relevant critical systems and services.
- Produce workable copies of any systems, data or applications that are covered under a backup job.
- Meet the unique commercial and operational requirements of the organisation (e.g. recovery time objectives, backup types, backup frequency) (see Control 5.30).
- Store backups in an appropriate location that is environmentally protected, physically distinct from the source data in order to prevent total data loss, and securely accessed for maintenance purposes (see Control 8.1).
- Mandate for regular testing of backup jobs, in order to guarantee data availability should the need arise to restore files, systems or applications at a moment’s notice. Backup tests should be measured against the organisation’s agreed recovery times to ensure adherence in the event of data loss or system interruption.
- Encrypt data that has been backed up, in accordance with its risk level.
- Check for data loss before running any backup jobs.
- Implement a reporting system that alerts maintenance staff to the status of backup jobs – including complete or partial failures – so that remedial action can be taken.
- Include data from cloud-based platforms that are not directly managed by the organisation.
- Store backup data in line with a topic-specific retention policy that takes into account the underlying nature and purpose of the data that’s been backed up, including transfer and/or archiving to storage media (see Control 8.10).
Supporting Controls
- 5.30
- 8.1
- 8.10
Manage all your compliance in one place
ISMS.online supports over 100 standards
and regulations, giving you a single
platform for all your compliance needs.
Changes and Differences from ISO 27002:2013
ISO 27002:2022-8.13 replaces ISO 27002:2003-12.3.1 (Information backup).
ISO 27002:2022-8.13 contains the same set of operational standards as its 2003 counterpart, with additional guidance offered in the below areas:
- Checking for data loss before running any backup jobs
- Implementing a reporting system
- Cloud-based platforms
- Storing backups in line with a topic-specific retention and archiving policy
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
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
How ISMS.online Helps
ISMS.online will also help you demonstrate compliance with the ISO 27002 standard by providing a management dashboard, reports and audit logs.
Our cloud-based platform offers:
- An easy to use and customise documentation management system.
- Access to a library of polished, pre-written documentation templates.
- A simplified process for conducting internal audits.
- An efficient method for communicating with management and stakeholders.
- A workflow module to streamline the implementation process.
ISMS.online has all of these features, and more.
Get in touch today to book a demo.