Skip to content
Work smarter with our new enhanced navigation!
See how IO makes compliance easier.
Read the blog

ISO 27002:2022 Control 5.33 – Best Practices for Record Protection

Records are a nebulous concept that some organisations struggle to classify and manage, for compliance purposes.

Records, within the scope of ICT, are another term for the data and information an organisation retains and/or uses to carry out its day to day business activities, including (but not limited to):

  1. Individual events
  2. Transactions
  3. Work processes
  4. Activities
  5. Functions

ISO defines records in the scope of their standards as “any set of information, regardless of its structure or form”, including “a document, a collection of data or other types of information which are created, captured and managed in the course of business”, including a record’s metadata.

Purpose of Control 5.33

Any organisation has an obligation to ensure that the data it holds – including but not limited to any persons, financial information or areas of operation – is kept safe and secure, and internal procedures remain compliant with all prevailing requirements.

Control 5.33 deals with the protection of business records against 5 major events:

  1. Loss
  2. Destruction
  3. Falsification
  4. Unauthorised access
  5. Unauthorised release or publication

Attributes Table

Control 5.33 is a preventive control that maintains risk by creating guidelines and procedures – including retention schedules – that fulfil an organisation’s legal, statutory, regulatory and contractual requirements relating to the protection and availability of any records that it holds.

Control Type Information Security Properties Cybersecurity Concepts Operational Capabilities Security Domains
#Preventive #Confidentiality #Identify #Legal and Compliance #Defence
#Integrity #Protect #Asset Management
#Availability #Information Protection



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.




General Guidance on Control 5.33

Control 5.33 acknowledges that an organisation’s needs are fluid when it comes to the amount and type of records that are required to do business from one day to the next.

As such, Control 5.33 categorises record management into 4 main attributes:

  1. Authenticity
  2. Reliability
  3. Integrity
  4. Useability

Within the scope of these attributes, Control 5.33 asks organisations to:

  1. Draft and publish guidelines that deal with four main functions, alongside topic-specific policies that caters to the underlying nature of the records in question:

    a) Record storage
    b) Record handling chain of custody
    c) Record disposal
    d) Preventing manipulation

  2. Maintain a functional records retention schedule that clearly outlines the length of time that records of differing types should be retained, relating to their individual business function.
  3. Create storage and handling procedures that take into account:

    a) any prevailing laws that deal with commercial record keeping
    b) “community and societal” expectations of how an organisation should handle its records

  4. Implement procedures that destroy records in a safe and appropriate manner the moment they’re not needed (after leaving the retention period).
  5. Classify records for protection (including appropriate retention periods and storage media used) based on their security risk, and various types, including (but not limited to):

    a) Accounting records
    b) Business transactions
    c) Personnel records
    d) Legal records

  6. Ensure that any storage procedures cater for an acceptable timeframe for retrieval, should the organisation be asked to produce them by a third party, or for internal use.
  7. Where electronic media is used to store records, consider and mitigate the possibility of access to or retrieval of records being inhibited by technological amendments, including the retention of cryptographic information (see Control 8.24).
  8. Adhere to manufacturer guidelines when storing or handling records on or via electronic media, including adequate consideration for the natural deterioration of said media.



climbing

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




Changes and Differences from ISO 27002:2013

27002:2022-5.33 replaces 27002:2013-18.1.3 (Protection of records), with various additions in the form of individual guidance points and general processes that need to be adhered to.

In the 2022 control, ISO acknowledge the importance of defining what constitutes a business record. 27002:2022-5.33 contains numerous examples of what ISO considers a record to be (see above), that are absent from 27002:2013-18.1.3.

Control 5.33 also focuses an organisation’s attention on two main guidance points that aren’t contained in its 2013 counterpart (guidelines 1 and 2 above), which in turn form the basis of an organisation’s record policy – in particular, a retention schedule that dictates how long records should be kept for, and any media-specific requirements.

Metadata has also made an appearance in records management for the first time. 27002:2013-18.1.3 contains no mention of it, whereas 27002:2022-5.33 considers it to be an “essential component”.

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

Using ISMS.online you can:

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 mint

We’re a Leader in our Field

4/5 Stars
Users Love Us
Leader - Winter 2026
Regional Leader - Winter 2026 UK
Regional Leader - Winter 2026 EU
Regional Leader- Winter 2026 Mid-market EU
Regional Leader - Winter 2026 EMEA
Regional Leader - Winter 2026 Mid-market EMEA

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