Bind resolved addresses to the approved hostname policy
An approved hostname resolves to an address outside the permitted destination range.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- DNS · Egress control
Estimated field mix
- Networking50%
- Security50%
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.
Acceptance criteria
- Validate every candidate address against policy.
- Reject private or special ranges unless explicitly authorized in the lab policy.
- Pin the validated resolution for the connection.
Implementation constraints
- The local test harness explicitly maps approved loopback fixtures; production defaults remain deny.
Verification to include
- Connect using an approved simulated resolution.
- Change resolution to an unapproved range and deny the request.
Deliverables
- Resolution-aware fetch policy.
Rollout and recovery
Fail closed on resolution ambiguity or unavailable policy.
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.