Verify tenant constraints through a least-privilege database writer
Application tests pass, but direct SQL imports use a role that can bypass expected safeguards.
- Focused work estimate
- 5h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Database permissions · Defense in depth
Estimated field mix
- Database engineering50%
- 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 case-management application filters most requests correctly, but imports and background commands can connect a case to another organization's project or assignee.
Setup prerequisites
- Create two synthetic organizations with overlapping display names.
- Use repository-level authorization and migration-backed constraints.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- ATENANT-101 · Map tenant ownership for case-management entities
- ATENANT-102 · Add composite uniqueness for tenant-owned relationship targets
- ATENANT-103 · Reject null organization scope in protected repository methods
- ATENANT-104 · Enforce same-organization case-to-project references with a foreign key
- ATENANT-105 · Keep case-comment inserts scoped during concurrent parent changes
- ATENANT-106 · Make bulk case imports validate every tenant relationship before commit
- ATENANT-107 · Carry tenant identity through background case-processing commands
- ATENANT-108 · Find legacy cross-tenant references without exposing case contents
Acceptance criteria
- Inventory grants for the application and import roles.
- Verify ordinary writers cannot disable constraints or change schema.
- Run same-tenant and cross-tenant write checks under the actual limited role.
Implementation constraints
- Use disposable local roles; do not alter production permissions.
Verification to include
- Write a valid relationship through the limited import role.
- Attempt cross-tenant insertion and constraint disabling and verify both are denied.
Deliverables
- Role/grant verification and direct-write tests
Rollout and recovery
Apply the limited role in the local import path; stop imports if required checks are bypassable.
Value of the work
For the engineer: Practice tenant-aware keys, foreign keys and direct-write denial tests.
For the team: Review defense in depth for data isolation across ordinary and privileged writers.
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.