CS0-004 CompTIA Cybersecurity Analyst CySA+ V4 (New Version) Free Practice Exam Questions (2026 Updated)

MITRE ATT & CK Navigator is primarily a visualization and analytical tool for understanding adversary behavior and evaluating defensive coverage against ATT & CK tactics and techniques. Analysts can create layers over ATT & CK matrices, highlight techniques associated with specific threat groups, compare adversary profiles, record detection coverage, and identify techniques for which defensive visibility or controls are insufficient.

MITRE explicitly states that ATT & CK Navigator can be used to visualize defensive coverage, support red-team and blue-team planning, and represent the frequency of detected techniques. MITRE's ATT & CK design guidance also recognizes defensive gap assessment as a means of identifying areas where an enterprise lacks sufficient defenses or visibility.

Navigator itself does not replicate adversary behavior; adversary-emulation platforms and red-team tools perform that function. It is not a malware reverse-engineering platform, nor does it independently build defensive tools or execute incident-response actions.

Its major operational value is translating ATT & CK's behavioral knowledge base into a visual map that lets defenders answer two questions: What behaviors are relevant to the threats we face, and where do our detections or controls have gaps?

Study Guide Reference: Security Operations → MITRE ATT & CK → ATT & CK Navigator → Tactics and Techniques → Threat Mapping → Detection Coverage → Gap Analysis.

PRODWEB-01 represents the highest remediation priority because vulnerability prioritization should combine asset value, vulnerability risk, and exploitation likelihood , rather than relying on severity alone. A production web server is typically more exposed and operationally significant than a development endpoint, and the correlated CMDB information provides the business context required to determine whether exploitation would materially affect organizational operations.

A mature vulnerability-management process evaluates technical severity together with internet exposure, business criticality, existing controls, active exploitation, threat intelligence, and the availability of remediation. CISA specifically recommends using known exploitation evidence as an input into vulnerability prioritization and provides risk-based methodologies such as SSVC for determining appropriate response actions.

This explains why simply choosing the system with the numerically highest isolated vulnerability score would be inadequate. DEVWIN11-01, for example, may contain significant findings but carries lower production value. A control-system asset may have high business importance but can present different exposure and exploitability conditions. The correlated attributes associated with PRODWEB-01 establish the strongest combined risk.

Study Guide Reference: Vulnerability Management → Vulnerability Prioritization → Asset Criticality → Exploitability → Threat Intelligence → CMDB Context → Risk-Based Remediation.

Windows Security Event ID 4624 records a successful logon session. Therefore, querying the Security log for event 4624 provides the analyst with historical evidence of successful logins to the affected workstation.

Get-WinEvent is the appropriate PowerShell cmdlet for retrieving Windows event records. The FilterHashtable parameter allows efficient server-side filtering using attributes such as LogName and ID, rather than retrieving an entire event log and filtering the results afterward. Microsoft specifically documents LogName and ID as valid FilterHashtable keys and recommends this approach for efficient event-log querying.

The command then uses Sort-Object TimeCreated -Descending so the newest login events appear first, and Export-Csv preserves the resulting records for investigation.

Option A does not use the correct PowerShell event-query syntax shown. Options C and D search inappropriate log channels and unrelated event IDs. The evidence needed is authentication history, making the Windows Security log and successful-logon identifier 4624 the correct combination.

Study Guide Reference: Incident Response and Management → Evidence Collection → Windows Event Logs → PowerShell → Get-WinEvent → Security Event ID 4624 → Timeline Reconstruction.

The observed activity corresponds to privilege escalation , meaning the attacker attempted to move from a lower level of authorization to a more powerful security context. Privilege escalation becomes important after initial compromise because an account or process obtained during initial access frequently lacks the permissions required to disable controls, access sensitive resources, modify protected system settings, dump credentials, or establish deeper persistence.

MITRE ATT & CK defines the Privilege Escalation tactic as adversary activity intended to obtain higher-level permissions on a system or network. Techniques can include exploiting vulnerabilities, manipulating access tokens, modifying accounts or group memberships, abusing misconfigurations, or executing processes under more privileged identities.

Exfiltration specifically concerns removing information from the compromised environment. Remote code execution describes obtaining the ability to execute attacker-controlled commands or code remotely; while RCE can sometimes lead to privilege escalation, they represent different objectives. Spoofing involves impersonating or falsifying an identity, address, or other trusted characteristic.

