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

PID 2264 (bash running as root) is suspicious because:

It has elevated privileges (root user).

Bash (command-line shell) is running with high CPU usage (14.0%), which is unusual unless actively being used.

If unauthorized, an attacker could be exfiltrating data via command-line methods like scp, wget, or custom scripts.

Why Not Other Options?

B (34218 - Xorg) → Xorg is a display server for GUI; no signs of exfiltration.

C (34834 - Cinnamon) → Cinnamon is a desktop environment, not a threat.

D (35963 - xrdp) → xrdp is a remote desktop service, expected behavior.

The user has become an insider threat by downloading software that contains malware onto a computer that eventually infects numerous other systems. An insider threat is a person or entity that has legitimate access to an organization’s systems, networks, or resources and uses that access to cause harm or damage to the organization. An insider threat can be intentional or unintentional, malicious or negligent, and can result from various actions or behaviors, such as downloading unauthorized software, violating security policies, stealing data, sabotaging systems, or collaborating with external attackers.

The MITRE ATT & CK framework is specifically designed for tracking Tactics, Techniques, and Procedures (TTPs) associated with cyber threats. It provides a detailed matrix of known adversarial behaviors, which is useful for correlating SIEM data to known attack patterns. According to CompTIA CySA+, MITRE ATT & CK is an industry-standard framework for threat intelligence and behavior analysis, making it the ideal tool for tracking malicious IP addresses and understanding their tactics. Other options like OSSTMM, the Diamond Model, and OWASP do not focus on TTPs as directly as MITRE ATT & CK does.

A discovery scan is a type of web application scanning that involves identifying active, internet-facing web applications and their URIs, without performing any intrusive or in-depth tests. This type of scan can help to understand the scope and structure of a web application before conducting more comprehensive vulnerability scans12. References: 1: OWASP Vulnerability Scanning Tools 2: CISA Web Application Scanning

This option represents the least impactful risk because it has the lowest base score among the four options, and it also requires high privileges, user interaction, and high attack complexity to exploit, which reduces the likelihood of a successful attack.

The correct answer is B because this is a critical infrastructure / ICS / OT environment. The safest option listed is a targeted, low-impact banner-grabbing approach against the known standard ports: TCP 80 for HTTP and TCP 502 for Modbus. In critical infrastructure, the analyst should avoid aggressive or broad scanning methods that could disrupt fragile industrial systems.

Exact supporting extract: the Secbay CySA+ guide states that vulnerability scanning of OT environments, including ICS and SCADA systems, requires specialized tools and methodologies because these environments have unique security requirements and constraints. It also states that vulnerabilities in ICS can have severe operational and safety implications.

The same guide explains that Modbus is a protocol used in industrial control systems and enables communication among devices connected to the same network.

The Sybex CySA+ Study Guide explains that service identification may be done by connecting and grabbing the banner or connection information provided by the service. It also explains that Nmap can perform service and version detection, but the more aggressive options are less appropriate for sensitive ICS environments.

Why the other options are incorrect:

A is incorrect because a general IT vulnerability scanner may be too intrusive for an oil and gas pipeline ICS environment.

C is incorrect because -A enables aggressive Nmap detection features, which may include OS detection, version detection, scripts, and traceroute. That is riskier in ICS/OT environments.

D is incorrect because Masscan is designed for high-speed scanning and is inappropriate for sensitive critical infrastructure networks.

B is best because it targets only the known ports and uses a less aggressive identification method.

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.

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​.

TheDiamond Model of Intrusion Analysisconsists offour core attributes:

Adversary– The threat actor behind the attack.

Capability– The tools and techniques used.

Infrastructure– The systems used by the adversary (e.g., botnets, C2 servers).

Victim– The target of the attack​.

Option A (Delivery)andOption B (Weaponization)are part of theCyber Kill Chain, not the Diamond Model.

Option C (Command and control)is an attack phase butnot a core attribute of the Diamond Model.

Option D (Capability) is correct, as it represents the tools and attack methods used by adversaries.

Thus,D is the correct answer.

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.

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

Microsegmentation involves dividing a network into smaller, isolated segments to restrict lateral movement within the network. This is crucial within a Zero Trust architecture, which assumes that no entity (internal or external) is inherently trustworthy. By limiting access to only necessary network segments, microsegmentation reduces the impact of a potential breach by containing it within a limited area. CompTIA emphasizes microsegmentation as an effective strategy to minimize risk and improve security posture by isolating resources based on the principle of least privilege.

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.

The lessons-learned register is an essential document that captures insights and feedback from past exercises or incidents, highlighting what went well and what did not. By utilizing this register, the SOC manager can identify specific areas for improvement and develop actionable steps to enhance future response efforts. According to CompTIA’s CySA+ and Security+ guidance, lessons learned fromtabletop exercises are crucial for iterative improvements in an incident response plan. Options A, B, and C are useful resources, but the lessons-learned register specifically focuses on reflection and improvement, which is the primary objective in this context.

The best way to ensure that the investigation complies with HR or privacy policies is to ensure that the case details do not reflect any user-identifiable information, such as name, email address, phone number, or employee ID. This can help protect the privacy and confidentiality of the user and prevent any potential discrimination or retaliation. Additionally, password protecting the evidence and restricting access to personnel related to the investigation can help preserve the integrity and security of the evidence and prevent any unauthorized or accidental disclosure or modification.

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.

Implementing input validation is the best way to mitigate the buffer overflow vulnerability at the application level. Input validation is a technique that checks the data entered by users or attackers against a set of rules or constraints, such as data type, length, format, or range. Input validation can prevent common web application attacks such as SQL injection, cross-site scripting (XSS), or command injection, which exploit the lack of input validation to execute malicious code or commands on the server or the client side. By validating the input before allowing submission, the web application can reject or sanitize any malicious or unexpected input, and protect the application from being compromised12. References: How to detect, prevent, and mitigate buffer overflow attacks - Synopsys, How to mitigate buffer overflow vulnerabilities | Infosec

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.

A CASB (Cloud Access Security Broker) is a security solution that acts as an intermediary between cloud users and cloud providers, and monitors and enforces security policies for cloud access and usage. A CASB can help organizations protect their data and applications in the cloud from unauthorized or malicious access, as well as comply with regulatory standards and best practices. A CASB can also provide visibility, control, and analytics for cloud activity, and identify and mitigate potential threats12

The other options are not correct. DMARC (Domain-based Message Authentication, Reporting and Conformance) is an email authentication protocol that helps email domain owners prevent spoofing and phishing attacks by verifying the sender’s identity and instructing the receiver how to handle unauthenticated messages34 SIEM (Security Information and Event Management) is a security solution that collects, aggregates, and analyzes log data from various sources across an organization’s network, such as applications, devices, servers, and users, and provides real-time alerts, dashboards, reports, and incident response capabilities to help security teams identify and mitigate cyberattacks56 PAM (Privileged Access Management) is a security solution that helps organizations manage and protect the access and permissions of users, accounts, processes, and systems that have elevated or administrative privileges. PAM can help prevent credential theft, data breaches, insider threats, and compliance violations by monitoring, detecting, and preventing unauthorized privileged access to critical resources78

1. How many employees clicked on the link in the phishing email?

According to the email server logs, 25 employees clicked on the link in the phishing email.

2. On how many workstations was the malware installed?

According to the file server logs, the malware was installed on 15 workstations.

3. What is the executable file name of the malware?

The executable file name of the malware is svchost.EXE.

Answers

1. 25

2. 15

3. svchost.EXE

Deploying EDR on the web server and the database server to reduce the adversaries capabilities and using micro segmentation to restrict connectivity to/from the web and database servers are two compensating controls that will help contain the adversary while meeting the other requirements. A compensating control is a security measure that is implemented to mitigate the risk of a vulnerability or an attack when the primary control is not feasible or effective. EDR stands for Endpoint Detection and Response, which is a tool that monitors endpoints for malicious activity and provides automated or manual response capabilities. EDR can help contain the adversary by detecting and blocking their actions, such as data exfiltration, lateral movement, privilege escalation, or command execution. Micro segmentation is a technique that divides a network into smaller segments based on policies and rules, and applies granular access controls to each segment. Micro segmentation can help contain the adversary by isolating the web and database servers from other parts of the network, and limiting the traffic that can flow between them. Official References:

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

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

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

Timeline analysis in digital forensics involves creating a chronological sequence of events based on system logs, file changes, and other forensic data. This process often uses graphical representations to illustrate and analyze how an incident unfolded over time, making it easier to identify key events and potential indicators of compromise. This approach is highlighted in CompTIA Cybersecurity Analyst (CySA+) practices as crucial for understanding the scope and sequence of a security incident. The other options do not involve chronological or graphical analysis to the extent that timeline analysis does.

The correct answer is B. Adversary emulation.

Adversary emulation is a technique that involves mimicking the tactics, techniques, and procedures (TTPs) of a specific threat actor or group to test the effectiveness of the security controls and incident response capabilities of an organization1. Adversary emulation can help identify and address the gaps and weaknesses in the security posture of an organization, as well as improve the readiness and skills of the security team. Adversary emulation can also help measure the dwell time, which is the duration that a threat actor remains undetected inside the network2.

The other options are not the best techniques to meet the CISO’s goals. Vulnerability scanning (A) is a technique that involves scanning the network and systems for known vulnerabilities, but it does not simulate a real attack or test the incident response capabilities. Passive discovery © is a technique that involves collecting information about the network and systems without sending any packets or probes, but it does not identify or exploit any vulnerabilities or test the security controls. Bug bounty (D) is a program that involves rewarding external researchers or hackers for finding and reporting vulnerabilities in an organization’s systems or applications, but it does not focus on a specific threat actor or group.

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.

