CS0-004 CompTIA Cybersecurity Analyst CySA+ V4 (New Version) Questions and Answers

Legacy systems present a significant security problem because they frequently cannot support current operating systems, security agents, encryption mechanisms, authentication controls, or vendor patches. When a business-critical legacy system cannot be remediated normally, strong network segmentation becomes an important compensating control. The objective is to reduce the system's reachable attack surface and restrict which users, hosts, protocols, and applications can communicate with it.

A segmented legacy asset might be placed in a dedicated VLAN or security zone and protected through restrictive firewall access-control rules, jump hosts, allowlisting, enhanced logging, and continuous monitoring. Even though segmentation does not remove the underlying vulnerability, it decreases exposure and makes exploitation or lateral movement considerably more difficult.

Degraded functionality is generally an effect or remediation constraint rather than the strongest reason for isolation. Asset obfuscation does not provide reliable security because hidden systems can still be discovered through enumeration or traffic analysis. A proprietary server is not automatically vulnerable merely because its implementation is proprietary; it may still support modern patches and security controls.

CS0-004 specifically covers segmentation as a vulnerability-scanning consideration, compensating controls as a mitigation strategy, and legacy systems as an important inhibitor to remediation.

Study Guide Reference: Vulnerability Management → Vulnerability Prioritization and Mitigation → Compensating Controls → Segmentation → Legacy-System Constraints.

ScoutSuite is specifically designed for security posture assessment of cloud environments, making it the best tool for establishing a cloud-security baseline. NCC Group describes ScoutSuite as an open-source, multi-cloud security-auditing tool that uses cloud-provider APIs to collect configuration information and identify risk areas across cloud environments.

This capability is fundamentally different from conventional host or web vulnerability scanning. A cloud baseline requires evaluation of configurations such as identity permissions, storage exposure, network controls, encryption settings, logging, cloud-native security services, and resource policies. ScoutSuite queries the cloud control plane and produces an organized view of configuration weaknesses that can be compared with security expectations.

OpenVAS is primarily a general-purpose vulnerability-assessment scanner for systems and network services. Nikto concentrates on web-server weaknesses and dangerous configurations. Metasploit is primarily an exploitation and penetration-testing framework. Although each has legitimate assessment uses, none is as directly suited to broad cloud configuration posture assessment as ScoutSuite.

The critical examination distinction is cloud configuration auditing versus traditional vulnerability scanning or exploitation .

Study Guide Reference: Vulnerability Management → Cloud Vulnerability Assessment → Configuration Baselines → ScoutSuite → Cloud APIs → Security Posture Assessment → Misconfiguration Identification.

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 zero-day vulnerability presents a special remediation problem because the affected organization may have confirmed exposure while no vendor patch is available. Until permanent remediation becomes possible, the organization should increase continuous monitoring for evidence that the vulnerability is being targeted or exploited. Threat-intelligence IoCs can be incorporated into SIEM, EDR, IDS/IPS, network monitoring, and threat-hunting workflows to identify suspicious connections, processes, authentication events, or other behaviors associated with the threat actor.

Continuous monitoring does not eliminate the vulnerability, but it strengthens detection capability during the exposure window and supports rapid containment if exploitation occurs. This approach should ordinarily be combined with available compensating controls such as segmentation, access restrictions, service disabling, configuration changes, or other vendor-recommended workarounds.

Sinkholing is primarily used to redirect malicious network traffic, particularly command-and-control or malicious-domain traffic, and is not a general solution for an unpatched zero-day. Eradication occurs after malicious artifacts or persistence mechanisms have been identified during incident response. Evidence acquisition is a forensic activity and does not reduce the immediate exploitation risk.

CS0-004 requires analysts to consider active exploitation/threat intelligence, patch/remediation availability, context, and compensating controls when prioritizing and mitigating vulnerabilities.

Study Guide Reference: Vulnerability Management → Prioritization → Active Exploitation → Patch Availability → Compensating Controls and Continuous Monitoring.

An after-action report (AAR) is the most comprehensive document associated with a closed incident because it consolidates the incident itself, the response activities performed, recovery actions, outcomes, deficiencies, and lessons identified during the event. NIST Cybersecurity Framework guidance specifically calls for preparing an after-action report that documents the incident, response and recovery activities, and lessons learned.

