Island Browser Integration for Elastic

Version 1.6.1 (View all)
Managed integration release status GA
Subscription level
What's this?
Basic
Developed by
What's this?
Elastic
Ingestion method(s) API
Minimum Kibana version(s) 9.1.5
9.0.8
8.19.5
8.18.8
Important - Managed integrations on Elastic Cloud Hosted

You can use this integration as an Elastic Managed integration on Elastic Cloud Hosted deployments running this version or later.

Island reimagines what the browser can be. By taking in the needs of the enterprise, Island delivers a dramatic positive impact on every layer of cybersecurity and all other functions of IT, while improving the end-user experience and productivity. Leveraging the open-source Chromium project that all major browsers are based on, Island provides fine-grain policy control over every facet of a user’s interaction with a web application giving the enterprise limitless visibility, control, and compliance with their most critical applications. As a result, Island can serve as the platform for the future of productive and secured work.

The Island Browser integration for Elastic allows you to collect logs using Island Browser API, then visualise the data in Kibana.

The Island Browser integration is compatible with v1 version of Island Browser API.

This integration periodically queries the Island Browser API to retrieve details for devices, users, and compromised credentials, and to collect SIEM events.

The SIEM Events data stream collects events through the Island SIEM integration. It supports three audit types: user audits, admin audits, and system audits.

The separate Audit and Admin Actions data streams are deprecated. New deployments should use SIEM Events instead.

This integration collects log messages of the following types:

  • SIEM Events: Collects user audits, admin audits, and system audits through the Island SIEM integration.
  • Admin Actions (deprecated): Collects all admin actions from the Island Browser via Admin Actions API endpoint. Use SIEM Events instead.
  • Audit (deprecated): Collects all timeline audits from the Island Browser via Audit API endpoint. Use SIEM Events instead.
  • Compromised Credential: Collects a list of all compromised credentials from the Island Browser via Compromised Credential API endpoint.
  • Device: Collects a list of all devices from the Island Browser via Device API endpoint.
  • User: Collects all the users from the Island Browser via User API endpoint.

Integrating Island Browser User, Device, Audit, Admin Actions, and Compromised Credential endpoint data with Elastic SIEM provides unified visibility into identity activity, device posture, account exposure, and security events across the environment. This integration enables analysts to correlate user behavior, device health, and credential risks within a single view, strengthening both detection and response capabilities.

Dashboards track total and active users, login trends, and group distributions, alongside device insights such as active, archived, and jailbroken states, OS platform distribution, policy updates, browser update status, Windows license status, and MDM provider compliance. Compromised Credential visualizations highlight account risks with timelines of exposed records, unresolved credential counts, breach source breakdowns, and distributions by status. Additional charts surface top impacted domains and most affected users, enabling security teams to quickly assess exposure, prioritize remediation, and mitigate identity-based threats.

Audit dashboards further enhance oversight by showing event activity over time, verdicts and reasons, top rules, users, source IPs, event types, geographic distributions, and compatibility modes. Saved searches and tables consolidate essential attributes—including verified emails, device and host IDs, IPs, MACs, users, and organizations—adding valuable investigative context. The Admin Actions dashboard shows activity over time, breaks down events by action domain, type, and status, and includes a table of the top source IPs. Together, these insights allow organizations to monitor user behavior, track device health, detect compromised accounts, analyze audit activity, and strengthen compliance, identity management, and endpoint security oversight.

This integration installs Elastic latest transforms. For more details, check the Transform setup and requirements.

Required permissions: The API key must belong to an Island account with administrator access (Admin or System Admin).

Authentication uses an API key as the required credential. The account used to create the key must also have permission to generate and manage API keys.

  1. Log in to Island Browser Management Console as an administrator (Admin or System Admin).
  2. From the Island Management Console, navigate to Modules > Platform Settings > System Settings > Integrations > API.
  3. Click + Create. The Create API Key drawer is displayed to assist in the key creation.
  4. Enter a Name.
  5. Select Full Admin or System Admin as the role for this API key.
  6. Click Generate API Key.
  7. Copy the API Key to your clipboard to be used when using the API Explorer.
  8. Click Save.

For more details, check Documentation.

Note

If an API key already exists and you need to create a new one, you must first deactivate and delete the existing key by selecting Deactivate and Delete API Key.

