Build a regression matrix for document-fetch trust-boundary failures
The fetcher has individual guards, but a client upgrade could bypass a guard only when redirects, DNS and retries combine.
- Focused work estimate
- 5h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Security testing · Boundary analysis
Estimated field mix
- Security50%
- Quality engineering30%
- Networking20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional knowledge service imports documents from customer-entered URLs. The importer follows redirects and trusts response metadata too broadly.
Setup prerequisites
- Build a local fetch adapter and controlled HTTP test servers.
- Use synthetic documents and deny network access outside the test allowlist.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- AFETCH-101 · Accept only explicitly supported document URL schemes
- AFETCH-102 · Bind document import requests to tenant-owned destination policies
- AFETCH-103 · Reject private and special-use destination addresses before connection
- AFETCH-104 · Revalidate every document redirect before following it
- AFETCH-105 · Enforce byte and time limits while streaming imported documents
- AFETCH-106 · Validate document type from bytes before publishing the import
Acceptance criteria
- Cover composed resolver, redirect, size and cancellation cases.
- Assert forbidden connection attempts and publication calls remain zero.
- Record expected failure codes without claiming universal attack coverage.
Implementation constraints
- All network behavior runs through local controlled adapters.
Verification to include
- Run an allowed redirected import through the complete pipeline.
- Combine redirect with resolution change and oversized body; stop at the earliest applicable guard.
Deliverables
- Adversarial fixture matrix and regression command
Rollout and recovery
Require the matrix for client upgrades; pin the last passing client revision if failures appear.
Value of the work
For the engineer: Practice defensive URL handling and bounded untrusted-input processing.
For the team: Review whether integrations can import content without expanding infrastructure access.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.