Loading...
Loading...
Browse 4 real-world technical and behavioral interview questions about Audit logging. Review scenarios, edge cases, and architectural best practices.
The damage is fixed before the leak by three earlier decisions: whether the token can be revoked and how fast that takes effect, how narrowly it was scoped, and whether your audit trail can attribute actions to that specific credential rather than only to the tenant.
Permission data is as privileged as the code that reads it, so a bulk write to it needs the same review, staged rollout and reversibility as a deploy. Derive grants from a source of truth rather than stamping them, assert tenant invariants continuously, and know how long a cached decision keeps the mistake alive.
You do not delete first. Erasure is a qualified right that yields where other law requires retention, so you triage each dataset by its lawful basis, erase what has no basis to be kept, suppress and restrict what must be retained, and put the residual judgement to legal and records management.
Role-based access permits this by design, so the control cannot be authorisation alone. You need a recorded relationship between clinician and patient, a break-glass path that costs something to use, read events in the audit log, and someone whose job is to review the exceptions.