ISO/IEC TR 5895:2022

Cybersecurity — Multi-party coordinated vulnerability disclosure and handling

This document clarifies and increases the application and implementation of ISO/IEC 30111 and ISO/IEC 29147 in multi-party coordinated vulnerability disclosure (MPCVD) settings, including the evolving commonly adopted practices in this area, by articulating: — The MPCVD life cycle and application of coordinated vulnerability disclosure (CVD) stages (preparation, receipt, verification, remediation[1] development, release, post-release) in MPCVD settings. — Stakeholders involved in MPCVD include users, vendors (coordinating, mitigating, and dependent vendors), reporters, and non-vendor coordinators (entities defined in ISO/IEC 29147 and ISO/IEC 30111). — The exchange of information between stakeholders during the vulnerability handling and disclosure process in a MPCVD settings. Clarifying the application of ISO/IEC 30111 and ISO/IEC 29147 in MPCVD settings illustrates the benefits of vulnerability disclosure processes. [1] Remediation is a defined term used in ISO/IEC 30111 and ISO/IEC 29147. This document uses the term "remediation" and verb “remediate” in the context of this definition.

Cybersécurité — Divulgation et traitement de vulnérabilité coordonnée entre plusieurs parties

General Information

• Status: Published
• Publication Date: 16-Jun-2022
• ICS: 35.030 - IT Security
• Technical Committee: ISO/IEC JTC 1/SC 27 - Information security, cybersecurity and privacy protection
• Drafting Committee: ISO/IEC JTC 1/SC 27 - Information security, cybersecurity and privacy protection
• Current Stage: 6060 - International Standard published
• Start Date: 17-Jun-2022
• Completion Date: 17-Jun-2022

Standards Content (Sample)

TECHNICAL ISO/IEC TR
REPORT 5895
First edition
2022-06
Cybersecurity — Multi-party
coordinated vulnerability disclosure
and handling
Cybersécurité — Divulgation et traitement de vulnérabilité
coordonnée entre plusieurs parties
Reference number
© ISO/IEC 2022
© ISO/IEC 2022
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii
© ISO/IEC 2022 – All rights reserved

Contents Page
Foreword .v
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Concepts . 1
4.1 General . 1
4.2 Relationship with other International Standards . 3
4.2.1 I SO/IEC 29147 - Vulnerability disclosure . 3
4.2.2 I SO/IEC 30111 - Vulnerability handling processes . 3
4.2.3 Risk reduction effectiveness . 4
5 MPCVD scenarios . 5
5.1 General . 5
5.2 MPCVD led by the vendor-coordinator (the owner of the technology developed) –
the “mitigating vendor” . 5
5.3 MPCVD process in non-owner cases . 5
6 MPCVD stakeholders .5
6.1 General . 5
6.2 Vendor . 5
6.2.1 Mitigating vendor . 5
6.2.2 Dependent vendor . 6
6.2.3 Mitigating vendor and coordination . 6
6.3 Non-vendor coordinator . . 6
6.4 Reporters . 6
6.5 Users . 6
6.6 Product security incident response team (PSIRT) function . 6
7 MPCVD life cycle . 6
7.1 General . 6
7.2 Policy development . 7
7.2.1 Preparation . 7
7.2.2 Policy . 7
7.3 Strategy development . 7
7.3.1 Information sharing strategy . 7
7.3.2 Disclosure strategy . 7
7.4 Know your customers . 8
7.5 Encrypted communication methods and conference calls . 8
7.6 Processes and controls . 8
8 MPCVD life cycle for each product .8
8.1 Product and user mapping . 8
8.2 Component analysis . 8
8.3 User analysis . 9
9 MPCVD life cycle for each vulnerability . 9
9.1 Receipt. 9
9.2 V erification . . 9
9.3 Remediation development . 10
9.4 Release . 10
9.5 Post-release . 10
9.6 Embargo period . 10
10 Information exchange .11
11 Disclosure .12
iii
© ISO/IEC 2022 – All rights reserved

12 Use case for hardware and further considerations .12
Bibliography .14
iv
© ISO/IEC 2022 – All rights reserved

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance
are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria
needed for the different types of ISO documents should be noted. This document was drafted in
accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives
orwww.iec.ch/members_experts/refdocs).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/
or on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC list of patent
declarations received (see patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see
www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 27, Information security, cybersecurity and privacy protection.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.
v
© ISO/IEC 2022 – All rights reserved

Introduction
Remediation of vulnerabilities in modern technology systems can vary and depend on the nature of the
vulnerable component. Certain vulnerability handling efforts can require multiple ecosystem players
taking action at multiple and interdependent layers within a given information and communication
technology (ICT) system. Mitigation can necessitate the engagement of the broad ecosystem of
stakeholders to develop, test and deploy mitigations in a manner geared to incentivize adoption by end
users.
For example, a vulnerability in a widely used software library (protocol) can entail action by different
ecosystem players as part of the remediation effort. As another example, a remediation development
and testing for a vulnerability in a hardware component can depend on an operating system running
on the hardware, and require different actions from different operating system providers. Du
...