Audit log, export & SIEM stream: how it works
The audit log shows who did what in your workspace and when, from which IP address and browser. Filter it, export it as CSV or JSON, choose how long it is kept, and send new entries to your own SIEM as signed batches.
Lesson 4 of 5 · How it works
How it works
Open «Security → Audit log». Every entry shows the time, the person, the action and the record, the IP address and the browser. Entries are part of a tamper-evident hash chain.
Filter by person, action (for example «login» or «sso.»), record type, IP address and dates. «Export Export downloads a list as a file: CSV or XLSX for Excel, or JSON for other software. Import loads records from a file into a list. More words in the glossary CSV» and «Export JSON» download what the filters show (up to 50,000 entries) after you confirm it is you; secrets in the details are hidden.
«Retention» decides how long entries are kept (forever by default, or 90 days to 7 years). Older entries are deleted once a day; the remaining chain still verifies.
«Stream to your SIEM»: enter an https endpoint and save. zmle shows a signing secret once and then posts new entries as JSON batches of up to 500, about every five minutes, with the header Zmle-Signature (HMAC-SHA256).
If your endpoint does not answer, zmle waits longer between attempts (up to an hour) and continues where it stopped, so nothing is skipped.
Where to find it
- Security → Audit log
/admin/security/audit - Security at zmle
/security
Settings that change it
- Security → Audit log → Retention
/admin/security/audit - Security → Audit log → Stream to your SIEM
/admin/security/audit
Checklist
Before you move on, check that you can:
- Open Security → Audit log
- Open Security → Audit log.
- Filter by person, action (for example login or sso.), record type, IP address and dates.
- Retention decides how long entries are kept (forever by default, or 90 days to 7 years).
- Stream to your SIEM: enter an https endpoint and save.
Tips and common mistakes
- Use «Send a test batch» after saving the endpoint: your receiver should check the signature and refuse batches older than five minutes.
- A new endpoint starts with the entries written from then on; export the history with «Export JSON» if your SIEM needs it.
- Only a super admin or the workspace owner can change retention or the stream; viewing needs the security view permission.