AGENT SKILL

hunting-for-data-exfiltration-indicators

Hunt for data exfiltration by analyzing Zeek and Suricata network telemetry for unusual data flows, DNS tunneling via large/frequent TXT queries, uploads to personal cloud storage, and encrypted-channel abuse, correlated against threat intel on destination domains. Use when hunting for data theft in a compromised environment, investigating unusual outbound data volumes, or determining what data was stolen during incident response.

License 许可
Apache-2.0
最近更新
2026-09-11
Stars
★ 0
Forks
0

01 前言 Front Matter

name
hunting-for-data-exfiltration-indicators
tags
[ "threat-hunting", "mitre-attack", "data-exfiltration", "dlp", "network-analysis", "proactive-detection" ]
author
mahipal
domain
cybersecurity
license
Apache-2.0
version
1.0
nist_csf
[ "DE.CM-01", "DE.AE-02", "DE.AE-07", "ID.RA-05" ]
subdomain
threat-hunting
description
Hunt for data exfiltration by analyzing Zeek and Suricata network telemetry for unusual data flows, DNS tunneling via large/frequent TXT queries, uploads to personal cloud storage, and encrypted-channel abuse, correlated against threat intel on destination domains. Use when hunting for data theft in a compromised environment, investigating unusual outbound data volumes, or determining what data was stolen during incident response.
nist_ai_rmf
[ "MEASURE-2.7", "MAP-5.1", "MANAGE-2.4" ]
mitre_attack
[ "T1046", "T1057", "T1082", "T1083", "T1048" ]
atlas_techniques
[ "AML.T0024", "AML.T0056" ]
d3fend_techniques
[ "File Metadata Consistency Validation", "Certificate Analysis", "Application Protocol Command Analysis", "Content Format Conversion", "File Content Analysis" ]

02 资源文件 7

03 SKILL.md 正文

Hunting for Data Exfiltration Indicators

When to Use

  • When hunting for data theft in compromised environments
  • After detecting unusual outbound data volumes or patterns
  • When investigating potential insider threat data theft
  • During incident response to determine what data was stolen
  • When threat intel indicates data exfiltration campaigns targeting your sector

Prerequisites

  • Network proxy/firewall logs with byte-level data transfer metrics
  • DLP solution or CASB with cloud upload visibility
  • DNS query logs for DNS exfiltration detection
  • Email gateway logs for attachment monitoring
  • SIEM with data volume anomaly detection capabilities

Workflow

  1. Define Exfiltration Channels: Identify potential channels (HTTP/S uploads, DNS tunneling, email attachments, cloud storage, removable media, encrypted protocols).
  2. Baseline Normal Data Flows: Establish baseline outbound data transfer volumes per user, host, and destination over a 30-day window.
  3. Detect Volume Anomalies: Identify hosts or users transferring significantly more data than baseline to external destinations.
  4. Analyze Transfer Destinations: Check destination domains/IPs against threat intel, identify newly registered domains, personal cloud storage, and foreign infrastructure.
  5. Inspect Protocol Abuse: Look for DNS tunneling (large/frequent TXT queries), ICMP tunneling, or data hidden in allowed protocols.
  6. Correlate with File Access: Link exfiltration indicators to file access events on sensitive file shares, databases, or repositories.
  7. Report and Contain: Document findings with evidence, estimate data exposure, and recommend containment actions.

Key Concepts

Concept Description
T1041 Exfiltration Over C2 Channel
T1048 Exfiltration Over Alternative Protocol
T1048.001 Exfiltration Over Symmetric Encrypted Non-C2
T1048.002 Exfiltration Over Asymmetric Encrypted Non-C2
T1048.003 Exfiltration Over Unencrypted/Obfuscated Non-C2
T1567 Exfiltration Over Web Service
T1567.002 Exfiltration to Cloud Storage
T1052 Exfiltration Over Physical Medium
T1029 Scheduled Transfer
T1030 Data Transfer Size Limits (staging)
T1537 Transfer Data to Cloud Account
T1020 Automated Exfiltration

Tools & Systems

Tool Purpose
Splunk SIEM for data volume analysis and SPL queries
Zeek Network metadata for data flow analysis
Microsoft Defender for Cloud Apps CASB for cloud exfiltration
Netskope Cloud DLP and exfiltration detection
Suricata Network IDS for protocol anomaly detection
RITA DNS exfiltration and beacon detection
ExtraHop Network traffic analysis for data flow

Common Scenarios

  1. Cloud Storage Exfiltration: User uploads sensitive documents to personal Google Drive or Dropbox via browser.
  2. DNS Tunneling: Malware exfiltrates data encoded in DNS subdomain queries to attacker-controlled nameserver.
  3. HTTPS Upload: Compromised system POSTs large data blobs to C2 server over encrypted HTTPS.
  4. Email Attachment Exfiltration: Insider forwards sensitive documents to personal email accounts.
  5. Staging and Compression: Adversary stages data in compressed archives before slow exfiltration to avoid detection.

Output Format

Hunt ID: TH-EXFIL-[DATE]-[SEQ]
Exfiltration Channel: [HTTP/DNS/Email/Cloud/USB]
Source: [Host/User]
Destination: [Domain/IP/Service]
Data Volume: [Bytes/MB/GB]
Time Period: [Start - End]
Protocol: [HTTPS/DNS/SMTP/SMB]
Files Involved: [Count/Types]
Risk Level: [Critical/High/Medium/Low]
Confidence: [High/Medium/Low]

04 同仓库更多 Skills

NeelakshSaxena
NeelakshSaxena/Vayu

runpodctl

Runpod CLI for managing GPU/CPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send/receive). Use for terminal/CI/scripting, Hub browse/deploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod

Start here for any Runpod task — running GPU/CPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-usage

How Runpod works and how to work it — pods vs serverless, GPU/VRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv/apt). Use to answer "how does X work", "which GPU", "how do I build a container", or "how do I stand up a workload on a pod". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-templates

Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says "run <X> on a pod" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-migrate

Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-mcp

Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU/CPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.

★ 0