detecting-ransomware-precursors-in-network

name	detecting-ransomware-precursors-in-network
description	Use when detects early-stage ransomware indicators in network traffic before encryption begins, including initial access broker activity, command-and-control beaconing, credential harvesting, reconnaissance scanning, and staging behavior. Uses network detection tools (Zeek, Suricata, Arkime), SIEM correlation rules, and threat intelligence feeds to identify ransomware precursor patterns such as Cobalt Strike beacons, Mimikatz network signatures, and RDP brute-force attempts.
domain	cybersecurity
tags	["ransomware","detection","network-security","incident-response","defense"]
subdomain	ransomware-defense
version	1.0.0
author	oyi77
license	Apache-2.0
nist_csf	["PR.DS-11","RS.MA-01","RC.RP-01","PR.IR-01"]

Detecting Ransomware Precursors In Network

Overview

Cybersecurity skill for detecting ransomware precursors in network. Follows industry best practices and security standards.

When to Use

Trigger phrases:

• "detecting ransomware precursors in network"

• "Detects early-stage ransomware indicators in network traffic before encryption b"

• Building detection rules for pre-ransomware network activity (the average time from Cobalt Strike deployment to encryption is 17 minutes)

• Monitoring for initial access broker (IAB) indicators that precede ransomware deployment

• Creating SIEM correlation rules that chain multiple precursor events into high-confidence alerts

• Tuning network detection systems to distinguish ransomware staging from normal administrative activity

• Investigating suspicious network patterns that may indicate ransomware operators have established a foothold

Do not use for post-encryption response (see recovering-from-ransomware-attack). This skill focuses on the pre-encryption detection window where containment can prevent data loss.

When NOT to Use

• When you lack proper authorization for testing
• For production systems without change management
• When the task requires legal or compliance expertise beyond technical scope

Prerequisites

• Network detection platform (Zeek/Bro, Suricata, or Arkime/Moloch) deployed on network TAP or SPAN ports
• SIEM platform (Splunk, Elastic Security, Microsoft Sentinel, or QRadar) ingesting network logs
• Threat intelligence feeds covering ransomware IOCs (CISA, abuse.ch, OTX, MISP)
• Network flow data (NetFlow/IPFIX) from core routers and firewalls
• DNS query logging from internal resolvers
• Full packet capture capability for incident investigation

Workflow

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

 () -> :
     {k: re.findall(v, text)  k, v  IOC_PATTERNS.items()}