ISO 27002:2022, Control 5.35 – Independent Review of Information Security

ISO 27002:2022 Revised Controls

Book a demo

young,male,and,female,partners,teamworking,togetherness,in,workspace,while

Information security is a core aspect of an organisation’s data governance practices.

So much so, that it’s necessary to eliminate complacency by conducting regular independent reviews of how an organisation manages the people, processes and technologies involved in maintaining an effective information security operation.

Purpose of Control 5.35

Control 5.35 requires organisations to carry out independent reviews of their information security practices – both at planned intervals and when major operational changes occur – to ensure that information security management policies are:

  • Adequate – They have the capacity to achieve adherence
  • Suitable – They try to achieve the correct goals
  • Effective – They work as intended

Attributes Table

Control 5.35 is a preventive and corrective control that maintains risk by creating processes that facilitate regular reviews of an organisation’s information security management practices.

Control TypeInformation Security PropertiesCybersecurity ConceptsOperational CapabilitiesSecurity Domains
#Preventive
#Corrective
#Confidentiality
#Integrity
#Availability
#Identify
#Protect
#Information Security Assurance#Governance and Ecosystem
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

Ownership of Control 5.35

Control 5.35 deals primarily with operational matters. As such, ownership should reside with the COO, or CISO (if present).

General Guidance on Control 5.35

The overarching aim is for management to create and implement processes that cater for independent reviews of their information security practices.

Reviews should focus on any changes that are required to improve an organisation’s approach to information security, including:

  1. The information security policy.
  2. Topic-specific policies.
  3. Related controls.

Any review should be conducted by a person inside or outside the organisation that doesn’t have a vested interest in what they are investigating, such as:

  1. Internal auditors.
  2. Independent departmental managers.
  3. Third-party organisations.

Whoever conducts the review should have the relevant operational competence to make a sound judgement on their findings, and (in the case of internal staff) their job role should not inhibit them from making a valid and legitimate assessment.

The results of the review should be thoroughly recorded, stored and reported to the Manager (or groups of Managers) who requested it, and in certain cases to C-suite level or ownership.

Reviewers should seek to establish whether or not information security practices are compliant with the organisation’s “documented objectives and requirements” stated within the information security policy, or any topic-specific policies.

Alongside periodic reviews, it may be necessary to initiate ad-hoc reviews. These reviews can be justified across 5 key areas:

  1. Any laws, guidelines or regulations are amended which affect the organisation’s information security operation.
  2. Major incidents occur that have an impact on information security (data loss, intrusion etc).
  3. A new business is created, or major changes are enacted to the current business.
  4. The organisation adopts a new product or service that has information security implications, or makes underlying changes to a current product or service.
  5. Major changes are made to the organisation’s bank of information security controls, policies and procedures.

Get a Headstart
on ISO 27002

The only compliance
solution you need
Book your demo

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

Supplementary Guidance

ISO/IEC 27007 and ISO/IEC TS 27008 contain further guidance on the practice of independent reviews.

Changes and Differences from ISO 27002:2013

27002:2022-5.35 replaces 27002:2013-18.1.2 (Independent review of information security).

27002:2022-5.35 contains the same general guidance as 27002:2013-18.1.2, but goes a step further in stipulating specific examples of when an organisation should carry out ad-hoc reviews, alongside its periodic reviews.

How ISMS.online Helps

ISMS.online streamlines the ISO 27002 implementation process by providing a sophisticated cloud-based framework for documenting information security management system procedures and checklists to assure compliance with recognised standards.

When you use ISMS.online, you will be able to:

create an ISMS that is compatible with ISO 27001 standards.
perform tasks and submit proof to indicate that they have met the requirements of the standard.
allocate tasks and track progress toward compliance with the law.
get access to a specialised team of advisors that will assist you throughout your path towards compliance.

Get in touch today to book a demo.

See how we can help you

Book a tailored hands-on session
based on your needs and goals
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 so pleased we found this solution, it made everything fit together more easily.
Emmie Cooney
Operations Manager Amigo
100% of our users pass certification first time
Book your demo

Streamline your workflow with our new Jira integration! Learn more here.