SECURE-SOFTWARE-DESIGN practice question 9 of 25
The product security incident response team (PSIRT) has decided to make a formal public disclosure, including base and temporal common vulnerability scoring system (CVSS) scores and a common vulnerabilities and exposures (CVE) ID report, of an externally discovered vulnerability. What is the most likely reason for making a public disclosure?
Full set: 118 questionsDomain Software Security Throughout the Lifecycle
A Product Security Incident Response Team (PSIRT) follows a structured process for handling vulnerability reports. A formal public disclosure, which includes assigning a CVE ID and CVSS scores, is a critical step in the Coordinated Vulnerability Disclosure (CVD) lifecycle. This action is only taken after the PSIRT has completed its internal investigation and triage process, which involves validating the report, reproducing the issue, and confirming its security impact. Therefore, the determination that the vulnerability is credible and affects the product is the fundamental prerequisite and primary reason for proceeding with a formal public disclosure to inform customers and the security community.
A. Increased public awareness leading to higher risk is a potential negative outcome that disclosure aims to mitigate with patches, not the reason for the disclosure itself.
B. A PSIRT would not issue a formal CVE and CVSS score for a vulnerability it has determined is not credible; such a report would be closed or rejected.
D. Notification from an external party only initiates the investigation process; it does not automatically trigger a public disclosure without prior validation and confirmation of credibility.
1. FIRST.org, "PSIRT Services Framework," Version 1.1, Section 3.3, Vulnerability Handling (p. 13). The framework outlines the typical PSIRT workflow as Triage -> Investigation -> Remediation -> Disclosure. This sequential process shows that disclosure occurs only after the investigation phase, where the credibility and impact of a potential vulnerability are determined.
2. Carnegie Mellon University, Software Engineering Institute (SEI), "The CERT Guide to Coordinated Vulnerability Disclosure," (2017), Section 4.2, "Analysis" (p. 21). This guide details the vulnerability analysis phase, stating, "The goal of the analysis phase is to understand a vulnerability report well enough to determine whether it describes a true vulnerability in your product or service." This confirmation is a necessary step before any disclosure activities are planned.
3. ISO/IEC 29147:2018, "Information technology — Security techniques — Vulnerability disclosure," Section 6.3, "Triage." This international standard specifies that after receiving a report, the vendor must perform a triage to "determine the report's accuracy and credibility." A decision to proceed is based on this initial validation, which precedes public disclosure.
Keep practicing
Take the free SECURE-SOFTWARE-DESIGN practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other SECURE-SOFTWARE-DESIGN practice questions
- Question 1The product team has been tasked with updating the user interface (UI). They will change …
- Question 2Automated security testing was performed by attempting to log in to the new product with …
- Question 3What is a best practice of secure coding?
- Question 4Using a web-based common vulnerability scoring system (CVSS) calculator, a security respo…
- Question 5Which category classifies identified threats that do not have defenses in place and expos…
- Question 6Company leadership has discovered an untapped revenue stream within its customer base and…
