# SIEM Event Collects the unified SIEM event stream from Island Enterprise Browser: user browser telemetry (Navigation, FileDownload, Copy, Print, Screenshot, Upload) merged with admin-console actions (setting changes, integration edits, user provisioning), delivered from a single durable server-side queue. **Sync Type: Incremental** ## Description Island holds matched audit records in a server-side queue per SIEM connector. Monad consumes that queue and acknowledges each batch, which permanently removes it from Island's side. Delivery is **at-least-once**: if Monad is interrupted after records are emitted but before Island records the acknowledgement, those records arrive again on the next sync. Dedupe downstream on `id`. Browser audits and admin actions share the same queue and a common core of fields (`id`, `timestamp`, `tenantId`, `userId`, `email`, `sourceIp`). Branch on `type` (browser audit) versus `actionType` / `entityType` (admin action). ## Prerequisites 1. An Island Enterprise Browser tenant with the Management Console accessible. 2. An account with the **admin** or **system-admin** role — required to view the SIEM integration panel and generate the bearer token. 3. A **Generic SIEM Integration** with the event types you want switched on (Users Events, Admin Events, System Events). Only enabled types reach the queue. 4. Network access from Monad to `api.island.io`, where Island serves the SIEM API. ## Authentication Bearer token (**SIEM Key**) plus an **Audit ID** identifying which SIEM queue to consume. Both come from the same Generic SIEM Integration. ### The two-credential trap Island exposes two separate credential panels in the Management Console. They are not interchangeable: | Purpose | Console panel | | --- | --- | | Management pull APIs (Devices, Users, Compromised Credentials) | System Settings → Integrations → **API** | | **SIEM event queue (this input)** | System Settings → Integrations → **SIEM** → Generic SIEM Integration | **Do not paste the key from the API panel into the SIEM Key field.** It is a different credential for a different set of endpoints and fails with `401 Unauthorized`. ### Generating the SIEM Key and Audit ID 1. Log into the Island Management Console with an **admin** or **system-admin** account. 2. Navigate to **System Settings → Integrations → SIEM**. 3. Under **Generic SIEM Integration**, click **Create Generic SIEM Integration Integration** and give it a name. 4. Under **Data Pipeline Configuration**, switch on the event types to send: **Users Events**, **Admin Events** and **System Events**. 5. Click **Generate API Key** and copy the key. This is the **SIEM Key**; it may only be shown once. 6. Copy the **Audit ID**. The console doesn't label it: it's the UUID at the end of the endpoint URL the integration shows, `https://api.island.io/services/siem/api/v3/Audits/`. ## Configuration ### Settings | Setting | Type | Required | Description | | ------- | ---- | -------- | ----------- | | SIEM Key | secret (string) | Yes | The SIEM bearer token, from Console → System Settings → Integrations → SIEM → Generic SIEM Integration → Setup. **Not** the API-panel key. | | Audit ID | string | Yes | UUID identifying the SIEM queue to consume: the last segment of the endpoint URL the Generic SIEM Integration shows. | There is no cron setting on this input — it consumes the queue continuously. ## Setup Walk-through 1. In the Island Management Console, generate the **SIEM Key** and **Audit ID** as described above. 2. In Monad, create a new input of type **Island SIEM Event**. 3. Paste in the **SIEM Key** and the **Audit ID**. 4. Save the input and attach it to a pipeline. ## Backfill and Replay Guarantees The SIEM queue has **no time-range parameter** — you cannot ask for "events since X". Plan around these limits: | Question | Answer | | --- | --- | | Can I backfill events from before the Audit ID was created? | **No.** The queue only contains events generated after the SIEM connector was created in the Console. | | Can I replay a batch that was already acknowledged? | **No.** Acknowledgement permanently removes the batch from Island's queue. | | Can I pause the pipeline without losing data? | **Yes.** Un-acknowledged batches remain in the queue until Monad consumes them. | | Can I get duplicates? | **Yes**, on an interrupted sync — delivery is at-least-once. Dedupe on `id`. | | Can I run two Monad inputs against the same Audit ID? | **No.** One Audit ID = one queue = one consumer. Two consumers each see an arbitrary subset of the events. Provision a second Audit ID in the Console for a second pipeline. | Provision the Audit ID as early as possible after installing Island — data older than it is not retrievable. ## Rate limits and throughput Island publishes no explicit ceiling; Monad caps outbound calls at roughly **1 request/second** per input. Each sync keeps consuming until the queue reports empty, so a burst backlog — a phishing wave, a DLP flurry, or the first sync after enabling the connector — drains in one pass rather than one batch per interval. ## Troubleshooting ### Common Issues 1. **`401 Unauthorized`** - Almost certainly the key from **Integrations → API** was pasted into the SIEM Key field. Copy the bearer token from **Integrations → SIEM → Generic SIEM Integration → Setup** instead. - If the token was revoked or rotated in the Console, generate a new one from the same panel. 2. **`403 Forbidden`** - The account that generated the SIEM Key must have the **admin** or **system-admin** role. - Verify the Audit ID belongs to the same tenant as the SIEM Key. 3. **`404 Not Found`** - The Audit ID does not exist on this tenant — a typo in the UUID, or the SIEM connector was deleted. Re-copy it from the end of the integration's endpoint URL. 4. **The input succeeds but no records appear** - The queue may be legitimately idle. Confirm the integration's **Data Pipeline Configuration** has the event types you expect switched on; only those reach the queue. - If you just created the integration, remember there is no backfill. Generate some activity of an enabled type and re-check. 5. **Redirect error** - The SIEM API never redirects. Re-copy the SIEM Key and Audit ID from the Generic SIEM Integration. If it persists, contact Monad support. 6. **EU tenants can't connect** - Monad pulls SIEM events from `api.island.io` for every region. If an EU tenant's connection test fails with `401` or `404` even with a freshly copied SIEM Key and Audit ID, contact Monad support. ## Example A browser-audit record: ```json { "id": "0554e3ab-8a63-4d21-a1e2-9f10b9c8e7d4", "createdDate": "2025-09-09T13:29:38.000Z", "updatedDate": "2025-09-09T13:29:38.000Z", "timestamp": "2025-09-09T13:29:38.000Z", "processedDate": "2025-09-09T13:29:39.412Z", "tenantId": "acme-corp", "userId": "auth0|65f2b3c4d5e6f7a8b9c0d1e2", "userName": "jane.doe", "email": "jane.doe@acme.example", "deviceId": "9a1b2c3d-4e5f-6789-abcd-ef0123456789", "clientEventId": "b4d0f5e6-2c8a-4901-8b3c-1d2e3f4a5b6c", "type": "FileDownload", "verdict": "Blocked", "verdictReason": "DLP: matched policy 'Block source code exfiltration'", "topLevelUrl": "https://drive.example.com/folder/engineering", "submittedUrl": "https://drive.example.com/api/download?fileId=abc123", "shortTopLevelUrl": "drive.example.com", "urlWebCategories": ["Business", "File Sharing"], "urlWebReputation": 82, "saasApplicationId": "550e8400-e29b-41d4-a716-446655440000", "saasApplicationName": "Example Drive", "saasApplicationCategory": "Cloud Storage", "ruleId": "policy-dlp-source-code", "ruleName": "Block source code exfiltration", "country": "United States", "region": "California", "countryCode": "US", "sourceIp": "10.24.7.42", "publicIp": "203.0.113.17", "machineName": "JANE-MBP-14", "matchedDevicePosture": "Compliant", "matchedUserGroup": "Engineering", "osPlatform": "MacOs", "origin": "Island", "incognito": false, "isIslandPrivateAccess": false } ``` An admin-action record from the same queue: ```json { "id": "7c1d3e4f-5a6b-7c8d-9e0f-1a2b3c4d5e6f", "createdDate": "2025-09-09T14:02:11.000Z", "timestamp": "2025-09-09T14:02:11.000Z", "tenantId": "acme-corp", "userId": "auth0|11223344556677889900aabb", "email": "sysadmin@acme.example", "sourceIp": "198.51.100.7", "actionType": "Update", "actionDomain": "Integrations", "actionStatus": "Success", "entityType": "SIEMConnector", "entityId": "8f2c1e40-1234-4bcd-90ef-abcdefabcdef", "entityName": "Generic SIEM Integration", "originalValueString": "{\"enabled\":false}", "newValueString": "{\"enabled\":true}", "reason": "Enabled SIEM connector for Monad pipeline" } ``` ## Related Articles - [Island Enterprise Browser documentation](https://documentation.island.io/) ## Sync frequency By default this input polls approximately every 10 seconds, with each sync beginning after the previous one completes. A cron schedule configured on the pipeline overrides this cadence. Each sync keeps consuming until the queue reports empty, so a backlog drains in one pass instead of one batch per interval. See [Input Sync Frequency](../../guides/sync-frequency) for details.