ISO 27002:2022, Control 5.22 – Monitoring, Review and Change Management of Supplier Services

ISO 27002:2022 Revised Controls

Book a demo

office,building.,skyscraper.,exterior,of,building

Purpose of Control 5.22

Control 5.22 stipulates the methods organisations should take when monitoring, reviewing and managing changes in a supplier’s information security practices and service delivery standards, and assessing the impact upon the organisation’s own levels of information security.

When managing the relationship with their suppliers, an organisation should seek to maintain a baseline level of information security that adheres to any agreements that have been entered into.

5.22 is a preventative control that modifies risk by maintaining an “agreed level of information security and service delivery” on the part of the supplier.

Attributes Table

Control TypeInformation Security PropertiesCybersecurity ConceptsOperational CapabilitiesSecurity Domains
#Preventative#Confidentiality
#Integrity
#Availability
#Identify#Supplier Relationships Security#Governance and Ecosystem
#Protection
#Defence
#Information Security Assurance

Ownership of Control 5.22

Ownership of Control 5.22 should rest with a member of senior management that oversees an organisation’s commercial operation, and maintains a direct relationship with an organisation’s suppliers, such as a Chief Operating Officer.

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

General Guidance on Control 5.22

Control 5.22 contains 13 main areas that organisations need to consider when managing supplier relationships, and the effect they have on their own information security standards.

Organisations need to take steps to ensure that employees who are responsible for managing SLAs and supplier relationships have the requisite levels of skill and technical resources to be able to adequately assess supplier performance, and information security standards are not being breached.

Organisations should draft policies and procedures which:

  1. Constantly monitor service levels in accordance with published SLAs, and any shortfalls are addressed.
  2. Monitor any changes made by the supplier to their own operation, including (but not limited to):

    a) Service enhancements
    b) The introduction of new applications, systems or software processes
    c) Relevant and meaningful revisions to the suppliers internal governance documents
    d) Any incident management procedural changes, or efforts intended to increase levels of information security
  3. Monitor any service-specific changes, including (but not limited to):

    a) Infrastructure amendments
    b) The application of emerging technologies
    c) The roll-out of product updates or version upgrades
    d) Changes in the development environment
    e) Logistical and physical changes to supplier facilities, including new locations
    f) Any changes to outsourcing partners or subcontractors
    g) The intention to subcontract, where the practice wasn’t previously in place
  4. Ask for regular service reports, analyse data and attend review meetings in accordance with agreed levels of service delivery.
  5. Audit outsourcing partners and subcontractors and pursue any areas for concern.
  6. Review security incidents in accordance with agreed Incident Management standards and practices, and the supplier agreement.
  7. Maintain a thorough record of information security events, tangible operational problems, fault logs and general barriers to the service delivery standards that have been agreed.
  8. Proactively respond to and take remedial action towards information security-related events.
  9. Highlight any information security vulnerabilities and mitigate them to the fullest extent.
  10. Analyse any relevant information security factors inherent within the suppliers relationship with its own suppliers and subcontractors.
  11. Ensure that service delivery is delivered to acceptable levels following significant supplier-side disruption, including disaster recovery.
  12. Outline key personnel in the supplier’s operation who are responsible for maintaining compliance and adhering to the terms of an agreement.
  13. Regularly audit a supplier’s ability to maintain a baseline information security standard.

Supporting Controls

  • 5.29
  • 5.30
  • 5.35
  • 5.36
  • 8.14

How ISMS.online Helps

ISO 27002 implementation is simpler with our step-by-step checklist that guides you through the whole process, from defining the scope of your ISMS through risk identification and control implementation.

Some of the key benefits of using ISMS.online include:

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

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