CompTIA CompTIA Cybersecurity Analyst CySA+ V4 (New Version) CS0-004 Exam Dumps: Updated Questions & Answers (September 2026)

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 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 -r file.pcap argument instructs TShark to read packets from the specified capture file, while -Y applies a Wireshark display filter . The expression "http or udp" therefore displays packets recognized as HTTP or packets using UDP.

Traditional HTTP traffic is unencrypted and can be dissected directly as HTTP. HTTPS normally carries HTTP inside TLS encryption and therefore is not displayed merely because the filter specifies http. DNS commonly operates over UDP, particularly for standard queries and responses, so ordinary DNS traffic satisfies the udp portion of the expression. Consequently, B is the best answer in the context of the available choices.

A technical distinction is important: the expression does not mean “HTTP or DNS specifically.” The udp portion matches UDP traffic generally, which can include protocols other than DNS. Nevertheless, within the examination scenario, the intended comparison is plaintext HTTP versus encrypted HTTPS together with standard UDP-based DNS.

Wireshark's documentation distinguishes display filters from capture filters, and TShark is the command-line network traffic analyzer within the Wireshark suite. CS0-004 places packet-analysis capabilities within Security Operations.

Study Guide Reference: Security Operations → Packet Analysis → Wireshark/TShark → PCAP Analysis → Display Filters → HTTP, UDP, and DNS.

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.

A comprehensive asset inventory is required because the discrepancy demonstrates that the organization lacks a reliable common understanding of which systems actually exist and should be covered by vulnerability and patch-management processes. Effective vulnerability management begins with asset discovery and inventory. Without accurate asset records, teams cannot determine whether missing systems represent decommissioned devices, unmanaged assets, duplicate IP addresses, dynamic addressing, scanning gaps, or endpoints that are not enrolled in the patch platform.

Reconciliation with the infrastructure team allows the organization to establish authoritative records for hostnames, IP addresses, operating systems, ownership, business function, physical or cloud location, patching status, and vulnerability-scanner coverage. Once that inventory exists, each security tool can be compared against the same source of truth.

Verbose scanner logging might explain specific scanning failures but cannot resolve discrepancies caused by unknown or unmanaged assets. Rebuilding report filters risks masking the real coverage problem. Rerunning patch deployment does not help when the organization has not established which assets should be receiving patches.

The governing principle is simple: an organization cannot reliably assess or patch assets it has not accurately inventoried .

Study Guide Reference: Vulnerability Management → Asset Discovery → Asset Inventory → Vulnerability Scanner Coverage → Patch Management → CMDB/Reconciliation → Shadow and Unmanaged Assets.

Improving the triage process addresses the underlying operational bottleneck described in the scenario. SOC triage determines which alerts require investigation, their relative severity, whether they represent true or false positives, and which cases require escalation. When triage is inefficient, alerts accumulate faster than analysts can classify them, causing backlog growth and SLA violations.

A mature triage workflow applies consistent severity criteria, asset criticality, threat context, confidence levels, enrichment, deduplication, and predefined escalation thresholds. This reduces analyst effort spent on low-value events while ensuring genuinely dangerous alerts reach investigators quickly. Modern SIEM and security analytics platforms similarly emphasize grouping and correlating alerts into incidents to reduce unnecessary investigation workload. Microsoft Sentinel, for example, uses analytics and correlation to reduce noise and consolidate related alerts into incidents.

Automating escalation does not resolve poor initial classification and can simply transfer excessive noise downstream. Better threat intelligence may enrich alerts but will not inherently correct a dysfunctional queue. Customer-service response is unrelated to SOC alert processing.

Study Guide Reference: Security Operations → SOC Operations → Alert Management → Triage → Prioritization → Escalation Procedures → Process Improvement.

192.168.76.5 — Patch; upgrade IIS to the current release

The correct remediation target is 192.168.76.5 , which is associated with an unsupported Microsoft IIS version and a CVSS score of 9.2 in the matching hotspot data. The remediation standard assigns vulnerabilities above 9.0 to the shortest remediation window, meaning the system requires action in seven days and therefore necessarily falls within the requested fourteen-day maximum. The corresponding remediation is to patch or upgrade IIS to a currently supported release .

