Free Practice Questions for the Cisco CyberOps Professional 300-215 Exam (2026 Updated)

After initial collection, the engineer should escalate the suspected compromise to the incident-response team and begin structured analysis. Comparing the new executables, timestamps, services, hashes, and configurations with trusted baselines helps determine what changed and whether the overnight update was abused. Investigating the intrusion attempt’s source connects the allegedly unsuccessful event to the later files and outbound communications. Options A and D begin potentially disruptive containment before the authorized response team has assessed the transaction systems’ criticality and selected a strategy. Option C adds external information sharing before the organization has validated scope and facts. NIST SP 800-61r3 states that incident handlers collect and analyze evidence, prioritize response, and investigate what happened, how, and why; it also requires escalation based on risk. This corresponds to CBRFIR incident analysis, correlation, and response-process objectives. NIST SP 800-61r3

Because no patch is yet available and exploitation depends on requests to a specific, rarely used URL, the immediate compensating control is a WAF rule that blocks that path before the request reaches OWA. This preserves general email access while removing the known trigger from the exposed attack surface. Option A is the permanent remediation but cannot provide immediate protection while the vendor is still developing the update. An IDS signature that detects successful exploitation is reactive and may only alert after compromise; prevention is preferable when the malicious request pattern is known. Disabling OWA ports through a stateful firewall would protect the server but unnecessarily eliminate the entire service. Cisco describes a WAF as an inline control that inspects HTTP and HTTPS requests and blocks malicious requests before they reach the application. This also maps to CBRFIR objective 3.6 on responding to zero-day exploitation. Cisco WAF overview

================

The -h option in the objdump command displays section headers of an object file. According to general usage and command-line documentation, and also explained in digital forensics tools discussions in the CyberOps course, the header information includes details about the name, size, VMA, LMA, file offset, and alignment of each section in the object file. This helps analysts understand how data is stored and organized within compiled files during forensic examinations.

During the initial phase of incident response, the two key actions are:

Disconnecting the server (B) to contain the threat and prevent lateral movement or further exfiltration.

Reviewing network logs (E) to understand the timeline and scope of the attack.

These are emphasized in the containment and detection stages of the incident response lifecycle outlined in NIST 800-61 and covered in the Cisco CyberOps training.

—

The confirmed malicious external IP addresses should be added to a blocklist, immediately preventing communication with the identified command-and-control infrastructure. Firewall Security Intelligence should also be configured to block C2 traffic using reputation intelligence and maintained custom lists or feeds. Cisco describes Security Intelligence as an early filtering layer that blocks known malicious IP addresses, URLs, and domains before deeper inspection is required. Deploying anti-malware on the firewall does not directly address the confirmed destination-based connections. Blocking all outbound UDP/53 traffic is overly broad and may disrupt legitimate DNS resolution. Restricting DNS to trusted resolvers can be a useful architectural control, but the keyed response specifically combines targeted blacklisting with threat-intelligence-based C2 filtering. This aligns with CBRFIR Incident Response Techniques objective 3.5: recommend mitigation for evaluated alerts from firewalls, SIEM, and Cisco Secure Network Analytics. Cisco Secure Firewall Security Intelligence

================

Ghidra is a free and open-source software reverse engineering (SRE) suite developed by the NSA. It includes disassembly, decompilation, and debugging tools specifically designed for analyzing malware and other compiled programs.

The Cisco CyberOps guide references Ghidra as a top tool for reverse engineering binary files during malware analysis tasks, making it ideal for understanding malicious code behavior at a deeper level.

YARA rules are pattern-matching rules used to identify malware based on specific strings, conditions, and binary patterns. They are most effective in memory or file scans where analysts search for known indicators or unique signatures via string matching.

Correct answer: C. string matching.

Comprehensive and Detailed Explanation:

Endpoint Detection and Response (EDR) tools provide behavioral analytics and continuous monitoring to detect malware such as backdoors, which is especially critical on endpoints like macOS devices. These tools are essential to detect post-compromise activities and contain threats before they spread.

