CompTIA CS0-004 Dumps - Pass CompTIA Cybersecurity Analyst CySA+ V4 (New Version) in 2026

The attacker is attempting lateral movement because an already compromised identity is being used to move from one cloud environment or subscription into another. Lateral movement describes adversary activity intended to reach additional systems, services, accounts, or resources after an initial foothold has been established.

MITRE ATT&CK specifically includes cloud-oriented lateral movement. Its Lateral Movement tactic documents adversaries using valid accounts to access additional cloud services and resources within compromised environments. MITRE also documents cloud-role manipulation that may enable movement into additional accounts, demonstrating how identity and role relationships can become lateral-movement pathways in cloud architectures.

Privilege escalation would apply if the attacker were primarily attempting to obtain greater permissions within the current security context. Persistence concerns maintaining long-term access. Execution concerns running malicious code or commands. Credential access involves obtaining credentials or authentication material.

In this scenario, the attacker already possesses a compromised user role. The objective is to use that existing access to traverse a trust boundary and reach another isolated subscription. That movement between security domains is the decisive indicator of the Lateral Movement tactic.

Study Guide Reference: Security Operations MITRE ATT&CK Lateral Movement Cloud Services Valid Accounts IAM Roles Cross-Subscription Access.

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.

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

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.