To identify the initial compromise, the analyst should start with the earliest suspicious activity in the timeline and pivot into the audit logs for the principal (identity) associated with that first alert.

Here, the first notable event is 02:00 excessive API failures tied to jdoe12@myorg.com. That commonly indicates password guessing, token misuse, or other authentication abuse attempts. The next events (02:15 metadata service access, 05:10 mass VM creation by a service account, 05:40 malware) look like follow-on activity after an initial foothold. Therefore, the best first step is to check whether those API failures were followed by any successful API calls by that user and then correlate those successful actions to the later stages in project staging-01.

This approach aligns with CySA+ guidance that analysts should use logs + timestamps to build a timeline and correlate events across identities/systems to understand scope and progression:

Sybex emphasizes correlating events from multiple sources and using that correlation to determine scope and impact:Exact extract (Sybex Study Guide): “Security analysts are often asked to help analyze that data… Knowing if other events are correlated with the initial event… [and] understanding what systems, users, services, or other assets were involved…”

Secbay underscores that logs and timestamps are key to forming an accurate incident timeline (which is exactly what we’re doing by starting from the earliest alert):Exact extract (Secbay Press): “System and application logs with timestamps help create a timeline of events, aiding in understanding when specific actions occurred during the incident.”

Why Option B is best vs. the others

B starts with the earliest suspicious identity and seeks successful API activity that would confirm compromise and explain subsequent actions (metadata access → service account actions → malware).

A is too broad initially (“all activity under project staging-01”) and anchors on a VM that only appears later; it’s not the best first pivot when you already have an earlier suspect identity.

C starts at the compute-instance phase (05:10) rather than the earliest authentication/API anomaly (02:00), so it’s more likely to find post-compromise actions rather than the initial entry.

D anchors on a specific later VM (fd031f) and compute APIs, again likely after the initial compromise.

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

Mike Chapple & David Seidl, CompTIA CySA+ Study Guide (CS0-003): correlate other events with the initial event; identify involved users/systems/services

Secbay Press, CompTIA CySA+ Exam Prep Guide (CS0-003): logs + timestamps build a timeline of events and support analysis of incident progression

Data exfiltration is the theft or unauthorized transfer or movement of data from a device or network. It can occur as part of an automated attack or manually, on-site or through an internet connection, and involve various methods. It can affect personal or corporate data, such as sensitive or confidential information. Data exfiltration can be prevented or detected by using compression, encryption, authentication, authorization, and other controls1

The network activity shows that a device on the network is sending an outbound email via a mail client to a non-company email address daily at 10:00 p.m. This could indicate that the device is compromised by malware or an insider threat, and that the email is used to exfiltrate data from the network to an external party. The email could contain attachments, links, or hidden data that contain the stolen information. The timing of the email could be designed to avoid detection by normal network monitoring or security systems.

The correct answer is A. Implanted a backdoor.

A backdoor is a method that allows an unauthorized user to access a system or network without the permission or knowledge of the owner. A backdoor can be installed by exploiting a software vulnerability, by using malware, or by physically modifying the hardware or firmware of the device. A backdoor can be used for various malicious purposes, such as stealing data, installing malware, executing commands, or taking control of the system.

In this case, the consultant implanted a backdoor in the website by using an HTML and PHP code snippet that displays an image of a shutdown button and an alert message that says “Exit”. However, the code also echoes the remote address of the server, which means that it sends the IP address of the visitor to the attacker. This way, the attacker can identify and target the visitors of the website and use their IP addresses to launch further attacks or gain access to their devices.

The code snippet is an example of a clickjacking attack, which is a type of interface-based attack that tricks a user into clicking on a hidden or disguised element on a webpage. However, clickjacking is not the main goal of the consultant, but rather a means to implant the backdoor. Therefore, option C is incorrect.

Option B is also incorrect because privilege escalation is an attack technique that allows an attacker to gain higher or more permissions than they are supposed to have on a system or network. Privilege escalation can be achieved by exploiting a software vulnerability, by using malware, or by abusing misconfigurations or weak access controls. However, there is no evidence that the consultant implemented privilege escalation on the website or gained any elevated privileges.

Option D is also incorrect because patching is a process of applying updates to software to fix errors, improve performance, or enhance security. Patching can prevent or mitigate various types of attacks, such as exploits, malware infections, or denial-of-service attacks. However, there is no indication that the consultant patched the web server or improved its security in any way.

A HTTP/404 error code means that the requested page or resource was not found on the web server. This could be caused by various reasons, such as incorrect URLs, moved or deleted pages, missing assets, or server misconfigurations123. The analyst should first identify the source of the requests and examine the related activity to determine if they are legitimate or malicious, and what actions need to be taken to resolve the issue. The other options are either premature or irrelevant without further investigation. References: 1: 404 Page Not Found Error: What It Is and How to Fix It 2: 404 Error Code: What Causes Them and How To Fix It 3: About 404 errors and how to Troubleshoot it?

From the logs, PC3 showsoutlook.exe spawning excel.exe at 1:15 PM, and laterexcel.exe spawning procdump.exe at 1:16 PM. This is highly suspicious becauseoutlook.exe should not normally launch Excel, andprocdump.exe is often used by attackers to dump process memory, which is a common technique in credential theft​.

PC1:Running expected Windows processes (wininit.exe spawning services.exe and lsass.exe).

PC2:Running a browser process (chrome.exe) from explorer.exe, which is normal.

PC3:Highly suspicious behavior (Excel spawning procdump.exe).

PC4:Running mstsc.exe (Remote Desktop) from explorer.exe, which is expected.

PC5:Running Firefox from explorer.exe, which is normal.

Thus,PC3 should be prioritized for investigationdue to its potential involvement in credential theft.

One of the best actions to take after the conclusion of a security incident to improve incident response in the future is to schedule a review with all teams to discuss what occurred, what went well, what went wrong, and what can be improved. This review is also known as a lessons learned session or an after-action report. The purpose of this review is to identify the root causes of the incident, evaluate the effectiveness of the incident response process, document any gaps or weaknesses in the security controls, and recommend corrective actions or preventive measures for future incidents. Official References: https://www.eccouncil.org/cybersecurity-exchange/threat-intelligence/cyber-kill-chain-seven-steps-cyberattack/

After recovering a compromised server to its previous state, the analyst should perform forensic analysis to determine the root cause, impact, and scope of the incident, as well as to identify any indicators of compromise, evidence, or artifacts that can be used for further investigation or prosecution. References: CompTIA CySA+ Study Guide: Exam CS0-003, 3rd Edition, Chapter 6, page 244; CompTIA CySA+ CS0-003 Certification Study Guide, Chapter 6, page 253.

The function that would help the analyst identify IP addresses from the same country is:

function x() { info=$(geoiplookup $1) & & echo “$1 | $info” }

This function takes an IP address as an argument and uses the geoiplookup command to get the geographic location information associated with the IP address, such as the country name, country code, region, city, or latitude and longitude. The function then prints the IP address and the geographic location information, which can help identify any IP addresses that belong to the same country. 

An incident manager should work with the legal and public relations entities to ensure correct processes are adhered to when communicating incident reporting to the general public, as a best practice. The legal entity can provide guidance on the legal implications and obligations of disclosing the incident, such as compliance with data protection laws, contractual obligations, and liability issues. The public relations entity can help craft the appropriate message and tone for the public communication, as well as manage the reputation and image of the organization in the aftermath of the incident. These two entities can help the incident manager balance the need for transparency and accountability with the need for confidentiality and security12. References: Incident Communication Templates, Incident Management: Processes, Best Practices & Tools - Atlassian

Proprietary systems are systems that are owned and controlled by a specific vendor or manufacturer, and that use proprietary standards or protocols that are not compatible with other systems. Proprietary systems can pose a challenge for vulnerability management, as they may not allow users to access or modify their configuration, update their software, or patch their vulnerabilities. In this case, two of the critical systems cannot be upgraded due to a vendor appliance that the company does not have access to. This indicates that these systems and associated vulnerabilities are examples of proprietary systems as inhibitors to remediation

A tabletop exercise is the most likely action that an analyst would perform after an incident has been investigated. A tabletop exercise is a simulation of a potential incident scenario that involves the key stakeholders and decision-makers of the organization. The purpose of a tabletop exercise is to evaluate the effectiveness of the incident response plan, identify the gaps and weaknesses in the plan, and improve the communication and coordination among the incident response team and other parties. A tabletop exercise can help the analyst to learn from the incident investigation, test the assumptions and recommendations made during the investigation, and enhance the preparedness and resilience of the organization for future incidents12. Risk assessment, root cause analysis, and incident response plan are all actions that an analyst would perform before or during an incident investigation, not after. Risk assessment is the process of identifying, analyzing, and evaluating the risks that may affect the organization. Root cause analysis is the method of finding the underlying or fundamental causes of an incident. Incident response plan is the document that defines the roles, responsibilities, procedures, and resources for responding to an incident345. References: Tabletop Exercises: Six Scenarios to Help Prepare Your Cybersecurity Team, Tabletop Exercises for Incident Response - SANS Institute, Risk Assessment - NIST, Root Cause Analysis - OWASP, Incident Response Plan | Ready.gov

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.