A lessons-learned document focuses primarily on what worked, what failed, and what should be improved. Those observations are important, but they represent only one component of a complete post-incident record. Root cause analysis has a narrower technical purpose: determining the fundamental condition that permitted the incident to occur or progress. A situation report is generally produced while an incident is ongoing to communicate current status, impact, actions, and outstanding issues.

An AAR is broader because it can incorporate the timeline, technical findings, containment and eradication actions, recovery results, stakeholder performance, root cause, lessons learned, and assigned corrective actions. NIST exercise guidance likewise treats lessons learned as information that becomes part of an after-action report.

Study Guide Reference: Reporting and Communication → Post-Incident Reporting → After-Action Reports → Lessons Learned → Root Cause Analysis → Corrective Actions.

Reimaging the disk is a recovery activity because it restores the compromised endpoint to a trusted operational state after malicious activity has been identified and contained. Reimaging replaces the affected operating environment with a known-good system image, removing uncertainty about hidden persistence mechanisms, modified system files, unauthorized software, or other residual effects of compromise.

Verification that malicious activity occurred belongs to the detection and analysis stage. Taking the system offline is a containment measure intended to prevent additional propagation, command-and-control communication, or damage. Writing the final report occurs during post-incident documentation and lessons-learned activities rather than operational restoration.

NIST's Recover function focuses on restoring affected assets and operations and verifying that restored systems are suitable for return to normal business use. A clean reimage is particularly appropriate where the integrity of the compromised operating system cannot be reliably established through selective malware removal.

After rebuilding, analysts should verify configuration, patch levels, security controls, credentials, and monitoring before reconnecting the machine to production.

Study Guide Reference: Incident Response and Management → Recovery → Reimaging → Known-Good Baselines → Restoration Validation → Return to Production.

The analyst must construct an accurate incident timeline . Patient zero is the earliest compromised system from which subsequent malicious activity originated or propagated. Determining it requires ordering events chronologically across all affected hosts and correlating authentication activity, process execution, network connections, malware creation times, lateral movement, and other evidence.

Raw logs alone do not communicate this sequence effectively. Logs from different systems must first use reliable timestamps and then be normalized and correlated. Once events are ordered, the analyst can work backward from known compromises to determine which host displayed the earliest credible signs of intrusion and whether subsequent systems were reached from that host.

Enabling additional monitoring helps detect future activity but does not reconstruct historical sequence by itself. Isolation is necessary during containment but does not establish which system was initially compromised. Shift-handoff improvements are useful organizationally but do not answer the forensic question. Malware composition analysis may identify relationships between samples, but it does not establish system-level chronology.

NIST's incident-response guidance emphasizes analysis, documentation, root-cause understanding, and after-action reporting as inputs to continuous improvement.

Study Guide Reference: Incident Response and Management → Timeline Analysis → Event Correlation → Patient Zero → Root Cause Analysis → After-Action Review.

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.

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.

Resource exhaustion is the most likely explanation because Linux top is specifically used to observe real-time system and process resource consumption. Its output provides system summary information and process-level metrics that allow an analyst to identify abnormal CPU or memory utilization, excessive process activity, load conditions, and other resource constraints. The Linux top manual describes the utility as providing a dynamic real-time view of the running system and its processes.

When an application becomes unresponsive while top indicates abnormally high processor consumption, memory pressure, or another exhausted resource, the immediate technical conclusion is resource exhaustion. An application can become starved of CPU time, physical memory, or other capacity, causing severe degradation or apparent failure.

Service disruption is a description of an outcome rather than the underlying condition demonstrated by process-resource statistics. Unauthorized software would require evidence showing an unexpected or prohibited process rather than simply excessive utilization. Filesystem changes are normally investigated through filesystem auditing, integrity monitoring, timestamps, logs, or forensic comparison; top does not primarily report file modifications.

The examination distinction is therefore between symptom and cause : the unresponsive application is the symptom, while excessive resource consumption revealed by top identifies the probable root cause.

Study Guide Reference: Security Operations → Host Analysis → Linux Utilities → top → CPU/Memory Analysis → Resource Exhaustion → Performance Anomalies.

