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

The NTP configuration on each system should be checked first, as it is essential for ensuring accurate and consistent time stamps across different systems. NTP is the Network Time Protocol, which is used to synchronize the clocks of computers over a network. NTP uses a hierarchical system of time sources, where each level is assigned a stratum number. The most accurate time sources, such as atomic clocks or GPS receivers, are at stratum 0, and the devices that synchronize with them are at stratum 1, and so on. NTP clients can query multiple NTP servers and use algorithms to select the best time source and adjust their clocks accordingly1. If the NTP configuration is not consistent or correct on each system, the time stamps of the logs and events may differ, making it difficult to correlate incidents across different systems. This can affect the security analysis and correlation of events, as well as the compliance and auditing of the network23. References: How the Windows Time Service Works, Time Synchronization - All You Need To Know, What is SIEM? | Microsoft Security

The correct answer is A because CVSS scores alone do not fully determine remediation priority. A vulnerability with a slightly lower CVSS score on a mission-critical system may need to be remediated before a higher-scoring vulnerability on a low-value or isolated system. The missing information is the criticality of the affected hosts/assets.

Exact supporting extract: the CySA+ All-in-One guide states that analysts should consider exploitability, whether a vulnerability is weaponized, patch availability, and asset value and criticality when determining remediation priority. It also explains that analysts must consider the impact to business operations when taking an asset offline for remediation.

The Secbay CySA+ guide also explains that vulnerability prioritization should evaluate severity, exploitability, and the criticality of affected systems. It specifically states that organizations should identify and prioritize vulnerabilities based on the criticality of the assets they affect and consider business operations, data sensitivity, and regulatory compliance.

Why the other options are incorrect:

A is correct because host criticality is required to confirm which vulnerability should be remediated first.

B is incorrect because SLAs define remediation timelines after prioritization, but the question asks what information is needed to confirm prioritization.

C is incorrect because KPIs measure program performance; they do not determine which vulnerable host is most critical.

D is incorrect because nothing in the question indicates these are zero-day vulnerabilities or that zero-days were excluded.

XDR logs will confirm the malware infection because XDR is a system that collects and analyzes data from multiple sources, such as endpoints, networks, cloud applications, and email security, to detect and respond to advanced threats12. XDR can provide a comprehensive view of the attack chain and the context of the malware infection. Firewall logs, IDS logs, and MFA logs are not sufficient to confirm the malware infection, as they only provide partial or indirect information about the network traffic, intrusion attempts, or user authentication. References: Cybersecurity Analyst+ - CompTIA, XDR: definition and benefits for MSPs| WatchGuard Blog, Extended detection and response - Wikipedia

Answer below images

Fuzzing is a testing technique where invalid or random data is inputted into a system to find vulnerabilities, crashes, or unexpected behaviors. It’s commonly used in software security to identify flaws that could lead to security breaches. According to CompTIA’s CySA+ curriculum, fuzzing is a dynamic testing method for exposing application weaknesses. Options like static testing (B) involve analyzing code without execution, while reverse engineering (A) and debugging (D) involve different methodologies for understanding or fixing code, not intentionally stressing it.

Part 1:

Part 2:

Based on the compliance report, I recommend the following changes for each server:

AppServ1: No changes are needed for this server.

AppServ2: Disable or upgrade TLS 1.0 and TLS 1.1 to TLS 1.2 on this server to ensure secure encryption and communication between clients and the server. Update Apache from version 2.4.17 to version 2.4.18 or greater on this server to fix any potential vulnerabilities or bugs.

AppServ3: Downgrade Apache from version 2.4.19 to version 2.4.18 or lower on this server to ensure compatibility and stability with the company’s applications and policies. Change the port number from 8080 to either port 80 (for HTTP) or port 443 (for HTTPS) on this server to follow the default port convention and avoid any confusion or conflicts with other services.

AppServ4: Update Apache from version 2.4.16 to version 2.4.18 or greater on this server to fix any potential vulnerabilities or bugs. Change the port number from 8443 to either port 80 (for HTTP) or port 443 (for HTTPS) on this server to follow the default port convention and avoid any confusion or conflicts with other services.

The correct answer is A because the analyst did not choose the vulnerability with the highest CVSS score. Instead, the analyst prioritized the vulnerability that is external-facing. That is a context-aware prioritization decision: the vulnerability’s exposure and location increase its likelihood of exploitation.

Exact supporting extract: the All-in-One CySA+ guide states that context awareness means prioritization depends on the situation, including whether the affected system is internal, external, or isolated. It further states that external systems may require faster remediation because they are more exposed to attacks and may be compromised faster.

The Secbay CySA+ guide also states that prioritizing vulnerabilities requires considering context, including whether vulnerabilities affect internal systems, external-facing systems, or isolated systems. It specifically notes that vulnerabilities exposed to external threats may receive higher priority due to increased risk exposure.

Why the other options are incorrect:

B is incorrect because the table does not provide asset criticality or business value.

C is incorrect because all listed vulnerabilities are weaponized, so exploit availability does not distinguish CVE-2023-8524 from the others.