Secure Email Gateway (e.g., Cisco ESA) plays a key role in blocking phishing emails—the initial vector in this attack. It uses filters and reputation analysis to prevent malicious links or attachments from reaching end users.

Incorrect Options:

C. DLP focuses on preventing data exfiltration, not phishing prevention or backdoor detection.

D. IPS is effective for known signature-based threats but less effective against phishing links and endpoint-level backdoors.

E. WAF protects web servers, not end-user devices from phishing or backdoor infections.

Therefore, the correct answers are: A and B.

To determine the correct script, we evaluate the following requirements:

The script must search for the IP address 192.168.100.100.

The output should be written to a file named parsed_host.log.

The matching lines should be printed to the console.

Analysis of the options:

Option A: Correct IP regex used and correct output filename, but reads from parsed_host.log instead of a source log file like test_log.log (not ideal for initial parsing).

Option C: The IP address used is 192.168.100.101 instead of 192.168.100.100 — incorrect.

Option D: Same IP address and logic as Option B, but uses print statement without parentheses, which is not valid in Python 3 unless using Python 2 — not ideal.

✅ Option B:

Uses correct IP: " 192.168.100.100 "

Reads from test_log.log (presumably the source log file).

Writes to output/parsed_host.log.

Prints each matching line and writes to output file — satisfying all conditions.

The repeated failed SSH authentications followed by a successful root login form a strong sequence indicating compromised user access. After entry, the account runs apt purge apache2, which removes the Apache package and its configuration data, directly explaining why customers can no longer reach the service. That command is an unauthorized system modification. Privilege escalation is not demonstrated because the successful session is already associated with root; no transition from lower to higher privilege is shown. The evidence also does not establish malware propagation or the traffic volume expected in a DDoS attack. CBRFIR Incident Response Techniques objectives 3.1 and 3.2 require responders to interpret security and system logs and correlate host and network activity by incident type. Here, authentication records and package-management activity create a coherent attack chain: credential compromise followed by destructive administrative action. Cisco CBRFIR v1.2 exam topics

================

The event log shown in the exhibit is Event ID 104, which in Windows indicates " The audit log was cleared. " This is a significant indicator of log tampering, a common post-exploitation technique used by attackers to hide their tracks after exfiltrating data or performing unauthorized actions.

The Cisco CyberOps Associate guide mentions:

" Log deletion events, especially Event ID 104, should be treated as potential evidence of malicious activity attempting to cover tracks " .

Combined with large data dumps to network shares, this indicates not only unauthorized activity but also deliberate efforts to erase forensic evidence—characteristic of log tampering.

Data loss prevention is the control most directly aligned with the incident’s root cause: an authorized insider removed sensitive customer information. DLP policies can identify regulated or confidential content, inspect transfers, alert on abnormal movement, and block unauthorized exfiltration through supported channels. Cisco explains that DLP uses rules to find sensitive information and detect abnormal transfers, including intentional disclosure of customer data. This makes option D a targeted post-incident recommendation under CBRFIR objectives 3.4 and 3.5. A penetration test may reveal exploitable technical weaknesses, antivirus addresses malware, and universal password changes address credential compromise; none directly controls misuse of legitimate access to move protected data. DLP should still be combined with least privilege, access reviews, logging, and user-behavior monitoring, but among the listed choices it best reduces recurrence. See Cisco’s DLP overview .

The combination of CPU spikes, disk usage peaks, and fluctuating PageFile.sys indicates excessive virtual memory paging, which may be a sign of malicious memory or file access behavior. PageFile.sys is part of the virtual memory system, and analyzing it can reveal which processes or payloads are consuming unusual amounts of memory, especially during exfiltration events.

Input validation (A) is a critical countermeasure to defend against command injection and related vulnerabilities, as discussed in the Cisco guide. Proper validation ensures that malicious commands or payloads are not accepted or executed by the web application.

