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

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.

C:\Users\Administrator\Desktop\CS0-004_with_discussion_files\img_58.bmp

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.

AI usage policies establish organizational boundaries for how artificial intelligence systems may be selected, accessed, configured, and used. They allow an organization to obtain operational benefits from AI while controlling risks involving confidential information, intellectual property, regulated data, model outputs, external AI services, and inappropriate automation. A strong policy can define approved platforms, prohibited data categories, validation requirements, human oversight, retention rules, acceptable use, and escalation procedures.

Prompt engineering is a technical method for constructing inputs that produce more useful model responses. It can improve output quality but does not establish enterprise-wide safeguards for protecting business objectives or sensitive information. A non-disclosure agreement establishes contractual confidentiality obligations between parties; it cannot govern the full technical and operational use of AI systems. An incident response policy determines how security incidents are managed and escalated, but it is reactive and not designed to establish routine AI governance.

CS0-004 explicitly addresses AI within Security Operations. The objectives identify AI risks including hallucinations, data exposure, model poisoning, and malicious prompts and identify governance considerations including legal or regulatory compliance and AI usage policies . AI use cases include log analysis, artifact comparison, incident investigation, event correlation, and automation.

Study Guide Reference: Security Operations → AI in Security Operations → AI Risks → Governance → AI Usage Policies → Data Protection.

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

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.

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 scenario describes an AI hallucination , commonly termed confabulation in formal AI risk-management literature. The defining characteristic is that the model produces information that appears plausible but is factually incorrect or unsupported. Here, the AI system introduces events that never occurred, contaminating the event-correlation process and potentially causing analysts to reach incorrect conclusions.

NIST's Generative AI Profile identifies confabulation as the production of confidently stated but erroneous or false content and treats it as an AI risk that requires verification and monitoring. NIST cybersecurity guidance also recognizes hallucination and confabulation as risks to information accuracy when AI is incorporated into cybersecurity workflows.

Data exposure would involve unauthorized disclosure of confidential or sensitive information. A malicious prompt involves intentionally crafted input designed to influence model behavior or bypass restrictions. Model poisoning occurs when an adversary manipulates training or model-related data to corrupt the system's behavior. None of these conditions is required in the scenario; the critical evidence is fabrication of nonexistent events.

Security analysts therefore must treat AI-generated correlation as analytical assistance rather than unquestioned evidence and validate important conclusions against authoritative logs and telemetry.

Study Guide Reference: Security Operations → Artificial Intelligence → AI Risks → Hallucinations → Data Exposure → Malicious Prompts → Model Poisoning → Human Validation.

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.

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.

The relevant follow-up is to assess the security configuration of the discovered VPN/IKE remote-access service , making option C the appropriate examination answer. Internet Key Exchange supports different negotiation modes, and Nmap includes specific capabilities for assessing IKE services. Nmap's ike-version script probes UDP port 500 and tests both Main and Aggressive Mode while identifying supported transforms and vendor characteristics.

Nmap's IKE library likewise explicitly supports generating either Main Mode or Aggressive Mode requests, enabling analysts to characterize the configuration of an exposed VPN endpoint. The security concern traditionally associated with this distinction is that Aggressive Mode exposes more negotiation information and has historically enabled offline attacks in some pre-shared-key configurations; Main Mode provides stronger identity protection during IKEv1 negotiation.

The other choices do not validate the security of the remote-access service. A web-server certificate is relevant to TLS-enabled HTTP services, BGP route publication relates to network routing, and ICMP ping only demonstrates basic reachability.

The analyst should therefore move from port discovery to service-specific configuration validation .

Study Guide Reference: Vulnerability Management → Nmap → Service Enumeration → VPN/IKE → UDP 500 → Main Mode/Aggressive Mode → Configuration Validation.

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.

Accurate time synchronization is essential for reliable log correlation, making Network Time Protocol the best answer. Security investigations routinely combine events from endpoints, servers, authentication infrastructure, firewalls, cloud services, intrusion-detection systems, and other platforms. If those systems maintain inconsistent clocks, the apparent order of events may be incorrect, making it difficult to reconstruct an attack timeline or correlate activity across multiple sources.

NTP is specifically designed to synchronize computer clocks across distributed systems. RFC 5905 defines NTPv4 as a protocol used to synchronize clocks across internet-connected systems. Synchronized timestamps enable the SOC to determine whether events occurring on separate systems actually belong to the same sequence—for example, authentication followed by process execution, lateral movement, and a subsequent network connection.

ZTNA controls access according to Zero Trust principles but does not synchronize timestamps. Account federation addresses identity interoperability. SASE combines network and security services for distributed environments. APIs can integrate tools and exchange information, but integrated data remains difficult to correlate accurately if each system's timestamps are inconsistent.

For forensic and operational analysis, a consistent time reference is therefore foundational to timeline reconstruction, event sequencing, SIEM correlation, and evidentiary accuracy .

Study Guide Reference: Security Operations → Logging and Monitoring → Time Synchronization → NTP → SIEM Correlation → Timeline Analysis.

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.

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.

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.

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

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.

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.