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

The Diamond Model of Intrusion Analysis is specifically suited to visually representing relationships between a threat actor, the infrastructure used during an intrusion, the actor's capabilities, and the victim. Its four principal vertices are adversary, infrastructure, capability, and victim . IP addresses and network services naturally map to infrastructure, while malware and attack tools map to capability.

The original Diamond Model describes an intrusion event through these four interconnected features and uses their relationships to support documentation, correlation, and analysis of malicious activity. This makes it particularly useful when the analyst wants to visualize intelligence rather than simply place activity into chronological stages.

EPSS predicts the probability that a vulnerability will be exploited and therefore does not model threat-actor infrastructure. The Cyber Kill Chain represents progressive stages of an intrusion, making it useful for understanding attack progression but less suitable for relational visualization. MITRE ATT & CK provides detailed behavioral information on adversary tactics and techniques; MITRE itself notes that ATT & CK and the Diamond Model are complementary, with the Diamond Model particularly useful for clustering and relating intrusion information.

Study Guide Reference: Security Operations → Threat Intelligence → Diamond Model → Adversary → Infrastructure → Capability → Victim → Threat Visualization.

Rebuilding the environment from infrastructure-as-code definitions is a recovery activity because the organization is restoring trusted operational capability after the ransomware incident has been controlled. IaC provides a particularly effective recovery mechanism because infrastructure can be reconstructed according to predefined, version-controlled configurations instead of attempting to repair every potentially compromised component manually.

During detection and analysis, responders establish that malicious activity occurred and determine its scope. Containment limits additional damage or spread. Eradication removes malicious artifacts, persistence, compromised credentials, and the underlying causes of the incident. Recovery then restores affected systems and services to normal operation while ensuring they are returned in a trustworthy state.

NIST defines recovery as the restoration of assets and operations affected by cybersecurity incidents and emphasizes verifying restored assets before normal operations resume. Tearing down potentially compromised infrastructure and deploying fresh resources from controlled IaC templates directly fulfills that purpose.

Post-incident activities occur after operational restoration and focus on lessons learned, reporting, process improvement, and corrective recommendations.

Study Guide Reference: Incident Response and Management → Containment → Eradication → Recovery → Infrastructure as Code → Rebuilding from Known-Good Configurations → Validation.

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 completed substantial analysis by validating the URL, confirming its credential-harvesting purpose, and establishing that the user accessed the malicious site. However, the investigation was closed without performing adequate containment . Even though there is no evidence that stolen credentials were subsequently used, the user's authentication material must be considered potentially exposed because the phishing site was specifically designed to collect credentials.

Containment should reduce the immediate opportunity for an attacker to exploit that exposure. Appropriate measures can include resetting the affected password, revoking active authentication sessions or tokens, temporarily restricting the account when warranted, blocking the malicious URL or domain, and checking the endpoint for additional malicious activity. The absence of observed credential misuse does not establish that credential capture did not occur.

Remedial training is valuable, but it is principally a corrective or post-incident measure and does not neutralize the immediate technical risk. Recovery would follow containment and eradication when affected services or systems require restoration.

NIST's current incident-response guidance emphasizes effective detection, response, and recovery actions to reduce incident impact rather than stopping after validation.

Study Guide Reference: Incident Response and Management → Incident Response Process → Analysis → Containment → Eradication → Recovery → Post-Incident Activities.

Compensating controls are appropriate when the preferred remediation cannot currently be implemented but the organization must still reduce exposure. A mission-critical system with an unpatched vulnerability for which no vendor patch exists is a classic example. The system cannot simply be removed from service because the business requires it, and conventional patching is unavailable.

The organization may therefore deploy alternative controls such as network segmentation, restrictive firewall rules, application allowlisting, disabling unnecessary services, enhanced monitoring, IPS signatures, access restrictions, or isolation of affected functionality. These measures do not eliminate the underlying defect; instead, they reduce the probability or impact of exploitation while a permanent solution is developed.

NIST's control framework is designed to allow security controls to be selected and tailored according to organizational mission requirements and risk, supporting the broader principle that organizations may apply appropriate alternative safeguards when operational constraints exist.

Option B requires no compensating control because remediation has already occurred. Option C describes a vulnerability that is not applicable to the organization's systems. Option D represents a false positive and therefore does not constitute an actual exposure requiring mitigation.

Study Guide Reference: Vulnerability Management → Mitigation → Compensating Controls → Patch Availability → Mission-Critical Systems → Segmentation and Monitoring.

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.

The Microsoft-Windows-PowerShell/Operational log is the appropriate source because PowerShell is commonly involved in script-based and memory-oriented attack activity, including techniques associated with fileless malware. The key requirement in the question is “requires additional configuration”: advanced PowerShell telemetry such as Script Block Logging must be enabled to provide the detailed execution visibility required by a SIEM.

