Appearance
SIEM Configuration
This guide walks administrators through setting up, configuring, and managing SIEM integrations in GhostAI.
Prerequisites
- Plan: Enterprise subscription required
- Role: Organization
adminorownerrole - SIEM access: Admin credentials for your target SIEM platform to create ingest endpoints and API tokens
Setup Wizard
GhostAI provides a guided setup wizard that walks you through SIEM integration configuration step by step.
Step 1: Choose Your SIEM
- Navigate to Admin Dashboard → SIEM tab
- Click New Integration
- Browse the list of 16 supported SIEMs or select Custom for unlisted platforms
- Each preset shows: SIEM name, logo, default output format, and a brief description
TIP
If your SIEM isn't listed, choose Custom and configure the endpoint URL, authentication, and output format manually.
Step 2: Name Your Integration
Give your integration a descriptive name (e.g., "Production Splunk", "Sentinel – Security Team"). You can have multiple integrations per SIEM if you need to send events to different indexes or workspaces.
Step 3: Configure Delivery
Choose your delivery method and configure the connection:
Webhook Push (Recommended)
| Field | Description | Default |
|---|---|---|
| Endpoint URL | Your SIEM's ingest endpoint URL | Preset-specific |
| Authentication type | bearer, api_key_header, basic, or custom | Preset-specific |
| Auth value | Token, API key, or base64 credentials | — |
| Custom headers | Additional HTTP headers (JSON object) | {} |
| Output format | JSON, CEF, LEEF, Splunk HEC, Sentinel, or OCSF | Preset default |
Pull API
For pull-based ingestion, no endpoint configuration is needed — GhostAI generates an HMAC token that your SIEM uses to poll events.
- Select Pull as the delivery type
- Copy the generated pull API token
- Configure your SIEM to poll
GET /api/admin/siem/pullwith theAuthorization: Bearer <token>header
Step 4: Configure Event Filters
Control which events are sent to your SIEM:
| Filter | Options |
|---|---|
| Categories | Select one or more: authentication, pii_detection, file_processing, admin_actions, chat_model, policy_config, system, compliance |
| Severity minimum | Only send events at or above: informational, low, medium, high, critical |
| Specific event types | Include or exclude individual event types from the catalog |
TIP
Start with all categories enabled and refine based on your SIEM's ingestion volume and cost. Use the Volume Estimate tool to preview expected event rates before enabling.
Step 5: Configure Minimization Policy
Choose how much detail appears in SIEM events:
| Policy | Description | When to Use |
|---|---|---|
| Standard | User IDs hashed, IPs truncated, email local parts masked | Default — balances visibility with privacy |
| Aggressive | Only event type, timestamp, org ID, and aggregate metrics retained | When SIEM is accessible to a broad audience |
| None | Full event fidelity with all fields | When SIEM is in the same security boundary as GhostAI |
Step 6: Configure Batch Settings
| Setting | Description | Default | Range |
|---|---|---|---|
| Batch size | Events per delivery batch | 100 | 1–1,000 |
| Flush interval | Maximum seconds between deliveries | 5 | 1–60 |
Smaller batches and shorter intervals reduce latency but increase HTTP request volume. For high-volume deployments, larger batches are more efficient.
Step 7: Test and Enable
- Click Send Test Event to deliver a sample event to your SIEM
- Verify the event appears in your SIEM's event viewer
- Optionally, run a Validation Burst (sends multiple event types) to verify format compatibility
- Click Enable to start streaming events
Configuration Options
Event Enrichment
Add custom key-value pairs to every event envelope:
json
{
"environment": "production",
"data_classification": "confidential",
"team": "security-operations"
}Set via the Custom Enrichment field in integration settings.
Multiple Integrations
You can create multiple SIEM integrations for the same organization:
- Send different event categories to different SIEM indexes
- Forward to both a primary and backup SIEM
- Use the Clone feature to duplicate an existing integration as a starting point
Integration Lifecycle
| Action | Effect |
|---|---|
| Enable | Start streaming events |
| Disable | Pause delivery; events are not buffered during downtime |
| Clone | Create a copy with a new name for A/B testing or migration |
| Delete | Permanently remove the integration and its delivery history |
Testing and Validation
Test Event
Send a single test event to verify connectivity:
- Navigate to the integration detail page
- Click Send Test Event
- Check your SIEM for an event with type
system.test_event
Validation Burst
Send a burst of events covering multiple types to verify format parsing:
- Click Validation Burst on the integration detail page
- GhostAI sends representative events from each enabled category
- Verify events parse correctly in your SIEM's search interface
Event Preview
Preview how events will look in the configured format without sending them:
- Navigate to Preview on the integration detail page
- Browse sample events in the configured output format
- Adjust format or enrichment settings if needed
Health Monitoring
Health Dashboard
Each integration has a health dashboard showing:
- Delivery success rate — Percentage of batches delivered successfully (target: >99.5%)
- Latency — p50, p95, p99 delivery latency
- Error rate — Failed deliveries over time with HTTP status breakdown
- Events delivered — Total and per-hour event counts
- Last successful delivery — Timestamp of the most recent successful batch
Health Score
A composite score (0–100) based on:
| Factor | Weight |
|---|---|
| Delivery success rate | 40% |
| Average latency | 20% |
| Error trend (improving/worsening) | 20% |
| Time since last success | 20% |
Gap Detection
GhostAI tracks sequence numbers per organization. The gap detection feature identifies:
- Missing sequence numbers (events that may have been lost)
- Duplicate deliveries
- Sequence resets
Access via Health → Gaps on the integration detail page.
Reconciliation
Compare delivered event counts against expected counts for a time range:
- Navigate to Health → Reconciliation
- Select a date range
- View expected vs delivered counts, broken down by event category
- Investigate discrepancies
Credential Rotation
Rotate Webhook Credentials
Rotate the authentication token used for webhook delivery without downtime:
- Navigate to the integration detail page
- Click Rotate Credentials
- Enter the new authentication value
- GhostAI immediately starts using the new credentials for subsequent deliveries
WARNING
Ensure your SIEM accepts the new credentials before rotating. GhostAI does not fall back to old credentials if the new ones fail.
Rotate Pull API Token
Generate a new HMAC token for the pull API:
- Navigate to the integration detail page
- Click Rotate Pull Token
- Copy the new token and update your SIEM's polling configuration
- The old token is immediately invalidated
Backfill
Replay historical events for a specific time range:
- Navigate to the integration detail page
- Click Backfill
- Enter start and end timestamps (ISO 8601)
- GhostAI replays events from the audit log through the integration's delivery pipeline
TIP
Backfill is useful when setting up a new SIEM integration to populate it with historical data, or when recovering from a delivery outage.
Content Packs
Each SIEM preset includes a downloadable content pack with:
- Dashboards — Pre-built visualizations for GhostAI events
- Saved searches — Common investigation queries
- Detection rules — Alert conditions for suspicious patterns
- Field mappings — Maps GhostAI event fields to your SIEM's data model
Download via Content Pack on the integration detail page, or programmatically via GET /api/admin/siem/content-packs/{preset_id}.
Troubleshooting
Events Not Appearing in SIEM
- Check the Health Dashboard for delivery errors
- Verify the endpoint URL is correct and reachable from GhostAI's network
- Send a Test Event and check the HTTP response status
- Verify authentication credentials are valid
- Check your SIEM's ingest logs for parsing errors
HTTP 401/403 Errors
- Verify the authentication value (token, API key) is correct
- Check that the token has sufficient permissions for the SIEM's ingest API
- Some SIEMs require specific scopes or roles — consult the SIEM-specific error remediation advice in the integration settings
HTTP 429 (Rate Limit)
- Increase the batch size to reduce the number of HTTP requests
- Increase the flush interval to space out deliveries
- Check your SIEM's ingestion rate limits and request a limit increase if needed
Events Missing Fields
- Verify the output format matches your SIEM's expected format
- Check the minimization policy — aggressive mode strips most fields
- Use Event Preview to inspect the exact payload being sent
Hash Chain Gaps
- Check the Gap Detection page for missing sequence numbers
- Gaps during integration downtime (disabled period) are expected
- Use Backfill to replay events for the gap period
- Use Reconciliation to verify delivered vs expected counts
High Delivery Latency
- Check network connectivity between GhostAI and your SIEM endpoint
- Reduce batch size for faster per-batch delivery
- Verify your SIEM's ingest endpoint is not overloaded
- Consider a SIEM endpoint in the same cloud region as your GhostAI deployment