In case of a phishing attack, it’s crucial to review what actions were taken by the employee and analyze the phishing email to understand its nature and impact.References: CompTIA CySA+ Study Guide: Exam CS0-003, 3rd Edition, Chapter 6, page 246; CompTIA CySA+ CS0-003 Certification Study Guide, Chapter 6, page 255.

Threat modelingis aproactiveapproach used toidentify, analyze, and mitigate potential threatsbefore they impact production systems. It is especially useful in early development stages to anticipate vulnerabilities and attack paths​.

Option B (Penetration testing)is areactive measureperformed on deployed systems, rather than prior to production.

Option C (Bug bounty)programs incentivize external researchers but do not proactively model risksbefore deployment.

Option D (SDLC training)improves security awareness but does notactively assess risks.

Thus,A (Threat modeling) is the best choice, as it enablesearly identification and mitigation of security risks​.

Performing a tabletop drill based on previously identified incident scenarios is the best way to test the changes to the BC and DR plans without any impact to the business, as it is a low-cost and low-risk method of exercising the plans and identifying any gaps or issues. A tabletop drill is a type of BC/DR exercise that involves gathering key personnel from different departments and roles and discussing how they would respond to a hypothetical incident scenario. A tabletop drill does not involve any actual simulation or disruption of the systems or processes, but rather relies on verbal communication and documentation review. A tabletop drill can help to ensure that everyone is familiar with the BC/DR plans, that the plans reflect the current state of the organization, and that the plans are consistent and coordinated across different functions. The other options are not as suitable as performing a tabletop drill, as they involve more cost, risk, or impact to the business. Simulating an incident by shutting down power to the primary data center is a type of BC/DR exercise that involves creating an actual disruption or outage of a critical system or process, and observing how the organization responds and recovers. This type of exercise can provide a realistic assessment of the BC/DR capabilities, but it can also cause significant impact to the business operations, customers, and reputation. Migrating active workloads from the primary data center to the secondary location is a type of BC/DR exercise that involves switching over from one system or site to another, and verifying that the backup system or site can support the normal operations. This type of exercise can help to validate the functionality and performance of the backup system or site, but it can also incur high costs, complexity, and potential errors or failures. Comparing the current plan to lessons learned from previous incidents is a type of BC/DR activity that involves reviewing past experiences and outcomes, and identifying best practices or improvement opportunities. This activity can help to update and refine the BC/DR plans, but it does not test or validate them in a simulated or actual scenario

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.

SOAR (Security Orchestration, Automation and Response) and SIEM (Security Information and Event Management) are solutions that can help centralize the workload for the internal security team by collecting, correlating, and analyzing alerts from different sources, such as EDR. SOAR can also automate and streamline incident response workflows, while SIEM can provide dashboards and reports for security monitoring and compliance. References: What is EDR? Endpoint Detection & Response, How Does the Cyber Kill Chain Protect Against Attacks?; What is EDR Solution?, EDR solutions secure diverse endpoints through central monitoring

CVSS 3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H is the attack vector that the analyst should remediate first, as it has the highest CVSSv3 score of 8.1. CVSSv3 (Common Vulnerability Scoring System version 3) is a standard framework for rating the severity of vulnerabilities, based on various metrics that reflect the characteristics and impact of the vulnerability. The CVSSv3 score is calculated from three groups of metrics: Base, Temporal, and Environmental. The Base metrics are mandatory and reflect the intrinsic qualities of the vulnerability, such as how it can be exploited, what privileges are required, and what impact it has on confidentiality, integrity, and availability. The Temporal metrics are optional and reflect the current state of the vulnerability, such as whether there is a known exploit, a patch, or a workaround. The Environmental metrics are also optional and reflect the context of the vulnerability in a specific environment, such as how it affects the asset value, security requirements, or mitigating controls. The Base metrics produce a score ranging from 0 to 10, which can then be modified by scoring the Temporal and Environmental metrics. A CVSS score is also represented as a vector string, a compressed textual representation of the values used to derive the score.

The attack vector in question has the following Base metrics:

Attack Vector (AV): Network (N). This means that the vulnerability can be exploited remotely over a network connection.

Attack Complexity (AC): Low (L). This means that the attack does not require any special conditions or changes to the configuration of the target system.

Privileges Required (PR): Low (L). This means that the attacker needs some privileges on the target system to exploit the vulnerability, such as user-level access.

User Interaction (UI): None (N). This means that the attack does not require any user action or involvement to succeed.

Scope (S): Unchanged (U). This means that the impact of the vulnerability is confined to the same security authority as the vulnerable component, such as an application or an operating system.

Confidentiality Impact ©: High (H). This means that the vulnerability results in a total loss of confidentiality, such as unauthorized disclosure of all data on the system.

Integrity Impact (I): High (H). This means that the vulnerability results in a total loss of integrity, such as unauthorized modification or deletion of all data on the system.

Availability Impact (A): High (H). This means that the vulnerability results in a total loss of availability, such as denial of service or system crash.

Using these metrics, we can calculate the Base score using this formula:

Base Score = Roundup(Minimum[(Impact + Exploitability), 10])

Where:

Impact = 6.42 x [1 - ((1 - Confidentiality) x (1 - Integrity) x (1 - Availability))]

Exploitability = 8.22 x Attack Vector x Attack Complexity x Privileges Required x User Interaction

Using this formula, we get:

Impact = 6.42 x [1 - ((1 - 0.56) x (1 - 0.56) x (1 - 0.56))] = 5.9

Exploitability = 8.22 x 0.85 x 0.77 x 0.62 x 0.85 = 2.8

Base Score = Roundup(Minimum[(5.9 + 2.8), 10]) = Roundup(8.7) = 8.8

Therefore, this attack vector has a Base score of 8.8, which is higher than any other option.

The other attack vectors have lower Base scores, as they have different values for some of the Base metrics:

CVSS:3.0/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H has a Base score of 6.2, as it has a lower value for Attack Vector (Physical), which means that the vulnerability can only be exploited by having physical access to the target system.

CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H has a Base score of 7.4, as it has a lower value for Attack Vector (Adjacent Network), which means that the vulnerability can only be exploited by being on the same physical or logical network as the target system.

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H has a Base score of 6.8, as it has a lower value for Attack Vector (Local), which means that the vulnerability can only be exploited by having local access to the target system, such as through a terminal or a command shell.

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.

Vulnerability management reporting and communication focuses on giving stakeholders the information they need to prioritize, assign, track, and complete remediation. That typically includes:

Risk severity / risk score (to prioritize and communicate urgency)

Timelines (when fixes are due, often tied to SLOs/SLAs and internal targets)

Dependencies (what must happen first or what systems/teams a fix relies on)

Remediation ownership / responsible parties (who is accountable for fixing each item)

This maps directly to Option D.

Exact extract (CompTIA CySA+ CS0-003 Exam Objectives – Vulnerability management reporting):

Vulnerability management reporting includes “Risk score … [and] Prioritization.”

Exact extract (Secbay Press – Key components of action plans used for reporting/communication):

“Timeline and Prioritization: Specify timelines for addressing each vulnerability…”

“Responsible Parties: Clearly identify individuals or teams responsible…”

“Communication Strategy: Outline how the organization will communicate progress…”

These are the same practical reporting/communication items expressed in Option D:

“Risk severity levels” ↔ risk score / severity used for prioritization

“Timelines” ↔ timeline definition in action plans

“Remediation ownership” ↔ responsible parties/accountability

“Dependencies” are commonly tracked because they affect timelines and ownership (for example, engineering/ops sequencing and prerequisite changes), and they align with the objective’s focus on prioritization/action planning and stakeholder communication.

Why the other options are not the best match:

A includes items that are valuable inputs to prioritization (risk assessment, BIA), but vulnerability reporting/communication (per objectives) is centered on reporting vulnerabilities, affected hosts, risk scoring, mitigations, recurrence, prioritization, and action plans, not BCPs as core reporting factors.

B mixes relevant items (MTTR, dependencies) with disaster recovery plans, which are DR/BC-focused rather than core vulnerability reporting elements.

C includes several incident response / SOC monitoring metrics (alert volume characteristics, MTTD) that are not the primary focus of vulnerability management reporting (even though false positives can be tracked as a VM metric, the overall set is misaligned).

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

CompTIA CySA+ CS0-003 Exam Objectives v4.0: vulnerability management reporting includes risk score and prioritization; action plans and stakeholder communication

Secbay Press, CompTIA CySA+ Exam Prep Guide (CS0-003): action plan components include timelines, responsible parties (ownership), and communication strategy

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​.

The correct answer is D because random-looking DNS requests can indicate malware using a domain generation algorithm (DGA) for command-and-control, but the analyst should first validate the suspicious domains using threat intelligence or reputation sources. The scenario asks what should be done first to determine whether Host X has been compromised, so enrichment and validation of the domain indicators is the best first step.

Exact supporting extract: the All-in-One CySA+ guide explains that malware may use DGAs for command-and-control exchanges and that high-entropy domains often look like gibberish to humans. It also warns that DGAs may have legitimate uses in content delivery networks, so additional analysis is needed to reduce false positives.

The same guide defines a DGA as a threat actor technique used to generate domain names rapidly using seemingly random but predictable processes so malware can eventually connect with command-and-control infrastructure.

Why the other options are incorrect:

A is incorrect because allowing the domains before validation may permit command-and-control or data exfiltration.

B is incorrect because reinstalling the software does not determine whether the DNS domains are malicious or legitimate.