Category 2 represents hosts whose RDP authentication characteristics indicate NTLM without Active Directory domain membership , making option C the correct interpretation. The Nmap command targets TCP port 3389 and executes RDP-related NSE scripts. Nmap's RDP scripts include rdp-ntlm-info, which obtains information through RDP services configured for CredSSP/Network Level Authentication, as well as rdp-enum-encryption, which evaluates supported RDP security layers and encryption.

Kerberos normally relies on a domain-based authentication infrastructure and a Key Distribution Center. A non-domain-joined workstation will typically rely on local authentication mechanisms and can use NTLM challenge-response authentication where appropriate. The absence of Active Directory domain characteristics, together with NTLM-specific RDP information, therefore distinguishes Category 2 from domain-integrated Kerberos authentication.

It is important operationally not to infer that every NTLM-capable system is necessarily outside Active Directory; domain members can fall back to NTLM under certain conditions. The examination conclusion depends on the combined evidence shown in the category output rather than NTLM alone.

Study Guide Reference: Vulnerability Management → Service Enumeration → Nmap NSE → RDP/3389 → NTLM → Kerberos → Active Directory Authentication Assessment.

The common underlying weakness is insufficient handling and validation of untrusted application input . XSS occurs when attacker-controlled content is processed and subsequently rendered in a manner that allows script execution. SQL injection occurs when untrusted values become part of database commands without appropriate separation between code and data.

OWASP recommends validating untrusted input early in the processing workflow and applying syntactic and semantic validation. For SQL injection specifically, OWASP identifies parameterized queries as the primary defensive technique and recommends allow-list input validation as an additional defensive layer. For XSS, context-appropriate output encoding and sanitization must also be applied; therefore input validation should be viewed as part of secure application handling rather than the sole technical control.

A WAF can provide defense in depth but does not correct vulnerable application code. HSTS forces browsers to use HTTPS and protects transport security; it does not prevent malicious input from being interpreted by an application. Endpoint protection similarly operates on hosts and does not repair web application data-handling flaws.

Study Guide Reference: Vulnerability Management → Application Vulnerabilities → XSS → SQL Injection → Input Validation → Output Encoding → Parameterized Queries → Secure Coding.

Residual risk is the risk that remains after security controls, safeguards, or mitigation measures have been implemented. No practical security program can eliminate every threat or vulnerability completely, so organizations evaluate the remaining exposure to determine whether additional treatment is required or whether management can formally accept it.

The distinction from inherent risk is particularly important. Inherent risk represents the level of exposure before controls are applied. For example, an internet-facing application containing sensitive information may have substantial inherent risk. After implementing strong authentication, patching, a web application firewall, monitoring, secure coding controls, and segmentation, its probability and impact of compromise may be reduced—but not eliminated. The remaining exposure is residual risk.

“Acceptable risk” describes risk that falls within an organization's approved tolerance or appetite; residual risk may or may not be acceptable. If the remaining exposure still exceeds tolerance, further controls, avoidance, transfer, or other treatment may be necessary. “Appropriate” is not a formal risk category in this context.

Risk management therefore follows a continuous cycle of identifying inherent exposure, applying controls, measuring the remaining residual exposure , and comparing that level with organizational risk tolerance.

Study Guide Reference: Vulnerability Management → Risk Analysis → Inherent Risk → Mitigating Controls → Residual Risk → Risk Acceptance → Risk Appetite and Tolerance.

A Privileged Access Management (PAM) solution provides the strongest control for credentials with root, domain administrator, and local administrative authority. Vulnerability scanners frequently require elevated permissions for credentialed assessments, but permanently exposing those credentials to scanning infrastructure creates substantial risk. If compromised, the scanner could provide an attacker with privileged access across a large portion of the environment.

PAM systems can protect privileged credentials through centralized vaulting, controlled checkout, tokenized or brokered authentication, rotation, session restrictions, auditing, and time-limited privilege. This aligns with the principle of least privilege, under which entities should receive only the access necessary to perform assigned functions. NIST defines least privilege in precisely this manner and applies the principle to privileged accounts.

Single sign-on improves authentication convenience but does not adequately secure highly privileged scanning credentials. A simple one-time password adds authentication assurance but lacks the credential governance and lifecycle controls provided by PAM. Agentless scanning changes scanner architecture but does not solve the underlying privileged-access requirement.

