ISO/IEC TR 5895:2022 サイバーセキュリティ—複数政党が調整した脆弱性の開示と処理 | ページ 2

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, 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, 2 (see www.iso.org/directives or www.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.

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. Due to these considerations, multiple vendors need to participate in remediation efforts involving certain vulnerabilities.

Yet vulnerability disclosure and handling processes as described in ISO/IEC 29147 and ISO/IEC 30111 primarily focus on processes involving one reporter and one vendor. Further discussion and considerations are necessary to explain how ISO/IEC 29147 and ISO/IEC 30111 practices apply in the context of multi-party coordinated vulnerability handling and disclosure (MPCVD).

ISO/IEC 29147 and ISO/IEC 30111:2019, Clause 8 briefly and generally address the complex situation of MPCVD, where a broader collaboration within the ecosystem is needed to identify and validate vulnerabilities, develop and test mitigations and finally make them available for end users. ISO/IEC 30111 refers to these situations as “cases where vendors can share vulnerability information in order to resolve the issue that involves components from multiple vendors” and provide five examples of such situations or reasons:

• a) A vulnerability which was reported that affects a specific piece of software, but is caused by an issue in an underlying operating system or hardware.
• b) Vulnerabilities in various product implementations of a flawed standard functional specification or in published algorithms.
• c) Vulnerabilities that are naturally induced by so far widely accepted development methodology.
• d) Vulnerabilities in commonly used libraries.
• e) Vulnerabilities in software components that lack a current maintainer.

The MPCVD effort for a vulnerability in a technology owned and manufactured by the vendor leading the process – the coordinating vendor, or mitigating vendor manages and leads the coordination effort. The mitigating vendor (example a) above) can entail different processes from one in which a broader collaboration is needed and there is no one distinct vendor of the technology (e.g. protocol-level vulnerabilities) (examples b) to e) above). These examples include both vendor-coordinated MPCVD and non-owner MPCVD. Recognizing MPCVD can raise unique considerations for vulnerability handling given the technical and coordination complexities. Several documents have been published to share norms and best practices in this evolving area. These best practices continue to be developed, iterated and improved as new challenges arise. This document builds upon these sources and refers to them.

The audience for this document includes, among others, the participants of the MPCVD process such as vendors (defined in ISO/IEC 29147:2018, 3.4), maintainers, producers, developers, manufacturers, suppliers ¹ , installers, or providers of a product or service, coordinators (including public coordinators), reporters (e.g. security researchers), and users of information technology products and services.

1 Scope

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

2 Normative references

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO/IEC 30111 and ISO/IEC 29147 and the following apply.

ISO and IEC maintain terminology databases for use in standardization at the following addresses:

Bibliography