Integration Benefits
- Visualize atSpoke users, teams, requests and webhooks in the JupiterOne graph.
- Map atSpoke users to employees in your JupiterOne account.
- Maintain awareness of systems atSpoke is interacting with through webhooks.
- Monitor changes to atSpoke users using JupiterOne alerts.
- Correlate atSpoke request types and volume with other security events.
How it Works
JupiterOne periodically fetches users, teams, and webhooks from atSpoke to
update the graph. Optionally, requests and request types are also fetched.
Write JupiterOne queries to review and monitor updates to the graph.
- Configure alerts to take action when JupiterOne graph changes.
Requirements
Support
If you need help with this integration, please contact
JupiterOne Support.
Integration Walkthrough
In atSpoke
- Log into atSpoke on a Business-level or Enterprise-level account (Teams-level
accounts do not provide API functionality).
- Go to My Profile.
- Select the API tab.
- Generate a token at the bottom of the page. Note that you can only have one
token for the whole atSpoke account, and it allows access to all things.
In JupiterOne
- From the top navigation of the J1 Search homepage, select Integrations
- Scroll to the atSpoke integration tile and click it.
- Click the Add Configuration button.
- Enter the Account Name by which you'd like to identify this atSpoke
account in JupiterOne. Ingested entities will have this value stored in
tag.AccountName when Tag with Account Name is checked.
- Enter a Description that will further assist your team when identifying
the integration instance.
- Select a Polling Interval that you feel is sufficient for your monitoring
needs. You may leave this as DISABLED and manually execute the integration.
- Enter the atSpoke API Key generated on the atSpoke site.
- Click Create Configuration once all values are provided.
atSpoke Request Tracking
When the integration runs, the JupiterOne graph will request the most recent 100
atSpoke requests. If there are more than 100 requests available and the first
100 are not enough to establish at least 14 days of history, JupiterOne will
keep collecting requests in batches of 100 until 14 days of history are
established or all requests are gathered.
These requests will be Record entities in the JupiterOne graph, and the
collection size will grow indefinitely (ie. old Records will not be deleted,
unlike users, teams, and webhooks which only show current in the J1 graph).
How to Uninstall
- From the top navigation of the J1 Search homepage, select Integrations
- Scroll to the atSpoke integration tile and click it.
- Identify and click the integration to delete.
- Click the trash can icon.
- Click the Remove button to delete the integration.
Data Model
Entities
The following entities are created:
| Resources |
Entity _type |
Entity _class |
|---|
| atSpoke Account |
atspoke_account |
Account |
| atSpoke Request |
atspoke_request |
Record |
| atSpoke Request Type |
atspoke_requesttype |
Configuration |
| atSpoke Team |
atspoke_team |
UserGroup |
| atSpoke User |
atspoke_user |
User |
| atSpoke Webhook |
atspoke_webhook |
ApplicationEndpoint |
Relationships
The following relationships are created/mapped:
Source Entity _type |
Relationship _class |
Target Entity _type |
|---|
atspoke_account |
HAS |
atspoke_request |
atspoke_account |
HAS |
atspoke_requesttype |
atspoke_account |
HAS |
atspoke_team |
atspoke_account |
HAS |
atspoke_user |
atspoke_account |
HAS |
atspoke_webhook |
atspoke_request |
HAS |
atspoke_requesttype |
atspoke_team |
HAS |
atspoke_user |
.png)