Hunt Server-Side Request Boundaries
Treat this card as advisory prioritization. Scope, TrafficPolicy, replay contracts, and native evidence remain authoritative.
Workflow
- Select a typed URL-fetch operation and preserve its method, identity, fields, and encoding.
- Pair an ordinary baseline with a same-shape negative control; change one URL component.
- Use
ssrf_boundary; usefile_fetch_parseronly for a typed import or parser. The SSRF specialist includes fixed internal and metadata destinations, so run it only if all are authorized. - Separate server-origin requests from redirects, reflection, validation, and caching. Preserve redacted replays, deltas, and evidence references whether or not a challenge artifact exists.
Evidence Gate
Confirm only a controlled target-origin request or protected-resource differential unexplained by
the paired control. Status, timing, DNS behavior, reflected URLs, and errors remain observations.
Keep any contract_missing result suspected rather than promoting it.
Stop Conditions
Stop without a typed sink, replay, safe comparison, or remaining policy budget. Do not add range scans or unapproved out-of-band destinations, and redact returned secrets.