All articles

    Threat intelligence

    Ransomware in 2026: Modern Tactics and the First 72 Hours

    Written by Khalid NamraPublished: 16 July 2026Updated: 16 September 20269 min read
    Ransomware in 2026: Modern Tactics and the First 72 Hours

    In three lines

    • By the time files are encrypted, the intrusion is old news.
    • The common entry points have been stable for years: valid credentials bought or phished, an internet-facing service missing a patch, and remote access exposed without multi-factor authentication.
    • This is where detection is still cheap.

    By the time files are encrypted, the intrusion is old news. Modern ransomware operations spend days or weeks inside a network first — stealing credentials, mapping file shares, deleting backups and exfiltrating data to use as leverage even if you restore cleanly.

    How the intrusion usually begins

    The common entry points have been stable for years: valid credentials bought or phished, an internet-facing service missing a patch, and remote access exposed without multi-factor authentication. None of these require sophisticated malware.

    • Compromised VPN or remote desktop access
    • Unpatched perimeter appliances
    • Phished credentials without MFA
    • Third-party or supplier access paths

    The signals that appear before encryption

    This is where detection is still cheap. Watch for shadow copies being deleted, backup agents stopped, new administrative accounts, mass file reads by a single account, archiving tools appearing on servers, and large outbound transfers to file-sharing services at unusual hours.

    The first 72 hours

    Hours zero to four are about containment and evidence at the same time: isolate affected hosts at the network level rather than powering them off, preserve memory and logs, and disable the compromised accounts. Powering a machine off destroys evidence that determines whether data was stolen.

    Hours four to twenty-four are for scope: which accounts, which systems, what was accessed, and whether backups are intact and offline. Hours twenty-four to seventy-two are for decisions — recovery sequencing, regulatory notification, customer communication and legal counsel.

    Backups only count if they are tested and offline

    Attackers target backup infrastructure deliberately and often first. At least one copy must be immutable or physically offline, restoration must be tested on a schedule against a realistic recovery time objective, and backup administration should require separate credentials from domain administration.

    The practical takeaway

    Detect the pre-encryption behaviour, isolate without powering off, keep one immutable offline backup, and decide the notification path before the incident.

    Related RASED services

    Official references

    Written by Khalid Namra

    Founder & CEO, RASED Solutions — engineering lead of RASED Solutions

    Khalid Namra building software since 2015 and leads the engineering and security teams behind RASED Solutions in Riyadh.