Skip to main content

atSpoke

Visualize atSpoke users, teams, requests and webhooks in the JupiterOne graph. Map atSpoke users to employees in your JupiterOne account. Monitor changes to atSpoke users using JupiterOne alerts. Correlate atSpoke request types and volume with other security events.

Installation​

To install this integration, you will need a Business or Enterprise level atSpoke account in order to create an API key for JupiterOne to access the system.

Configuration on atSpoke​

  1. Log into atSpoke on a Business-level or Enterprise-level account (Teams-level accounts do not provide API functionality).
  2. Go to My Profile.
  3. Select the API tab.
  4. 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.

Configuration in JupiterOne​

To install the atSpoke integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select atSpoke. Click New Instance to begin configuring the integration.

Creating an atSpoke instance requires the following:

  • The Account Name used to identify the atSpoke account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • 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 once all values are provided to finalize the integration.

note

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).

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.