Pass the CompTIA CySA+ CS0-004 Questions and answers with ExamsMirror

The organization cannot completely block the malicious URL because it remains necessary for a legitimate business process. Instead, the security team is implementing compensating controls that reduce exposure while preserving required functionality. These controls include limiting access to explicitly authorized users, restricting network paths through firewall and cloud security-group rules, increasing monitoring, and ensuring that systems interacting with the external resource are fully patched.

A compensating control is an alternative safeguard used when the preferred control—such as completely removing access to the risky resource—is operationally impractical. The important distinction is that the underlying risk still exists; the organization is reducing its likelihood or potential impact through layered protections.

Patching is only one component of the response and therefore does not describe the overall mitigation. Configuration management concerns maintaining approved system configurations and controlling changes. Attack surface management focuses on identifying and reducing externally or internally exposed assets and services, but the scenario specifically describes alternative safeguards around a business-required risk.

The combination of access restriction, enhanced monitoring, and system hardening is therefore characteristic of compensating-control implementation.

Study Guide Reference: Vulnerability Management → Vulnerability Mitigation → Compensating Controls → Network Segmentation → Monitoring → Patch Management → Risk-Based Remediation.

Legacy systems commonly inhibit vulnerability remediation because they may depend on obsolete operating systems, unsupported applications, specialized hardware, outdated protocols, or vendor products for which security updates are no longer provided. Even when a vulnerability is accurately identified, the organization may be unable to apply a modern patch without breaking compatibility, interrupting a critical business process, or violating vendor support requirements.

NIST guidance explicitly recognizes that legacy systems create unique security-management challenges, while federal cybersecurity guidance warns that products remaining in service after vendor support ends may lack effective mechanisms for addressing newly discovered vulnerabilities.

In such circumstances, vulnerability-management teams may need to use compensating controls such as segmentation, firewall restrictions, application allowlisting, stronger access controls, enhanced monitoring, or service isolation while planning migration or replacement. These controls reduce exposure but do not remove the underlying software defect.

“Controlled systems,” “shared systems,” and “closed systems” do not inherently prevent remediation. A shared system may require greater coordination, but it can still be fully supported and patchable. The defining issue with legacy technology is that technical and vendor constraints can directly prevent normal remediation .

Study Guide Reference: Vulnerability Management → Remediation Constraints → Legacy Systems → End-of-Life Technology → Patch Availability → Compensating Controls → System Replacement.

/var/log/auth.log is the appropriate source because it records authentication and authorization activity on Debian/Ubuntu-style Linux systems, including password-related events, SSH logins, PAM authentication, and other authorization events. Canonical's Ubuntu documentation specifically identifies /var/log/auth.log as the authorization log used for password prompts, sudo, and remote logins.

The command performs three operations. cat /var/log/auth.log sends the log contents to standard output. The pipe forwards that data to grep "User1", which selects records containing the required username. Finally, > linux-events.txt redirects the resulting matching records into the requested flat-file report. Because auth.log can contain both accepted and rejected authentication activity, the command can capture successful and unsuccessful events associated with User1.

sssd is not the general authentication log path shown in the scenario and may contain only SSSD-specific events. A faillog-oriented source emphasizes failed logins and therefore does not satisfy the requirement to collect both successful and failed activity. /var/log/syslog contains broad system messages but is less precise than the dedicated authentication log.

Study Guide Reference: Security Operations → Linux Log Analysis → /var/log/auth.log → cat → grep → Output Redirection → Authentication Investigation.

The activity is consistent with Virtual Network Computing (VNC) remote-control sessions. VNC provides interactive graphical access to another computer, which can manifest to the local user as unexpected mouse movement, windows opening, applications launching, or terminal sessions appearing without direct user interaction.

The network evidence distinguishes VNC from the other possibilities. Nmap's official VNC detection documentation demonstrates VNC services operating on TCP port 5900 and provides NSE functionality for querying VNC protocol versions and supported security mechanisms. When traffic logs show connections consistent with VNC services and users simultaneously observe visible remote desktop activity, VNC is the strongest correlation.