C is incorrect because blocking all outbound connections is a containment action, not the best first investigative step.

D is correct because threat intelligence helps validate whether the suspicious domains are known malicious infrastructure or legitimate generated domains.

The key phrase is “analyzes suspicious data after scanning”. Before you can prioritize remediation, you must first ensure the scan results are valid—i.e., determine whether the findings are true positives vs. false positives. That validation step is a core part of vulnerability management because it prevents wasting time remediating issues that do not actually exist and ensures your prioritization decisions are based on accurate findings.

The All-in-One CySA+ CS0-003 guide explicitly states that after receiving vulnerability scan data, the analyst’s review process must focus on validating reported vulnerabilities (true/false positives). It also directly ties this to remediation/prioritization.

Exact extract (All-in-One Exam Guide):

“It is up to the analyst to review and make sense of vulnerability data and findings… The two most important outcomes of the review process are to determine the validity of reported vulnerabilities…”

It further emphasizes the importance of differentiating true positives from false positives for remediation and prioritization:

Exact extract (All-in-One Exam Guide):

“Distinguishing true positives from false positives… can be a tricky part of vulnerability remediation and prioritization.”

So, Option B (determine true/false positives) is the best action specifically to prioritize remediation tasks based on scan results.

Why the other options are not best:

A: Sending to IR may be appropriate if there is evidence of an active incident, but the question is framed as post-scan vulnerability management (not confirmed incident handling). Validation comes first.

C: Tickets and timeframes are important (often driven by SLAs/SLOs), but setting those correctly depends on confirming the findings are real and understanding severity/impact first.

D: Compensating controls and risk register entries are appropriate when remediation is not immediately feasible, but again you must confirm validity and then prioritize based on risk/impact.

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

Mya Heath et al., CompTIA CySA+ All-in-One Exam Guide (CS0-003): validating vulnerability scan results; true/false positives; link to remediation prioritization

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

The correct answers are A. System criticality and D. Threat intelligence.

A company may reprioritize a vulnerability score when the affected system is more important to the business than the raw CVSS score alone indicates. A vulnerability on a business-critical system may receive higher priority than the same vulnerability on a low-value system. The CySA+ materials state that vulnerabilities may be prioritized based on system criticality, including the critical nature of the data processed and the business processes that use the host.

Threat intelligence can also cause reprioritization. If intelligence shows that a vulnerability is being actively exploited in the wild or targeted by relevant threat actors, the organization should raise its priority even if the base vulnerability score is not the highest. The Secbay CySA+ guide states that organizations should incorporate threat intelligence to understand the current threat landscape and prioritize vulnerabilities actively exploited in the wild.

Why the other options are incorrect:

B. Alert volume is an incident response or monitoring metric, not a direct reason to reprioritize a vulnerability score.

C. Unexpected outage may affect operations, but it is not a standard vulnerability score reprioritization factor.

E. Patch availability affects remediation planning and timing, but the two strongest score-reprioritization factors in this question are asset/system criticality and threat intelligence.

F. Public relations may affect communications strategy after an incident, but it is not a core vulnerability prioritization factor.

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

Regular expressions are powerful tools for searching text based on specific patterns, making them ideal for parsing Linux log files to detect security events with repeatable patterns. In Bash, regular expressions can be used in commands like grep or awk to efficiently filter log data. CompTIA CySA+emphasizes the use of regular expressions in log analysis for pattern matching, a common requirement for identifying suspicious activities in log files. Options B, C, and D are less suited for this specific task due to their limited pattern-matching capabilities or platform constraints.

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/

The output shows that the web application has a cross-origin resource sharing (CORS) header that allows any origin to access its resources. This is a security misconfiguration that could allow malicious websites to make requests to the web application on behalf of the user and access sensitive data or perform unauthorized actions. The tuning recommendation is to configure the Access-Control-Allow-Origin header to only allow authorized domains that need to access the web application’s resources. This would prevent unauthorized cross-origin requests and reduce the risk of cross-site request forgery (CSRF) attacks.

The key goal of the containment stage in an incident response process is to limit further damage from occurring. This involves taking immediate steps to isolate the affected systems or network segments to prevent the spread of the incident and mitigate its impact. Containment strategies can be short-term, to quickly stop the incident, or long-term, to prepare for the eradication and recovery phases.

Data breach notification laws for personally identifiable information (PII) generally require organizations to provide timely notification to (1) regulatory authorities (regulators/data protection authorities) and (2) affected individuals (customers/data subjects), within legally mandated timeframes.

The Secbay Press CySA+ CS0-003 guide explicitly describes this requirement in multiple places:

Regulatory reporting + notifying affected individuals:Exact extract (Secbay Press): “Reporting the incident to regulatory authorities and notifying affected individuals in accordance with… privacy laws…”

Timeliness is required by law:Exact extract (Secbay Press): “Timeliness of Reporting: Adhering to stipulated timeframes for reporting incidents…”

Customers/affected individuals must be notified within the legally mandated timeframe:Exact extract (Secbay Press): “Sending notifications to customers within the legally mandated timeframe after confirming a data breach.”

These extracts directly support Option D: Regulators and affected customers.

Why the other options are incorrect

A (Service providers and business associates): Those relationships may have contractual notification requirements, but breach notification laws for PII focus on regulators and affected individuals.

B (Law enforcement and the media): These may be involved depending on incident type/requirements, but they are not universally required recipients under PII breach notification laws.

C (CERTs and industry associations): These are optional coordination entities, not mandated recipients for PII breach notification laws.

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

Secbay Press, CompTIA CySA+ Exam Prep Guide (CS0-003): notify regulatory authorities and affected individuals; timeliness requirements; legally mandated timeframe for customer notifications

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

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.

ThePHP script allows remote users to execute system commands via the system() function, meaning an attacker can send arbitrary commands to the server​.

Option A (Cross-site scripting - XSS)is incorrect because this script does not inject JavaScript into a webpage.

Option B (Reverse shell)is possible if an attacker sends a crafted command, but the script itself is more of a general backdoor than a dedicated reverse shell.

Option D (Logic bomb)is incorrect because a logic bomb is typicallytriggered by a specific event or daterather than executing arbitrary commands on demand.

Thus,C (Backdoor attempt) is the best answer, as this scriptgrants unauthorized remote command execution.

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

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.

An information sharing organization is a group or network of organizations that share threat intelligence, best practices, or lessons learned related to cybersecurity issues or incidents. An information sharing organization can help security analysts learn about new ransomware campaigns or other emerging threats, as well as get recommendations or guidance on how to prevent, detect, or respond to them. An information sharing organization can also help security analysts collaborate orcoordinate with other organizations in the same industry or region that may face similar threats or challenges.

Comprehensive Detailed Explanation:To safely analyze malware while avoiding unintended disclosure of company information, it is best to use a local sandbox in a microsegmented environment. Here’s why:

A. Upload the malware to the VirusTotal website

Risk: VirusTotal and similar services are public and may share uploaded files with other security vendors, potentially exposing proprietary or sensitive information.

B. Share the malware with the EDR provider

Limitation: While EDR providers may offer insight, sharing potentially sensitive malware samples externally still introduces risk of disclosure or data leaks.

C. Hire an external consultant to perform the analysis

Cost and Risk: Hiring an external consultant can be costly and may introduce risks related to third-party handling of sensitive data. Although it may provide insights, this is typically not the most efficient initial response.

D. Use a local sandbox in a microsegmented environment

Explanation: A local sandbox provides a secure, isolated environment for malware analysis without exposing sensitive data outside the organization. Microsegmentation enhances security by further isolating the sandbox from the network, preventing lateral movement if the malware attempts to communicate externally.

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.

Conducting regular code reviews using OWASP best practices is the most effective action to reduce risks associated with the application development. Code reviews are a systematic examination of the source code of an application to detect and fix errors, vulnerabilities, and weaknesses that may compromise the security, functionality, or performance of the application. Code reviews can help to improve the quality and security of the code, as well as to identify and remediate common security risks, such as insufficient logging capabilities. OWASP (Open Web Application Security Project) is a global nonprofit organization that provides free and open resources, tools, standards, and best practices for web application security. OWASP best practices for logging include following a common loggingformat and approach, logging relevant security events and data, protecting log data from unauthorized access or modification, and using log analysis and monitoring tools to detect and respond to security incidents. By following OWASP best practices for logging, developers can ensure that their web applications have sufficient and effective logging capabilities that can help to prevent, detect, and mitigate security threats.

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​.

Making a forensic image of the device and creating a SRA-I hash is the best step to preserve evidence, as it creates an exact copy of the device’s data and verifies its integrity. A forensic image is a bit-by-bit copy of the device’s storage media, which preserves all the information on the device, including deleted or hidden files. A SRA-I hash is a cryptographic value that is calculated from the forensic image, which can be used to prove that the image has not been altered or tampered with. The other options are not as effective as making a forensic image and creating a SRA-I hash, as they may not capture all the relevant data, or they may not provide sufficient verification of the evidence’s authenticity. Official References:

https://www.sans.org/blog/forensics-101-acquiring-an-image-with-ftk-imager/

https://swailescomputerforensics.com/digital-forensics-imaging-hash-value/

The XML file containsJavaScript embedded within a < description > tagthat executes an alert message, which is a commonCross-Site Scripting (XSS)attack vector. The issue occurs becausethe XML schema does not restrict the input to safe characters, allowingarbitrary script executionwhen the XML file is processed by a vulnerable application.

