制定威胁狩猎查询与排查计划
围绕可检验的攻击假设规划日志查询、基线分析与升级流程,输出检测候选和数据缺口。
完整提示词
<context>
A hunt looks for attacker activity that existing detections miss. Hunts that produce nothing useful usually start from a vague idea ("look for bad stuff"), discover halfway through that the needed telemetry is missing, drown in results with no baseline of what normal looks like, or end without writing anything down. A good hunt has a testable hypothesis tied to an attacker technique, checks data availability first, defines in advance what a finding looks like, and ends in durable outputs whatever the result: new detections, data gaps to fix, hardening tickets, or a documented negative.
</context>
<task>
Plan a hunt:
<hypothesis>
{{hypothesis}}
</hypothesis>
<data_sources>
{{data_sources}}
</data_sources>
Query language: {{siem}} (if empty, write readable pseudocode with field names stated). Time box: {{timebox_hours}} hours.
1. Sharpen the hypothesis into one testable statement: actor behaviour, technique (ATT&CK name, id marked `[VERIFY]` if unsure), where it would happen, and in what time window. If the input is too vague to choose a technique or a place, propose two or three candidate hypotheses and ask which to pursue, then stop.
2. Scope: systems, accounts and look-back period, limited by retention.
3. Data check: for each data source needed, say whether the input shows it is available, what fields the hunt relies on, and the gap if it is not. If a critical source is missing, say whether the hunt can still proceed and with what blind spot.
4. Hunt queries: three to six queries that move from broad to narrow, each with the question it answers, the query, the fields assumed, and the expected volume. Prefer techniques that surface rare behaviour: stacking (least frequent values across hosts), first-seen analysis, parent-child outliers, time-of-day and peer comparison.
5. Baseline and analysis: what legitimate activity will appear (software deployment, backup agents, admin scripts) and how to set it aside without hiding an attacker who imitates it.
6. Define a finding in advance: the specific observations that would count as confirmed malicious, suspicious-needs-escalation, or benign.
7. Escalation: what to do if something is found mid-hunt (stop hunting, preserve evidence, hand to incident response with the query and results).
8. Outputs: detection candidates (in plain language, ready for a rule), data gaps to fix, hardening opportunities, and how to document a negative result.
9. Check that each query uses only fields named in the data check and fits the time box; trim if not.
</task>
<constraints>
- Do not invent data sources or fields the user did not list; label assumed fields clearly.
- Queries are for the defender's own environment. Do not suggest active probing of systems outside it.
- Keep the plan within the time box; mark optional queries if it would run over.
{{> output/uncertainty}}
</constraints>
<output_format>
## Hypothesis
One sentence, then the technique and why it is plausible here.
## Scope
Bullets.
## Data check
Table: Source | Available? | Fields used | Retention | Gap.
## Hunt queries
Numbered; each with Question, Query (fenced block), Fields assumed, Expected volume.
## Baseline and analysis
Bullets.
## What a finding looks like
Three short lists: Confirmed malicious, Escalate, Benign.
## Escalation
Short numbered list.
## Outputs
Detection candidates, data gaps, hardening, documentation.
</output_format>可替换内容
- {{hypothesis}}
- {{data_sources}}
- {{siem}}
- {{timebox_hours}}
- {{> output/uncertainty}}
- [VERIFY]
分类与标签
编程开发、威胁狩猎、日志查询、安全监测、事件升级