CompTIA CS0-003 - CompTIA CyberSecurity Analyst CySA+ Certification Exam

When two vulnerabilities are both high severity (CVSS 8.1 and 8.5) and no compensating controls exist, the deciding factor for remediation prioritization becomes business impact and asset criticality/value (what matters most to the organization if compromised or taken offline for remediation).

That is exactly what a Business Impact Analysis (BIA) is used for: it is a formalized method to determine asset criticality/value designations and to prioritize response/remediation work based on business impact.

Supporting exact extracts:

The Secbay Press CS0-003 guide explicitly states that Business Impact Analysis is used to align vulnerability prioritization with critical business functions:Exact extract (Secbay Press): “Business Impact Analysis: … Considers the potential impact of vulnerabilities on critical business functions … prioritizing vulnerabilities that could impact core business processes.”

It also describes the vulnerability prioritization process as combining severity/exploitability with asset criticality assessment (which is informed by business owners and BIA outputs):Exact extract (Secbay Press): “Asset Criticality Assessment: Evaluate the criticality of assets affected… Consider the importance of assets in business operations, data sensitivity, and regulatory compliance.”

The All-in-One CS0-003 guide reinforces that asset value (sensitivity + criticality) is one of the most important drivers of remediation timing/prioritization:Exact extract (All-in-One Exam Guide): “Asset value is… one of the most important factors in determining how quickly you should remediate vulnerabilities…” and asset value is tied to “sensitivity and criticality.”

Applying this to the scenario

HQFIN01 supports financial transactions for the largest business unit → typically extremely high criticality (availability) and often high sensitivity/integrity requirements.

HQADMIN02 is used by a privileged user and could be high risk too (admin access), but the question asks what the team would do to determine prioritization: the correct step is to reference BIA/value designation and then prioritize based on which asset is more critical to business operations.

Why the other options are incorrect

A (Review BCP and patch what takes longer to bring online): BCP/DR planning is not the primary method for vulnerability remediation ranking; prioritization is risk-based and commonly driven by asset criticality/business impact (BIA), not “time to bring online.”

B (Fix the faster one first): Speed of remediation is not the main driver; risk reduction and business impact are.

D (Least recent backups): Backup recency matters for recovery and resilience, but it’s not the primary determinant for vulnerability remediation priority versus asset criticality and business impact.

References (CompTIA CySA+ CS0-003 documents / study guides used):

Secbay Press, CompTIA CySA+ Exam Prep Guide (CS0-003): BIA used to prioritize vulnerabilities impacting critical business functions; asset criticality assessment in prioritization process

Mya Heath et al., CompTIA CySA+ All-in-One Exam Guide (CS0-003): asset value (sensitivity + criticality) drives how quickly vulnerabilities should be remediated

Exploit code maturity in the CVSS v.3.1 temporal metrics refers to the reliability and availability of exploit code for a vulnerability. Public availability of exploit code increases the exploit code maturity score.

The availability of exploit code affects the ' Exploit Code Maturity ' metric in CVSS v.3.1. This metric evaluates the level of maturity of the exploit that targets the vulnerability. When exploit code is readily available, it suggests a higher level of maturity, indicating that the exploit is more reliable and easier to use.

The endpoint log entry shows that a new account named “admin” has been created on a Windows system with a local group membership of “Administrators”. This indicates that a new account has been introduced on the system with administrative privileges. This could be a sign of malicious activity, such as privilege escalation or backdoor creation, by an attacker who has compromised the system.

The correct answer is A because SLOs — service-level objectives are measurable targets used to evaluate whether a service or process is meeting expected performance levels. When incident response is outsourced to a third party, SLOs help the organization measure whether the provider is meeting key performance expectations, such as detection time, response time, remediation time, and reporting quality.

Exact supporting extract: the Secbay CySA+ guide defines SLOs as specific, measurable targets set for the performance and reliability of a service or process. It also states that SLOs provide a framework for defining and measuring effectiveness, and that reporting on SLOs allows stakeholders to assess performance and make informed decisions.

The same guide explains that SLOs depict explicit measurements and may be set by a company or defined as part of a service-level agreement with a service provider. It also states that estimating whether SLOs are being met is a typical component of SLA management.

The official CySA+ objectives include SLOs under metrics and KPIs for reporting and communication.

Why the other options are incorrect:

B is incorrect because SLOs are performance targets, not a method for identifying hidden costs.

C is incorrect because SLOs may support risk management, but they do not directly calculate an objective risk score.

D is incorrect because risk appetite is a governance/risk-management concept, not the purpose of SLOs.

A is correct because SLOs allow the organization to measure third-party IR performance against defined KPIs.

1. Analyze the Log Evidence: The log displays a specific sequence of rapid-fire events (within 18 seconds) characteristic of automated reconnaissance tools used to map Active Directory environments.