The key vulnerability-management principle is that remediation priority is not determined exclusively by the existence of a vulnerability. Analysts must consider severity, asset context, exposure, business importance, exploitability, available remediation, and organizational service-level requirements. A product that has reached an unsupported state represents additional risk because standard security updates may no longer be supplied.

Upgrading the affected IIS installation directly removes the unsupported software condition rather than merely reducing exposure around it. A compensating control would be appropriate when remediation cannot immediately be performed, but it would not supersede a supported upgrade when that upgrade is operationally available.

Study Guide Reference: Vulnerability Management → Vulnerability Prioritization → CVSS → Remediation Timeframes → End-of-Life/Unsupported Software → Patching and Upgrading.

YARA is specifically designed to identify and classify suspicious or malicious files through pattern-based rules . A YARA rule can contain textual strings, hexadecimal byte sequences, regular expressions, metadata, file characteristics, and Boolean conditions. This makes YARA particularly effective when an analyst already has a binary specimen on an isolated analysis system and needs to determine whether it contains patterns associated with malware.

The official YARA documentation describes YARA as a tool for helping malware researchers identify and classify malware samples using textual and binary patterns. Rules consist primarily of strings and logical conditions that determine whether a file matches the defined characteristics.

The strings utility can reveal printable characters embedded within a binary and is useful during preliminary static analysis, but it does not itself classify the file against structured malware-detection signatures. VirusTotal can perform multi-engine analysis, but submitting a potentially sensitive binary from an isolated environment to an external service may be inappropriate and is unnecessary when local YARA detection is available. WHOIS provides registration information about internet resources and has no direct binary-malware detection capability.

Study Guide Reference: Security Operations → Malware Analysis → Static Analysis → YARA → Signature and Pattern Matching → Binary/File Analysis.

The analyst should prioritize tlindy because the activity associated with that account presents the strongest anomaly in the supplied access-log evidence. Web access-log analysis is fundamentally contextual: an analyst compares source information, request behavior, authentication activity, timestamps, response codes, geographic indicators, user-agent characteristics, and established behavioral expectations to determine which entry warrants immediate investigation.

The fact that the organization is explicitly identified as being based in the United States is an important contextual clue. Geographic or behavioral activity inconsistent with the expected operating profile of an account can raise investigative priority, particularly when combined with unusual authentication or web-request characteristics. Importantly, geographic deviation alone does not prove compromise; VPN services, business travel, cloud infrastructure, and remote-working arrangements can produce legitimate anomalies. The correct SOC action is therefore investigation rather than immediate attribution.

This question tests the analyst's ability to distinguish normal activity from anomalous activity using log context , rather than simply searching for a particular HTTP status code or username. CySA+ expects analysts to correlate multiple data points before establishing whether activity represents an indicator of compromise.

The uploaded examination material identifies tlindy as the account requiring first investigation.

Study Guide Reference: Security Operations → Log Analysis → Web Application Logs → Behavioral Indicators → Anomaly Detection → User and Entity Context.

Tactics, techniques, and procedures represent the behavioral characteristics of an adversary rather than merely individual technical artifacts. A tactic describes the adversary's objective, a technique identifies how that objective is achieved, and procedures represent the specific implementation observed during an intrusion. Consequently, TTP intelligence allows defenders to understand how an attacker operates , including patterns of reconnaissance, persistence, privilege escalation, lateral movement, command-and-control activity, and other operational behaviors.

Options A and B focus primarily on indicators of compromise such as IP addresses and hashes. These are useful for detection, but they are comparatively fragile because attackers can replace infrastructure, change domains, regenerate malware, or modify files to produce different hashes. Option C is broader than an individual IoC, but tools can likewise be replaced or modified. Behavioral knowledge is generally more durable because changing established operational methods imposes greater cost on an adversary.

The CS0-004 objectives explicitly place TTPs, Pyramid of Pain, MITRE ATT & CK, attribution, IoC analysis, and behavioral indicators within threat intelligence and threat-hunting concepts.

Study Guide Reference: Security Operations → Threat Intelligence and Threat Hunting → TTPs → Pyramid of Pain → MITRE ATT & CK → Behavioral IoCs.