Free Practice Questions for CompTIA CS0-003 Exam

Server-Side Request Forgery (SSRF) occurs when an attacker manipulates a web server to make unauthorized internal or external requests, often to access internal resources or exfiltrate data.

A Web Application Firewall (WAF) is the best mitigation because it:

Filters and blocks malicious requests before they reach the server.

Prevents attackers from sending unauthorized requests to internal services.

Can detect and block SSRF patterns in incoming traffic.

Why Not Other Options?

B (CASB) → Used for cloud access control, not effective against SSRF.

C (Forward Proxy) → Helps with outbound traffic control, but SSRF involves incoming requests.

D (MFA) → Helps with authentication but does NOT prevent SSRF attacks.

The best action that the SOC manager can recommend to help ensure new employees are accountable for following the company policy is to require all new employees to sign a user agreement to acknowledge the company security policy. A user agreement is a document that defines the rights and responsibilities of the users regarding the use of the company’s systems, networks, or resources, as well as the consequences of violating the company’s security policy. Signing a user agreement can help ensure new employees are aware of and agree to comply with the company security policy, as well as hold them accountable for any breaches or incidents caused by their actions or inactions.

Determining the asset value of each system is the best action to perform first, as it helps to categorize and prioritize the systems based on the sensitivity of the data they host. The asset value is a measure of how important a system is to the organization, in terms of its financial, operational, or reputational impact. The asset value can help the security analyst to assign a risk level and a protection level to each system, and to allocate resources accordingly. The other actions are not as effective as determining the asset value, as they do not directly address the goal of promoting confidentiality, availability, and integrity of the data. Interviewing the users who access these systems may provide some insight into how the systems are used and what data they contain, but it may not reflect the actual value or sensitivity of the data from an organizational perspective. Scanning the systems to see which vulnerabilities currently exist may help to identify and remediate some security issues, but it does not help to categorize or prioritize the systems based on their data sensitivity. Configuring alerts for vendor-specific zero-day exploits may help to detect and respond to some emerging threats, but it does not help to protect the systems based on their data sensitivity.

The correct answer is A. 121.19.30.221.

Based on the log files and the organization’s priorities, the host that warrants additional investigation is 121.19.30.221, because it is the only host that accessed a file containing sensitive data and is not from the partner vendor’s range.

The log files show the following information:

The IP addresses of the hosts that accessed the web server

The date and time of the access

The file path of the requested resource

The number of bytes transferred

The organization’s priorities are:

Unauthorized data disclosure is more critical than denial of service attempts

Denial of service attempts are more important than ensuring vendor data access

According to these priorities, the most serious threat to the organization is unauthorized data disclosure, which occurs when sensitive, protected, or confidential data is copied, transmitted, viewed, stolen, altered, or used by an individual unauthorized to do so123. Therefore, the host that accessed a file containing sensitive data and is not from the partner vendor’s range poses the highest risk to the organization.

The file that contains sensitive data is /reports/2023/financials.pdf, as indicated by its name and path. This file was accessed by two hosts: 121.19.30.221 and 216.122.5.5. However, only 121.19.30.221 is not from the partner vendor’s range, which is 216.122.5.x. Therefore, 121.19.30.221 is a potential unauthorized data disclosure threat and warrants additional investigation.

The other hosts do not warrant additional investigation based on the log files and the organization’s priorities.

Host 134.17.188.5 accessed /index.html multiple times in a short period of time, which could indicate a denial of service attempt by flooding the web server with requests45. However, denial of service attempts are less critical than unauthorized data disclosure according to the organization’s priorities, and there is no evidence that this host succeeded in disrupting the web server’s normal operations.

Host 202.180.1582 accessed /images/logo.png once, which does not indicate any malicious activity or threat to the organization.

Host 216.122.5.5 accessed /reports/2023/financials.pdf once, which could indicate unauthorized data disclosure if it was not authorized to do so. However, this host is from the partner vendor’s range, which is required to have access to monthly reports and is the only external vendor with authorized access according to the organization’s requirements.

Therefore, based on the log files and the organization’s priorities, host 121.19.30.221 warrants additional investigation as it poses the highest risk of unauthorized data disclosure to the organization.

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.

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

EDR stands for Endpoint Detection and Response, which is a layer of defense that monitors endpoints for malicious activity and provides automated or manual response capabilities. EDR can protect against external threats regardless of the device’s operating system, as it can detect and respond to attacks based on behavioral analysis and threat intelligence. EDR is also one of the tools that CompTIA CySA+ covers in its exam objectives. Official References:

https://www.comptia.org/certifications/cybersecurity-analyst

https://www.comptia.org/blog/the-new-comptia-cybersecurity-analyst-your-questions-answered

https://resources.infosecinstitute.com/certification/cysa-plus-ia-levels/

Fuzzing is a process used to test applications by inputting unexpected or random data to see how the application behaves. This method is particularly effective in identifying vulnerabilities such as buffer overflows, input validation errors, and other anomalies that could cause the application to crash or behave unexpectedly. By using fuzzing, the security team can ensure the new application is robust and capable of handling unexpected strings with anomalous formats without crashing.

Business process interruption is the inhibitor to remediation that this scenario illustrates. Business process interruption is when the remediation of a vulnerability or an incident requires the disruption or suspension of a critical or essential business process, such as the point-of-sale application. This can cause operational, financial, or reputational losses for the organization, and may outweigh the benefits of the remediation. Therefore, the organization may decide to postpone or avoid the remediation until a more convenient time, such as a change freeze window, which is a period of time when no changes are allowed to the IT environment12. Service-level agreement, degrading functionality, and proprietary system are other possible inhibitors to remediation, but they are not relevant to this scenario. Service-level agreement is when the remediation of a vulnerability or an incident violates or affects the contractual obligations or expectations of the service provider or the customer. Degrading functionality is when the remediation of a vulnerability or an incident reduces or impairs the performance or usability of a system or an application. Proprietary system is when the remediation of a vulnerability or an incident involves a system or an application that is owned or controlled by a third party, and the organization has limited or no access or authority to modify it3. References: Inhibitors to Remediation — SOC Ops Simplified, Remediation Inhibitors - CompTIA CySA+, Information security Vulnerability Management Report (Remediation…

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)