Addigy
Visualize Addigy users and policies in the JupiterOne graph, map Addigy users to employees, and monitor changes through queries and alerts.
- Installation
- Data Model
- Types
Installation
You will need to create an API client_id and client_secret key on Addigy. See
their documentation for more information.
Configuration in Addigy
When creating credentials for this integration, ensure the user account has the necessary permissions:
- For Basic Authentication: The user must have Owner role permissions to access the internal API endpoints
- For API Key Authentication: The API key must have access to query users, devices, and policies
The integration requires read access to:
- Devices (
/api/devicesor/devices) - Policies (
/api/policiesor/oa/policies/query) - Users (
/o/{orgId}/users/query- API Key only)
Configuration in JupiterOne
To install the Addigy integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Addigy. Click New Instance to begin configuring your integration.
Creating an instance requires the following:
-
The Account Name used to identify the Addigy account in JupiterOne. Ingested entities will have this value stored in
tag.AccountNamewhen theAccountNametoggle 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
DISABLEDand manually execute the integration. -
Your Addigy Username, Password,
client_id, andclient_secret.
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 |
|---|---|---|
| Addigy Device | addigy_hostagent | HostAgent |
| Addigy Policy | addigy_policy | Policy |
| Addigy User | addigy_user | User |
| Host | addigy_host | Host |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
addigy_host | HAS | addigy_hostagent |
addigy_hostagent | HAS | addigy_policy |
addigy_policy | CONTAINS | addigy_policy |
addigy_user | HAS | addigy_policy |
Mapped Relationships
The following mapped relationships are created:
Source Entity _type | Relationship _class | Target Entity _type | Direction |
|---|---|---|---|
addigy_hostagent | PROTECTS | user_endpoint | FORWARD |
Addigy Host
addigy_host inherits from Host
| Property | Type | Description | Specifications |
|---|---|---|---|
encrypted | boolean | ||
fileVaultEnabled | boolean | ||
firewallEnabled | boolean | ||
isAppleSilicon | boolean | ||
lastOnline | number | ||
platform | string | ||
policyId | string | ||
systemVersion | string | ||
totalDiskSpace | number | ||
totalMemory | number | ||
user | string |
Addigy Hostagent
addigy_hostagent inherits from HostAgent
| Property | Type | Description | Specifications |
|---|---|---|---|
category | string | ||
encrypted | boolean | ||
ethernetMacAddress * | string | null | ||
fileVaultEnabled | boolean | ||
firewallEnabled | boolean | ||
hostname | string | ||
isAppleSilicon | boolean | ||
lastOnline | number | ||
macAddress | array of strings | ||
make | string | ||
model | string | ||
platform | string | ||
policyId | string | ||
serial | string | ||
serialNumber | string | ||
systemVersion | string | ||
totalDiskSpace | number | ||
totalMemory | number | ||
user * | string | null | ||
wifiMacAddress | string |
Addigy Policy
addigy_policy inherits from Policy
| Property | Type | Description | Specifications |
|---|---|---|---|
downloadPath | string | ||
id * | string | ||
orgid | string | ||
parent | string |
Addigy User
addigy_user inherits from User