Microsoft documents that enabling Script Block Logging causes PowerShell to record processed commands, functions, scripts, and script blocks in the Microsoft-Windows-PowerShell/Operational channel. In Windows PowerShell, Script Block Logging generates Event ID 4104 , which contains script-block content and can provide valuable evidence when investigating malicious PowerShell execution. Microsoft also specifically identifies malicious PowerShell scripts as a post-exploitation technique associated with fileless attack activity.

The DPAPI operational log concerns cryptographic data-protection activity. UserPnp/DeviceInstall relates to device installation events, while TerminalServices-LocalSessionManager provides Remote Desktop and terminal-session telemetry. Those sources can be valuable during investigations but are not the primary log channel for capturing PowerShell-based fileless execution.

Study Guide Reference: Security Operations → Logging and Monitoring → Windows Event Logs → PowerShell Logging → Event ID 4104 → Script Block Logging → Fileless Malware Detection.

The original scan fails because Nmap's host-discovery process concludes that the target appears offline before conducting the intended full port scan. Option C adds -Pn , instructing Nmap to skip normal host discovery and proceed with scanning the target as though it is online. The -p- option then instructs Nmap to test the complete TCP port range rather than only its default set.

This is appropriate when a live host does not respond to discovery probes because ICMP echo traffic or other discovery packets may be filtered by firewalls, host-based controls, or network policy. A system can therefore appear “down” to Nmap's discovery phase while still exposing reachable TCP services.

Option B uses -sn, which performs host discovery without a port scan and therefore contradicts the requirement. Option A scans only a limited set of explicitly identified ports and includes unrelated functionality. Option D unnecessarily changes the scope to an entire /24, performs operating-system detection and DNS resolution, and invokes an SSL cipher script; none of those modifications addresses the immediate host-discovery problem.

Study Guide Reference: Vulnerability Management → Nmap → Host Discovery → -Pn → Full Port Scanning -p- → Firewall/ICMP Filtering → Scan Troubleshooting.

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.

The recurring weekly conference call is intended to manage and facilitate team coordination . The analyst's stated objectives are to understand workflow processes and the capabilities of the engineers participating in the cybersecurity improvement project. Regular coordination meetings provide a structured mechanism for sharing operational updates, clarifying responsibilities, identifying dependencies, communicating blockers, aligning technical activities, and understanding which personnel possess the expertise required for particular tasks.

Nothing in the scenario indicates an incident requiring formal incident-response training. Training would normally involve exercises, tabletop scenarios, simulations, procedures, or instruction designed to build response capability. There is also no vendor involvement, so a vendor information session would not satisfy the stated objective. Likewise, no customer request is identified.

The distinguishing clue is the combination of a cross-functional task force, workflow understanding, skills visibility, and recurring communication . These elements support internal project coordination rather than external communication or formal instruction.

Within CySA+, reporting and communication extends beyond writing final reports. Analysts must communicate effectively with technical teams, coordinate activities with relevant stakeholders, provide appropriate status information, and ensure security work is understood and actionable across organizational functions.

Study Guide Reference: Reporting and Communication → Stakeholder Communication → Team Coordination → Roles and Responsibilities → Workflow Management → Cross-Functional Collaboration.

Clearly defined roles and responsibilities are foundational to incident-response preparation because responders must know in advance who has authority to make decisions and who performs specific technical, management, legal, communications, and recovery functions. Attempting to determine ownership while an active compromise is developing introduces delays, duplicated effort, communication failures, and potentially conflicting actions.

Preparation should define escalation paths, decision-making authority, contact mechanisms, incident leadership, technical responsibilities, evidence-management responsibilities, and coordination with business, legal, privacy, communications, and external parties where applicable. NIST's current incident-response guidance emphasizes preparation across organizational risk-management activities so organizations can respond and recover efficiently when incidents occur.

An after-action report is produced after an incident and documents the event, response actions, recovery, and lessons learned. Data-integrity validation is important during evidence analysis and recovery but is not the primary organizational foundation of preparation. Chain of custody must be established when evidence is collected and transferred, particularly where legal proceedings may occur, but it represents one procedure within a broader incident-response capability.

Without predefined ownership, even technically sound procedures may fail operationally.

Study Guide Reference: Incident Response and Management → Preparation → Incident Response Plan → Roles and Responsibilities → Escalation → Communication → Authority and Coordination.

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.

Triage occurs during the analysis phase because responders must determine what an alert represents, how serious it is, which assets are affected, and what response priority should be assigned before taking broader containment or recovery actions.

Triage typically involves validating the alert, gathering supporting telemetry, establishing whether the event is a true positive, determining scope and impact, identifying affected identities or systems, correlating indicators, and assigning severity. The outcome provides the evidence required to decide whether an event should be escalated into formal incident handling and what subsequent actions are justified. NIST incident-handling guidance has historically emphasized analyzing incident-related information in order to determine the appropriate response, while the current NIST framework continues to emphasize efficient incident detection, response, and recovery.

Isolation belongs to containment because it restricts the compromised asset's ability to communicate or spread malicious activity. Reimaging normally occurs during recovery after the environment has been contained and malicious persistence addressed. Alert writing is part of detection engineering or security-monitoring operations rather than a defining incident-analysis activity.

