𝔖 Scriptorium
✦   LIBER   ✦

📁

ISO/IEC 29147:2018 Information technology — Security techniques — Vulnerability disclosure Abstract


Year
2018
Tongue
English
Leaves
42
Edition
2
Category
Library

⬇  Acquire This Volume

No coin nor oath required. For personal study only.

✦ Synopsis


This document provides requirements and recommendations to vendors on the disclosure of vulnerabilities in products and services. Vulnerability disclosure enables users to perform technical vulnerability management as specified in ISO/IEC 27002:2013, 12.6.1[1]. Vulnerability disclosure helps users protect their systems and data, prioritize defensive investments, and better assess risk. The goal of vulnerability disclosure is to reduce the risk associated with exploiting vulnerabilities. Coordinated vulnerability disclosure is especially important when multiple vendors are affected. This document provides:

— guidelines on receiving reports about potential vulnerabilities;

— guidelines on disclosing vulnerability remediation information;

— terms and definitions that are specific to vulnerability disclosure;

— an overview of vulnerability disclosure concepts;

— techniques and policy considerations for vulnerability disclosure;

— examples of techniques, policies (Annex A), and communications (Annex B).

Other related activities that take place between receiving and disclosing vulnerability reports are described in ISO/IEC 30111.

This document is applicable to vendors who choose to practice vulnerability disclosure to reduce risk to users of vendors' products and services.

✦ Table of Contents


Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviated terms
5 Concepts
5.1 General
5.2 Structure of this document
5.3 Relationships to other International Standards
5.3.1 ISO/IEC 30111
5.3.2 ISO/IEC 27002
5.3.3 ISO/IEC 27034 series
5.3.4 ISO/IEC 27036-3
5.3.5 ISO/IEC 27017
5.3.6 ISO/IEC 27035 series
5.3.7 Security evaluation, testing and specification
5.4 Systems, components, and services
5.4.1 Systems
5.4.2 Components
5.4.3 Products
5.4.4 Services
5.4.5 Vulnerability
5.4.6 Product interdependency
5.5 Stakeholder roles
5.5.1 General
5.5.2 User
5.5.3 Vendor
5.5.4 Reporter
5.5.5 Coordinator
5.6 Vulnerability handling process summary
5.6.1 General
5.6.2 Preparation
5.6.3 Receipt
5.6.4 Verification
5.6.5 Remediation development
5.6.6 Release
5.6.7 Post-release
5.6.8 Embargo period
5.7 Information exchange during vulnerability disclosure
5.8 Confidentiality of exchanged information
5.8.1 General
5.8.2 Secure communications
5.9 Vulnerability advisories
5.10 Vulnerability exploitation
5.11 Vulnerabilities and risk
6 Receiving vulnerability reports
6.1 General
6.2 Vulnerability reports
6.2.1 General
6.2.2 Capability to receive reports
6.2.3 Monitoring
6.2.4 Report tracking
6.2.5 Report acknowledgement
6.3 Initial assessment
6.4 Further investigation
6.5 On-going communication
6.6 Coordinator involvement
6.7 Operational security
7 Publishing vulnerability advisories
7.1 General
7.2 Advisory
7.3 Advisory publication timing
7.4 Advisory elements
7.4.1 General
7.4.2 Identifiers
7.4.3 Date and time
7.4.4 Title
7.4.5 Overview
7.4.6 Affected products
7.4.7 Intended audience
7.4.8 Localization
7.4.9 Description
7.4.10 Impact
7.4.11 Severity
7.4.12 Remediation
7.4.13 References
7.4.14 Credit
7.4.15 Contact information
7.4.16 Revision history
7.4.17 Terms of use
7.5 Advisory communication
7.6 Advisory format
7.7 Advisory authenticity
7.8 Remediations
7.8.1 General
7.8.2 Remediation authenticity
7.8.3 Remediation deployment
8 Coordination
8.1 General
8.2 Vendors playing multiple roles
8.2.1 General
8.2.2 Vulnerability reporting among vendors
8.2.3 Reporting vulnerability information to other vendors
9 Vulnerability disclosure policy
9.1 General
9.2 Required policy elements
9.2.1 General
9.2.2 Preferred contact mechanism
9.3 Recommended policy elements
9.3.1 General
9.3.2 Vulnerability report contents
9.3.3 Secure communication options
9.3.4 Setting communication expectations
9.3.5 Scope
9.3.6 Publication
9.3.7 Recognition
9.4 Optional policy elements
9.4.1 General
9.4.2 Legal considerations
9.4.3 Disclosure timeline
Annex A (informative) Example vulnerability disclosure policies
Annex B (informative) Information to request in a report
Annex C (informative) Example advisories
Annex D (informative) Summary of normative elements
Bibliography


📜 SIMILAR VOLUMES


BS ISO/IEC 27035:2011 Information techno
✍ BSi 📂 Library 📅 2011 🏛 BSi 🌐 English

Descriptors: Data processing, Computers, Management, Data security, Data storage protection, Anti-burglar measures, Computer networks, Computer software, Computer hardware, Data transmission, Information exchange, Documents, Records (documents), Classification systems ICS: 35.040 (Character sets

[ISO/IEC 29100:2011] Information technol
✍ ISO/IEC JTC 1/SC 27 Information security cybersecurity privacy protection 📂 Library 📅 2011 🏛 ISO 🌐 English

ISO/IEC 29100:2011 provides a privacy framework which specifies a common privacy terminolog; defines the actors and their roles in processing personally identifiable information (PII); describes privacy safeguarding considerations; and provides references to known privacy principles for inform

ISO/IEC 27003:2010, Information technolo
✍ ISO/IEC/JTC 1/SC 27 📂 Library 📅 2010 🏛 Multiple. Distributed through American National St 🌐 English

ISO/IEC 27003:2010 focuses on the critical aspects needed for successful design and implementation of an Information Security Management System (ISMS) in accordance with ISO/IEC 27001:2005. It describes the process of ISMS specification and design from inception to the production of implementation p