ISC · Security and Confidentiality and Privacy · 7 practice questions
Ransomware First Response: Isolate or Power Off?
For active ransomware, isolate affected systems from the network while keeping them powered on to preserve volatile evidence. Below, follow a workstation incident through immediate isolation and coordinated evidence preservation.
Try one first
Hint
Prioritize containment and preserving volatile forensic evidence before taking actions that destroy memory, alter live state, or trigger public disclosure.
Answer D. The immediate priority is containment and evidence preservation. Isolate the host from the network while leaving it powered so incident responders can collect volatile data (memory, running processes, live connections, current logs) and image storage for later analysis. Actions such as shutting down, credential changes, reimaging, or public notifications should be coordinated after containment and rapid triage to avoid destroying evidence or impeding the investigation.
Why not A: Notifying stakeholders is tempting because legal and reputational obligations exist. It fails as the immediate first step because premature public disclosure or broad notifications before containment and scoping can spread inaccurate information, impede effective investigation, and should be coordinated with legal and incident response once scope is rapidly assessed.
Why not B: This option tempts because credential resets are a common step to block attacker access quickly. It fails as the single immediate action because resetting credentials can disrupt forensic collection, may not terminate attacker persistence or lateral access, and can alter live evidence or alert the attacker; credential changes should be coordinated as part of containment.
Why not C: Powering off is tempting because it appears to halt encryption and speed recovery. It is incorrect because shutting down destroys volatile memory (potential encryption keys, live sessions, and transient logs) that are critical for investigation and scope determination; reimaging should occur only after evidence is preserved.
Step by step
- Recognize the active incident
An accounting workstation is powered on, displays a ransom note, and has files renamed with a .locked extension. Monitoring shows SMB activity to shared resources and outbound connections to an unfamiliar IP; network-attached backups remain reachable.
- Isolate without cutting power
Immediately isolate the workstation, activate incident response, and disconnect or otherwise protect reachable backups from compromised systems and accounts. Leave the workstation powered on to preserve RAM; network isolation does not necessarily stop local encryption.
- Preserve volatile evidence promptly
Have incident responders promptly capture RAM and document running processes and active connection information. Do not reboot or power off before this collection, because those actions destroy volatile evidence.
- Coordinate disk and log collection
Coordinate forensic disk imaging and preservation of relevant endpoint, authentication, and network logs. A disk image preserves stored evidence but does not replace the RAM capture.
Key points
- Remember: Disconnect the network path, not the power cord, to contain network activity while preserving RAM.
- Network isolation does not necessarily stop encryption of files already on the workstation.
- RAM capture and disk imaging preserve different evidence; a disk image does not replace memory capture.
How the exam traps you
- Power off first, then image the disk. Keep the workstation powered on so responders can capture RAM and other volatile evidence.
- Leave the workstation connected to observe the attacker. Isolate immediately rather than allow continued network spread or outbound transfers.
Question 2
Hint
Focus on the condition that could let the ransomware attack reach the recovery source, not just the production environment.
Answer C. If backups are online and accessible with the same privileged credentials as production, an attacker who gains those credentials can reach, encrypt, or delete the backups, removing the ability to restore. That defeats the intended protection of daily backups; effective defenses isolate backups (offline, immutable, or protected by separate credentials) so an attacker cannot corrupt the recovery source.
Why not A: Testing frequency matters because infrequent restores can delay discovery of restore failures, which is a valid concern. Still, less frequent testing does not directly allow ransomware to reach or corrupt backups in the way that shared online access with common credentials does, so it is a less limiting condition.
Why not B: This is tempting because "encryption" is commonly linked with ransomware, but encryption at rest generally protects backups rather than weakening them. Encrypted backups remain useful for recovery as long as the organization can access the decryption keys; encryption by itself does not make backups more vulnerable to ransomware.
Why not D: Email filtering is a preventive control that can reduce infection risk but does not weaken the backups themselves. It doesn't limit the usefulness of backups after a ransomware event in the way that accessible, unisolated backups would.
Question 3
Hint
Focus on the pattern of authentication logs (volume/distribution of failed attempts and subsequent successful logins) and whether there is evidence of phishing or an unpatched exploit.
Answer D. The large volume of distributed failed logins from many external IPs followed by some successful logins is characteristic of credential-stuffing or password-spraying using breached or weak credentials. Investigators found no phishing attachments and the VPN had been recently patched, making an email-delivered payload or an unpatched VPN exploit less consistent with the observed log pattern. Because MFA was not enforced for remote access, attackers could reuse or guess credentials to take over accounts and deploy ransomware.
Why not A: An unpatched VPN exploit is a known ransomware vector and thus tempting, but the appliance had been patched recently and the logs show distributed, high-volume authentication attempts, behavior more consistent with credential-based attacks than with a single exploit that yields immediate remote code execution.
Why not B: Phishing is common and plausible, but investigators found no evidence of delivered or opened malicious attachments. The authentication-log pattern of many external failed attempts followed by successful logins points toward credential compromise rather than an email-delivered payload.
Why not C: An insider could perform encryption and leave a ransom note, but the presence of numerous external IPs conducting failed logins across many accounts before successful external logins indicates an external, distributed attack pattern inconsistent with a single insider acting alone.
Question 4
Hint
Focus on the point where the facts show the attack has moved from possibility to actual impact on files or systems.
Answer B. Unreadable files, renamed files, and a ransom note are classic, direct indicators that ransomware has executed and encrypted data. At that point the organization should escalate from monitoring to active incident response (isolate affected systems, preserve evidence, and begin recovery and remediation procedures).
Why not A: Tempting because phishing emails are a common ransomware delivery method, but the email itself indicates only a potential vector; it does not prove that ransomware executed or affected systems.
Why not C: This suggests malware was detected, but if the file was quarantined before execution, the evidence points to a blocked or contained threat rather than active ransomware encrypting data.
Why not D: Performance changes can result from many benign causes, and because the backup completed successfully there is no direct evidence of encryption or ransom activity; this is too nonspecific to declare an active ransomware incident.
Question 5
Hint
Compare the timeline: did data leave the environment before files were locked, and what does the ransom note threaten to do with the files? Focus on origin of the SFTP session and the phishing event.
Answer B. The timeline shows a phishing click followed by an SFTP transfer of the finance archive to an external IP using 'svc_backup' before files were locked, and the ransom note threatens publication, consistent with data theft followed by extortion. The later creation of a local admin account and scheduled tasks modifying file servers supports unauthorized lateral movement and deployment of ransomware by external actors.
Why not A: This is tempting because insiders can access finance data, but the evidence points to external credential compromise: a phishing click preceded an external SFTP transfer from 'svc_backup' and the vendor denies that account, making external attackers more likely than an insider acting alone.
Why not C: Vendor error is unlikely given the vendor's statement that it did not use that external IP and that 'svc_backup' is not its account; additionally, the extortionary threat and the timing of the external transfer before encryption point to deliberate exfiltration rather than an accidental vendor script.
Why not D: This conflicts with the facts: logs show a large outbound transfer to an external IP before files were locked, and the ransom note threatens to publish files, both of which support exfiltration followed by extortion rather than purely destructive encryption.
Question 6
Hint
Focus on the first action during an active attack, not the final recovery step.
Answer C. When ransomware is actively encrypting files, the immediate priority is containment. Disconnecting affected devices or isolating network segments limits lateral movement and prevents further encryption of shared data. Because backups exist, recovery should follow containment and coordination with the incident response team.
Why not A: Rebooting might seem to halt a process, but it can destroy volatile forensic evidence, may not stop network-based components, and could allow the attacker to resume activity. Isolation preserves evidence and prevents further spread.
Why not B: Paying may seem to promise the quickest recovery, but it does not guarantee decryption, encourages attackers, and should not be done while the attack may still be spreading. The immediate priority is containment and then recovering from backups if available.
Why not D: Deleting the ransom note ignores the underlying infection; continuing normal operations risks further encryption and lateral movement. The note is a symptom, containment and incident response are required.
Question 7
Hint
Map each alert to the specific 'immediate containment' triggers listed in the IR policy, focus on confirmed credential compromise (credential dumping), not on suspicious activity alone.
Answer A. EDR has confirmed credential-dumping malware on Alice's workstation and reported extracted credentials, which directly satisfies the IR policy's 'confirmed credential dumping' trigger. That confirmation requires immediate containment and forced credential rotation to prevent misuse of the stolen credentials. The other alerts remain monitoring-level under the policy (failed logins without successful authentication, a click with no credential submission, and a scheduled non-sensitive backup) and do not by themselves require immediate containment.
Why not B: Multiple failed logins can be suspicious, but the policy classifies failed attempts without any successful authentication or corroborating evidence as monitoring-level; immediate resets or account take-downs are not required by that trigger alone.
Why not C: A large upload could resemble exfiltration, but the DLP labeled the transfer non-sensitive and it occurred during a scheduled backup to a known partner. The policy requires confirmed exfiltration of sensitive data to trigger immediate containment.
Why not D: While caution against false positives is reasonable, the policy explicitly mandates immediate containment and credential rotation when credential dumping is confirmed; waiting would risk attackers abusing the extracted credentials for lateral movement.
Common questions
Should I unplug a ransomware-infected computer?
Disconnect its network connection, not its power cord. Keep it powered on so incident responders can preserve volatile evidence.
Does disconnecting the network stop ransomware encryption?
It limits access to shared resources and interrupts outbound connections. It does not necessarily stop encryption of local files.
Why capture RAM if responders will image the disk?
RAM can contain running processes, active session information, and encryption keys that a disk image may not preserve. Powering off destroys that volatile evidence.
Watch it solved
A full CPA ISC task-based simulation on Threats and attacks, worked step by step.
SIEM Attack Identification | CPA ISC Simulation (TBS) on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Threats and attacks
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.