The sequence is therefore important: detect → analyze/triage → contain → eradicate → recover → conduct post-incident activities .

Study Guide Reference: Incident Response and Management → Incident Response Process → Detection → Analysis/Triage → Containment → Eradication → Recovery.

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.

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.

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 server output indicates an initiated unauthorized session , which is the most significant security condition among the available answers. During compromise analysis, login/session data must be evaluated for unexpected users, remote origins, terminals, login times, active processes, and activity inconsistent with the server's expected operational baseline.

Linux session utilities provide precisely this type of evidence. The who utility reports users who are currently logged into a system, while w provides additional information such as the login name, terminal, remote host, login time, idle time, and currently associated process. An unexpected active session on a web application server—particularly one inconsistent with normal administrative activity—is therefore a material indicator of possible unauthorized access.

“Too many users” would require evidence that session volume itself exceeded an established threshold. High resource consumption would instead require CPU, memory, load-average, or process-utilization evidence. Abnormal idle times might warrant investigation but do not independently establish compromise.

The analyst should treat the unauthorized session as an investigative pivot and correlate it with authentication logs, source addresses, process execution, privilege changes, and network connections.

Study Guide Reference: Incident Response and Management → Analysis → Host-Based Evidence → User Sessions → Authentication Activity → Unauthorized Access → Event Correlation.

Tactics, techniques, and procedures (TTPs) occupy the highest level of the Pyramid of Pain because they represent the adversary's operational behavior rather than disposable technical artifacts. The model describes how different types of defensive indicators impose progressively greater disruption on an attacker when defenders successfully detect and deny them.

An IP address is comparatively easy to replace by changing hosting infrastructure, using a proxy, acquiring a new virtual server, or moving command-and-control services. Domain names similarly can be registered or replaced with relatively limited operational impact. Tools create greater difficulty because replacing or substantially modifying malware, frameworks, or utilities requires more attacker effort.

TTPs are significantly more costly to change because they encompass how the adversary conducts operations : the sequence and methods used for initial access, persistence, credential access, privilege escalation, lateral movement, command and control, and other objectives. Forcing attackers to change established behavior may require retraining personnel, redesigning operational processes, developing new capabilities, or adopting unfamiliar techniques.

This is why behavioral detection is strategically valuable. Indicators such as hashes and IP addresses may disappear quickly, while detections focused on adversary behavior can remain useful across multiple toolsets and infrastructure changes.

Study Guide Reference: Security Operations → Threat Intelligence → Pyramid of Pain → TTPs → Behavioral Indicators → Adversary Tracking.

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.

Application programming interfaces (APIs) provide the most direct mechanism for retrieving, exchanging, and integrating information between separate security technologies. A product console normally exposes only the information and workflows chosen by the vendor for its graphical interface. An API can provide programmatic access to underlying alerts, events, asset information, telemetry, configuration objects, or investigation data, allowing an analyst to combine information from multiple systems into a richer analytical view.

CISA describes security-analysis workflows in which integration enables defenders to connect existing analytical tools and automate data-handling processes, while modern security platforms commonly expose APIs specifically to ingest or exchange telemetry.

SOAR can certainly integrate multiple tools, but its primary purpose is orchestration and automation of security workflows. If the requirement is specifically to access and combine information not readily exposed in individual consoles , APIs are the underlying capability most directly suited to retrieving that data. Infrastructure as code defines and provisions infrastructure through machine-readable templates; it does not primarily aggregate security telemetry. Playbooks establish standardized investigation or response procedures but do not themselves provide interfaces into external product data.

The key phrase is “enhanced view into data.” This requires programmatic access and integration rather than merely workflow documentation or automation.

Study Guide Reference: Security Operations → Security Tool Integration → APIs → Data Enrichment → Automation/Orchestration → SOC Process Improvement.

Option C represents the appropriate YARA matching approach because the analyst is searching for an encoded representation of ActiveMime , not necessarily the literal plaintext string. The grep -rail ActiveMime * command performs a case-insensitive recursive search for the textual value ActiveMime. If the payload contains that value encoded—commonly through Base64 or another transformed representation—the literal byte sequence will not be present and grep will therefore fail to identify it.

YARA is designed specifically for pattern-based identification of malicious or suspicious content. Its string modifiers support encoded representations. YARA's official documentation states that the base64 modifier searches for Base64-encoded forms of a specified string, while base64wide extends this behavior to wide-character representations. Therefore, a rule constructed to detect the encoded form of ActiveMime can identify relevant documents without requiring the literal plaintext sequence to occur in the file.

The essential examination concept is the distinction between literal text searching and malware-oriented encoded-pattern matching . Rules that search only for ordinary ASCII ActiveMime reproduce the limitation of the unsuccessful grep command.

Study Guide Reference: Security Operations → Malware Analysis → YARA → Signature/Pattern Matching → Encoded Content → Base64/Base64wide → File Analysis.