Skip to content

Incident Response

github-actions[bot] edited this page Nov 17, 2026 · 2 revisions

Blue Team operations, threat detection, digital forensics, and standardized response procedures

Part of the ULTIMATE CYBERSECURITY MASTER GUIDE

Blue Team DFIR SIEM


More defensive resources: Curated detection, DFIR, Suricata and YARA research maps external source projects to existing PNWC field guides.

Packet Capture & Triage

Reference Description
Wireshark Master Filter List Indexed display/capture filters for packet triage
Wireshark Field Cheat Sheet Protocol-focused display filter reference
Advanced Capture Guide Deeper packet capture analysis and troubleshooting

Capture scope and evidence interpretation are separate from Wazuh detection rules.

Honeypots & Wireless Monitoring

Reference Description
Endpoint Visibility Index Windows/Linux host telemetry, Sysmon, auditd and osquery
IDS & IPS Index Wired and wireless detection setup, sensor visibility and verification
Honeypot Index Select a deception platform and review deployment constraints
Raspberry Pi Lab Small dedicated decoy sensor
Proxmox Lab Isolated virtualized decoys
ESP32-S3 Lab Microcontroller-based deception examples
Honeypot โ†’ Wazuh Export decoy telemetry to SIEM
Kismet + Wazuh Correlate wireless findings with SIEM alerts
nzyme + Wazuh Wireless monitoring and log correlation

Threat-intelligence and vulnerability API reference: Security API Catalog covers NVD CVE 2.0, the official CISA KEV feed, GHSA, URLhaus, VirusTotal, GreyNoise and safe enrichment workflows. See the OSINT threat-feed script for existing provider integrations, with the documented URLhaus authentication review still outstanding.

Evidence Collection & Detection Validation

Reference Description
Velociraptor/ForensicArtifacts Triage Authorized evidence collection and triage
Sigma/Elastic/Wazuh Validation Verify detection rules and event mappings
Atomic Red Team Lab Verification Confirm detections with controlled simulations

Scope collection and simulations before using any client environment.

๐ŸŽฏ Purpose

Index for the Incident Response section - covering blue team operations, log aggregation infrastructure, network intrusion detection and response, DFIR processes, and SIEM integration guides.

โš™๏ธ Function

Links to log aggregation and visibility setup (log_agg.md), wireless/network intrusion response procedures (network_intrusion.md), and provides an attack taxonomy, tool ecosystem reference, playbook overview, and SIEM configuration guidance.

๐Ÿ† Goal

Enable blue team operators to quickly find the right IR procedure, log source configuration, or detection rule for an active or suspected incident.

๐Ÿ“‹ When To Use

  • Starting incident response work: find the right playbook or log configuration file
  • Setting up a new SIEM or log aggregation infrastructure from scratch
  • Responding to a wireless intrusion, rogue AP, or physical plant hack scenario

๐Ÿ“‹ Table Of Contents


๐ŸŽฏ Overview

For incident interpretation and source-backed historical research, see Case Studies, including physical access control and security-token incidents.

Incident response preparation detection containment recovery and improvement

Coordinate containment with business needs and preserve evidence before destructive changes.

Welcome to the Incident Response (IR) and Digital Forensics section. This directory focuses strictly on visibility, detection, and defense. It provides the architecture, configurations, and standard operating procedures (SOPs) required to ingest telemetry, hunt for adversaries, and respond to active threats systematically.

Core Objectives:

  • Centralize Logs: Ingest data from endpoints, servers, and network devices into a SIEM.
  • Detect Threats: Write SIGMA rules and custom alerts to catch malicious activity generated in your environment.
  • Analyze Artifacts: Perform digital forensics on memory (RAM) and disk images to establish timelines and indicators of compromise (IoCs).
  • Standardize Response: Utilize playbooks to handle specific incidents (e.g., Ransomware, Insider Threat) consistently and thoroughly.

๐Ÿ—‚๏ธ Tool & Infrastructure Categories

๐Ÿ“Š Log Aggregation & SIEM

Central nervous systems for security telemetry.

Platform / Guide Description Deployment Complexity
ELK Stack (Elastic) Docker compose files and configs for Elasticsearch, Logstash, and Kibana. ๐ŸŸก MEDIUM
Wazuh Deployment guides for the Wazuh manager, agent registration, and rule tuning. ๐ŸŸก MEDIUM
Splunk Setup for Splunk Free/Enterprise trial and creating optimal data indexes. ๐ŸŸข LOW
Graylog Configuration for lightweight, scalable log management and parsing. ๐ŸŸก MEDIUM

๐Ÿ‘๏ธ Endpoint Visibility (EDR)

Instrumentation for host-level telemetry.

Tool / OS Description Integration
Windows (Sysmon) Installation scripts and configs (SwiftOnSecurity/Olaf Hartong) for granular event tracing (Process creation, network connections). High
Linux (Auditd/Syslog) Hardening logging configurations for Linux servers and standardizing syslog output. Medium
Osquery SQL-powered operating system instrumentation for proactive threat hunting. High

