agentleFS
lza6lza6/claw-code-tingfeng/skills/reverse/threat-hunting/SKILL.md

threat-hunting

Skill5 starsChanged 15 days agoMITView on GitHub

Use for blue-team threat hunting, detection engineering with Sigma/YARA, SIEM query design, and incident detection validation.

12 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use web-pentest, incident-triage and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • samklee1Skill

    web-pentest

    Orchestrates authorized web app pentesting on Kali Linux using Opus sub-agents with difficulty-aware planning (TDA/EGATS), browser-first exploration, iterative verification, two-layer review (per-sub-agent + phase-level), optional cross-model gap audit (GPT/codex via codex-plugin-cc), and enforced KB updates. Trigger on: pentesting, penetration testing, web app security assessment, vulnerability assessment, OWASP testing, PTES, attack surface mapping, API security testing, pentest reporting, or 'help me test this app'. NOT for network-only pentesting, malware analysis, reverse engineering, or CTFs.

    Also in 4 projects that use this

  • testified-ossSkill

    incident-triage

    Triage production incidents with severity assessment, root cause hypothesis, impact analysis, and escalation recommendations. Use when analyzing outages, errors, or production issues.

    Also in 3 projects that use this

  • msewellSkill

    threat-modeling

    Produces structured threat models for software systems using STRIDE on data flow diagrams. Generates DFDs with trust boundaries, identifies threats per element, scores risks, and defines concrete mitigations. Outputs a complete threat model Markdown document through phased, interactive delivery. Use when threat modeling a system, analyzing security threats, identifying attack surfaces, performing STRIDE analysis, assessing security risks in architecture, creating a threat model document, or when the user mentions threat model, attack surface, trust boundaries, STRIDE, or security risk analysis.

    Also in 3 projects that use this

The file

Files
SKILL.md

Threat Hunting & Detection Engineering

ACTION REQUIRED(读完后立刻执行)

  1. NOW: 确认蓝队/狩猎授权与数据源范围(SIEM、EDR 导出)
  2. NOW: 明确假说(hypothesis)再查数,避免无脑刷告警
  3. NEXT: 工具与数据接入方式
  4. ACT: 假说 → 查询 → 验证 → 规则化

适用场景

  • 威胁狩猎(hypothesis-driven)
  • Sigma / YARA 检测工程
  • 告警调优、误报分析
  • 与 malware-analysis/:样本侧 IOC → 本 skill 落地检测
  • 与 digital-forensics/:案件伪影 → 横向狩猎

工作流

1. 建假说

例:攻击者用 living-off-the-land 做横向
→ 数据源:Sysmon 1/3/10、Windows Security 4624/4648
→ 成功标准:发现异常父进程或罕见账户日志源

2. 查询与堆叠

□ 基线:正常管理员行为时段与主机
□ 异常:新服务、编码 PowerShell、异常出站
□ 关联:同账号多主机短时登录

3. 规则化

# Sigma 骨架见 malware-analysis;本 skill 强调:
# - 误报面
# - 数据源字段映射
# - 响应 playbook 链接

4. 验证

□ 原子测试(Atomic Red Team)仅在授权实验室
□ 回放历史日志验证召回

工具链

工具用途
Sigma CLI / sigmac规则转换
YARA文件/内存
SIEM(ELK/Splunk 等)查询
osquery端点狩猎
Atomic Red Team检测验证(实验室)

参考

  • references/hunting-loop.md
  • ../malware-analysis/references/yara-sigma-rules.md
  • ../digital-forensics/

路由上下文

上游: MASTER R27 下游: 确认入侵 → forensics;恶意样本 → malware-analysis MUST NOT: 在无授权生产环境跑攻击模拟

任务完成自检

  • 是否有明确假说与结论?
  • 规则是否注明误报与数据源?
  • Checklist?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.