Purpose
Purpose
The Exabeam integration enables AirMDR to:
- Ingest Exabeam cases, and alerts that are not part of a case, with their risk scores, priorities, rules and MITRE ATT&CK techniques.
- Investigate the threat timeline behind a case or alert: each detection with its risk score, rarity, the users and devices involved, and the query that reproduces its events.
- Score users and hosts by Exabeam risk, the same way Exabeam defines entity risk, and flag notable entities.
- Search raw event logs and read context tables such as watchlists.
- Write results back to Exabeam: add case notes, update or close cases, update alerts, escalate alerts into cases, and add or remove watchlist records.
Supported Versions
Supported Versions
Authentication
Authentication
Authentication methodAirMDR authenticates with an Exabeam API key using the OAuth 2.0 client credentials flow:
- Client ID: the Key value of the API key.
- Client Secret: the Secret value of the API key.
- API URL: the API gateway for your Exabeam region.
Permission sets
Permission sets
Exabeam API keys have no OAuth scopes. Each key is given a permission set when it is created. Choose the set that covers the skills you want AirMDR to run:
Exabeam names its permission sets in the API Keys dialog. If one set cannot cover everything, choose the one for the capabilities you need most: the connection check passes as long as the key can read alerts, cases or events.
Pre-requisites
An Exabeam administrator with full access to the subscription. Only full-access administrators can create API keys.The region your Exabeam subscription is hosted in, which selects the API gateway.You are logged in to AirMDR with a role that can manage integration connections.
Setup Steps
1
Create an API key
- Sign in to the Exabeam Security Operations Platform.
- On the lower left, select Settings, then API Keys.
- Select New API Keys (or New Keys when keys already exist).
- Enter a descriptive Key Name, such as
AirMDR. - In Permissions, select the permission set that covers the capabilities you want, as listed under Permission sets above.
- Select Create.
- Copy the Key and the Secret into an approved password manager.
Create a key used only by AirMDR, so it can be rotated or revoked on its own.
2
Find your API gateway
Use the API gateway for your region, not the console address.
3
Configure the connection in AirMDR
- Open the Exabeam integration in the AirMDR Integrations Dashboard.
- Select the Connections tab, then Add New Connection.
- Enter a unique Instance name, such as
yourorg-exabeam, and a short Description. - Enter the API URL, the Client ID (the Key) and the Client Secret (the Secret).
- Select Save.
Saving runs a connection check: AirMDR requests a token and then makes one real read of alerts, cases or events. A wrong key, a wrong region, or a permission set that reaches none of them is reported immediately.
Skills Provided by this Integration
Risk scores
Exabeam risk scores are on a 0 to 100 scale on New-Scale licenses, where Exabeam treats 90 or more as notable. Older Security Operations and Fusion licenses add up detection scores with no upper limit, where 75 or more is critical by default. The skills that filter or flag by risk take the threshold as an input, so set the threshold your analysts use.Data Flow & Security
What AirMDR reads- Threat Center cases and alerts, their notes, history and threat timelines.
- Raw event logs, when Search Exabeam Events is run.
- Context table metadata and records.
- Only the skills marked Changes Exabeam above, and only when the API key has the matching write permission. A read-only permission set keeps the integration read-only.
- The Client Secret is stored encrypted and is sent only to the Exabeam token endpoint.
- Access tokens are cached encrypted and reused for their 4-hour life. Saving the connection always requests a new one.
- All calls use HTTPS to the Exabeam regional API gateway.
Error Handling
Evaluate the Exabeam API
Run the following commands to check that your API key works, replacing the region and credentials. Step 1: Request an access tokenaccess_token and expires_in of 14400 seconds.
Step 2: Search the last day of cases
rows list. HTTP 403 means the permission set of the key does not include Threat Center cases.
Support & Maintenance
- Contact AirMDR Support through your designated support channel.
- Rotate the API key at least every 12 months, as Exabeam recommends, and update the AirMDR connection with the new Key and Secret.