๐Ÿ•ธ๏ธ Network Security Monitoring (NSM)

Kismet + Wazuh Wireless IDS Lab: Deploy a fixed-channel 802.11 intrusion sensor, forward alerts into Wazuh, classify deauthentication events and build correlation/timeline dashboards. This is complementary to Ethernet-layer Snort/Suricata. The nzyme + Wazuh integration adds per-network disconnection thresholds, webhook/syslog forwarding and multi-sensor investigation guidance.

Visibility into East/West and North/South traffic flows.

Technology Focus Area Common Tools
Zeek (Bro) Connection logging, protocol analysis, and metadata extraction. Zeek, RITA
IDS / IPS Signature-based network threat detection and prevention. Suricata, Snort
Packet Capture Workflows for capturing and analyzing raw .pcap files. Wireshark, TShark, TCPDump
Wi-Fi Deauthentication Detection Analyze legitimate vs spoofed 802.11 disconnects; PMF, monitor-mode capture, Kismet WIDS alerts and SIEM triage Kismet, Wireshark, TShark, AP/controller logs

๐Ÿ”ฅ Firewalls & Network Enforcement

Guide Use
OpenBSD PF Firewall PF rulesets, NAT, network-edge deployments, high availability, and logging

Pair firewall enforcement with network intrusion response and log aggregation. For analysis of an acquired binary, use the Reverse Engineering index after the sample is contained. For a dedicated, isolated malware-triage workstation, see the REMnux Malware Analysis Guide.


๐Ÿ“˜ IR Playbooks & SOPs

Step-by-step containment, eradication, and recovery guides.

Playbook Scenario Focus
Malware Outbreak Ransomware / Worms Isolation, identification, and eradication steps.
Phishing Analysis Malicious Emails Header analysis, attachment detonation, URL scanning.
Unauthorized Access Compromised Credentials Investigating brute force and impossible travel alerts.
Wireless Intrusion Rogue APs / Network Breaches Investigating unauthorized access to local/private networks.

๐Ÿ”Ž Digital Forensics

Post-incident artifact extraction and timeline reconstruction.

Domain Description Primary Tools
Memory Analysis Cheatsheets for extracting malware, processes, and keys from RAM. Volatility, Rekall
Disk Forensics Guides for parsing NTFS artifacts, registry hives, and event logs. Autopsy, KAPE, FTK Imager
Live Response Scripts for gathering volatile data safely from a compromised host. KAPE, Custom Scripts
Tsurugi Bento Portable DFIR Windows-first field response USB, triage workflows, evidence export and verification. Bento / SyMenu, Sysinternals, imaging and hashing tools

PNWC Field-response Toolkit: JWrapper & ScreenConnect Abuse

Illustrative JWrapper remote access abuse attack path

Case-study attack-path diagram illustrating a possible remote-access software abuse chain. This is not proof that a JWrapper or ScreenConnect installation is malicious; verify the installation and client authorization using read-only triage first.

The PNWC JWrapper & ScreenConnect RAT Remediation Toolkit documents investigation and remediation of a specific remote-access-software abuse pattern observed in PNWC field cases. Use its read-only detection workflow first and preserve evidence before considering the state-changing remediation functions. A ScreenConnect installation alone is not evidence of malware; validate the installer, publisher, customer authorization, persistence mechanisms, timeline and network indicators. Verify the current IOCs and attribution independently rather than treating a dated campaign description as a current threat advisory.

Cross-reference the live-response guide for evidence acquisition, and the phishing analysis SOP for initial delivery-vector triage.

๐Ÿš€ Deployment & Operations Workflow

Building The Lab & Testing

1. Infrastructure Standup:
   โ””โ”€> Choose a SIEM (Wazuh or ELK recommended for beginners).
   โ””โ”€> Deploy the centralized log server using the guides in `/SIEM/`.

2. Telemetry Ingestion:
   โ””โ”€> Deploy Agents (Sysmon + Winlogbeat, or Wazuh Agent) to your Homelab VMs.
   โ””โ”€> Verify logs are indexing correctly in your SIEM dashboard.

3. Attack Simulation (Red -> Blue):
   โ””โ”€> Generate noise! Run an attack from your Kali machine against a target VM.
   โ””โ”€> Execute a reverse shell, run a port scan, or drop an EICAR file.

4. Threat Hunting & Analysis:
   โ””โ”€> Pivot to your SIEM. 
   โ””โ”€> Write queries to trace the attack chain (Initial Access -> Execution -> C2).
   โ””โ”€> Trigger alerts and follow the corresponding IR Playbook to "respond."

โš ๏ธ Critical Security, Privacy & Legal Warning

๐Ÿ”ด Blue Team Legal & Ethical Guidelines

โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•
                    โš ๏ธ CRITICAL WARNING โš ๏ธ
โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•

