DataStax
Visualize DataStax Astra organizations, users, roles, databases, and access, map DataStax Astra users to employees, and monitor changes through queries and alerts.
- Installation
- Data Model
- Types
Installation
To connect this integration, you create a read-only custom role in DataStax Astra, generate an application token bound to that role, and provide the token along with your organization name in JupiterOne.
Prerequisites
You need a DataStax Astra user who can create custom roles and generate application tokens. These actions require the Write Custom Role and Write Token permissions, which are included in the built-in Organization Administrator role. For details on Astra permissions, see the DataStax role-based access control documentation.
Create a custom role in DataStax
- In the Astra Portal, go to Settings and set the organization filter to the organization you want JupiterOne to monitor.
- Create a new custom role and assign the following read permissions:
- View DB
- Read IP Access List
- Read User
- Read Custom Role
- Set the role's resource scope to All databases so the role has access to all current and future databases in the organization.
- Save the role.
The View DB permission lets the role read database information returned by DevOps API requests. For guidance on resource scopes and custom-role mechanics, see the custom roles documentation.
Generate an application token
- In the Astra Portal, go to Settings and confirm the organization filter is set to your target organization.
- Open Tokens.
- Under Generate New Token, select the custom role you created.
- Optionally add a description and set an expiration. The default is Never expire.
- Select Generate Token and copy the generated
AstraCS:token. The token is shown only once.
For more detail, see the application token documentation.
Configuration in JupiterOne
To install the DataStax integration in JupiterOne, navigate to the Integrations tab and select DataStax. Click New Instance to begin configuring your integration.
Creating an instance requires the following:
- Organization Name: the DataStax organization name for the account you want JupiterOne to monitor.
- Token: the application token you generated above, obtained from the Astra Portal Tokens section.
You can also set the following common fields:
- Account Name used to identify the DataStax account in JupiterOne.
- Description to help identify the integration instance, if desired.
- Polling Interval that is sufficient for your monitoring needs. You may
leave this as
DISABLEDand run the integration manually.
Click Create once all values are provided to finalize the integration.
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 |
|---|---|---|
| Access List | datastax_access_list | Firewall |
| Access List Address | datastax_access_list_address | Configuration |
| Access Role | datastax_access_role | AccessRole |
| Database | datastax_database | Database |
| Organization | datastax_organization | Organization |
| User | datastax_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
datastax_access_list | HAS | datastax_access_list_address |
datastax_database | ASSIGNED | datastax_access_list |
datastax_organization | HAS | datastax_database |
datastax_organization | HAS | datastax_access_list |
datastax_organization | HAS | datastax_user |
datastax_user | ASSIGNED | datastax_access_role |