Solution: Implement Input Validation Using an XML Schema Constraint

Option Benforces awhitelist approachby allowingonly alphanumeric characters and spaces([a-zA-Z 0-9]*).

This prevents the inclusion ofmalicious JavaScript or special characterssuch as < , > , or & , which are required for XSS injection​.

Why are the other options incorrect?

Option A: Restricts input to aSocial Security Number (SSN) format ([0-9]{3}-[0-9] {2}-[0-9]{4}). While it prevents JavaScript injection, it is too restrictive and would break legitimate text-based content in the XML.

Option C: Restricts input toonly numeric values ([0-9]*), preventing JavaScript injection but also breaking legitimate non-numeric content in the < description > field.

Option D: Restricts input to asingle positive integer, which does not align with the expected text-based content.

Thus,Option Bis the correct answer, as it enforces proper input validation while still allowing expected text input​.

Communicating with staff about the official public communication plan is important to avoid unauthorized or inaccurate disclosure of information that could harm the organization’s reputation, security, or legal obligations. It also helps to ensure consistency and clarity of the messages delivered to the public and other stakeholders.

https://resources.sei.cmu.edu/asset_files/Handbook/2021_002_001_651819.pdf

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.

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.

Abackdooris a deliberate vulnerability inserted into the code, often allowing unauthorized access.

Source code review (Option D)is the best way to detect malicious code before it is deployed to production.

SDLC training (Option A)is helpful but does not directly prevent the insertion of backdoors.

Dynamic analysis (Option B)detects vulnerabilities at runtime but may not always identify backdoors in code.

Debugging (Option C)is useful for troubleshooting but does not address security vulnerabilities.

???? Reference:CompTIA CySA+ CS0-003 Official Study Guide, Secure Software Development Practices.

APIs are designed for standardized, well-defined communication between systems. Compared to one-off scripts (which can break when outputs, formats, versions, or endpoints change), API-based integrations are typically more stable and maintainable because they use vendor-supported interfaces intended for integration and automation across tools.

Secbay Press explicitly describes why APIs are used for tool integration: they enable “seamless data sharing, workflow automation, and orchestration across the security stack,” which reduces the overhead of maintaining brittle, custom script-based connections.

Exact extract (Secbay Press): “Integrate security tools and systems using APIs to enable seamless data sharing, workflow automation, and orchestration across the security stack.”

The Sybex Practice Tests reinforce the idea that API integration is the best choice when you need real-time or up-to-date integration between tools (another maintenance and reliability advantage over scripts/flat files):

Exact extract (Sybex Practice Tests): A SOAR integration question where real-time query capability is needed selects “API” as the best integration type.

Why the other options are not the most important reason here:

B is unrelated to vendor-to-vendor communication.

C can be true sometimes, but customization isn’t the primary driver versus standardization and maintainability.

D is about pipeline security; APIs can be used in CI/CD contexts, but that’s not the core reason for choosing APIs over scripts for vendor tool communication.

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

Secbay Press, CompTIA CySA+ Exam Prep Guide (CS0-003): APIs enable seamless cross-tool integration and orchestration

Chapple/Seidl, CompTIA CySA+ Practice Tests (CS0-003): API is the best integration type for real-time tool integration

Geoblocking is the best mitigation technique for unusual network scanning activity coming from a country that the company does not do business with, as it can prevent any potential attacks or data breaches from that country. Geoblocking is the practice of restricting access to websites or services based on geographic location, usually by blocking IP addresses associated with a certain country or region. Geoblocking can help reduce the overall attack surface and protect against malicious actors who may be trying to exploit vulnerabilities or steal information. The other options are not as effective as geoblocking, as they may not block all the possible sources of the scanning activity, or they may not address the root cause of the problem. Official References:

https://www.blumira.com/geoblocking/

https://www.avg.com/en/signal/geo-blocking

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.

Mean time to detect (MTTD) is a metric that measures the average time it takes for an organization to discover or detect an incident. It is a key performance indicator in incident management and a measure of incident response capabilities. A low MTTD indicates that the organization can quickly identify security threats and minimize their impact12.

SOAR stands for security orchestration, automation, and response, which is a term that describes a set of tools, technologies, or platforms that can help streamline, standardize, and automate security operations and incident response processes and tasks. SOAR can help minimize human engagement and aid in process improvement in security operations by reducing manual work, human errors, response time, or complexity. SOAR can also help enhance collaboration, coordination, efficiency, or effectiveness of security operations and incident response teams.

Transfer is the risk management principle that is accomplished by purchasing cyber insurance. Transfer is a strategy that involves shifting the risk or its consequences to another party, such as an insurance company, a vendor, or a partner. Transfer does not eliminate the risk, but it reduces the potential impact or liability of the risk for the original party. Cyber insurance is a type of insurance that covers the losses and damages resulting from cyberattacks, such as data breaches, ransomware, denial-of-service attacks, or network disruptions. Cyber insurance can help transfer the risk of cyber incidents by providing financial compensation, legal assistance, or recovery services to the insured party. Official References:

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

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

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

To mitigate brute-force attacks, implementing an account lockout policy (C) prevents continuous attempts by locking the account after a set number of failed logins. Blocking inbound connections on TCP port 3389 (RDP) from untrusted IP addresses (F) limits access, reducing the attack surface. According to CompTIA Security+, these controls effectively prevent unauthorized access. While blocking specific IPs (D) or disabling RDP (E) can also help, the lockout and firewall rules provide broader, proactive protection against this attack type.

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.

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

Asimulation(such as atabletop exercise or full-scale IR drill) is the best way to demonstrate real-world readiness without affecting operations​.

Option A (Reviewing lessons-learned and playbooks)is valuable but does not actively test readiness.

Option C (Deploying malware)is highly risky and unethical in a production environment.

Option D (Disaster recovery site testing)focuses on DR, not security incident readiness.

Thus,B is the best choice, as simulations effectivelytest incident response capabilities without operational disruption.

tcpdump is a command-line tool that can capture and analyze network packets from a given interface or file. The -n option prevents tcpdump from resolving hostnames, which can speed up the analysis. The -r option reads packets from a file, in this case packets.pcap. The host [IP address] filter specifies that tcpdump should only display packets that have the given IP address as either the source or thedestination. This command can help the security analyst detect connections to a suspicious IP address by collecting the packet captures from the gateway. Official References:

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

https://www.reddit.com/r/CompTIA/comments/tmxx84/passed_cysa_heres_my_experience_and_how_i_studied/

The best practice for securing access to sensitive data is to implement multifactor authentication (MFA), which combines multiple factors of authentication to enhance security.

Option B (Biometrics + Device with a Personalized Code) uses two strong factors:

Biometrics (something you are)

A device with a personalized code (something you have)This combination significantly reduces the risk of unauthorized access​.

Option A (Randomized Code) is good but weaker than biometrics because it relies only on something you have.

Option C (Passphrase) is single-factor authentication, which is susceptible to brute-force attacks​.

Option D (One-time Code + Push Notification) is useful, but email-based authentication can be vulnerable to phishing and MITM attacks.

Documenting the process in a step-by-step format on the team wiki ensures the junior analyst has a clear, repeatable reference. This approach also supports consistency and accuracy, and the documentation can be updated or referenced by other team members as needed. CompTIA emphasizes the importance of procedural documentation in both CySA+ and Security+ for ensuring team members have reliable resources for task execution, which aids in knowledge retention and standardized practices across the team.

When a patch cannot be deployed due to conflicting routine system upgrades, updating the risk register and requesting a change to the Service Level Agreement (SLA) is a practical approach. It allows for re-evaluation of the risk and adjustment of the SLA to reflect the current situation.

Comprehensive Detailed Explanation:SOAR (Security Orchestration, Automation, and Response) solutions are implemented to streamline security operations and improve efficiency. Key benefits include:

C. Reduce repetitive tasks: SOAR solutions automate routine and repetitive tasks, which helps reduce analyst workload and minimize human error.

F. Generate reports and metrics: SOAR platforms can automatically generate comprehensive reports and performance metrics, allowing organizations to track incident response times, analyze trends, and optimize security processes.

Other options are less relevant to the core functions of SOAR:

A. Minimize security attacks: While SOAR can aid in quicker response, it does not directly minimize the occurrence of attacks.

B. Itemize tasks for approval: Task itemization for approval is more relevant to project management tools.

D. Minimize setup complexity: SOAR solutions often require significant setup and integration with existing tools.

E. Define a security strategy: SOAR is more focused on automating response rather than strategy definition.

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

The activities taken by the process with PID 1024 will provide the best insight into this potentially malicious process, based on the anomalous behavior. BGInfo.exe is a legitimate tool that displays system information on the desktop background, but it can also be used by attackers to gather information about the compromised host or to disguise malicious processes12. By monitoring the activities of PID 1024, such as the files it accesses, the network connections it makes, or the commands it executes, the analyst can determine if the process is benign or malicious.

Data loss prevention (DLP) is a tool that can prevent the exposure of PII outside of an organization by monitoring, detecting, and blocking sensitive data in motion, in use, or at rest.

Comprehensive Detailed Explanation:The nmap scan results show that Telnet (port 23) is open. Telnet transmits data, including credentials, in plaintext, which is insecure and should be disabled to enhance security. Here’s an explanation of each option:

A. Disable all protocols that do not use encryption

Explanation: Disabling unencrypted protocols (such as Telnet) reduces exposure to man-in-the-middle (MITM) attacks and credential sniffing. Telnet should be replaced with a secure protocol like SSH, which provides encryption for transmitted data.

