CS0-003 Reporting and Communication Practice Question
A cybersecurity analyst needs to communicate the risk of a newly discovered vulnerability in a legacy system to the executive leadership. Which approach best translates the technical risk into business risk?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Explain the vulnerability's potential impact on revenue, customer trust, and compliance penalties
Executives care about business impact. Relating the vulnerability to potential financial loss, reputational damage, or regulatory penalties is the most effective way to communicate risk.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Explain the vulnerability's potential impact on revenue, customer trust, and compliance penalties
Why this is correct
This approach is correct because it reframes a purely technical finding in terms executives already use to make decisions: revenue at risk, reputational damage from lost customer trust, and quantifiable regulatory fines. Framing risk this way lets leadership weigh remediation cost against concrete business consequences instead of abstract technical severity.
- ✗
Provide the CVSS score and technical exploit details
Why it's wrong here
Presenting only the CVSS score and step-by-step exploit mechanics assumes a level of technical fluency executives typically lack, and it omits any tie to financial or reputational consequence. Without business framing, leadership cannot judge whether the risk justifies budget or downtime, so the communication fails its purpose even though the data itself is accurate.
- ✗
Recommend immediate patching without further justification
Why it's wrong here
Simply telling leadership to patch immediately skips the analysis step entirely, giving no rationale for why the fix is urgent, what happens if it is delayed, or what resources the request requires. Executives making budget and prioritization decisions need supporting context, not a bare directive, especially for legacy systems where patching can itself introduce operational risk.
- ✗
Describe the attack vector and required privileges
Why it's wrong here
Detailing the attack vector and the privilege level an attacker needs is meaningful to a penetration tester or engineer assessing exploitability, but it says nothing about what the organization stands to lose. This level of technical specificity does not map to dollars, downtime, or liability, so it fails to help non-technical decision-makers prioritize the response.
Go deeper
Related to this question
Learn chapter
Nessus Vulnerability Scanner
Key term
Vulnerability
A vulnerability is a weakness in a system, network, or software that could be exploited by a threat to cause harm or unauthorized access.
Key term
Risk
Risk is the possibility that an event or action will negatively affect an organization's ability to achieve its goals, often measured in terms of likelihood and impact.
About these practice questions
This CS0-004 question is part of Courseiva's 701-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CS0-004 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CS0-004 exam.