ISO 27002:2022, Control 5.28 – Collection of Evidence

ISO 27002:2022 Revised Controls

Book a demo

woman,using,laptop,indoor.close up,hand

Purpose of Control 5.28

Collating accurate evidence in a timely manner is a crucial aspect of incident management that informs everything from disciplinary action to legal proceedings and regulatory investigations.

Control 5.28 allows organisations to fulfil their internal and external obligations, by managing evidence throughout the reporting and resolution of information security incidents in a robust and consistent way.

Attributes Table

5.28 is a corrective control that maintains risk by creating procedures which identify, collect, store and preserve evidential material, relating to information security events.

Control TypeInformation Security PropertiesCybersecurity ConceptsOperational CapabilitiesSecurity Domains
#Corrective#Confidentiality
#Integrity
#Availability
#Detect
#Respond
#Information Security Event Management#Defence

Ownership of Control 5.28

Control 5.28 deals with the explicit legal and disciplinary consequences of collecting evidence relating to an information security incident.

Whilst ISO 27002 largely deals with internal technical matters pertaining to information security, there are circumstances where procedural adherence is a legal matter, such is the case in Control 5.28.

Organisations should consider delegating ownership of Control 5.28 to an appropriate member of senior management with overall responsibility for HR and/or legal matters.

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

General Guidance on Control 5.28

Control 5.28 explicitly states that evidence collection procedures should be formulated with the express purpose of fulfilling the organisation’s disciplinary and/or legal obligations.

Furthermore, evidence collection should be preoccupied with fulfilling obligations across different regulatory environments and legal jurisdictions, to ensure that incidents are able to be analysed by multiple distinct external bodies to the same degree, across several variables, including:

  • storage media
  • assets and devices
  • device status (login attempts, power status etc.)

Organisations need to be able to demonstrate that:

  1. Their incident records are complete, and haven’t been interfered or tampered with.
  2. Electronic evidence is a perfect replica of physical evidence, where applicable.
  3. Internal systems and ICT platforms involved in collecting evidence had the operational capacity to do so, when the evidence was recorded.
  4. The individuals involved in collecting evidence are suitably qualified and certified to carry out their respective roles.
  5. They have the legal entitlement to collect digital evidence, where required.

Supplementary Guidance

Control 5.28 warns organisations about making any assumption as to the relevancy of any evidence collected towards future legal proceedings.

Organisations are encouraged to address any doubts by seeking legal advice and/or involving law enforcement authorities at the earliest opportunity, in order to avoid accidental or wilful destruction of incident-related evidence.

It helps drive our behaviour in a positive way that works for us
& our culture.

Emmie Cooney
Operations Manager, Amigo

Book your demo

Since migrating we’ve been able to reduce the time spent on administration.
Jodie Korber
Managing Director Lanrex
100% of our users pass certification first time
Book your demo

Changes and Differences From ISO 27002:2013

27002:2022-5.28 replaces 27002:2013-16.1.7 (Collection of evidence).

27002:2022-5.28 adheres to the same operational principles as 27002:2013-16.1.7, with four notable additions:

  • the need to ensure that evidence is free from tampering
  • ICT systems were operating correctly during the collection process
  • the organisation has the legal right to collect certain pieces of digital evidence
  • any electronic evidence collected is identical (to the extent that this possible) to the physical original

How ISMS.online Helps

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.

Get in touch today to book 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

We’re cost-effective and quick

Discover how that will boost your ROI
Get your quote

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