Reject public exposure introduced by default configuration
An omitted access setting turns a private storage resource public.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Cloud security
Estimated field mix
- Security70%
- Cloud infrastructure30%
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 application team manages a small database, cache, and object store. Reviewers struggle to distinguish harmless configuration changes from destructive replacements.
Setup prerequisites
- Author synthetic infrastructure plans and state snapshots; use local files only and no cloud credentials.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Evaluate effective exposure including defaults.
- Identify the exact field causing exposure.
- Keep unknown defaults unresolved.
Implementation constraints
- Use explicit provider-schema fixtures rather than live provider assumptions.
Verification to include
- Detect a public-access transition.
- Keep unknown provider behavior blocked for review.
Deliverables
- Exposure policy check.
Rollout and recovery
Start with the modeled resource types; reject unsupported exposure analysis.
Value of the work
For the engineer: Practice infrastructure risk analysis, plan integrity, and least-privilege change workflows.
For the team: Give infrastructure reviewers concrete change scope and recovery consequences.
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.