CS0-004 Exam Dumps - CompTIA CySA+ Questions and Answers

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.

/var/log/auth.log is the appropriate source because it records authentication and authorization activity on Debian/Ubuntu-style Linux systems, including password-related events, SSH logins, PAM authentication, and other authorization events. Canonical's Ubuntu documentation specifically identifies /var/log/auth.log as the authorization log used for password prompts, sudo, and remote logins.

The command performs three operations. cat /var/log/auth.log sends the log contents to standard output. The pipe forwards that data to grep "User1", which selects records containing the required username. Finally, > linux-events.txt redirects the resulting matching records into the requested flat-file report. Because auth.log can contain both accepted and rejected authentication activity, the command can capture successful and unsuccessful events associated with User1.

sssd is not the general authentication log path shown in the scenario and may contain only SSSD-specific events. A faillog-oriented source emphasizes failed logins and therefore does not satisfy the requirement to collect both successful and failed activity. /var/log/syslog contains broad system messages but is less precise than the dedicated authentication log.

Study Guide Reference: Security Operations → Linux Log Analysis → /var/log/auth.log → cat → grep → Output Redirection → Authentication Investigation.

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

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

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

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

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

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.

A SIEM alert is an indication requiring validation; it is not automatically a confirmed security incident. The analyst must therefore begin with triage . Triage establishes whether the activity is legitimate or malicious, determines the affected systems or accounts, evaluates severity and business impact, and establishes the appropriate investigative and escalation path.

Typical triage activities include reviewing the underlying events, checking source and destination information, identifying affected assets, correlating supporting telemetry, evaluating detection confidence, examining threat intelligence, and determining whether the alert represents a true positive. Only after this assessment can the incident be assigned an appropriate priority and routed to the correct responders.

Contacting an incident coordinator before establishing whether the alert represents meaningful risk may create unnecessary escalation. Recovery activities occur substantially later, after detection, analysis, containment, and eradication activities have established what happened and controlled the threat. Escalating directly to the help desk is similarly premature and may be inappropriate for a security event.

NIST's current incident-response model places detection and analysis before response and recovery actions and emphasizes determining event characteristics so appropriate response actions can follow.

Study Guide Reference: Incident Response and Management → Detection → Alert Validation → Triage → Analysis → Severity Determination → Escalation.

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.

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.

Operational technology environments frequently contain specialized controllers, industrial control systems, supervisory control and data acquisition equipment, embedded operating systems, and vendor-specific devices that were designed primarily for availability, safety, deterministic operation, and long service life. Traditional enterprise security controls—such as endpoint detection agents, vulnerability scanners, host-based firewalls, aggressive patching mechanisms, or modern authentication software—may not be supported and can potentially interfere with operational processes.

For this reason, organizations often implement compensating controls around OT assets when the preferred security control cannot be deployed directly. Examples include network segmentation, tightly controlled firewall rules, protocol allowlisting, passive monitoring, secure jump servers, access restrictions, enhanced logging, and additional physical controls. These measures reduce risk without requiring unsupported software to be installed on sensitive industrial devices.

High network bandwidth consumption is not the defining reason for compensating controls. Scheduled outage windows can actually facilitate maintenance rather than explain why alternative controls are required. Likewise, lack of encryption may be a weakness in some environments, but it does not explain the broader compatibility problem.

CS0-004 specifically places OT, ICS, and SCADA under critical-infrastructure concepts in Security Operations and separately recognizes compensating controls as a formal vulnerability mitigation strategy.

Study Guide Reference: Security Operations → Critical Infrastructure → OT/ICS/SCADA → Security Architecture → Compatibility Constraints and Compensating Controls.

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.