The strongest design is therefore to place high-impact administrative credentials under dedicated privileged-access controls rather than treating them as ordinary service credentials.

Study Guide Reference: Vulnerability Management → Credentialed Scanning → Scanner Permissions → PAM → Least Privilege → Credential Vaulting and Rotation.

The analyst should prioritize 10.203.10.11 because the scan output identifies that host as presenting the Windows SMB exposure relevant to the critical vulnerability. Vulnerability prioritization requires matching the vulnerability's technical prerequisites against the characteristics discovered on each host rather than simply patching every responding system indiscriminately.

Modern SMB services commonly use TCP port 445 . Microsoft documents TCP 445 as a required port for SMB-based file services, with port 139 associated with older NetBIOS-based implementations. Therefore, a Windows host exposing the affected SMB service satisfies an essential condition for applicability and should be prioritized when the vulnerability specifically targets open SMB ports.

The -Pn option is also significant operationally because it instructs Nmap to treat targets as online without relying on normal host-discovery probes. The analyst can consequently inspect reachable service ports even when systems do not respond to standard discovery methods.

The remaining hosts either do not expose the vulnerable SMB service or do not match the required Windows/service profile described by the scenario. Priority should follow confirmed applicability, exposure, severity, and exploitability.

Study Guide Reference: Vulnerability Management → Nmap → Port Scanning → SMB → TCP 445/139 → Vulnerability Applicability → Remediation Prioritization.

The Pyramid of Pain illustrates the increasing operational difficulty imposed on an adversary when defenders successfully detect and deny progressively more behavioral indicators. At the lower levels are artifacts that attackers can replace relatively easily, such as hash values and IP addresses. Higher levels include domain names, network or host artifacts, tools, and ultimately tactics, techniques, and procedures (TTPs) .

Its central defensive lesson is that not all indicators impose equal cost on an attacker. Blocking one IP address may require the attacker only to obtain another server. Detecting a specific malware hash can often be defeated by recompiling or modifying the file. Detecting the attacker's established behaviors and operational methods creates substantially greater difficulty because the adversary may need to redesign procedures, change tooling, retrain operators, or alter an established intrusion methodology.

The Pyramid of Pain was developed specifically to describe this relationship between indicators and the amount of operational “pain” defenders impose when those indicators are denied.

Option B describes impact measurement, not indicator durability. Option C concerns intelligence-source classification. Option D resembles threat-modeling approaches such as STRIDE rather than the Pyramid of Pain.

Study Guide Reference: Security Operations → Threat Intelligence → Pyramid of Pain → Indicators of Compromise → Tools → TTPs → Behavioral Detection.

Prowler is designed for cloud security assessment, configuration review, and compliance evaluation, which directly meets the requirement to establish cloud-security baselines. The project's official repository describes Prowler as an open-source cloud security platform that automates security and compliance assessments across cloud environments and provides extensive security checks, reporting, and remediation guidance.

Baseline assessments establish an expected security posture against which subsequent configurations and changes can be evaluated. Prowler can examine cloud settings such as identity permissions, logging, encryption, public exposure, network controls, storage configuration, and service-specific security features. This allows the vulnerability-management team to identify deviations from security and compliance expectations.

Metasploit is an exploitation framework used primarily for penetration testing and validation of exploitable weaknesses. Maltego is an information-gathering and relationship-mapping platform frequently associated with OSINT and infrastructure reconnaissance. MITRE CALDERA is an adversary-emulation platform used to exercise defensive controls using automated attack techniques.

The term “cloud environment” combined with “security baselines” points directly toward a cloud posture and compliance assessment tool rather than exploitation, OSINT, or adversary simulation.

Study Guide Reference: Vulnerability Management → Cloud Assessments → Prowler → Security Baselines → Configuration Auditing → Compliance Checks → Cloud Security Posture.

Chain of custody is the formal process used to document the collection, possession, transfer, handling, analysis, and disposition of evidentiary artifacts. Its purpose is to establish an auditable history demonstrating who controlled the evidence, when custody changed, why it was transferred, and what actions were performed on it.

NIST defines chain of custody as tracking evidence throughout its collection, safeguarding, and analysis lifecycle while documenting each individual who handled it, relevant timestamps, and the purpose of transfers. This is critical when multiple systems, analysts, forensic teams, or external parties participate in an investigation because undocumented handling could undermine confidence in the evidence's integrity or admissibility.