An internally addressable source address establishes only where traffic originated; it does not explain interactive mouse and keyboard activity. A reverse tunnel can provide an attacker with connectivity through network restrictions, but the tunnel itself does not identify the remote-control protocol responsible for the graphical symptoms. RDP can also provide interactive remote access, but it uses a different protocol and service profile; the traffic evidence in the scenario aligns with VNC instead.

An analyst should therefore correlate endpoint symptoms with network protocol and port evidence , rather than diagnosing remote access solely from visible user-interface behavior.

Study Guide Reference: Security Operations → Network Traffic Analysis → Remote Access → VNC → RDP → Ports/Protocols → Indicators of Unauthorized Remote Control.

The communication plan is the appropriate document because it establishes who must be contacted during an incident, how communications should occur, which channels are authorized, and how information should be escalated to internal and external stakeholders.

Incident-response communications may involve security personnel, executive leadership, legal counsel, privacy teams, public relations, human resources, business owners, vendors, regulators, law enforcement, customers, and other parties depending on incident severity. NIST's incident-response guidance emphasizes coordination with relevant stakeholders as part of an effective response capability. A communication plan operationalizes that requirement by maintaining contact information, responsibilities, escalation paths, notification requirements, and approved communication methods.

An organization chart identifies reporting relationships but may not contain emergency contact details, alternate channels, external contacts, or escalation procedures. A previous incident report documents a historical event and should not be treated as the authoritative contact source. Standard operating procedures can describe technical or administrative steps, but stakeholder communications are more appropriately centralized in the incident communication plan.

Maintaining this information in advance is critical because incident response frequently occurs under time pressure and may involve unavailable or compromised normal communication systems.

Study Guide Reference: Reporting and Communication → Communication Plan → Stakeholder Contacts → Escalation Paths → Internal/External Notifications → Out-of-Band Communications.

Eradication addresses the root causes and malicious mechanisms that allow an attacker to remain inside the environment. Typical eradication actions include deleting malware, removing persistence mechanisms, disabling unauthorized accounts, resetting compromised credentials, eliminating malicious scheduled tasks or services, correcting exploited vulnerabilities, and rebuilding systems when trust cannot be restored.

This differs fundamentally from containment. Containment is intended to limit immediate damage or prevent further spread , such as isolating an infected workstation, blocking an IP address, disabling a network segment, or temporarily suspending an account. These measures can interrupt attacker activity, but they do not necessarily remove the underlying foothold. Microsoft security architecture guidance similarly distinguishes containment from eradication and describes eradication procedures as completely removing the threat from the environment.

Detection identifies that suspicious or malicious activity exists; it does not remove access. Denial of service is an attack or availability condition rather than a recognized incident-response phase.

Therefore, if the examination asks which phase permanently removes the adversary's access , the correct answer is eradication because this is where attacker persistence and the enabling compromise are eliminated before normal operations are fully restored.

Study Guide Reference: Incident Response and Management → Containment → Eradication → Persistence Removal → Credential Reset → Malware Removal → Vulnerability Remediation.

The ZAP finding concerns information disclosure through the HTTP Server response header , so the correct remediation is to suppress or minimize that header while leaving the website operational. OWASP ZAP maintains specific alerts for servers that disclose the web-server application or version through this response field. The version-disclosure rule is categorized as information exposure because detailed server identification can assist reconnaissance and vulnerability targeting.

Removing unnecessary product and version information reduces information available to an attacker without interrupting legitimate HTTP requests. This directly satisfies the requirement to remediate the finding while maintaining service availability.

Geo-blocking does not correct server-version disclosure and may unnecessarily deny legitimate users based on location. OCSP stapling relates to certificate-revocation status in TLS and is irrelevant to an HTTP server-header disclosure. Blocking incoming HTTP entirely would make the current endpoint unavailable, contradicting the requirement to keep the site operational.