The critical analytical distinction is therefore the attacker's objective demonstrated by the logs : attempting to obtain elevated access indicates privilege escalation rather than merely establishing execution or transferring data.

Study Guide Reference: Security Operations → Malicious Activity Analysis → MITRE ATT & CK → Privilege Escalation → Account/Permission Changes → System Log Interpretation.

During an active cybersecurity incident, responders must assume that systems associated with the compromise may no longer provide trustworthy confidentiality or integrity until their status has been established. If the incident could involve the organization's email infrastructure, discussing response strategy, investigative findings, affected assets, or containment actions through corporate email could unintentionally provide the attacker with intelligence about the organization's response.

Therefore, the email system may be compromised is the strongest explanation. Incident-response communication plans should define approved communication methods, relevant stakeholders, escalation paths, and alternative communication channels so responders can continue coordinating when ordinary enterprise systems are unavailable or untrusted. NIST's current incident-response guidance emphasizes integrating communication and stakeholder coordination throughout response activities.

Option C is too broad. Modern email commonly uses transport encryption, although encryption alone would not make a compromised mailbox or server trustworthy. Option D concerns public-relations coordination but does not explain why email itself should be avoided. Option A describes a specific gateway vulnerability that the scenario does not establish.

The core principle is out-of-band communication : when normal communication infrastructure may be under attacker control, responders should use a previously approved independent channel.

Study Guide Reference: Reporting and Communication → Incident Communications → Communication Plan → Out-of-Band Communications → Stakeholder Coordination → Compromised Communication Channels.

Zero Trust is based on the principle that access should not be implicitly trusted merely because a user, workload, or device has already entered the enterprise environment. Access decisions are continuously evaluated using identity, authentication state, device posture, authorization, contextual information, and resource sensitivity. The scenario's emphasis on continuously validating and verifying access therefore directly describes Zero Trust.

Traditional perimeter-oriented models tend to treat internal network position as a degree of trust. Zero Trust removes that assumption and requires explicit verification before granting access to protected resources. It also supports least privilege, granular authorization, segmentation, and ongoing assessment of sessions or identities.

Secure access service edge combines networking and security capabilities delivered through a distributed service architecture and can support Zero Trust implementations, but SASE itself is not the fundamental principle described. A next-generation firewall provides application-aware traffic inspection and policy enforcement but does not by itself establish continuous identity-centric verification. Privileged access management specifically controls elevated or administrative accounts; it is an important component of access security but addresses a narrower scope than Zero Trust.

The CS0-004 objectives explicitly identify Zero Trust Network Architecture , SASE, hybrid cloud, IAM, PAM, authentication, and authorization as Security Operations architecture concepts.

Study Guide Reference: Security Operations → Network Architecture → Zero Trust Network Architecture → IAM → Authentication and Authorization → Least Privilege.

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.

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.

Encryption at rest primarily protects the confidentiality of stored information when an unauthorized party obtains physical or logical access to the storage medium. This is particularly important for laptops because portable devices can be lost or stolen, giving an attacker possession of the disk outside the organization's normal network and endpoint protections.

NIST guidance on storage encryption specifically addresses laptops and other end-user devices and explains that storage encryption combines encryption and authentication to restrict unauthorized access to stored information. NIST further notes that threats involving lost or stolen end-user devices can expose information to unauthorized parties.

Encryption does not inherently prevent an authenticated and authorized user from copying information while the system is unlocked; data loss prevention controls are more directly suited to that objective. Regulatory requirements may mandate encryption in some environments, but compliance is an external requirement rather than the fundamental security reason encryption at rest exists. Option D confuses confidentiality with integrity and network protection. Encryption of data stored on a laptop is not primarily intended to validate whether network data has been modified.

The examination concept is the CIA triad: encryption primarily supports confidentiality , especially when physical possession of the storage device is lost.

Study Guide Reference: Security Operations → Data Protection → Encryption at Rest → Full-Disk Encryption → Confidentiality → Lost/Stolen Endpoint Protection.

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.

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.

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.

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.

A phishing simulation click rate measures user susceptibility to phishing and is therefore primarily an indicator of employee security awareness and behavior . If a simulated phishing message is delivered to employees and a percentage of recipients click the embedded malicious-style link, that percentage provides evidence about how effectively users are recognizing and resisting social-engineering attempts.

