Technical Anshu
Tutorials Blog
Incident Walkthrough

Ransomware Attack Day What Happens When Your Four Security Layers Work Together

Ransomware day is not about whether the attack comes. It is about whether Tuesday's disaster is a lost morning or a lost business. Here is the same attack, in an office that built the four layers - and one that did not.

By Technical AnshuWindows 10 / 11Small Office IT
Watch the complete IT security setup in the video - all four layers shown step by step

Let us walk through the attack honestly. 9:12 AM: a staff member opens an attachment that looked like an invoice. It was not. Malware starts encrypting files on that PC and reaches for the shared folders. In an unprepared office, this story ends with a ransom note on every screen. In an office with the firewall, endpoint, antivirus and backup layers in place, the same morning plays out very differently. This page follows the prepared office, hour by hour - and notes where each layer earns its cost.

RANSOMWARE DAY - TIMELINE IN A PREPARED OFFICE
09:12 Attachment opened on ACCOUNTS-02 09:13 Antivirus/EDR flags mass file changes, isolates the PC from network 09:20 Staff member reports it immediately (no-blame culture) 09:30 IT confirms scope: 1 PC + part of one shared folder 10:00 Server share rolled back to 08:00 clean snapshot 11:30 PC wiped and reimaged from standard image, patches verified 12:15 Offline/cloud backup restore test on restored data Files open fine 13:00 Accounts team working again. Total loss: one morning Ransom paid: None Data lost: ~1 hour of work on one folder
Example timeline for an office with all four layers working. The two quiet heroes are the immediate report at 09:20 and the tested backup at 12:15.
1

Hour One - Detection and Isolation Decide Everything

Ransomware spreads at machine speed, so the first minutes are worth more than the next days. In the prepared office, the antivirus/EDR layer notices hundreds of files being renamed and encrypted - behaviour no invoice program shows - and isolates the PC from the network automatically. The staff member, trained that reporting brings help rather than blame, calls IT within minutes instead of quietly rebooting and hoping.

  1. Disconnect first, investigate second - pull the network cable or let EDR isolate the machine
  2. Do not pay, do not negotiate, and do not delete anything yet - evidence matters
  3. Check the shared folders and server immediately for encrypted files and ransom notes
  4. Change the involved user passwords from a clean device
2

The Firewall and Endpoint Layers Show Their Value

While the cleanup starts, the other layers explain why the damage stayed small. The firewall had no open ports, so the attackers could not also walk in from the internet to finish the job or steal data twice. Every other PC was fully patched, so the malware could not jump machine-to-machine using known Windows flaws - the sideways movement that turns one bad PC into a whole encrypted office simply found no doors. The endpoint console shows exactly which machines the infected PC talked to, so the investigation has a map instead of a panic.

3

Restore - Where the Backup Layer Pays for Itself

Now the question that decides the day: are the backups clean and reachable? The attacker deleted the server's shadow copies - they always try - but the offline and immutable copies were beyond reach, exactly as the 3-2-1 setup intended. Because the office runs a monthly restore test, nobody is experimenting under pressure; the restore procedure is a known drill.

  1. Restore shared data to the last clean point before the attack - verify timestamps carefully
  2. Wipe and reimage the infected PC completely; never trust a cleaned one
  3. Restore the PC's local files from backup after the rebuild
  4. Scan restored data before it rejoins the network
4

After the Day - The Fixes That Prevent a Sequel

Within the week, the office reviews how the attachment got past the mail filter, adds the lesson to the next phishing session, and checks every layer again end to end. Total cost: one lost morning, one rebuilt PC, and some pride. Compare the unprepared version of this day: no isolation, unpatched PCs encrypting one by one, a permanently connected backup drive encrypted too, and a stranger demanding payment for the business's own data - with days or weeks of downtime and no guarantee. The four layers did not stop the click. They stopped the click from mattering.

Honest line: this walkthrough is the good version, not a guaranteed version. A stealthier attack that sits quietly for weeks can poison backups too, and recovery can take days. The layers turn a probable catastrophe into a probable bad morning - in security, that difference is the entire game.

Watch the Full Video

See the complete security setup live - firewall, endpoint, antivirus and backup, all in one video.

Watch Full Video
Common Questions (FAQ)

Should an office ever pay the ransom?

The consistent advice from law enforcement and security professionals is no: payment does not guarantee your data back, marks you as a payer for future attacks, and may fund further crime. A tested backup is the reliable exit - which is why it must exist before the attack.

How do we know backups are clean and not already encrypted?

Restore from a point clearly before the infection time, verify sample files open correctly, and scan the restored data. The monthly restore-test habit means you already know your backups work and how far back clean copies go.

One PC got encrypted but nothing else. Was it still serious?

Yes - treat it as a full incident. Ransomware on one machine means an attacker or malware got inside; find the entry point, check other machines, and reset involved passwords. The quiet cases are where second attacks are planted.

This guide is based on the Complete IT Security Setup video by Technical Anshu - stuck on any step, ask in the video comments and you will get a reply.