Chapter 4 · Reading 3 of 12
Ransomware
Security+ SY0-801 · Objectives 3.4
When the campus advising office loses access to its schedule, students lose access to a service. Students still arrive, staff need a safe check-in process and advisors need reliable access to the records they are authorized to view. These operational needs determine which functions should be restored first.
Ransomware is a type of malicious software designed to block access to a computer system or its data, usually by encrypting the data, until a ransom is paid to the attacker. Other ransomware techniques include threatening to report the person to law enforcement due to pirated software or pornography and threatening to expose sensitive information or photos. Ransomware has been identified as one of the most prevalent threats that has been on the rise over the past couple of years.
Types of Ransomware
We can classify ransomware based on their behavior and actions:
- Crypto Ransomware: Encrypts files on a victim's system and demands payment for the decryption key. Examples include Cryptolocker and WannaCry.
- Locker Ransomware: Locks the victim out of their system by denying access to the computer or device. It does not typically encrypt files but makes the system unusable until the ransom is paid.
- Scareware: Displays fake warnings or alerts, often claiming that the system is infected with viruses, and demands payment to resolve the fictitious issues. Unlike other types, scareware may not actually lock or encrypt data.
- Doxware (Extortionware): Threatens to publish the victim's sensitive data unless the ransom is paid. It combines encryption with extortion tactics.
Ransomware Identifiers
Ransomware identifiers are specific characteristics, behaviors, and signatures that help detect and identify ransomware infections. These identifiers can be used by cybersecurity professionals and security software to recognize and mitigate ransomware attacks.
- File Encryption Activity: Sudden and widespread encryption of files with unusual extensions or filenames, often followed by the creation of ransom notes.
- Mass File Renaming: Files are renamed with new extensions or prefixes/suffixes indicating encryption. For example, a file originally named "document.txt" might be renamed to "document.txt.locked" or "document.txt.encrypted."
- Ransom Notes: The presence of ransom notes in affected directories. These notes typically provide instructions for paying the ransom and recovering the encrypted files. They are often named "README.txt," "DECRYPT_INSTRUCTIONS.html," or similar.
- Unusual Network Activity: Anomalous network traffic patterns, such as connections to known command-and-control (C2) servers or large amounts of data being sent to external IP addresses.
- Suspicious Processes: Unusual processes running on the system, often consuming significant CPU or memory resources. These processes may have names similar to legitimate system processes but with slight variations.
Testing restoration in isolation
Select a recovery point from before the earliest supported compromise time, restore into an isolated environment and validate a business transaction. Check identities and dependencies before reconnecting. Restoring files addresses availability. Evidence that records were copied before encryption creates a separate confidentiality investigation.
Proving that a service is back
A backup console marks last night’s job successful. Ask a scheduler to describe the smallest meaningful recovery test. Can an authorized user find a synthetic appointment, change its time and see the change reflected at the advising desk? That transaction tests dependencies a file count misses. Use an isolated recovery environment and preserve the original incident evidence. If the most recent usable backup predates several bookings, arrange reconciliation with the people who recorded them. Keep the separate question of whether anyone copied student information open until evidence answers it.
Inspect the three records, then use the evidence to answer the question.
1. Observe
Record the demand and inaccessible files.
B1 / 00:00 / restore verified
2. Determine scope
Identify affected hosts and services.
B2 / 06:00 / restore verified
3. Validate recovery
Test a clean restore point.
Compromise began 07:00. B3 was taken at noon.
Apply the reading
A workstation displays a ransom demand. What should you establish before promising recovery?
Compare your reasoning
Determine the affected scope, preserve available evidence, and validate a clean recovery point. A demand alone does not reveal the condition of every file.