NIST research specifically identifies phishing-simulation click rates as a commonly used measure for evaluating the effectiveness of phishing-related security-awareness programs. NIST also cautions that raw click rates should be interpreted in context because phishing messages differ substantially in difficulty; the Phish Scale was developed to provide context for click-rate and report-rate results.

The metric does not primarily measure email-filter effectiveness because a controlled simulation may intentionally bypass or be allowlisted through technical filtering so employee behavior can be evaluated. It is unrelated to data-loss prevention false positives. It also does not directly measure response speed; metrics such as reporting time or mean time to respond would be more appropriate for that purpose.

Therefore, click rate is fundamentally a human-risk and awareness metric .

Study Guide Reference: Reporting and Communication → Security Metrics → Security Awareness → Phishing Simulations → Click Rate → Reporting Rate → Human Risk Measurement.

The scan results identify two systems exposing services that permit communications without transport encryption, making B the correct count. The analyst must examine each discovered service rather than merely count open ports, because the security property being evaluated is whether the identified protocol transmits its session or application data without adequate encryption.

Common examples include HTTP instead of HTTPS, Telnet instead of SSH, and legacy FTP rather than protected file-transfer alternatives. The presence of an unencrypted service does not automatically prove that sensitive information is currently being transmitted, but it identifies a configuration that can expose credentials, commands, session content, or application data to interception when used.

The correct vulnerability-management workflow is to map discovered ports to services, determine the security characteristics of those protocols, verify whether encryption is available and enforced, and then prioritize remediation according to asset exposure and business requirements. Where possible, administrators should disable unnecessary cleartext services or replace them with cryptographically protected equivalents.

This question therefore tests interpretation of vulnerability or port-scan output , not simple arithmetic. The two affected systems are those whose discovered services permit cleartext communications.

Study Guide Reference: Vulnerability Management → Scan Result Interpretation → Ports and Protocols → Cleartext Services → Encryption in Transit → Remediation and Secure Configuration.

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 service-level agreement (SLA) formally establishes measurable service expectations between a provider and a customer. These expectations commonly include availability targets, response times, resolution times, service quality thresholds, escalation conditions, reporting requirements, and other measurable performance indicators. NIST describes an SLA as a document that specifies technical performance promises and how performance or disputes will be handled. NIST security-control guidance also notes that service-level agreements can define performance expectations and measurable outcomes.

That makes an SLA the appropriate document when management needs to determine whether contractual performance requirements were violated. KPIs contained in the agreement provide objective measures against which actual service performance can be compared.

TTPs describe adversary behavior and have no contractual purpose. A return-on-investment report evaluates financial effectiveness rather than service obligations. A risk management plan describes how organizational risks will be identified and treated. A memorandum of understanding records cooperation or intent between parties, but it typically does not provide the detailed operational performance guarantees associated with an SLA.

The clues are customer, signed agreement, contractual breach, and measurable KPIs —all of which strongly identify a service-level agreement.

Study Guide Reference: Reporting and Communication → Service-Level Agreements → KPIs → Contractual Requirements → Performance Metrics → Compliance and Escalation.

Secure access service edge is specifically designed for environments in which users, devices, applications, and workloads are distributed beyond a traditional enterprise network perimeter. SASE integrates networking and security functions into a service-oriented architecture so policy enforcement can follow the user or workload rather than depend solely on traffic traversing a centralized corporate boundary.

This makes SASE particularly suitable for a perimeter-less topology , where employees may work remotely, applications may reside in multiple cloud providers, and services may be accessed directly over the internet. Typical SASE implementations combine software-defined wide-area networking with cloud-delivered security controls such as secure web gateways, cloud access security brokerage, firewall-as-a-service, and Zero Trust-oriented access controls.

A hybrid cloud network connects private and public cloud resources but can still operate using conventional network boundaries. Cloud-native computing describes an application and infrastructure design approach based on cloud technologies such as containers, microservices, and automation; it does not inherently define perimeter-less access security. A content delivery network distributes content geographically for performance and availability and is not an enterprise access-security architecture.

The CS0-004 Security Operations objectives explicitly identify SASE, Zero Trust Network Architecture, and hybrid cloud as network architecture concepts analysts must understand.

Study Guide Reference: Security Operations → Network Architecture Concepts → SASE → Zero Trust Network Architecture → Distributed/Cloud Security.

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.