Validate document type from bytes before publishing the import
A remote server labels an executable-looking payload as text and the importer publishes it under a trusted document type.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Content validation · Untrusted data
Estimated field mix
- Security80%
- Backend20%
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
Acceptance criteria
- Allow a declared finite set of document formats.
- Check supported signatures and parser outcomes against claimed type.
- Keep mismatched or malformed content quarantined.
Implementation constraints
- Do not execute imported content or trust file extensions.
Verification to include
- Import valid synthetic text and supported document bytes.
- Mismatch content type and bytes and verify no published object.
Deliverables
- Format gate and mismatch cases
Rollout and recovery
Gate new imports before publication; retain quarantined bytes under restricted retention.
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.