B. Configure client certificates for domain services

Explanation: While client certificates enhance authentication security, they are more relevant to services like LDAP over SSL (port 636), which is already secure. This would not address the Telnet vulnerability.

C. Ensure that this system is behind a NGFW

Explanation: A Next-Generation Firewall (NGFW) provides enhanced network security, but it may not mitigate the risks of unencrypted protocols if they are allowed internally.

D. Deploy a publicly trusted root CA for secure websites

Explanation: Public root CAs are used for website authentication and encryption, relevant only if this system is hosting a publicly accessible HTTPS service. It would not impact Telnet security.

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).

Data masking is a technique that replaces sensitive data with fictitious or anonymized data, while preserving the original format and structure of the data. This way, the data can be used for testing purposes without revealing the actual Pll information. Data masking is one of the best practices for data analysis of confidential data1. References: CompTIA CySA+ CS0-003 Certification Study Guide, page 343; Best Practices for Data Analysis of Confidential Data

The CISO’s requirements prioritize protecting customer (sensitive) data with encryption both in transit and at rest. The database that violates the most critical requirements—especially for sensitive/customer data—should be remediated first.

Why Database4 is the highest priority

Sensitive data + no encryption in transit (Port 80): Port 80 indicates HTTP (clear-text), which means no encryption in transit. Secbay explicitly states: “HTTP is a clear-text protocol that is generally secured via an SSL/TLS tunnel to produce HTTPS transmission.”

Uses weak/unsupported TLS version (TLS 1.1) + sensitive data: Even if TLS is “listed,” TLS 1.1 is not considered acceptable in modern secure configurations. Secbay’s protocol acceptability list marks TLS 1.1 = No (not acceptable), while TLS 1.2/1.3 are acceptable.

Customer data must be encrypted in transit and at rest: Secbay provides the exact requirement-style statement: “The organization implements encryption for sensitive data both in transit and at rest… Sensitive customer data is encrypted…”

So Database4 is the most severe because it involves Sensitive (customer) data while failing the “encryption in transit” requirement (HTTP/80) and also relying on an unacceptable TLS version (1.1).

Why the other databases are lower priority

Database3: TLS 1.2 on 443 + encryption at rest enabled + sensitive data → it already meets the CISO requirements.

Database2: Port 80 (no transit encryption) and encryption at rest disabled, but the data type is proprietary, not explicitly customer/sensitive. It is still important, but Database4 is worse because it impacts sensitive/customer data.

Database1: Data type is public; while TLS 1.1 is weak, it does not violate the “customer data” requirement and is less severe than Database4’s clear-text transport for sensitive data.

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

Secbay Press, CompTIA CySA+ Exam Prep Guide (CS0-003): encrypt sensitive customer data in transit and at rest

Secbay Press, CompTIA CySA+ Exam Prep Guide (CS0-003): HTTP is clear-text; TLS 1.1 not acceptable while TLS 1.2/1.3 are acceptable

When documenting a physical incident in a network data closet, taking photos provides a clear and immediate record of the situation, which is essential for thorough incident documentation and subsequent investigation.

Proper documentation of an incident in a data closet should include taking photos of the impacted items. This provides visual evidence and helps in understanding the physical context of the incident, which is crucial for a thorough investigation. Backing up configuration files, recording connections, and creating network diagrams, while important, are not the primary means of documenting the physical aspects of an incident.

During an incident, the legal team plays a crucial role in handling regulatory compliance and reviewing legal implications, such as contractual obligations and reporting requirements. Advising on regulatory reporting (Option C) ensures the organization meets legal mandates, while reviewing contracts (Option B) can address new or emergency services needed during the incident. According to CompTIA CySA+ and Security+ guidelines, these legal responsibilities are vital for compliance and risk management.Options related to staffing, damage assessments, and clearances typically fall under operational or HR responsibilities rather than legal purview.

Hacktivists are threat actors who use cyberattacks to promote a social or political cause, such as environmentalism, human rights, or democracy. They may target companies that they perceive as violating their values or harming the public interest. Hacktivists often use techniques such as defacing websites, launching denial-of-service attacks, or leaking sensitive data to expose or embarrass their targets12. References: An introduction to the cyber threat environment, page 3; What is a Threat Actor? Types & Examples of Cyber Threat Actors, section 2.

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.

Reviewing the code and debugging the code are two methods that can help a developer identify and fix runtime errors in the code. Reviewing the code involves checking the syntax, logic, and structure of the code for any errors or inconsistencies. Debugging the code involves running the code in a controlled environment and using tools such as breakpoints, watches, and logs to monitor the execution and find the source of errors. Both methods can help improve the quality and security of the code. 

The MITRE ATT & CK framework is widely used for tracking and categorizing Tactics, Techniques, and Procedures (TTPs) of adversaries. TTPs help analysts understand the behaviors and methods attackers employ during incidents, making this framework particularly useful in SIEM dashboards for correlating and identifying threats. While the other options (OSSTMM, Diamond Model, OWASP) offer various security methodologies, MITRE ATT & CK is specifically focused on documenting adversary behaviors, making it the best fit here. CompTIA CySA+ often emphasizes MITRE ATT & CK for mapping and understanding threat behaviors in incident response.

The metric that measures how quickly something is detected/identified is Mean Time to Detect (MTTD). Although MTTD is often used in incident detection, it directly matches the wording “how quickly … are identified” because it measures the time between occurrence and detection.

Secbay Press defines MTTD explicitly as the time to detect an issue:

Exact extract (Secbay Press):

“Mean Time to Detect (MTTD) is… the average time taken to identify and detect a security incident… Mean time to detect is how long it took… to when it was detected.”

Why the other options are not best:

KPI is a category/type of measure (a key metric), not the specific metric itself. Secbay distinguishes metrics vs KPIs and lists MTTD as a KPI example.

SLO is a service objective/target, not a measurement of detection speed by itself.

Alert volume measures quantity of alerts, not detection time.

Exact extract (Secbay Press):

“KPI: Mean Time to Detect (MTTD) and Mean Time to Respond (MTTR).”

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.

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​.

The correct answer is A. XML.

STIX and OpenloC are two standards for representing and exchanging cyber threat intelligence (CTI) information. STIX stands for Structured Threat Information Expression and OpenloC stands for Open Location and Identity Coordinates. Both standards use XML as the underlying data format to encode the information in a structured and machine-readable way. XML stands for Extensible Markup Language and it is a widely used standard for defining and exchanging data on the web. XML uses tags, attributes, and elements to describe the structure and meaning of the data. XML is also human-readable, as it uses plain text and follows a hierarchical and nested structure.

XML is not the only format that can be used to make STIX and OpenloC information readable by both humans and machines, but it is the most common and widely supported one. Other formats that can be used include JSON, CSV, or PDF, depending on the use case and the preferences of the information producers and consumers. However, XML has some advantages over other formats, such as:

XML is more expressive and flexible than JSON or CSV, as it can define complex data types, schemas, namespaces, and validation rules.

XML is more standardized and interoperable than PDF, as it can be easily parsed, transformed, validated, and queried by various tools and languages.

XML is more compatible with existing CTI standards and tools than other formats, as it is the basis for STIX 1.x, TAXII 1.x, MAEC, CybOX, OVAL, and others.

The best resource to ensure secure configuration of cloud infrastructure is A. CIS Benchmarks. CIS Benchmarks are a set of prescriptive configuration recommendations for various technologies, including cloud providers, operating systems, network devices, and server software. They are developed by a global community of cybersecurity experts and help organizations protect their systems against threats more confidently1

PCI DSS, OWASP Top Ten, and ISO 27001 are also important standards for information security, but they are not focused on providing specific guidance for hardening cloud infrastructure. PCI DSS is a compliance scheme for payment card transactions, OWASP Top Ten is a list of common web application security risks, and ISO 27001 is a framework for establishing and maintaining an information security management system. These standards may have some relevance for cloud security, but they are not as comprehensive and detailed as CIS Benchmarks

