Visualize Feroot users, groups, project folders, projects, alerts, and domains, map Feroot users to employees, and monitor changes through queries and alerts.
- Installation guide
- Feroot data model
This integration requires an API key with
Admin Read-only permissions on Feroot.
Configuration in Feroot
To create an API Key on Feroot:
- Navigate to Settings > Account > Developer and click Create new API key.
- Select the
Admin Read-onlyrole for the new key.
- Once the key is created, access it from the List of API keys, and copy the key.
To install the Feroot integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Feroot. Click New Instance to begin configuring your integration.
Creating a configuration requires the following:
The Account Name used to identify the Feroot account in JupiterOne. Ingested entities will have this value stored in
AccountNametoggle 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.
Lastly, your Feroot API Key.
Click Create once all values are provided to finalize the integration.
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.
The following entities are created:
|Resources||Entity ||Entity |
The following relationships are created:
|Source Entity ||Relationship ||Target Entity |