To collect user, admin, and system audits through the SIEM API, set up the Generic SIEM Integration in the Island Management Console and copy the Audit ID.

  1. Log in to the Island Management Console as an administrator (Full Admin or System Admin).
  2. Navigate to Modules > Platform Settings > System Settings > Integrations > SIEM.
  3. Click Setup for the Generic SIEM Integration.
  4. Click Generate API Key if you need a dedicated SIEM API key. The API key must belong to an Island account with administrator access (Admin or System Admin).
  5. Copy the Audit ID displayed for the SIEM connector. You will need this value when configuring SIEM Events in Elastic.

Note: Audit and Admin Actions are deprecated. Use SIEM Events for new deployments. Do not enable SIEM Events together with Audit or Admin Actions to avoid collecting duplicate logs.

This integration supports both Elastic Agentless-based and Agent-based installations.

Agentless integrations allow you to collect data without having to manage Elastic Agent in your cloud. They make manual agent deployment unnecessary, so you can focus on your data instead of the agent that collects it. For more information, refer to Agentless integrations and the Agentless integrations FAQ.

Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. This functionality is in beta and is subject to change. Beta features are not subject to the support SLA of official GA features.

Elastic Agent must be installed. For more details, check the Elastic Agent installation instructions. You can install only one Elastic Agent per host.

  1. In the top search bar in Kibana, search for Integrations.

  2. In the search bar, type Island Browser.

  3. Select the Island Browser integration from the search results.

  4. Select Add Island Browser to add the integration.

  5. Enable and configure only the collection methods which you will use.

    • To Collect logs from Island Browser API, you'll need to:

      • Configure URL and API Key. SIEM Events must use https://api.island.io. User, Device, Compromised Credential, and the deprecated Audit and Admin Actions data streams must use https://management.island.io. The URL applies to every data stream enabled in the policy, so collect SIEM Events in a separate integration policy from the management API data streams.
      • Enable/Disable the required datasets.
      • For SIEM Events, provide the Audit ID from the Generic SIEM Integration in the Island Management Console.
      • For each dataset, adjust the integration configuration parameters if required, including the Interval, Batch Size etc. to enable data collection.
  6. Select Save and continue to save the integration.

To collect user, admin, and system audits through the Island SIEM integration:

  1. Complete the SIEM integration setup in the Island Management Console.
  2. Enable SIEM Events in Fleet, set URL to https://api.island.io, and configure API Key and Audit ID.
  1. In the top search bar in Kibana, search for Dashboards.
  2. In the search bar, type Island Browser.
  3. Select a dashboard for the dataset you are collecting, and verify the dashboard information is populated.
  1. In the top search bar in Kibana, search for Transforms.
  2. Select the Data / Transforms from the search results.
  3. In the search bar, type island_browser.
  4. All transforms from the search results should indicate Healthy under the Health column.

For more information on architectures that can be used for scaling this integration, check the Ingest Architectures documentation.

This input is used in this integration:

This integration dataset uses the following APIs:

The data streams below collect a full snapshot of Island Browser devices and users on every polling interval, so their backing indices hold one copy of each record per interval.

The package bounds the growth of these source data streams with a retention that depends on the deployment type:

Data stream Self-managed and Elastic Cloud Hosted (ILM policy) Serverless (data stream lifecycle)
logs-island_browser.device-* logs-island_browser.device-default_policy: roll over after 30d, delete 30d after rollover delete 30d after rollover
logs-island_browser.user-* logs-island_browser.user-default_policy: roll over after 30d, delete 30d after rollover delete 30d after rollover

On self-managed and Elastic Cloud Hosted deployments the ILM policy applies. The data stream lifecycle shipped with the package is not used there. ILM counts the delete age from the rollover of a backing index, so a document can remain for up to the rollover age plus the delete age. On Serverless, ILM is not available and the data stream lifecycle applies instead. It also works per backing index: Elasticsearch rolls the write index over automatically on age, size, or document count, and deletes a backing index once the retention has passed since it rolled over. A document therefore stays for the retention plus up to one rollover interval. The rollover age is derived from the retention and is an implementation detail that Elasticsearch may change. Where the package installs a transform, the transform's destination indices are not affected by either.

To keep data for a different period:

  • Self-managed and Elastic Cloud Hosted: edit the ILM policy in Kibana under Stack Management → Index Lifecycle Policies, or with PUT _ilm/policy/<policy name>. A package upgrade reinstalls the package's ILM policies, so check your change after upgrading.
  • Serverless: set the retention on the data stream, for example PUT _data_stream/logs-island_browser.device-default/_lifecycle with the body {"data_retention": "90d"}. Replace default with your namespace.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.