File integrity monitoring (E) helps detect unauthorized changes such as log deletion or binary modification, making it a crucial tool in recognizing and investigating tampering attempts.Blocking port 443 (B) would disable HTTPS and is not a practical solution. Antivirus (C) does not prevent form-based application attacks, and merely updating the application (D) may not be sufficient without addressing the underlying input validation flaw.

—

Fileless malware resides in memory and does not leave traditional file artifacts, making it difficult for antivirus solutions to detect. The most effective next step is to isolate the endpoints to prevent lateral movement and perform memory forensics to capture volatile data and identify any running malicious processes.

The alert shown is based on a Snort rule for a Unicode directory traversal attack against IIS web servers (Microsoft platform). The key detail here is the payload content " ../..%c0%af../ " which is a classic IIS-specific exploit related to CVE-2000-0884.

Since the company only uses Unix systems, they are not vulnerable to this IIS-specific attack. Therefore, these alerts are triggered by irrelevant traffic or misapplied signatures, resulting in False Positives.

As defined in the Cisco CyberOps guide:

“False Positive: an alert is generated for traffic that is not actually malicious or relevant to the protected environment”.

Process Explorer is an advanced Windows-based utility that shows real-time data about running processes, CPU usage, services, DLLs, and handles. It is specifically designed for this kind of investigation and is part of the Sysinternals Suite.

In the provided Wireshark capture, we see multiple TCP SYN packets being sent from different source IP addresses to the same destination IP address (192.168.1.159:80) within a short time window. These SYN packets do not show a corresponding SYN-ACK or ACK response, indicating that these TCP connection requests are not being completed.

This pattern is indicative of a SYN flood attack, a type of Denial of Service (DoS) attack. In this attack, a malicious actor floods the target system with a high volume of TCP SYN requests, leaving the target ' s TCP connection queue (backlog) filled with half-open connections. This can exhaust system resources, causing legitimate connection requests to be denied or delayed.

The countermeasure for this scenario, as highlighted in the CyberOps Technologies (CBRFIR) 300-215 study guide under Network-Based Attacks and TCP SYN Flood Attacks, involves:

Increasing the backlog queue: This allows the server to hold more half-open connections.

Recycling the oldest half-open connections: This ensures that legitimate connections have a chance to be established if the backlog fills up.

Cloud instances, containers, virtual disks, and network interfaces may be created and removed automatically in response to scaling, deployment, or recovery events. If responders do not preserve snapshots, volatile memory, provider audit records, and relevant cloud-native logs promptly, deprovisioning can destroy or detach evidence needed to reconstruct the incident. Persistent cloud storage exists, so option B is false. Many forensic tools can analyze virtual disks, memory images, logs, and exported artifacts; compatibility may require adaptation but is not universally absent. Providers also expose audit and service logs, although customer access and retention vary by service and contract. CBRFIR Fundamentals objective 1.7 explicitly covers evidence-gathering issues in virtualized environments and major cloud vendors. NISTIR 8006 likewise catalogs cloud-computing forensic challenges, emphasizing that cloud characteristics alter evidence identification, collection, preservation, and examination. NISTIR 8006 cloud forensic challenges

================

Volatility is purpose-built for extracting and interpreting artifacts from volatile-memory images. Its Windows pslist, psscan, and pstree capabilities can enumerate active processes, scan for terminated or unlinked process structures, and reconstruct parent-child relationships present when memory was acquired. Sleuth Kit and Autopsy primarily analyze file systems and disk images. The dd utility can acquire raw data, including a device image when used appropriately, but it does not itself interpret operating-system process structures. SIFT is a broader forensic workstation that can contain numerous tools; it is not the most precise answer when Volatility is offered directly. Cisco includes memory-forensics tools within Fundamentals objective 1.6.d and explicitly lists Volatility among the tools whose purpose and functionality candidates must recognize under Forensics Techniques objective 2.6. The official Volatility documentation confirms that pslist lists processes present in a Windows memory image. Volatility pslist documentation