The remediation principle is therefore minimize externally exposed implementation details while preserving application functionality . Server banners are not themselves an exploit, but they can improve an attacker's ability to fingerprint technology and select applicable exploits.

Study Guide Reference: Vulnerability Management → Web Application Scanning → OWASP ZAP → Information Disclosure → HTTP Server Headers → Banner Suppression → Secure Configuration.

The analyst should collect the Netstat output first because current network-connection information is highly volatile and will change immediately when the server is disconnected. netstat-type evidence can identify active TCP/UDP connections, listening services, remote endpoints, and potentially the communication channels associated with an attacker or command-and-control infrastructure.

Digital-forensic acquisition follows the order of volatility : evidence most likely to disappear or change should be captured before more persistent artifacts. RFC 3227 explicitly directs investigators to proceed from volatile to less-volatile evidence and identifies information such as routing data, ARP cache, process state, memory-related information, and network state as highly time-sensitive.

The ARP table is also volatile and should be captured early, but the wording “before disconnecting the server from the network” makes active connection state particularly important because those sessions will terminate when network connectivity is removed. ShellBags are persistent forensic artifacts stored within Windows Registry data and can be collected later from disk. A hard-disk image is critical but comparatively nonvolatile and should follow acquisition of live state.

Therefore, live network-session information takes priority.

Study Guide Reference: Incident Response and Management → Evidence Acquisition → Order of Volatility → Live Response → netstat → Network Connections → Forensic Preservation.

An agent-based scan relies on software installed directly on the endpoint to collect local system state and report vulnerability or configuration information to the management platform. Because the agent has local visibility, its findings can be influenced by endpoint configuration, agent policy, update state, privileges, enabled assessment modules, or configuration changes that determine what information is collected and evaluated.

The scenario indicates that regularly scheduled assessment activity initially failed to identify the newly disclosed vulnerability, but the condition became visible after a configuration change. Among the available choices, that behavior most strongly aligns with an agent-based assessment whose local collection or assessment configuration had to be updated before the vulnerability could be detected.

An external scan evaluates systems from outside the organizational boundary and focuses primarily on externally reachable services. A network scan examines hosts and services remotely and is governed mainly by network reachability and scanner capabilities. A credentialed scan authenticates into a system to obtain deeper visibility, but the defining characteristic in the question is the persistent endpoint-based assessment affected by configuration.

CySA+ vulnerability-management objectives distinguish assessment techniques by perspective, authentication level, deployment method, and resulting visibility. Analysts must understand why different scanning architectures can produce different findings.

Study Guide Reference: Vulnerability Management → Vulnerability Scanning Methods → Agent-Based Scanning → Network Scanning → Credentialed Scanning → Scan Configuration and Coverage.

A paid, subscription-based threat intelligence service is best classified as closed-source intelligence because access is restricted to authorized subscribers rather than being freely available to the public. Commercial threat-intelligence providers typically collect, analyze, correlate, and curate indicators and adversary information before distributing that intelligence through authenticated portals, APIs, or feeds.

NIST identifies several external intelligence-source categories, including open-source repositories, commercial threat feeds, and external information-sharing partners . A commercial feed relevant to a company's specific industry may provide higher-context intelligence regarding threat actors, infrastructure, malware, vulnerabilities, campaigns, and indicators affecting that vertical.

OSINT, by contrast, originates from publicly accessible sources and normally does not require restricted subscription access. Threat mapping is the activity of associating adversary behavior or intelligence with infrastructure, campaigns, frameworks, or organizational assets. Threat modeling is a structured process used to identify potential threats and weaknesses in systems or applications; it is not an intelligence-source classification.

The examination clue is “paid subscription.” Restricted commercial access distinguishes the feed from publicly obtainable OSINT.

Study Guide Reference: Security Operations → Threat Intelligence → Intelligence Sources → Open-Source Intelligence → Closed/Commercial Intelligence → Industry-Specific Threat Feeds.