D is incorrect because recurrence is not the deciding factor shown. Some internal vulnerabilities have similar or higher counts.

A is correct because the deciding factor is the vulnerability’s external exposure, which is context awareness.

Cloud-specific misconfigurations are security issues that arise from improper or inadequate configuration of cloud resources, such as storage buckets, databases, virtual machines, or containers. Cloud-specific misconfigurations may not be detected by the current scanners that are designed for on-premises environments, as they may not have the visibility or access to the cloud resources or the cloud provider’s APIs. Therefore, one of the implications that should be considered on the new hybrid environment is that cloud-specific misconfigurations may not be detected by the current scanners.

Step 1: Analyzing the SFTP Log

The SFTP log provides a record of file transfer and login activities:

User “sjames” logged in from several IP addresses:

192.168.10.32 and 192.168.10.37 (internal network IPs)

32.111.16.37 and 41.21.18.102 (external IPs)

We see file alterations in the /var/www directory, which is commonly the web directory.

Modified files: about_us.html, index.html

Suspicious activity:

192.168.11.102 and 41.21.18.102 modified the files.

32.111.16.37 had failed login attempts, indicating possible unauthorized access attempts.

The most suspicious IP here is 41.21.18.102, as it’s associated with direct file modifications, possibly indicating unauthorized access.

Step 2: Reviewing Netstat

The netstat output shows active connections and their states:

IP 41.21.18.102 has an ESTABLISHED connection with port 22, commonly used for SFTP.

IP 32.111.16.37 is also attempting connections, and 32.111.16.37 connections are in a TIME_WAIT state, showing prior connections were recently closed.

The netstat output reaffirms 41.21.18.102 is actively connected and potentially involved in malicious activities.

Step 3: Checking the HTTP Access Log

The HTTP Access log shows access to about_us.html:

32.111.16.37 repeatedly accessed /about_us.html with 404 errors, indicating attempts to reach non-existing pages.

41.21.18.102 accessed the 200 status code, showing successful page requests, but since this IP was modifying files directly on the server, it might be testing or verifying changes.

Again, 41.21.18.102 stands out as it matches both successful file modification and page request patterns, while 32.111.16.37 shows unsuccessful attempts.

Step 4: Selecting the IP of Concern

Based on the above analysis:

Answer: 41.21.18.102 should be the IP of concern due to its direct file modifications on critical web files (about_us.html, index.html).

Step 5: Identifying the Indicator of Compromise

Potential indicators include unauthorized file modifications:

Modified index.html file is the correct answer, as it indicates direct changes to website content and is often a clear sign of compromise.

Step 6: Selecting Corrective Actions

To mitigate and prevent further compromise:

Change the password on the “sjames” account: The account was used across various IPs, indicating potential account compromise.

Block external SFTP access: Restricting SFTP to internal IPs only would prevent unauthorized external modifications. Since 41.21.18.102 was external, this would stop similar threats.

Summary

IP of Concern: 41.21.18.102

Indicator of Compromise: Modified index.html file

Corrective Actions:

Change the password on the sjames account

Block external SFTP access

These selections address both the immediate security breach and implement a preventative measure against future unauthorized access.

The first step in building a disaster recovery plan (DRP) for critical on-prem applications is to determine what is actually “critical” to the business, how long the organization can tolerate those applications being down, and therefore what restoration order (prioritization) is required. That prioritization must come from business/data owners and stakeholders, because they understand operational dependencies, business impact, and acceptable downtime.

This is essentially the start of a Business Impact Analysis (BIA) and related continuity prioritization work, which precedes choices like vendors, contracts, or site geography. You don’t select a DR site/vendor or negotiate agreements until you know which systems must be restored first and what recovery objectives you must meet.

Supporting exact extracts:

The All-in-One CS0-003 guide explains that the foundation is identifying critical systems and determining tolerable outage time (used to prioritize restoration):Exact extract (All-in-One Exam Guide): “The key is to determine which of the organization’s critical systems are needed for survival and then estimate the outage time that can be tolerated by the organization…” It then connects those determinations directly to prioritization:Exact extract (All-in-One Exam Guide): “These estimates will help you determine how to prioritize response team efforts to restore these assets.”

The Secbay Press CS0-003 guide lays out the early BIA/risk identification steps in order, starting with identifying what’s critical before recovery priorities:Exact extract (Secbay Press): “1. Identify critical processes and resources2. Identify outage impacts and estimate downtime3. Identify resource requirements4. Identify recovery priorities”

Why the other options are not the first step:

A / C (vendor selection / vendor agreements): those come after requirements are defined (RTO/MTD, criticality, order of restoration).

D (define geographic area): location considerations are important, but they are driven by requirements and constraints discovered during BIA/continuity prioritization (what needs to be recovered, how fast, and with what dependencies).

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

Mya Heath et al., CompTIA CySA+ All-in-One Exam Guide (CS0-003): determine critical systems and tolerable outage time; used to prioritize restoration

Secbay Press, CompTIA CySA+ Exam Prep Guide (CS0-003): BIA / risk identification process steps (identify critical processes/resources → estimate downtime → recovery priorities)