Integration
SIEM export
BaseLLM sends a content-free summary of the channels you choose to your own SIEM. Export runs every 60 seconds by default, and the same request carries the same correlation ID in your SIEM and in BaseLLM.
Channels
| Channel | Contents |
|---|---|
| audit | Who made which HTTP call |
| usage | Tokens, latency and cost |
| pii | Which type of personal data was detected and what was done |
| injection | Prompt injection attempts: rule group, outcome, model scores |
| policy | Which limit or policy was triggered |
| operational_error | Application errors (ERROR) |
You can turn each channel on or off separately; all six are on by default. Info and warn logs are not sent. A failed model call doesn't appear in the usage channel; it shows up in audit with its HTTP status code.
What is sent, and what isn't
| Sent to your SIEM | Never sent to your SIEM |
|---|---|
| Time, event type, outcome | Prompts, messages and model responses |
| User / API key ID, project ID | API keys, passwords, provider keys |
| Request ID (correlation ID) | The personal data itself |
| Token counts, latency, cost, model | Policy detail fields not on the allowlist |
| Personal data: type, count, mode applied | |
| Policy: policy name, limit, amount used | |
| Error message and a short stack trace (up to 512 characters) |
Supported products and record format
| Product | Transport | Format |
|---|---|---|
| Splunk | HTTP (HEC) | JSON |
| Microsoft Sentinel | HTTP (Logs Ingestion API) | JSON |
| Google SecOps | HTTP (ingestion) | JSON |
| IBM QRadar | Syslog or REST | CEF / JSON |
| Exabeam, Securonix | REST | JSON |
| FortiSIEM | Syslog (TCP/UDP) | CEF |
| Wazuh | Syslog or Manager API | CEF / JSON |
| Security Onion | Syslog or HTTP | CEF / JSON |
{ "@timestamp": "2026-09-30T10:15:02Z",
"event": { "kind": "usage", "action": "chat.completion",
"outcome": "success" },
"correlation_id": "31a8ba07-…",
"resource": { "type": "project", "id": "…" },
"fields": { "model": "…", "inputTokens": 812,
"outputTokens": 240, "latencyMs": 1430,
"costAmount": 0.0123, "costCurrency": "USD" },
"id": "…" }
Nine products are supported, with one active destination at a time. The JSON envelope depends on the destination: Splunk {event}, Sentinel an array, REST {events:[…]}. CEF records have severity 0, so write your alert rules against field values.
Export settings
| Setting | Default | Range / note |
|---|---|---|
| SIEM_EXPORT_INTERVAL_SECONDS | 60 s | 15–3600 s; applies after restart |
| SIEM_EXPORT_BATCH_SIZE | 200 records per channel | 10–500 |
| HTTP retries | Up to 3 attempts | 0.25 s, 0.5 s, 1 s backoff |
| Timeout per request | 30 s | — |
Each run reads and sends new records from the enabled channels. If sending fails, the same records are retried on the next run: network errors and 5xx responses are retried, 4xx responses are not. An error in one channel doesn't stop the others.
License, endpoints and caveats
| Method | Path | What it does |
|---|---|---|
| GET | /admin/siem | Configuration and channel status (cursors[].lastError) |
| PUT | /admin/siem | Save; returns 400 when the license doesn't include it |
| POST | /admin/siem/test | Sends a siem.connection_test record |
The feature is enabled by the siem_export flag in the license: on in Enterprise and trial licenses, off in the Individual license; export stops when the license expires. All endpoints require the system_admin role; in the UI, go to Integrations › SIEM export. Connection details are stored encrypted (enc:v1:) and masked as *** in API responses.
- Syslog/CEF is sent over plain TCP/UDP; protect it at the network layer.
- HTTP destinations must use a valid certificate; self-signed certificates aren't supported.
- With multiple instances, the same record may be sent more than once; deduplicate on the id field in your SIEM.