Red Hand Resources
Practical knowledge for network defenders
Investigation playbooks, capture tutorials, practical explainers, and free tools to help you move from network evidence to a confident decision.
From the community
Latest from r/redhand
Learn and apply
Tutorials and explainers
Capture better evidence, solve common problems, and put network data to work.
Your DNS Architecture Has a Blind Spot the Size of Active Directory
Turn on the DNS Server analytical channel, keep the recursive events, and drop the junk before it reaches your SIEM. You keep the evidence that catches forwarder hijacking without paying to index every bit of noise.
Open resourceThe Best DNS Logging on Your Network Is Free, Built-In, and Switched Off
You probably already own most of the DNS telemetry you need. Windows has it switched off, macOS hides the names, and Linux needs help with process attribution, but each can tell you far more than the DNS server alone.
Open resourceCreating PCAP files on Windows
Windows already has pktmon. Use the ready-made PowerShell script, or follow the commands yourself, and you will have a PCAPNG file ready to analyze.
Open resourceCreating PCAP files on Linux
Chances are Linux already has everything you need. Pick the interface with the default route, capture full packets with tcpdump, and cap the packet count so the file does not fill the disk.
Open resourceCreating PCAP files on macOS
Your Mac already has tcpdump. Find the interface carrying the traffic, capture full packets, and stop at a sensible packet count before the file gets too large.
Open resourceWorking with AWS VPC Flow Logs
If packet capture across AWS is too expensive or awkward, VPC Flow Logs are the cheaper evidence source. Send them to S3, add the useful fields, and remember that they are delayed metadata, not packets.
Open resourceNetFlow vs. PCAP
NetFlow is lightweight metadata that scales well for long-term monitoring. PCAP is much larger, but it keeps the packet contents you need for deep inspection and forensic analysis.
Open resourceDetection and triage
Investigation guides
Understand the behavior, review the right evidence, and decide when to escalate.
Investigating ARP Scans
ARP scanning is common during inventory and troubleshooting, but an attacker can also use it to map nearby systems. Treat it as a discovery signal, then check the source and what happened next.
Read investigation guideInvestigating Port Sweeps
A port sweep can build a target list for exploitation or lateral movement. It matters most when the source is not approved and later connects to one of the services it found.
Read investigation guideInvestigating Port Scans
Security tools perform port scans routinely, but an attacker can use one to profile a chosen target. The ports tested and any successful follow-through matter more than the scan label alone.
Read investigation guideInvestigating Control Connections
Control connections are essential for legitimate administration and useful to an attacker operating a compromised system. Confirm who connected, what they used, and whether commands or files followed.
Read investigation guideInvestigating Service Enumerations
Identity, inventory, backup, and monitoring tools generate plenty of legitimate enumeration. Worry when a user endpoint or unusual process performs it and then uses what it discovered.
Read investigation guideInvestigating Login Brute-Force Attempts
Network traffic can show the pattern, but authentication logs tell you whether these were actually rejected logins. A success after repeated failures is the result to act on.
Read investigation guideInvestigating Web Scraping Activities
Crawlers and monitoring systems scrape sites legitimately every day. Risk goes up when an unknown source systematically collects sensitive, internal, or authenticated content.
Read investigation guideInvestigating HTTPS Beacons
Malware beacons, updates, telemetry, and notifications can all produce the same regular HTTPS pattern. The process, destination, timing, and any follow-on activity tell you which one you have.
Read investigation guideInvestigating SYN Floods
A SYN flood may be an attack, heavy legitimate demand, or a broken client. Confirm that the service was actually affected before treating the traffic volume as proof.
Read investigation guideInvestigating SOCKS Tunnels
Approved proxies and VPNs rely on tunneling, and attackers use the same capability to pivot or hide traffic. Identify the process, the endpoints, and what the tunnel carried.
Read investigation guideInvestigating Suspicious Endpoints
Reputation is a starting point, not proof. Outbound contact from an internal device, especially through an unknown process or repeated connection, matters far more than an unanswered inbound probe.
Read investigation guideInvestigating Collection Activities
Backups, synchronization, and software delivery move large volumes every day. Escalate when sensitive data is staged by an unusual process or followed by external transfer, deletion, or encryption.
Read investigation guideAnalyze traffic
Free tools
Upload a packet capture or monitor live endpoint traffic with Red Hand.
Red Hand PCAP Analyzer
Upload a PCAP and get a focused report of suspicious behavior, exposed services, threat intelligence matches, and unusual activity, without digging through packets yourself.
Open free toolRed Hand Collector
Install Collector on Windows, macOS, or Linux and stream compact network and process telemetry to Red Hand. The report updates as activity happens, so slow scans, recurring connections, and other patterns have time to show themselves.
Open free toolNo matching resources
Try a broader search or choose a different resource tag.