================

The exhibit shows a series of process executions that form a suspicious chain involving scripting engines and obfuscated commands:

One critical indicator is cmd.exe executing PowerShell with obfuscated (Base64-encoded) arguments. The use of Base64 is a known method used by attackers to mask malicious commands. This aligns with attack techniques defined under MITRE ATT & CK T1059 (Command and Scripting Interpreter) and T1086 (PowerShell abuse). Therefore, option D is valid.

Another important IOC is WScript.exe acting as a parent of cmd.exe, which is abnormal in typical business environments. This indicates potential misuse of Windows Script Host (WSH) to launch commands, often seen in phishing or malware dropper scenarios. Thus, option E is also valid.

Options A and B by themselves are not definitive IOCs—PowerShell and cmd.exe are legitimate administrative tools and frequently used in Windows environments.

Option C is not supported by the exhibit—the reverse (powershell.exe initiated by WScript.exe) is what ' s seen, not the other way around.

These patterns align with the CyberOps Technologies (CBRFIR) 300-215 study guide, which specifies that chaining of interpreters (e.g., WScript → cmd → PowerShell) with encoded commands is a key indicator of compromise during forensic analysis.

The report must document both the initiating attack vector and the evidence connecting the affected host to the incident. The phishing attempt explains how the user was induced to access the infected PDF, establishing the likely initial-access mechanism. The DNS requests provide corroborating telemetry showing the workstation attempting to resolve or communicate with infrastructure associated with the suspicious domain. Together, these facts support a defensible causal chain from delivery to post-compromise activity. A malicious insider is not supported by the scenario. Although the domain is an important IOC, the observed DNS activity is stronger report evidence than merely repeating that the domain looked suspicious. A command-and-control callback should not be asserted unless traffic analysis establishes that function. CBRFIR Fundamentals objective 1.1 specifically requires analysis of the components needed for a root cause analysis report. Cisco CBRFIR v1.2 exam topics

================

Cisco Secure Malware Analytics (formerly Threat Grid) enables deep file behavior analysis, including TCP/IP stream analysis and behavioral indicators such as file system activity, process injection, registry changes, and command and control communication. These are essential in understanding what the suspicious file does post-execution, especially given the described behavior of creating a fake folder and outbound connection attempts.

—

TCPdump is a CLI-based packet capture tool that is widely used for real-time traffic inspection and analysis on Unix/Linux systems.

TCPshark is a variant CLI tool used similarly for packet analysis.

Although Wireshark is a powerful network protocol analyzer, it requires a GUI. Therefore, it is not suitable for environments without a graphical interface.

Generic Routing Encapsulation (GRE) is a tunneling protocol used to encapsulate a wide variety of network layer protocols inside point-to-point connections. If packets encapsulated with GRE are bypassing monitoring tools, it ' s likely due to tunneling—where payloads are hidden within another protocol. Tunneling can obscure malicious content or lateral movement in a network and is a common method used in data exfiltration.

To prevent macro-based attacks, the Cisco CyberOps study guide emphasizes the importance of limiting execution of unauthorized or unsigned macros. " Requiring that all macros be digitally signed and limiting execution only to those that meet the required trust level is a key mitigation strategy against malicious macros. " Additionally, enabling features like Controlled Folder Access helps in protecting sensitive directories from unauthorized changes by untrusted applications, including those launched via malicious macros .

These two measures—enforcing signed macro policies and leveraging controlled folder access—directly help in mitigating the risk posed by embedded malicious macros in documents.

The use of repetitive patterns in images is a known indicator of steganography, which is an anti-forensics technique used to hide malicious code or files inside seemingly benign content such as image or audio files. The repetitive patterns suggest that the image may contain embedded hidden data. This technique is particularly difficult to detect through conventional scanning or antivirus software.

