Hunting for Data Staging Before Exfiltration

Overview

Before exfiltrating data, adversaries typically stage collected files in a central location (MITRE ATT&CK T1074). This involves creating archives with tools like 7-Zip, RAR, or tar, consolidating files from multiple directories, and using temporary or hidden staging directories. This skill detects staging behavior by analyzing process creation logs for archiver activity, monitoring file system events in common staging paths, and identifying anomalous file consolidation patterns.

Prerequisites

• EDR or Sysmon telemetry with process creation and file system events
• Windows Event Logs (Event ID 4688) or Sysmon Event ID 1, 11
• Python 3.8+ with standard library
• Access to process creation logs in JSON/CSV format

Steps

1. Detect Archive Tool Execution — Monitor for 7z.exe, rar.exe, tar, zip, and WinRAR process creation with compression arguments
2. Identify Staging Directories — Flag file writes to common staging locations (Recycle Bin, %TEMP%, ProgramData, hidden directories)
3. Detect Large File Consolidation — Identify patterns of multiple file reads followed by writes to a single directory
4. Monitor Sensitive Path Access — Track bulk reads from document directories, database paths, and network shares
5. Analyze Archive Metadata — Extract and analyze archive file sizes, creation times, and source paths
6. Score Staging Risk — Apply heuristic scoring based on archive size, source diversity, staging path suspicion, and timing
7. Generate Hunt Report — Produce a structured report with staging event timeline and MITRE ATT&CK mapping

Expected Output

• JSON report of detected staging events with risk scores
• Archive creation timeline with source file analysis
• MITRE ATT&CK mapping (T1074.001, T1074.002, T1560)
• Staging directory heat map showing suspicious write activity

Verification Criteria

Confirm successful execution by validating:

• [ ] All prerequisite tools and access requirements are satisfied
• [ ] Each workflow step completed without errors
• [ ] Output matches expected format and contains expected data
• [ ] No security warnings or misconfigurations detected
• [ ] Results are documented and evidence is preserved for audit

Compliance Framework Mapping

This skill supports compliance evidence collection across multiple frameworks:

• SOC 2: CC7.2 (Anomaly Detection), CC7.3 (Incident Identification)
• ISO 27001: A.12.4 (Logging & Monitoring), A.16.1 (Security Incident Management)
• NIST 800-53: SI-4 (System Monitoring), IR-4 (Incident Handling), RA-5 (Vulnerability Scanning)
• NIST CSF: DE.AE (Anomalies & Events), DE.CM (Continuous Monitoring), DE.DP (Detection Processes)

Claw GRC Tip: When this skill is executed by a registered agent, compliance evidence is automatically captured and mapped to the relevant controls in your active frameworks.

Deploying This Skill with Claw GRC

Agent Execution

Register this skill with your Claw GRC agent for automated execution:

# Install via CLI
npx claw-grc skills add hunting-for-data-staging-before-exfiltration

# Or load dynamically via MCP
grc.load_skill("hunting-for-data-staging-before-exfiltration")

Audit Trail Integration

When executed through Claw GRC, every step of this skill generates tamper-evident audit records:

• SHA-256 chain hashing ensures no step can be modified after execution
• Evidence artifacts (configs, scan results, logs) are automatically attached to relevant controls
• Trust score impact — successful execution increases your agent's trust score

Continuous Compliance

Schedule this skill for recurring execution to maintain continuous compliance posture. Claw GRC monitors for drift and alerts when re-execution is needed.