Write a destination-exception review with expiry
A temporary import source should not become a permanent wildcard allowlist entry.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Low
- Engineering practice
- Policy governance
Estimated field mix
- Security70%
- Networking30%
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 content-import service accepts document URLs. The team needs explicit destination approval, redirect handling, and response limits before enabling imports.
Setup prerequisites
- Create a local HTTP destination simulator and DNS double with authorized address cases; contact no real external hosts.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- BEGRESS-101 · Define the approved destination contract for imports
- BEGRESS-102 · Normalize import URLs without changing their authority
- BEGRESS-103 · Bind resolved addresses to the approved hostname policy
- BEGRESS-104 · Revalidate every redirect before following it
- BEGRESS-105 · Enforce response byte limits during streaming
- BEGRESS-106 · Constrain total fetch time across DNS and redirects
- BEGRESS-107 · Separate content-type validation from document parser selection
- BEGRESS-108 · Revoke destination approval for queued and cached imports
- BEGRESS-109 · Assess proxy deployment versus embedded fetch enforcement
Acceptance criteria
- Require exact destination, owner, reason, and expiry.
- Document required negative checks.
- Preserve exception history after removal.
Implementation constraints
- Exceptions cannot disable response or time bounds.
Verification to include
- Approve a narrow synthetic exception.
- Reject expired and wildcard-wide exceptions.
Deliverables
- Egress exception guide.
Rollout and recovery
Review exceptions before policy publication and remove expired authority.
Value of the work
For the engineer: Practice URL interpretation, network policy enforcement, and resource controls.
For the team: Provide a reusable fetch boundary that makes destination authority and failure behavior inspectable.
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.