According to the CyberOps Technologies (CBRFIR) 300-215 study guide, steganography is defined as “concealing malicious content or instructions within ordinary files such as .jpg, .png, or audio files, allowing the content to bypass security filters and reach the target system without detection”.

—

The code includes syntax and modules such as import win32con, import win32api, and uses Python-specific formatting like def, try/except, and print, clearly indicating that this is written in Python. It also uses the wmi module to monitor process creation events—a common technique in Python-based process monitoring scripts on Windows.

—

The syntax identifies Python: it uses import, defines a function with def, terminates the function header with a colon, and relies on indentation rather than braces. The requests library sends an HTTP GET request to the supplied URL, and response.status_code returns the server’s HTTP result code. Repeated execution can test whether a website responds successfully, which makes “website-uptime monitor” the closest description among the choices. Strictly, this short function performs one availability check; a production monitor would add scheduling, timeouts, exception handling, expected-status logic, logging, and alerting. It neither parses a dataset nor implements a content-management system, and it does not write response content to a file. Option D is therefore correct. This is within CBRFIR objectives 2.4 and 2.5. The official Requests quick-start documentation demonstrates requests.get() and status_code in this exact role.

The transmogrify anti-forensics technique refers specifically to the act of modifying the file header of a malicious file to disguise it as another file type. This type of manipulation helps evade detection by signature-based security tools and forensics analysis systems that rely on file headers to determine file type and purpose.

For example, a malicious .exe file might have its header changed to appear as a .jpg or .pdf to trick analysts or automated systems into treating it as benign. This tactic is particularly effective in bypassing content filtering and malware detection solutions that do not perform deep inspection beyond headers.

Comprehensive and Detailed Explanation:

The log entry contains the following key elements:

The timestamp: (04/Jan/2022:20:18:06 +0000)

HTTP method and URI: " GET /%60%60%60%60%60%60/ HTTP/2.0 "

HTTP status code: 404

User-Agent: Mozilla/5.0 ... Firefox/95.0

