easyMultiple Choice
Executive Summary for SOC Manager: Critical Vulnerability Without Exploitation
A critical vulnerability affected the customer portal, but no evidence of exploitation was found. What should the executive summary emphasize? If the primary audience is legal/privacy stakeholder, which content choice is most appropriate?
⚠ Common exam trap
The CS0-004 exam often tests the misconception that an executive summary should include all technical findings, but the trap here is that legal/privacy stakeholders require a risk-focused, non-technical summary, not operational or scanner output details.
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
✓
Business risk, customer impact assessment, remediation status, and remaining exposure
The executive summary for legal/privacy stakeholders must focus on business risk, customer impact, remediation status, and remaining exposure. Since no exploitation was found, the summary should communicate the potential regulatory and privacy implications (e.g., GDPR, CCPA) and the steps taken to close the vulnerability, not technical details. This aligns with the CS0-004 objective of tailoring communication to the audience's need for risk-based, non-technical summaries.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A list of analyst shift times only
Why it's wrong here
Providing only a list of analyst shift times is entirely inappropriate for an executive-level report concerning a critical vulnerability. Executives require information that directly addresses the business impact, risk posture, and strategic remediation efforts, not granular operational scheduling details. Shift times offer no insight into the vulnerability's severity, customer exposure, or the organization's overall security posture, rendering them irrelevant for high-level decision-making.
- ✗
Every command the scanner executed
Why it's wrong here
Presenting every command executed by a vulnerability scanner is overly technical and provides excessive detail unsuitable for an executive audience. Executives are concerned with the *results* of the scan, such as identified vulnerabilities, their potential impact, and the status of remediation, rather than the specific syntax of the tools used. This level of technical granularity obscures the critical business implications and strategic decisions that executives need to make.
- ✓
Business risk, customer impact assessment, remediation status, and remaining exposure
Why this is correct
This option correctly identifies the essential elements for an executive-level report on a critical vulnerability. Executives require a clear understanding of the business risk posed by the vulnerability, a thorough assessment of its potential customer impact (including legal and privacy implications), the current status of remediation efforts, and the organization's remaining exposure. This strategic information enables informed decision-making regarding resource allocation, risk acceptance, and communication strategies, aligning security posture with business objectives.
- ✗
Raw packet captures from the scan
Why it's wrong here
Including raw packet captures from the vulnerability scan in an executive report is inappropriate due to their highly technical nature and sheer volume. While crucial for in-depth technical analysis or forensic investigation by security engineers, these captures provide no high-level strategic value for executives. Presenting such granular data would overwhelm the audience and distract from the critical business implications, remediation progress, and overall risk posture that executives need to understand.
Go deeper
Related to this question
Learn chapter
Legal Considerations in Incident Response
Key term
Impact
Impact is the measure of the potential damage or harm that a risk event could cause to an organization's assets, operations, or reputation.
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.
About these practice questions
One of 701 original CS0-004 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.