Cyberhaven
Visualize Cyberhaven Endpoints and monitor changes through queries and alerts.
- Installation
- Data Model
- Types
- Release Notes
Installation
Requirements
- A Cyberhaven role carrying the
endpoint__readpermission, and an API key assigned to that role. - Appropriate permissions in JupiterOne to setup new integration.
Configuration in Cyberhaven
Authentication
Cyberhaven uses token-based authentication to secure its API endpoints. To authenticate, you must first create an API key in the Cyberhaven Console and use it to generate a temporary bearer token. JupiterOne performs this exchange for you; you only supply the API key.
Note: Create the role before generating the key. The role attached to the key must carry the
endpoint__readpermission, otherwise Cyberhaven rejects the request.
Refer to the Cyberhaven documentation for guidance on creating an API role: Creating an API Role
Generate an API Key
- Navigate to Preferences > Users and API keys, then open the API Keys tab.
- Click New API Key.
- Provide a name to identify the API key.
- Select a role from the list. The role must include the
endpoint__readpermission. - Specify a validity period (up to one year).
- Click Save.
- Copy and securely store the generated API key.
Configuration in JupiterOne
- From the JupiterOne Search homepage, navigate to Integrations from the top menu.
- Search for Cyberhaven, then select it.
- Click Add Instance, then provide the following information:
- Cyberhaven API Key: Use the key generated in the Generate an API Key section.
- Cyberhaven Tenant Name: Your tenant's subdomain only — not the full console URL. If you sign in at
https://acme.cyberhaven.io, enteracme. - Account Name: A label for identifying this Cyberhaven instance in JupiterOne. If Tag with Account Name is enabled, this value is stored in
tag.AccountNamefor all ingested entities. - Description: (Optional) A brief description to help your team identify this integration.
- Polling Interval: Choose an appropriate interval for your monitoring needs. You can also select
DISABLEDto manually execute the integration.
- Once all values are entered, click Create Instance.
Next Steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Entities
The following entities are created:
| Resources | Entity _type | Entity _class |
|---|---|---|
| Account | cyberhaven_account | Account |
| Endpoint | cyberhaven_endpoint | Host |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
cyberhaven_account | HAS | cyberhaven_endpoint |
Cyberhaven Account
cyberhaven_account inherits from Account
Cyberhaven Endpoint
cyberhaven_endpoint inherits from Host
| Property | Type | Description | Specifications |
|---|---|---|---|
deploymentGroup | string | ||
lastActiveUserId | string | ||
lastActiveUsername | string | ||
sensorVersion | string |
Release Notes
- 2025-04-22 — New Cyberhaven integration: ingests endpoint devices and account information with host entity types.