The status code 404 indicates that the requested resource was not found on the server. This is a standard HTTP response that signifies the server could not locate the requested URI (in this case, likely due to a malformed or invalid path /\`````/, where %60 is the URL-encoded form of the backtick character " " ).

There is no clear evidence of SQL injection, WAF detection, or redirection in this log. The use of encoded backticks may suggest probing behavior, but the log does not show a definitive attack signature.

Therefore, the correct interpretation is:

Answer: D. The requested page was not found.

When Web Application Firewalls (WAFs) are configured to block specific patterns (like ${), attackers may bypass this using URL encoding (e.g., %24%7B). In such cases, the WAF must decode these patterns before applying matching rules. Enabling URL decoding ensures the WAF recognizes encoded payloads and applies protections appropriately. This is a recommended hardening strategy against bypass techniques for command injection and remote code execution.

Isolating the infected endpoint immediately interrupts SMB-based propagation while preserving SMB for the business-critical application elsewhere. Blocking the known command-and-control IP also prevents the malware from receiving instructions or exfiltrating information. This is targeted containment: it reduces active risk without imposing an organization-wide outage. Disabling SMB on every network would be operationally damaging and ignores the stated dependency. SSL inspection may improve visibility into future encrypted traffic, but deploying it is slower and does not immediately stop the compromised host’s lateral movement. Reimaging and credential resetting may be appropriate during eradication and recovery, but performing them before containment and evidence collection can destroy useful forensic artifacts and leave the C2 infrastructure accessible from other affected systems. CBRFIR Incident Response Techniques objective 3.5 requires selecting mitigations from evaluated EDR, SIEM, IPS, and related alerts. Cisco CBRFIR v1.2 exam topics

The alert box in the screenshot ( " HACKED BY 1337 " ) is a classic sign of Cross-Site Scripting (XSS). This occurs when unvalidated input is executed as code in a browser.

To prevent this:

The Cisco CyberOps Associate guide recommends strict input validation as the primary defense against XSS and similar web-based injection attacks.

The first and most important step in forensic analysis is to preserve the integrity of the data. According to best practices outlined in the Cisco CyberOps Associate guide and NIST 800-86, forensic investigators must first produce a forensically sound, bit-by-bit copy of the system’s data (i.e., imaging). This enables analysis to occur without altering the original evidence, which is essential for legal admissibility and maintaining the chain of custody.

Removing the backdoor eradicates the known foothold, but it does not correct the entry control that failed. Because the established initial-access vector was a phishing email, deploying email sandboxing directly reduces recurrence by detonating new or suspicious attachments in an isolated environment and assessing their behavior before users can open them. An antimalware sweep may support scoping, but signature-based scanning alone is weaker against a sophisticated actor and does not close the email-delivery gap. Threat intelligence improves awareness, and management reporting is necessary governance, yet neither control analyzes attachments at the point of entry. Cisco states that Secure Email can submit new and suspicious files for behavioral file analysis in a sandbox. The selection also aligns with CBRFIR Incident Response Techniques objectives 3.4 and 3.8: recommend post-incident action and the appropriate Cisco security solution for detection and prevention. Cisco Secure Email Gateway data sheet

================

In the recovery phase, the goal is to restore affected systems to normal operations and ensure the threat has been completely eradicated. According to the CyberOps Associate guide:

" This phase may include restoring data from clean backups, replacing compromised systems, and the re-installation of the Operating System (OS) and applications " .

Also:

" During recovery, scanning hosts with updated antivirus and removing vulnerabilities ensures systems do not get reinfected " .

Option C correlates the external intelligence with the observed authentication sequence and then tests what the account did after access. The IP-range match is an IOC because it connects the session to infrastructure associated with a malicious actor. Repeated failures, an off-hours success, and subsequent account behavior can form IOAs by showing credential guessing, account compromise, discovery, privilege misuse, or lateral movement. Internal logs should not be evaluated in isolation when relevant external intelligence is available. A successful login after repeated failures increases rather than removes suspicion, and merely waiting for more attempts risks allowing an active compromise to continue. CBRFIR Incident Response Techniques objectives 3.2 and 3.9 require responders to correlate host and network data and interpret internal and external threat-intelligence feeds to determine IOCs and IOAs. The selected action performs both requirements directly. Cisco CBRFIR v1.2 exam topics

================

In cloud environments, investigators typically do not have access to the physical storage devices where the data resides. This restricts traditional forensic processes, such as imaging or direct disk access, which are commonly used in on-premises investigations.

The command in the image uses schtasks /create with the ONLOGON schedule and System user context to execute test.exe. This is a well-documented persistence technique, where an attacker ensures that a malicious executable is launched automatically at each system logon. This kind of scheduled task creation aligns with persistence techniques in the MITRE ATT & CK framework (T1053).

—

The Cisco Secure Firewall Threat Defense (Firepower) includes advanced capabilities such as intrusion prevention, URL filtering, and deep packet inspection. According to the CyberOps guide, it can detect and block C2 communications by analyzing traffic patterns and comparing them to threat intelligence data. The guide specifically states: " Advanced solutions such as Firepower provide detection capabilities for command and control (C2) traffic by identifying unusual outbound connections and behavioral anomalies " .

A hex editor exposes a file or storage artifact as raw bytes, normally presenting hexadecimal values beside their ASCII interpretation. Investigators use that view to inspect file signatures and headers, locate embedded strings, identify byte patterns, compare altered regions, examine slack or unstructured data, and make controlled changes to a working copy when required. It is not a network-monitoring platform, so option B describes a packet or flow-analysis tool. Option C describes sandboxing or dynamic malware analysis. Option D is closer to a disassembler or decompiler, which translates executable machine instructions into assembly or higher-level representations. Cisco’s current blueprint explicitly separates these roles: objective 1.6.a covers HxD, Hiew, and Hex Fiend in DFIR, while objective 1.6.b covers disassemblers and debuggers for basic malware analysis. Therefore, examining and manipulating binary data is the precise answer. Cisco CBRFIR v1.2 exam topics

================

The RunOnce row is the only autorun-related key marked as newly created as well as modified. Windows processes values under RunOnce when a user logs on and normally deletes each value after it is invoked. An attacker can therefore create a value containing a malicious command so that the payload executes automatically at the next logon, providing boot-or-logon autostart persistence. The ordinary Run key is also an autorun location, but the exhibit records only a modification, not the newly created entry specified in the question. Winlogon and Environment can be security-relevant, yet their displayed activity does not match the required evidence. Option D is consequently the precise artifact-based conclusion. This supports CBRFIR objectives 2.3 and 3.9 concerning host artifacts and indicators. Microsoft documents the behavior and locations of the Run and RunOnce keys .

The exhibit shows multiple ARP reply packets with the same IP addresses (192.168.51.105 and 192.168.51.201) being mapped to different MAC addresses, which triggers the message: " duplicate use of [IP] detected " . This is a strong indicator of an ARP spoofing (or poisoning) attack.

ARP spoofing occurs when a malicious actor sends falsified ARP messages to associate their MAC address with the IP address of another host. This misleads other devices on the network and allows interception or redirection of traffic.

The Cisco CyberOps Associate guide specifically recommends configuring port security on switches as a method to mitigate ARP spoofing, by limiting the number of MAC addresses allowed per port or statically assigning legitimate MAC addresses to switch ports.

Unexpected changes to normally read-only financial files are high-confidence evidence of unauthorized activity, even when antivirus and initial dynamic analysis are inconclusive. The defensible next step is to isolate the workstation, preventing possible command-and-control traffic, exfiltration, or lateral movement, while preserving its current state for examination. Detailed forensic analysis can then compare hashes and metadata, inspect alternate data streams, recover relevant memory and logs, and determine which process altered each file. Resetting, restoring, or replacing antivirus prematurely can destroy volatile evidence and break the incident timeline. Option C also assumes a benign system error before that conclusion has been proved. CBRFIR v1.2 Forensics Processes objective 4.4 specifically tests selecting the next evaluation step from a file’s distinguishing characteristics; the course also emphasizes collecting and examining digital evidence before remediation. Cisco CBRFIR v1.2 exam topics

================

IIS stores website access logs by default under %SystemDrive%\inetpub\logs\LogFiles, so copying those files preserves requests, client addresses, status codes, and timestamps relevant to the web-server compromise. Windows service start, stop, failure, and configuration events are written by the Service Control Manager to the System log; exporting those filtered events from the affected Windows server directly addresses the attacker’s shutdown of critical services. The Security log may contain authentication or object-access evidence, but it is not the specified source for Service Control Manager events. C:\Windows\Temp\Logs is not the standard IIS logging directory, and the service evidence belongs to the affected Windows server, not the IIS server’s Security log. This maps to CBRFIR Forensics Techniques objective 2.2: identify required forensic files and their host locations. Microsoft IIS logging Microsoft Event Viewer overview

================

Steganography is the anti-forensics technique of hiding malicious content within seemingly innocent files, such as image, audio, or video files. The goal is to conceal data or code in a way that avoids suspicion and detection, thereby making traditional security inspection tools ineffective unless they are explicitly designed to detect hidden data within media files.

Steganography differs from encryption because it does not simply make data unreadable; it hides the existence of the data itself. It is commonly used in cyber operations to hide command-and-control instructions or to exfiltrate sensitive information in covert ways.

Dynamic malware analysis involves executing the malware in a controlled environment to observe its behavior, such as file creation, network traffic, or system modifications. A sandbox is designed for this purpose—it safely executes and monitors suspicious code without risking the host system. The other tools (Decompiler, Unpacker, Disassembler) are primarily used in static analysis.

Correct answer: D. Sandbox

—