The MTTR (Mean Time to Resolution) decreases by 20% is the best possible outcome that this effort hopes to achieve, as it reflects the improvement in the efficiency and effectiveness of the incident response process by reducing analyst alert fatigue. Analyst alert fatigue is a term that refers to the phenomenon of security analysts becoming overwhelmed, desensitized, or exhausted by the large number of alerts they receive from various security tools or systems, such as DLP (Data Loss Prevention) or CASB (Cloud Access Security Broker). DLP is a security solution that helps to prevent unauthorized access, use, or transfer of sensitive data, such as personal information, intellectual property, or financial records. CASB is a security solution that helps to monitor and control the use of cloud-based applications and services, such as SaaS (Software as a Service), PaaS (Platform as a Service), or IaaS (Infrastructure as a Service). Both DLP and CASB can generate alerts when they detect potential data breaches, policy violations, or malicious activities, but they can also produce false positives, irrelevant information, or duplicate notifications that can overwhelm or distract the security analysts. Analyst alert fatigue can have negative consequences for the security posture and performance of an organization, such as missing or ignoring critical alerts, delaying or skipping investigations or remediations, making errors or mistakes, or losing motivation or morale. Therefore, it is important to reduce analyst alert fatigue and optimize the alert management process by using various strategies, such as tuning the alert thresholds and rules, prioritizing and triaging the alerts based on severity and context, enriching and correlating the alerts with additional data sources, automating or orchestrating repetitive or low-level tasks or actions, or integrating and consolidating different security tools or systems into a unified platform. By reducing analyst alert fatigue and optimizing the alert management process, the effort hopes to achieve a decrease in the MTTR, which is a metric that measures the average time it takes to resolve an incident from the moment it is reported to the moment it is closed. Alower MTTR indicates a faster and more effective incident response process, which can help to minimize the impact and damage of security incidents, improve customer satisfaction and trust, and enhance security operations and outcomes. The other options are not as relevant or realistic as the MTTR decreases by 20%, as they do not reflect the best possible outcome that this effort hopes to achieve. SIEM ingestion logs are reduced by 20% is not a relevant outcome, as it does not indicate any improvement in the incident response process or any reduction in analyst alert fatigue. SIEM (Security Information and Event Management) is a security solution that collects and analyzes data from various sources, such as logs, events, or alerts, and provides security monitoring, threat detection, and incident response capabilities. SIEM ingestion logs are records of the data that is ingested by the SIEM system from different sources. Reducing SIEM ingestion logs may imply less data volume or less data sources for the SIEM system, which may not necessarily improve its performance or accuracy. Phishing alerts drop by 20% is not a realistic outcome, as it does not depend on the integration of DLP and CASB or any reduction in analyst alert fatigue. Phishing alerts are notifications that indicate potential phishing attempts or attacks, such as fraudulent emails, websites, or messages that try to trick users into revealing sensitive information or installing malware. Phishing alerts can be generated by various security tools or systems, such as email security solutions, web security solutions, endpoint security solutions, or user awareness training programs. Reducing phishing alerts may imply less phishing attempts or attacks on the organization, which may not necessarily be influenced by the integration of DLP and CASB or any reduction in analyst alert fatigue. False positive rates drop to 20% is not a realistic outcome

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.

SLA (Service Level Agreement) is the best term to describe the document that defines the expectation to network customers that patching will only occur between 2:00 a.m. and 4:00 a.m., as it reflects the agreement between a service provider and a customer that specifies the services, quality, availability, and responsibilities that are agreed upon. An SLA is a common type of document that is used in various industries and contexts, such as IT, telecom, cloud computing, or outsourcing. An SLA typically includes metrics and indicators to measure the performance and quality of the service, such as uptime, response time, or resolution time. An SLA also defines the consequences or remedies for any breaches or failures of the service, such as penalties, refunds, or credits. An SLA can help to manage customer expectations, formalize communication, improve productivity, and strengthen relationships. The other terms are not as accurate as SLA, as they describe different types of documents or concepts. LOI (Letter of Intent) is a document that outlines the main terms and conditions of a proposed agreement between two or more parties, before a formal contract is signed. An LOI is usually non-binding and expresses the intention or interest of the parties to enter into a future agreement. An LOI can help to clarify the key points of a deal, facilitate negotiations, or demonstrate commitment. MOU (Memorandum of Understanding) is a document that describes a mutual agreement or cooperation between two or more parties, without creating any legal obligations or commitments. An MOU is usually more formal than an LOI, but less formal than a contract. An MOU can help to establish a common ground, define roles and responsibilities, or outline expectations and goals. KPI (Key Performance Indicator) is a concept that refers to a measurable value that demonstrates how effectively an organization or individual is achieving its key objectives or goals. A KPI is usually quantifiable andspecific, such as revenue growth, customer satisfaction, or employee retention. A KPI can help to track progress, evaluate performance, or identify areas for improvement.

Risk scoringis the best method for prioritizing patching, as it considers factors likeCVSS severity, exploitability, asset criticality, and business impact​.

Option A (Affected hosts)is relevant but does notdetermine prioritywithout a risk assessment.

Option C (Mitigation strategy)is useful but focuses on alternative protections rather than prioritization.

Option D (Annual recurrence)is not a standard method for vulnerability prioritization.

Thus,B is the correct answer, asrisk scores allow organizations to prioritize patching efforts effectively​.

Time synchronization is the process of ensuring that all systems in a network have the same accurate time, which is essential for correlating data points from different sources. If the system has an issue with time synchronization, the analyst may have difficulty matching events that occurred at the same time or in a specific order. Access rights, network segmentation, and invalid playbook are not directly related to the issue of correlating data points. Verified References: [CompTIA CySA+ CS0-002 Certification Study Guide], page 23

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.

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 Command and Control stage of the Cyber Kill Chain describes the communication between the attacker and the compromised system. The attacker may use this channel to send commands, receive data, or update malware. If the analyst discovers unusual outbound connections to an IP that was previously blocked, it may indicate that the attacker has established a command and control channel and bypassed the security controls. References: Cyber Kill Chain® | Lockheed Martin

Input validation vulnerabilities occur when an application fails to properly validate or sanitize user input, allowing malicious data to be processed. This can lead to various attacks, most notably cross-site scripting (XSS).

Option A:DNS poisoning

Incorrect Choice:DNS poisoning involves corrupting the DNS cache to redirect users to malicious sites. It is not related to input validation vulnerabilities.

Option B:Pharming

Incorrect Choice:Pharming redirects users from legitimate websites to fraudulent ones, typically through DNS poisoning or host file manipulation. It is not directly related to input validation.

Option C:Phishing

Incorrect Choice:Phishing involves tricking individuals into providing sensitive information through deceptive emails or websites. It exploits human behavior rather than technical input validation flaws.

Option D:Cross-site scripting

Correct Choice:Cross-site scripting (XSS) attacks occur when an application includes untrusted data in a web page without proper validation or escaping. This allows attackers to execute malicious scripts in users ' browsers, leading to data theft, session hijacking, or defacement. Remediating input validation vulnerabilities is essential to prevent XSS attacks.

Part 1:

Part 2:

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

AppServ1: No changes are needed for this server.

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

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

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

In digital forensics, a write blocker is a critical tool used to prevent any modifications to the source drive during imaging. When a forensic image is created, it should be an exact bit-for-bit copy of the original evidence. If a write blocker is not used, system processes or other unintended changes can alter the contents of the drive, leading to a hash mismatch between the original and the image copy​.

Chain of custody (Option A)ensures proper documentation of who accessed the evidence, but it does not directly affect the hash values.

Legal authorization (Option B)is necessary but unrelated to the technical integrity of the image.

Data integrity verification (Option C)is part of the process, but in this scenario, the failure to maintain integrity stems from the lack of a write blocker​.

Thus, the correct answer isD, as using a write blocker would have prevented any unintended changes to the data​.

In this scenario, the security analyst is presented with multiple vulnerabilities, including a critical zero-day vulnerability affecting the web server with a CVSS score of 10. The CVSS (Common Vulnerability Scoring System) provides a standardized method for rating IT vulnerabilities, with a score of 10 indicating the highest severity.

Option A:Contact the web systems administrator and request that they shut down the asset.

Correct Choice:Given the critical nature of a zero-day vulnerability with a CVSS score of 10, immediate action is warranted to prevent potential exploitation. Shutting down the affected web server reduces the attack surface and mitigates the risk until a patch or workaround is available. This aligns with incident response best practices, where containment is a priority to prevent further damage.

Option B:Monitor the patch releases for all items and escalate patching to the appropriate team.

Incorrect Choice:While monitoring for patches is essential, it is a reactive approach. In the case of a zero-day vulnerability with active exploitation potential, waiting for a patch without implementing immediate protective measures exposes the organization to significant risk.

Option C:Run the vulnerability scan again to verify the presence of the critical finding and the zero-day vulnerability in the environment.

Incorrect Choice:Re-scanning may confirm the vulnerability ' s presence but does not address the immediate threat. Action to mitigate the risk should take precedence over verification, especially when the vulnerability is known and critical.

Option D:Forward the advisory to the web security team and initiate the prioritization strategy for the other vulnerabilities.

Incorrect Choice:Communicating with the web security team is important; however, in the face of a critical zero-day vulnerability, immediate action (such as shutting down the affected asset) is necessary before addressing other vulnerabilities.

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

The best practice that the company should follow with this proxy is to decommission the proxy. Decommissioning the proxy involves removing or disposing of the proxy from the rack and the network, as well as deleting or wiping any data or configuration on the proxy. Decommissioning the proxy can help eliminate the vulnerability on the proxy, as well as reduce the attack surface, complexity, or cost of maintaining the network. Decommissioning the proxy can also free up space or resources for other devices or systems that are in use or needed by the company.

A prioritized list of critical systems defined by executive leadership is the best option to use to develop a business continuity plan. A business continuity plan (BCP) is a system of prevention and recovery from potential threats to a company. The plan ensures that personnel and assets are protected and are able to function quickly in the event of a disaster1. A BCP should include a business impact analysis, which identifies the critical systems and processes that are essential for the continuity of the business operations, and the potential impacts of their disruption2. The executive leadership should be involved in defining the critical systems and their priorities, as they have the strategic vision and authority to make decisions that affect the whole organization3. A diagram of all systems and interdependent applications, a repository for all the software used by the organization, and a configuration management database in print at an off-site location are all useful tools for documenting and managing the IT infrastructure, but they are not sufficient to develop a comprehensive BCP that covers all aspects of the business continuity4. References: What Is a Business Continuity Plan (BCP), and How Does It Work?, Business continuity plan (BCP) in 8 steps, with templates, Business continuity planning | Business Queensland, Understanding the Essentials of a Business Continuity Plan

