mirror of
https://github.com/suitenumerique/meet.git
synced 2026-10-08 14:32:32 +00:00
briquet
22a05207dc
Add a core.audit package emitting one Elastic Common Schema JSON line per security-relevant action on a dedicated "audit" logger. Only lasuite.* and entity.target.raw.* extends on ECS core fields. Each event names the data stream it belongs to (data_stream.*, event.dataset) and carries a unique event.id. The audit logs reads the actor, auth method, tenant and network fields from the request it is given, else from the request being served, which AuditLogMiddleware keeps in a context variable so that a service needs no request argument. A person is identified by primary key, OIDC sub when the account has one and email domain, with its privileges as user.roles; an internal peer calling the backend by service.origin.name. The tenant is the application client id, else that domain. The client IP is DRF's throttle ident, which now honours a NUM_PROXIES setting. The middleware also replaces the inbound X-Request-ID with a fresh id, unless REQUEST_ID_TRUST_HEADER says the ingress overwrites it, and echoes it in the response and the gunicorn access log. Audit events carry it as http.request.id, next to the client's user agent. An action is defined with a dotted name with its default ECS category and types, validated at import against the types ECS expects in that category, so a call site only names what was attempted. A category or types given to audit.log win over them, and a bare dotted name is accepted too. Meet declares all of the events core/auditing.py: - audit.register lists the fields describing a model as a target, an ECS entity.target, and its ECS entity type. Every target carries its model name and primary key, so an unregistered one is still identified, and a user target its OIDC sub. - audit.register_auth_method names the lasuite.auth.method of a DRF authentication class AuditViewMixin audits every response of the CRUD actions a view maps in audit_actions, and of the extra actions naming theirs with @action(audit_action=...), from finalize_response: the outcome, reason and status come from the response. An exception DRF does not handle is recorded as an internal error before it propagates. The core.audit app also records Django's login, failed login and logout signals.