While this section focuses on DEFENSE, mishandling incident data, logs, 
and malware carries significant legal, regulatory, and operational risks.

1. DATA PRIVACY & COMPLIANCE (PII/PHI)
   โ–บ Log aggregators often capture highly sensitive data (Passwords, PII, PHI).
   โ–บ DO NOT upload sensitive organizational data to public log repositories.
   โ–บ Violating data handling procedures can breach GDPR, HIPAA, CCPA, and PCI-DSS.
   โ–บ Always anonymize or sanitize logs before sharing for educational purposes.

2. MALWARE HANDLING
   โ–บ Analyzing live malware (Phishing attachments, Ransomware binaries) is dangerous.
   โ–บ NEVER detonate malware on a production or host-connected network.
   โ–บ DO NOT upload proprietary, targeted malware to public sandboxes (e.g., VirusTotal) 
     as it alerts the attacker that they have been detected.
   โ–บ Only analyze malware in strictly isolated, host-only virtual environments.

3. CHAIN OF CUSTODY (For Professional Responders)
   โ–บ If analyzing a real-world breach that may involve law enforcement:
   โ–บ DO NOT use standard live-response scripts that overwrite volatile memory.
   โ–บ Follow strict Chain of Custody (CoC) procedures.
   โ–บ Ensure write-blockers are used for disk imaging.
   โ–บ Mishandling evidence renders it inadmissible in court.

4. EDUCATIONAL USE ONLY
   โ–บ These resources are for learning defensive security in authorized environments.
   โ–บ DO NOT use forensic tools on systems you do not own or lack explicit 
     written permission to analyze. (Deploying EDR/Forensic tools without consent 
     can be legally construed as unauthorized access/wiretapping).

โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•

๐Ÿค Contributing

We welcome contributions from SOC Analysts, Threat Hunters, and Incident Responders.

What We Accept:

  • โœ… Custom SIGMA rules or SIEM queries (Splunk SPL, KQL, Elastic Lucene).
  • โœ… DFIR cheatsheets and artifact mapping (e.g., Windows Registry persistence locations).
  • โœ… Playbooks for emerging threats.
  • โœ… Hardening configs for endpoints.

Submission Guidelines:

  1. Fork the repository.
  2. Ensure any shared logs or PCAPs are completely sanitized of real-world PII/credentials.
  3. Document prerequisites and tool versions for SIEM configurations.
  4. Submit a Pull Request with a clear description of the defensive value.

๐Ÿ“š Resources

Frameworks & Methodologies

Tools & Communities


๐Ÿ”— Quick Links

Internal Links


๐Ÿ“Š Repository Statistics

๐Ÿ“ Categories: SIEM, EDR, NSM, Forensics, Playbooks
๐Ÿ” Focus: Threat Hunting, Log Aggregation, Artifact Analysis
๐Ÿ’ป Core Platforms: Windows, Linux, ELK, Wazuh, Splunk
๐Ÿ”„ Last Updated: June 2026
๐Ÿ‘ฅ Maintained by: Pacific Northwest Computers (PNWC)
๐Ÿ“ Status: Active - Defensive Operations Ready

Related Files

  • log_agg.md - Log aggregation and SIEM feed configuration (the visibility prerequisite for all IR work)
  • network_intrusion.md - Wireless intrusion / rogue AP / plant hack IR procedure (Scenario IR-NET-001)
  • ../Documentation/wireshark.md - Wireshark filters for the PCAP analysis referenced in network_intrusion.md
  • ../Documentation/bjorn_pi.md - Bjorn Pi is exactly the kind of "plant" device described in IR-NET-001
  • ../Homelab/ - Homelab lab setup where this IR infrastructure would be deployed and tested

๐Ÿ›ก๏ธ Use These Resources Responsibly: Authorization is MANDATORY

Visibility is the foundation of security - use these tools ethically and legally.

Repository: ULTIMATE CYBERSECURITY MASTER GUIDE

Maintained by: Pacific Northwest Computers


โš ๏ธ CRITICAL: These are ATTACK TECHNIQUES - Written authorization is REQUIRED โš ๏ธ

โš ๏ธ Unauthorized use is a FEDERAL CRIME with up to 10 years imprisonment โš ๏ธ

โš ๏ธ ALWAYS obtain explicit written authorization before using any technique โš ๏ธ

โญ Star this repo if you find it useful! โญ


Master Index | Start Here | Legal Notice


๐Ÿ“‘ All Pages in Incident Response

Guides & Reference

Digital Forensics

Digital Forensics / Disks

Digital Forensics / Live Data

Digital Forensics / Memory

Endpoint Visibility

Endpoint Visibility / Linux

Endpoint Visibility / Windows

Firewalls

Honey Pot

IDS&IPS

SIEM


๐Ÿ“‚ Folder: IncidentResponse | โœ๏ธ Suggest an edit | ๐Ÿ—บ๏ธ Browse by Topic

Clone this wiki locally