The output shows that port 80 is open and running an HTTP service, indicating that the host could potentially be vulnerable to web-based attacks. The other options are not relevant for this purpose: the host is responsive to the ICMP request, as shown by the “Host is up” message; the host is not running a mail server, as there is no SMTP or POP3 service detected; the host is not allowing unsecured FTP connections, as there is no FTP service detected.References: According to the CompTIA CySA+ Study Guide: Exam CS0-003, 3rd Edition123, one of the objectives for the exam is to “use appropriate tools and methods to manage, prioritize and respond to attacks and vulnerabilities”. The book also covers the usage and syntax of nmap, a popular network scanning tool, in chapter 5. Specifically, it explains the meaning and function of each option in nmap, such as “-sV” for version detection2, page 195. Therefore, this is a reliable source to verify the answer to the question.

The formal incident declaration is crucial to identify and document the staff who have the authority to declare an incident, ensuring that incidents are handled by authorized personnel. References: CompTIA CySA+ Study Guide: Exam CS0-003, 3rd Edition, Chapter 5: Incident Response, page 197.

The signature of the malware is a unique identifier that can be used to compare it with known malware samples and their behaviors. Open-source threat intelligence sources provide information on various types of malware, their indicators of compromise, and their mitigation strategies. By cross-referencing the signature with these sources, the analyst can determine the type of malware and its telemetry. The other options are not relevant for this purpose: configuring the EDR to perform a full scan may not provide additional information on the malware type; transferring the malware to a sandbox environment may expose the analyst to further risks; logging in to the affected systems and running netstat may not reveal the malware activity.

To determine the highest priority for remediation, we must compare the configuration of each VM against the three mandatory security requirements:

No public IPs

All data secured at rest (Encryption = Yes)

No insecure ports/protocols (No unencrypted protocols like HTTP/Telnet)

1. Analyze the Compliance of VM_PRD_DB (Option A):

Asset Type: Production Database (High Value Target).

IP Config: public - > FAIL. (A production database should never be directly exposed to the internet; it should reside in a private subnet).

Encryption: no - > FAIL. (Violates the " data secured at rest " policy).

Ingress Port: 80 (HTTP) - > FAIL. (Port 80 is cleartext/unencrypted. Using an insecure protocol on a public interface puts data confidentiality at immediate risk).

Conclusion: This asset violates all three security policies and exposes the organization ' s most critical data (Production DB) to the public internet via an insecure channel.

2. Why the other options are lower priority:

B. VM_DEV_DB:

It uses a private IP (Pass) and Port 443 (Secure). It only fails the " Encryption " check. Since it is a Development box and not publicly exposed, the risk is significantly lower.

C. VM_DEV_Web02:

It exposes Port 22 (SSH). While exposing SSH to the internet is poor practice, SSH is a secure protocol (encrypted), unlike Port 80. It also has encryption at rest enabled.

D. VM_PRD_Web01:

It exposes Port 3389 (RDP). While RDP is a common attack vector (ransomware entry point), the server has " Encryption at rest " enabled (Pass).

Comparison: While VM_PRD_Web01 is risky due to RDP, VM_PRD_DB is riskier because it involves a Database (higher impact than a web server) communicating over Port 80 (cleartext) with No Encryption at rest.

 XSS (cross-site scripting) is the vulnerability type that the security analyst is validating, as the snippet shows an attempt to inject a script tag into the web application. XSS is a web security vulnerability that allows an attacker to execute arbitrary JavaScript code in the browser of another user who visits the vulnerable website. XSS can be used to perform various malicious actions, such as stealing cookies, session hijacking, phishing, or defacing websites. The other vulnerability types are not relevant to the snippet, as they involve different kinds of attacks. Directory traversal is an attack that allows an attacker to access files and directories that are outside of the web root folder. XXE (XML external entity) injection is an attack that allows an attacker to interfere with an application’s processing of XML data, and potentially access files or systems. SSRF (server-side request forgery) is an attack that allows an attacker to induce the server-side application to make requests to an unintended location. Official References:

https://portswigger.net/web-security/xxe

https://portswigger.net/web-security/ssrf

https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html

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 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.

Attack simulationsproviderealistic, hands-on scenariosthat mirror true incidents, allowing SOC analysts topractice detection, analysis, and response skillsunder real-world pressure. These simulations are crucial for developing and reinforcing SOC procedures and incident workflows.

Phishing assessments (A)are targeted, limited training.

OpenVAS (B)is a vulnerability scanner, not a training tool.

SOAR (D)is a response automation tool.

Honeypots (E)help observe attacker behavior, but aren ' t training-focused.

???? Reference:

CS0-003 Objectives 3.3 – Incident Response Training

Mya Heath All-in-One – Chapter 14: Post-Incident Activities and Training

Implementing controls to block execution of untrusted applications can prevent privilege escalation attacks that leverage native Windows tools, such as PowerShell, WMIC, or Rundll32. These tools canbe used by attackers to run malicious code or commands with elevated privileges, bypassing system security policies and controls. By restricting the execution of untrusted applications, organizations can reduce the attack surface and limit the potential damage of privilege escalation attacks.

The correct answer is C. Impact.

The impact metric is the best way to measure the degree to which a system, application, or user base is affected by an uptime availability outage. The impact metric quantifies the consequences of the outage in terms of lost revenue, productivity, reputation, customer satisfaction, or other relevant factors. The impact metric can help prioritize the recovery efforts and justify the resources needed to restore the service1.

The other options are not the best ways to measure the degree to which a system, application, or user base is affected by an uptime availability outage. The timeline metric (A) measures the duration and frequency of the outage, but not its effects. The evidence metric (B) measures the sources and types of data that can be used to investigate and analyze the outage, but not its effects. The scope metric (D) measures the extent and severity of the outage, but not its effects.

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.

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

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.

The best action that would allow the analyst to gather intelligence without disclosing information to the attackers is to upload the binary to an air gapped sandbox for analysis. An air gapped sandbox is an isolated environment that has no connection to any external network or system. Uploading the binary to an air gapped sandbox can prevent any communication or interaction between the binary and the attackers, as well as any potential harm or infection to other systems or networks. An air gapped sandbox can also allow the analyst to safely analyze and observe the behavior, functionality, or characteristics of the binary. 

A mean time to remediate (MTTR) is a metric that measures how long it takes to fix a vulnerability after it is discovered. A MTTR of 30 days would best protect the organization from the new attacks that are exploited 45 days after a patch is released, as it would ensure that the vulnerabilities are fixed before they are exploited

The Diamond Model of Intrusion Analysis is a framework that describes the relationship between four components of a cyberattack: adversary, capability, infrastructure, and victim. It helps analysts understand the behavior and motivation of threat actors, as well as the tools and methods they use to compromise their targets12. References: Main Analytical Frameworks for Cyber Threat Intelligence, section 4; Strategies, tools, and frameworks for building an effective threat intelligence team, section 3.

When prioritizing vulnerabilities, analysts consider theCVSS score, whether the system isinternet-facing, and ifsensitive datais involved. The primary goal is to mitigate the mostexploitableandimpactfulrisks first.

Let ' s break down the key components:

Attack Vector (AV): Whether the attack can be launched remotely (N = Network) or locally (L = Local).

Attack Complexity (AC): The difficulty of executing the attack (L = Low, H = High).

Privileges Required (PR): The level of access needed for exploitation (N = None, L = Low, H = High).

User Interaction (UI): Whether user interaction is required for the attack (N = No, R = Required).

Scope (S): Whether the attack affects other systems (C = Changed, U = Unchanged).

Confidentiality (C), Integrity (I), Availability (A): The impact level (H = High, L = Low, N = None).

Evaluating Each System:

System 1 (CVSS: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H)

Internet-facing✅

No sensitive data❌

High confidentiality and availability impact✅

Moderate risk due to requiring low privileges

System 2 (CVSS: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H)

Not internet-facing❌

No sensitive data❌

Lower priority since it’s local-only

System 3 (CVSS: AV:P/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:L)

Internet-facing✅

Contains sensitive data✅

But very low likelihood of exploit (requires physical access, high privileges, user interaction)

Lower priority due to high attack complexity

System 4 (CVSS: AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:H)

Internet-facing✅

No sensitive data❌

No privileges required for exploitation✅

High impact on confidentiality and availability✅

Most critical due to remote exploitability and system-wide scope

System 5 (CVSS: AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N)

Internet-facing✅

Contains sensitive data✅

But requires high privileges, high attack complexity, and user interaction

Lower priority than System 4

System 6 (CVSS: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H)

Not internet-facing❌

No sensitive data❌

Same as System 2 (low priority due to being local-only)

Final Decision: Patch System 4 First

System 4 is themost criticalbecause:

It isinternet-facing(higher exposure).

It has ahigh CVSS score.

Itrequires no privileges(easy to exploit).

It hassystem-wide scope impact(can affect other systems).

Thus, it should bepatched firstto minimize security risks.

The correct answer is C. Legal department.

According to the CompTIA Cybersecurity Analyst (CySA+) certification exam objectives, one of the tasks for a security analyst is to “report and escalate security incidents to appropriate stakeholders and authorities” 1. This includes reporting any inappropriate use of resources, such as installing cryptominers on workstations, which may violate the company’s policies and cause financial and reputational damage. The legal department is the most appropriate group to escalate this issue to first, as they can advise on the legal implications and actions that can be taken against the employee. The legal department can also coordinate with other groups, such as law enforcement, help desk, or board members, as needed. The other options are not the best choices to escalate the issue to first, as they may not have the authority or expertise to handle the situation properly.

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.

===========