THR-12: 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.
Renumbered: Formerly THR-06 in SCF 2025.4.
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 (25)
| Framework | Mapping Values |
|---|---|
| CIS CSC 8.1 | 16.2 |
| CIS CSC 8.1 IG2 | 16.2 |
| CIS CSC 8.1 IG3 | 16.2 |
| CSA IoT SCF 2 | TRN-03 SET-05 |
| NIST 800-53 R5.2 | RA-05(11) |
| NIST 800-53B R5 (low) (source) | RA-05(11) |
| NIST 800-53B R5 (moderate) (source) | RA-05(11) |
| NIST 800-53B R5 (high) (source) | RA-05(11) |
| NIST 800-82 R3 | RA-05(11) |
| NIST 800-82 R3 LOW OT Overlay | RA-05(11) |
| NIST 800-82 R3 MODERATE OT Overlay | RA-05(11) |
| NIST 800-82 R3 HIGH OT Overlay | RA-05(11) |
| NIST 800-171 R3 (source) | 03.14.01.a |
| NIST 800-171A R3 (source) | A.03.14.01.a[01] A.03.14.01.a[02] |
| 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 |
| SCF DPMP 2026 | 5.15 |
| Shared Assessments SIG 2025 | T.2 |
US (11)
| Framework | Mapping Values |
|---|---|
| USA Federal CISA CPG 2022 | 4.B |
| USA Federal DHS CISA SSDAF | 4.c |
| USA Federal C2M2 2.1 | THREAT-1m |
| USA Federal EO 14028 | 4e(iv) 4e(viii) |
| USA Federal CJIS Security Policy 6.0 | RA-5(11) |
| USA Federal FedRAMP R5 (low) | RA-05(11) |
| USA Federal FedRAMP R5 (moderate) | RA-05(11) |
| USA Federal FedRAMP R5 (high) | RA-05(11) |
| USA Federal FedRAMP R5 (LI-SaaS) | RA-05(11) |
| USA California CCPA 2025 | 7123(c)(6) |
| USA Texas DIR SCSC 2.2 2025 | RA-05(11) |
EMEA (2)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | PSS-03.01B PSS-03.01B.4 PSS-03.02B PSS-03.02AC |
| EMEA EU DORA RTS 2024 | Article 10.2(e) |
APAC (5)
| Framework | Mapping Values |
|---|---|
| APAC Australia IoT Code of Practice 2024 | 2.0 |
| APAC Australia ISM June 2026 | ISM-1616 ISM-1717 ISM-1755 ISM-1756 |
| APAC Malaysia RMiT 2025 | 11.7 |
| APAC New Zealand NZISM 3.9 | 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 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.14.01.A |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
Threat Management (THR) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with THR domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with THR domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with THR domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Threat management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Threat management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
Level 3 — Well Defined
Threat Management (THR) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with THR domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with THR domain capabilities are well-documented and kept current by process owners. ▪ A threat management team, or similar function, is appropriately staffed and supported to implement and maintain THR domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of threat management operations (e.g., threat intelligence solution and bug bounty solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with THR domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists 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 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- THR-12_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
Micro/Small
- Subscribe to free threat intelligence feeds (e.g., CISA alerts)
Small
- CISA alerts subscription
- Basic threat awareness program
Medium
- Vulnerability Disclosure Program (VDP)
- "bug bounty" program
Large
- Vulnerability Disclosure Program (VDP)
- "bug bounty" program
Enterprise
- Vulnerability Disclosure Program (VDP)
- "bug bounty" program