THR-06: Vulnerability Disclosure Program (VDP)
Mechanisms exist to establish a Vulnerability Disclosure Program (VDP) to assist with the secure development and maintenance of Technology Assets, Applications and/or Services (TAAS) that receives unsolicited input from the public about vulnerabilities in organizational TAAS.
Control Question: Does the organization establish a Vulnerability Disclosure Program (VDP) to assist with the secure development and maintenance of Technology Assets, Applications and/or Services (TAAS) that receives unsolicited input from the public about vulnerabilities in organizational TAAS?
General (20)
| Framework | Mapping Values |
|---|---|
| CIS CSC 8.1 | 16.2 |
| CSA IoT SCF 2 | TRN-03 SET-05 |
| NIST 800-53 R5 (source) | RA-5(11) |
| NIST 800-53B R5 (low) (source) | RA-5(11) |
| NIST 800-53B R5 (moderate) (source) | RA-5(11) |
| NIST 800-53B R5 (high) (source) | RA-5(11) |
| NIST 800-82 R3 LOW OT Overlay | RA-5(11) |
| NIST 800-82 R3 MODERATE OT Overlay | RA-5(11) |
| NIST 800-82 R3 HIGH OT Overlay | RA-5(11) |
| NIST 800-218 | RV.1.3 |
| PCI DSS 4.0.1 (source) | 6.3.1 |
| PCI DSS 4.0.1 SAQ A (source) | 6.3.1 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 6.3.1 |
| PCI DSS 4.0.1 SAQ B-IP (source) | 6.3.1 |
| PCI DSS 4.0.1 SAQ C (source) | 6.3.1 |
| PCI DSS 4.0.1 SAQ C-VT (source) | 6.3.1 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 6.3.1 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 6.3.1 |
| Shared Assessments SIG 2025 | T.2 |
| SCF CORE Mergers, Acquisitions & Divestitures (MA&D) | THR-06 |
US (9)
| Framework | Mapping Values |
|---|---|
| US CISA CPG 2022 | 4.B |
| US DHS CISA SSDAF | 4.c |
| US EO 14028 | 4e(iv) 4e(viii) |
| US FedRAMP R5 (source) | RA-5(11) |
| US FedRAMP R5 (low) (source) | RA-5(11) |
| US FedRAMP R5 (moderate) (source) | RA-5(11) |
| US FedRAMP R5 (high) (source) | RA-5(11) |
| US FedRAMP R5 (LI-SaaS) (source) | RA-5(11) |
| US - CA CCPA 2025 | 7123(c)(6) |
EMEA (1)
| Framework | Mapping Values |
|---|---|
| EMEA EU Cyber Resiliency Act Annexes | Annex 1.2(5) |
APAC (4)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2024 | ISM-1616 ISM-1717 ISM-1755 ISM-1756 |
| APAC Australia IoT Code of Practice | Principle 2 |
| APAC New Zealand NZISM 3.6 | 5.9.23.C.01 5.9.24.C.01 5.9.24.C.02 5.9.25.C.01 5.9.26.C.01 5.9.26.C.02 5.9.27.C.01 |
| APAC Singapore MAS TRM 2021 | 13.2.2 |
Capability Maturity Model
Level 0 — Not Performed
There is no evidence of a capability to establish a Vulnerability Disclosure Program (VDP) to assist with the secure development and maintenance of Technology Assets, Applications and/or Services (TAAS) that receives unsolicited input from the public about vulnerabilities in organizational TAAS.
Level 1 — Performed Informally
C|P-CMM1 is N/A, since a structured process is required to establish a Vulnerability Disclosure Program (VDP) to assist with the secure development and maintenance of Technology Assets, Applications and/or Services (TAAS) that receives unsolicited input from the public about vulnerabilities in organizational TAAS.
Level 2 — Planned & Tracked
Threat Management (THR) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Identify cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements for threat management. o Subscribe to threat feeds to maintain situational awareness of emerging threats.
- Threat management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
- The HR department, in conjunction with cybersecurity personnel, helps ensure secure practices are implemented in personnel management operations to help manage threats.
- IT/cybersecurity personnel:
- A Vulnerability Disclosure Program (VDP) is formed to receive and triage unsolicited input from the public about vulnerabilities in organizational TAAS.
Level 3 — Well Defined
Threat Management (THR) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Subscribes to threat feeds to maintain situational awareness of emerging threats. o Develops Indicators of Exposure (IOE) to better understand potential attack vectors that attackers could use to attack the organization. o Implements a Threat Awareness Program (TAP) that includes a cross-organization information-sharing capability. o Implements a “threat hunting” capability to actively identify internal threats.
- A Security Operations Center (SOC), or similar function:
- An Integrated Security Incident Response Team (ISIRT), or similar function, exists to form an on-demand, integrated team of cybersecurity, IT, data privacy and business function representatives that can execute coordinated incident response operations, including a cross-discipline incident handling capability.
- Cybersecurity personnel enable security awareness training on recognizing and reporting potential indicators of insider threat.
- A Vulnerability Disclosure Program (VDP) is formed to receive and triage unsolicited input from the public about vulnerabilities in organizational TAAS.
Level 4 — Quantitatively Controlled
See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to establish a Vulnerability Disclosure Program (VDP) to assist with the secure development and maintenance of Technology Assets, Applications and/or Services (TAAS) that receives unsolicited input from the public about vulnerabilities in organizational TAAS.
Level 5 — Continuously Improving
See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to establish a Vulnerability Disclosure Program (VDP) to assist with the secure development and maintenance of Technology Assets, Applications and/or Services (TAAS) that receives unsolicited input from the public about vulnerabilities in organizational TAAS.
Assessment Objectives
- THR-06_A01 a public reporting channel is established for receiving reports of vulnerabilities in organizational systems and system components.
Evidence Requirements
- E-TDA-16 Vulnerability Disclosure Program (VDP)
-
Documented evidence of a Vulnerability Disclosure Program (VDP) (e.g., bug bounty).
Technology Design & Acquisition
Technology Recommendations
Medium
- Vulnerability Disclosure Program (VDP)
- "bug bounty" program
Large
- Vulnerability Disclosure Program (VDP)
- "bug bounty" program
Enterprise
- Vulnerability Disclosure Program (VDP)
- "bug bounty" program