Record useful access-denial audits without copying documents
Security receives Denied entries with no action name, while application debug logs include complete document metadata. Neither source is suitable for reviewing a partner complaint.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Security logging · Data minimization · Audit access
Estimated field mix
- Security60%
- Privacy engineering40%
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 manufacturing company shares purchase-order documents with partner organizations. Buyers, partner administrators, and read-only agents use the same API. Recent support reports suggest list filters and background downloads disagree about who may see an order.
Setup prerequisites
- HTTP APIs
- Session authentication
- Tenant-scoped data access
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Record actor reference, scoped action, tenant reference, reason code, and correlation ID.
- Exclude document text, credential values, request bodies, and raw download URLs.
- Protect audit queries with a dedicated read permission and bounded date range.
Implementation constraints
- Security audit records are append-only; generic analytics must not receive sensitive audit detail.
Verification to include
- Follow an authorized denial investigation through its correlation ID.
- Attempt audit access as a partner agent and scan secret-like fixture values for absence.
Deliverables
- Minimized audit schema and investigation example
Rollout and recovery
Mirror fixture denials into the new sink and inspect redaction before enabling operator queries.
Value of the work
For the engineer: Practice authorization as a service-level invariant, including revocation timing, concurrent membership changes, and asynchronous data delivery.
For the team: Inspect a concrete record of cross-organization denial, least-privilege decisions, and access-recovery behavior using fictional partner records.
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.