- Visualize Addigy users, policies, and device agents in the JupiterOne graph.
- Map Addigy users to employees in your JupiterOne account.
- Monitor changes to Addigy device agents using JupiterOne alerts.
- JupiterOne periodically fetches services, teams, and users from Addigy to update the graph.
- Write JupiterOne queries to review and monitor updates to the graph, or leverage existing queries.
- Configure alerts to take action when JupiterOne graph changes, or leverage existing alerts.
- JupiterOne requires an API
client_id
andclient_secret
. You need permission to create a user in Addigy that will be used to obtain the id and secret. Jupiterone also needsusername
andpassword
of an admin user to retrieve user information from the Addigy internal API. - You must have permission in JupiterOne to install new integrations.
If you need help with this integration, please contact JupiterOne Support.
- From the top navigation of the J1 Search homepage, select Integrations
- Scroll to the Addigy integration tile and click it.
- Click the Add Configuration button and configure the following settings:
- Enter the Account Name by which you'd like to identify this {{provider}}
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 Username and Password used to authenticate with Addigy.
- Enter the client_id and client_secret generated in previous steps.
- Click Create Configuration once all values are provided.
- From the top navigation of the J1 Search homepage, select Integrations
- Scroll to the Addigy 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.
The following entities are created:
Resources | Entity _type |
Entity _class |
---|---|---|
Addigy Device | addigy_hostagent |
HostAgent |
Addigy Policy | addigy_policy |
Policy |
Addigy User | addigy_user |
User |
The following relationships are created:
Source Entity _type |
Relationship _class |
Target Entity _type |
---|---|---|
addigy_hostagent |
HAS | addigy_policy |
addigy_policy |
CONTAINS | addigy_policy |
addigy_user |
HAS | addigy_policy |
The following mapped relationships are created:
Source Entity _type |
Relationship _class |
Target Entity _type |
Direction |
---|---|---|---|
addigy_hostagent |
PROTECTS | *user_endpoint* |
FORWARD |