ISO 27002:2022, Control 5.20 – Addressing Information Security Within Supplier Agreements

ISO 27002:2022 Revised Controls

Book a demo

business,people,working,in,conference,room

Purpose of Control 5.20

Control 5.20 governs how an organisation forms a contractual relationship with a supplier, based on their security requirements and the type of suppliers they deal with.

5.20 is a preventative control that maintains risk by establishing mutually agreeable obligations between organisations and their suppliers that deal with information security.

Whereas Control 5.19 governs with information security throughout the relationship, Control 5.20 is preoccupied with how organisations form binding agreements from the start of a relationship.

Attributes Table

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

Ownership of Control 5.20

Ownership of Control 5.20 should be dependent on whether or not the organisation operates their own legal department, and the underlying nature of any signed agreement.

If the organisation has the legal capacity to draft, amend and store their own contractual agreements without third party involvement, ownership of 5.20 should rest with the person who holds ultimate responsibility for legally binding agreements within the organisation (contracts, memos of understanding, SLAs etc.)

If the organisation outsources such agreements, ownership of Control 5.20 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.

We’re cost-effective and quick

Discover how that will boost your ROI
Get your quote

General Guidance on Control 5.20

Control 5.20 contains 25 guidance points that ISO state “can be considered” (i.e. not necessarily all of them) in order to fulfil an organisation’s information security requirements.

Regardless of what measures are adopted, Control 5.20 explicitly states that both parties should exit the process with a “clear understanding” of their information security obligations to one another.

  1. A clear description should be provided detailing the information that needs to be accessed in any way, and how that information is going to be accessed.
  2. The organisation should classify the information to be accessed in accordance with its published classification scheme (see Control 5.10, Control 5.12 and Control 5.13).
  3. Adequate consideration should be given to the supplier-side classification scheme, and how that relates to the organisation’s classification of information.
  4. Both parties’ rights should be categorised into four main areas – legal, statutory, regulatory and contractual. Within these four areas, various obligations should be clearly outlined, as is standard in commercial agreements, including accessing PII, intellectual property rights and copyright stipulations. The agreement should also cover how each of these key areas will be addressed in turn.
  5. Each party should be obligated to enact a series of concurrent controls that monitor, assess and manage information security risk levels (such as access control policies, contractual reviews, systems monitoring, reporting and periodic auditing). In addition, the agreement should clearly outline the need for supplier personnel to adhere to an organisation’s information security standards (see Control 5.20).
  6. There should be a clear understanding of what constitutes both acceptable and unacceptable use of information, and physical and virtual assets from either party.
  7. Procedures should be put in place that deal with the levels of authorisation required for supplier-side personnel to access or view an organisation’s information (e.g. authorised user lists, supplier-side audits, server access controls).
  8. Information security should be considered alongside the supplier’s own ICT infrastructure, and how that relates to the type of information that the organisation has provided access to, the risk criteria and the organisation’s base set of business requirements.
  9. Consideration should be given to what courses of action the organisation is able to take in the event of a breach of contract on the part of the supplier, or failure to comply with individual stipulations.
  10. The agreement should clearly outline a mutual Incident Management procedure that clearly stipulates what needs to happen when problems arise, particularly concerning how the incident is communicated between both parties.
  11. Personnel from both parties should be given adequate awareness training (where standard training is not sufficient) on key areas of the agreement, specifically concerning key risk areas such as Incident Management and the provision of access to information.
  12. Adequate attention should be given to the use of subcontractors. If the supplier is permitted to use subcontractors, the organisations should take steps to ensure that any such individuals or companies are aligned with the same set of information security requirements as the supplier.
  13. Where it’s legally possible and operationally relevant, organisations should consider how supplier personnel are screened prior to interacting with their information, and how screening is recorded and reported to the organisation, including non-screened personnel and areas for concern.
  14. Organisations should stipulate the need for third-party attestations that verify the supplier’s ability to fulfil organisational information security requirements, including independent reports and third-party audits.
  15. Organisations should have the contractual right to assess and audit a supplier’s procedures, relating to Control 5.20.
  16. Suppliers should have an obligation to deliver reports (at varying intervals) that cover the effectiveness of their own processes and procedures, and how they intend to address any issues raised in such a report.
  17. The agreement should take steps to ensure the timely and thorough resolution of any defects or conflicts that take place during the course of the relationship.
  18. Where relevant, the supplier should operate with an robust BUDR policy, in line with the organisation’s needs, that covers off three main considerations:

    a) Backup type (full server, file and folder etc, incremental etc.)
    b) Backup frequency (daily, weekly etc.)
    c) Backup location and source media (onsite, offsite)
  19. Data resilience should be achieved by operating with a disaster recovery location that is separate from the supplier’s main ICT site, and is not subject to the same level of risk.
  20. The supplier should operate with a comprehensive change management policy that gives advance notification to the organisation of any changes that may affect information security, and provide the organisation with the ability to reject such changes.
  21. Physical security controls (building access, visitor access, room access, desk security) should be enacted that are relevant to the kind of information they are permitted to access.
  22. When the need arises to transfer information between assets, sites, servers or storage locations, the supplier should ensure that data and assets are protected from loss, damage or corruption throughout the process.
  23. The agreement should outline a comprehensive list of actions to be taken by either party in the event of termination (see also Control 5.20), including (but not limited to):

    a) Asset disposal and/or relocation
    b) Information deletion
    c) Return of IP
    d) Removal of access rights
    e) Ongoing confidentiality obligations
  24. Further to point 23, the supplier should outline precisely how it intends to destroy/permanently delete the organisation’s information the moment it is no longer required (i.e. in the event of a termination).
  25. If, at the end of a contract, the need arises to handover support and/or services to another provider not listed on the agreement, steps are taken to ensure that the process results in zero business interruption.

Supporting controls

  • 5.10
  • 5.12
  • 5.13
  • 5.20

Are you ready for
the new ISO 27002

We’ll give you an 81% headstart
from the moment you log in
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

To aid organisations in managing supplier relationships, Control 5.20 states that organisations should maintain a register of agreements.

Registers should list all agreements held with other organisations, and categorised by the nature of the relationship, such as contracts, memorandums of understanding and information-sharing agreements.

Changes and Differences from ISO 27002:2013

ISO 27002:2022-5.20 replaces 27002:2013-15.1.2 (Addressing security within supplier agreements).

ISO 27002:2022-5.20 contains numerous additional guidance thats deal with a broad range of technical, legal and compliance-related topics, including:

  • Handover procedures
  • Information destruction
  • Termination clauses
  • Physical security controls
  • Change management
  • Backups and information redundancy

Broadly speaking, ISO 27002:2022-5.20 puts a much greater emphasis on what occurs at the end of a supplier relationship, and allocates far more importance to how a supplier achieves redundancy and data integrity throughout the course of an agreement.

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.

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

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