返回提示词目录第 1388 页

分析网络抓包摘要与异常流量

依据抓包统计识别可疑连接与通信模式,列出合理解释、证据及后续过滤核查命令。

完整提示词

<context>
Raw captures are too large to paste, so analysts work from summaries: conversation statistics, DNS query lists, TLS server names, HTTP request lines. Those summaries hide the answer in patterns rather than single packets: connections at near-regular intervals with similar sizes (beaconing), more bytes going out than coming in (exfiltration), long random-looking subdomains or bursts of failed lookups (DNS tunnelling or generated domains), TLS to a bare IP or with a server name that does not fit the certificate, and cleartext protocols carrying credentials. Each pattern has innocent look-alikes, such as update checks, telemetry, backups and video calls, so conclusions need the evidence and the alternative side by side.
</context>

<task>
Answer this question: {{question}}

<capture_summary>
{{capture_summary}}
</capture_summary>

1. If the summary has no timestamps, hosts or byte counts relevant to the question, say what output to generate (for example conversation statistics, DNS query names, TLS handshake server names) and stop.
2. Answer first, in two or three sentences, with a confidence level.
3. Protocol overview: the protocols and their share, and anything unexpected for the network (cleartext protocols, uncommon ports, protocols on non-standard ports).
4. Notable connections: hosts and destinations worth attention, with timing, volume, direction and why each stands out.
5. Patterns, where the data supports them:
   - Beaconing: interval regularity (mean, spread, jitter), consistent request and response sizes, persistence across the capture.
   - Data transfer: outbound versus inbound byte ratio, large uploads to unusual destinations, transfers outside working hours.
   - DNS: long or high-entropy subdomains, many unique subdomains under one domain, TXT-heavy traffic, bursts of non-existent domain responses, newly seen domains.
   - TLS and HTTP: server name versus certificate mismatches, self-signed certificates, rare client fingerprints if given, unusual user agents, POST requests to bare IPs.
6. Benign explanations for each suspicious pattern and how to tell them apart.
7. Inspect next: specific display filters or tool commands phrased for common analysers (for example `dns.qry.name contains "example"`, `tls.handshake.type == 1`, `http.request.method == "POST"`, `ip.addr == 10.1.4.22`), and which host or log data to correlate (endpoint process for the connection, proxy logs, DNS server logs).
8. Before answering, check that every claim cites values present in the summary and that interval or ratio calculations are shown.
</task>

<constraints>
- You only see the summary, not the packets; never describe payload content that is not in the input.
- Do not attribute traffic to a named threat actor or malware family; describe the behaviour.
- Defang external IPs and domains in the narrative (`198.51.100[.]14`, `cdn-sync[.]example`).
- Analysis covers traffic the user is authorised to capture on their own network; do not suggest probing external hosts.
{{> output/uncertainty}}
</constraints>

<output_format>
## Answer
Two or three sentences with confidence.

## Protocol overview
Short table or bullets.

## Notable connections
Table: Source | Destination (defanged) | Protocol/port | Count | Bytes out/in | Timing | Why notable.

## Patterns
Subsections only for patterns found, each with the numbers.

## Benign explanations
Bullets paired with the suspicious pattern.

## Inspect next
Numbered list of filters, commands and correlations, each with what it would confirm.
</output_format>

可替换内容

  • {{question}}
  • {{capture_summary}}
  • {{> output/uncertainty}}
  • [.]

分类与标签

编程开发、网络抓包、流量分析、异常连接、安全排查

前往 AI 图片创作