20:06:05 (LDAP Reads): The attacker queries the directory for high-value groups (Domain Admins) and critical infrastructure (Domain Servers). They are not trying to log in; they are reading the membership lists to see who is important and where the servers are.

20:06:09 (EDR Enumeration): The attacker checks the local Administrators group. This is to see if the current compromised user has admin rights or who does.

20:06:23 (SMB Connections): The host PC021 attempts to connect to multiple other hosts. This indicates the attacker is testing where they can move laterally using the credentials or access they currently have.

2. Why this is " Finding the Shortest Path " (Option A): This behavior is the textbook signature of tools like BloodHound (or its data collector, SharpHound).

Concept: Adversaries use these tools to visualize relationships in Active Directory. They query LDAP to find out: " I am User A. Which computers can I access? Who is a Domain Admin? Is a Domain Admin logged into a computer I can access? "

Goal: The tool calculates the mathematical " shortest path " (graph theory) from the attacker ' s current low-level foothold to the ultimate target (Domain Admin).

The combination of LDAP querying (mapping the graph) and SMB connection attempts (verifying sessions/local admin rights) confirms the adversary is mapping out the network to find the most efficient route to total compromise.

Why the other options are incorrect:

B. An adversary is performing a vulnerability scan: Vulnerability scanners (like Nessus or Qualys) typically probe ports and services to identify unpatched software (CVEs). They generally do not focus on querying LDAP for " Domain Admins " group membership as their primary action.

C. An adversary is escalating privileges: While the attacker intends to escalate privileges eventually, the logs show enumeration (Discovery phase). They are currently looking for the path to escalate, not actively exploiting a vulnerability (like a kernel exploit) to change their privilege level in this specific snapshot.

D. An adversary is performing a password stuffing attack: Password stuffing involves high volumes of failed authentication attempts against a login service. The logs here show read operations and connection attempts, not the " Invalid Credential " errors associated with stuffing.

Awareness training and education are essential to help staff recognize phishing emails and understand safe email practices, particularly when using legacy applications that might not have the latest securityfeatures. Training helps build a culture of security mindfulness, which is critical for preventing social engineering attacks. According to CompTIA Security+ and CySA+ frameworks, user education is a fundamental aspect of organizational defense against phishing. Options like replacing applications or implementing MFA (while helpful) do not directly address the need for user awareness in this scenario.

Application security scanning is a process that involves testing and analyzing applications for security vulnerabilities, such as injection flaws, broken authentication, cross-site scripting, and insecure configuration. Application security scanning can help identify and fix security issues before they become exploitable by attackers. Using application security scanning as part of the pipeline for the continuous integration/continuous delivery (CI/CD) flow can help mitigate the problem of finding the same vulnerabilities in a critical application during security scanning. This is because application security scanning can be integrated into the development lifecycle and performed automatically and frequently as part of the CI/CD process.

The discovery of unapproved accounts accessing shared data, along with data discrepancies, strongly indicates unauthorized changes.

Indicators of Unauthorized Changes:

Unexpected user permissions found during audits​.

Modified or deleted data without proper documentation.

Altered system or security configurations, allowing unintended access.

Why Not Other Options?

A. Filesystem Anomaly: This refers to unexpected behavior in the file structure, such as corrupt metadata or missing files, rather than unauthorized user access.

B. Illegal Software: Would involve unlicensed or unauthorized applications, not unauthorized file modifications.

D. Data Exfiltration: If data was removed, it might be exfiltration, but in this case, data modifications were detected instead.

To prevent unauthorized changes, security teams should use:

File Integrity Monitoring (FIM) to detect unauthorized modifications.

Access control audits to verify correct user permissions.

SIEM tools to analyze logs for anomalies.

Indicators of compromise (IoCs) are pieces of data or evidence that suggest a system or network has been compromised by an attacker or malware. IoCs can include IP addresses, domain names, URLs, file hashes, registry keys, network traffic patterns, user behaviors, or system anomalies. IoCs can be used to detect, analyze, and respond to security incidents, as well as to share threat intelligence with other organizations or authorities. IoCs can produce the data needed for an executive briefing on possible threats to the organization, as they can provide information on the source, nature, scope, impact, and mitigation of the threats.

The correct regular expression to match a GET request to this API endpoint is " https://10\.1\.2\.3/api\?id=\d+ " . This pattern checks for the specific URL with an id parameter that accepts integer values. The syntax \d+ matches one or more digits, which aligns with the requirement for a single integer argument. Other options either use incorrect syntax or do not accurately capture the expected URL format. Regular expressions are vital in filtering and identifying patterns in logs, as recommended by CompTIA Cybersecurity Analyst (CySA+) practices for threat hunting and log analysis.