Packaging and labeling are important evidence-preservation procedures, but they represent only individual activities within the broader evidence-management process. Storage and containment protect artifacts from alteration or unauthorized access but do not provide the complete historical record of possession. Post-incident reporting documents investigation conclusions and response actions after the incident rather than tracking evidence throughout its lifecycle.

The decisive phrase is “properly recorded.” A defensible record of every evidence transfer and handler is specifically the function of chain of custody.

Study Guide Reference: Incident Response and Management → Digital Forensics → Evidence Acquisition → Chain of Custody → Evidence Integrity → Documentation and Preservation.

Attack methodology frameworks help defenders analyze security from an adversary-centric perspective . Rather than focusing exclusively on individual vulnerabilities, these frameworks organize how attackers pursue objectives, which behaviors they use, and how their activity progresses or relates across an intrusion.

MITRE ATT & CK is a representative example. MITRE describes ATT & CK as a knowledge base based on real-world adversarial behavior and states that tactics represent why an adversary performs an action, while techniques represent how the adversary achieves that objective. By understanding these behaviors, defenders can design detections, controls, threat hunts, and response procedures that address realistic attacker methods rather than isolated theoretical weaknesses.

Option A describes continuous vulnerability remediation or rapid operational deployment. Option B describes risk-based vulnerability prioritization using probability and consequence. Option D describes Zero Trust architecture, which assumes that access should not be trusted solely because of network location or prior authentication.

The central purpose of an attack methodology framework is therefore to model and understand adversary behavior so defensive controls can be aligned against realistic attack techniques and objectives .

Study Guide Reference: Security Operations → Attack Methodology Frameworks → MITRE ATT & CK → Adversary Behavior → Tactics → Techniques → Procedures → Defensive Mapping.

The analyst should first establish a legal hold because the suspected breach involves personnel records and evidence that may become relevant to regulatory, disciplinary, civil, or other legal proceedings. A legal hold prevents potentially relevant information from being deleted, overwritten, modified, rotated out under normal retention schedules, or otherwise destroyed before the organization's legal and investigative obligations are understood.

Preservation must precede destructive or potentially evidence-altering actions. NIST describes digital forensics as retrieving, storing, and analyzing electronic information while ensuring that evidence is captured reliably without alteration. RFC 3227 similarly emphasizes preserving evidence, following proper collection procedures, documenting handling, and maintaining chain of custody.

Log correlation and timeline construction are important investigative activities, but they should occur after preservation requirements have been established. Resetting credentials may subsequently be required for containment, but the scenario first raises an evidence-preservation obligation. Restoring files from backup would be especially premature because it could alter timestamps, overwrite artifacts, or otherwise complicate forensic analysis.

The examination principle is therefore preserve first when legal implications are reasonably foreseeable; analyze and remediate afterward under controlled procedures .

Study Guide Reference: Incident Response and Management → Evidence Acquisition → Legal Hold → Evidence Preservation → Chain of Custody → Timeline Analysis → Regulatory/Legal Considerations.

The CIO is implementing risk avoidance because the organization is eliminating the activity or technology that creates the risk. The legacy system no longer receives security updates, so continued operation would maintain exposure to vulnerabilities that may eventually become impossible to remediate. By phasing out and ultimately decommissioning the system, the organization removes that source of risk instead of continuing to operate it under additional controls.

NIST recognizes acceptance, avoidance, mitigation, sharing, and transfer as established risk-response approaches. Avoidance differs from mitigation because mitigation would retain the legacy system while implementing controls that reduce its likelihood or impact—for example, segmentation, strict access controls, application allowlisting, or enhanced monitoring.

Risk acceptance would involve deliberately continuing to operate the system after management acknowledges and approves the remaining exposure. Risk transference would shift some financial or operational consequences to another party, such as through insurance or contractual arrangements.

The phrase “phase out” is the decisive indicator. The organization intends to stop using the risk-producing technology entirely, making avoidance the most precise classification.

Study Guide Reference: Vulnerability Management → Risk Management → Risk Responses → Avoidance → Mitigation → Acceptance → Transference → Legacy and End-of-Life Systems.