Bind document import requests to tenant-owned destination policies
One tenant configures an approved host and another tenant unexpectedly inherits permission to fetch from it.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Tenant isolation · Authorization
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.
Acceptance criteria
- Resolve allowlists within the requesting tenant.
- Require authorization before creating a fetch job.
- Reject unknown policy references without disclosing other tenants' hosts.
Implementation constraints
- Store policy version with the import request.
Verification to include
- Import through the tenant's approved synthetic host.
- Reuse another tenant's policy ID and verify zero fetch calls.
Deliverables
- Scoped destination-policy service
Rollout and recovery
Deploy tenant resolution before enabling saved policies; disable import on ambiguous ownership.
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.