Re: [I] Document and complete a supported audit trail for regulated deployments [polaris]

["richiebachala (via GitHub)" <gi...@apache.org>]

richiebachala commented on issue #5561:
URL: https://github.com/apache/polaris/issues/5561#issuecomment-6105398644

   Thanks for the detailed write-up. I checked several of the gaps against current `main` and they hold:
   
   - `InMemoryBufferEventListener.flush` retries 5 times, then `onFlushError` logs and discards the batch.
   - Authorization denials surface as `ForbiddenException` from `PolarisAuthorizerImpl` / `AuthorizationDecision`; there is no event type for them, so a denied `loadTable` emits `BEFORE_LOAD_TABLE` only.
   - Nothing in `service/auth` dispatches events, so authentication failures produce none.
   
   The architecture questions (durable delivery, fail-closed, authn/authz event types) need a dev-list decision, so I won't touch those here.
   
   The first item, "no documented path", can be partly addressed now without deciding anything: a `managing-security` docs page that states what is recorded today, what is not, the delivery semantics as they currently are (best-effort, bounded backlog drops, buffered events lost on abrupt termination), that the `events` table is not a compliance store, and how to correlate with CloudTrail via `SESSION_TAGS_IN_SUBSCOPED_CREDENTIAL`. It would describe current behaviour only and be updated as the list makes decisions.
   
   Would a PR like that be welcome as a first step? Happy to adjust scope.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@polaris.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org