SIEM streaming for the audit log
EvenTier streams its audit log, both the change log and the sign-in and security events, to your security information and event management (SIEM) system. Events arrive as HMAC-signed HTTPS POSTs, or your SIEM polls a pull API that returns NDJSON.
- Set up in
- Admin → Settings → Organization settings → SIEM export
- Who can set it up
- An administrator with the Manage settings permission
- Plans
- Every plan
Changes and security events in one stream
The stream carries both tabs of Admin → Audit logs, Changes and Security events. Change events (kind audit) record changes to requests, people, roles and settings, with the actor and the before and after values. Security events (kind security_audit) cover sign-ins and failed sign-ins, multi-factor authentication (MFA), lockouts, password changes, API key use, refused access and EvenTier staff access, each with its outcome and reason.
- Both delivery methods use the same event IDs, so a consumer that switches methods can skip duplicates
- Security events for EvenTier staff access leave out the source IP and user agent
Signed webhook delivery
Add a webhook subscription with your HTTPS endpoint, and EvenTier POSTs each event to it as JSON: {"event": {...}}. The X-EvenTier-Signature header carries a timestamp and an HMAC-SHA256 signature in the same format as EvenTier's webhooks, so your receiver can check both.
- Failed deliveries are retried with exponential backoff. A retry goes only to subscriptions that have not yet received the event
- Each subscription shows its last delivery and its last error
- The URL must use HTTPS and resolve to a public address. Redirects are not followed
Pull API
Your SIEM polls GET /api/audit/stream with a pull-API token. Each response is NDJSON, one event per line in time order, and its X-EvenTier-Next-Cursor header holds the cursor for the next poll.
- Start from a point in time with ?since=<ISO 8601 time>
- Set ?limit= for up to 1,000 events per response. The default is 200
- A cursor marks a position in time, so it keeps working after retention deletes old events. A cursor that cannot be resumed gets a 410 response with the code CURSOR_EXPIRED
- To rotate a token without a gap, generate the new one before revoking the old one
Keep events longer than the workspace does
On EvenTier Cloud, the change log is kept for 30 days on Standard and 7 days on Free, or longer with an audit retention add-on. Sign-in and security events are kept for 400 days. Streaming them to your SIEM keeps a copy for as long as your own policy requires.
Set up SIEM streaming
- 01
Open the SIEM export tab
The tab holds webhook subscriptions and pull-API tokens. Use either one, or both.
- Where:
- Admin → Settings → Organization settings → SIEM export
- Permission:
- Administrator with Manage settings
- 02
Add a webhook subscription
Enter a name and your collector's HTTPS URL, then choose Create. Copy the signing secret right away. It is not shown again.
- 03
Verify each delivery
Read t and v1 from the X-EvenTier-Signature header. Compute an HMAC-SHA256 of <t>.<raw body> with the signing secret, and compare its hex digest with v1 in constant time. Reject the request if they differ, or if t is more than five minutes from your clock.
- 04
Or generate a pull-API token
Under Pull-API tokens, add a label, choose Generate and copy the token. Point your SIEM at the endpoint shown on the tab, with the header Authorization: Bearer <token>. On each poll, pass the previous response's X-EvenTier-Next-Cursor back as ?cursor=.
- 05
Check that events arrive
Each subscription shows its last delivery and last error, and each token shows when it was last used. Turn a subscription off or revoke a token from the same tab.
Data flow
EvenTier sends events out and reads nothing from your SIEM. Webhook deliveries go only to the HTTPS URL you set, and the pull API answers only requests that carry a valid token for your workspace.
Each change event
- Kind audit, an ID and the time
- The action, the actor and the record it changed
- Before and after values, the source IP and the user agent
Each security event
- Kind security_audit, an ID and the time
- The action, its outcome and the reason
- The actor type (user, EvenTier staff or system), the request method and path, and for sign-ins, the email entered
Stored by EvenTier
- Webhook signing secrets, encrypted at rest
- Pull-API tokens, stored as hashes
- Each subscription's last delivery and last error
Questions about SIEM streaming
- Should I use the webhook or the pull API?
- The webhook pushes each event to an HTTPS endpoint shortly after it is recorded. The pull API needs only outbound access from your SIEM, and it resumes from its cursor after an outage.
- Can the webhook reach a collector on a private network?
- No. A webhook URL must resolve to a public address. A SIEM inside your network can poll the pull API instead.
- Is there a packaged app for Splunk, Sentinel or Datadog?
- No. Any collector that can receive an HTTPS POST or poll an HTTPS endpoint can use the stream, since both methods use plain HTTPS and JSON.
Related integrations
- OktaSAML or OIDC sign-in, with SCIM provisioning and group push.
- Microsoft Entra IDSAML or OIDC sign-in, SCIM provisioning, or scheduled directory sync with profile photos.
- SlackRequest updates in a channel, one thread per request, and thread replies added to the request.
- All integrationsIdentity, chat, migration, SIEM, the REST API and signed webhooks.
Get notified when signup opens.
EvenTier is in private early access. Leave your work email and we will let you know when you can create a workspace.
No card. We use your email only for your early-access invite and launch news. Privacy Policy