Feroot

Visualize Feroot users, groups, project folders, projects, alerts, and domains, map Feroot users to employees, and monitor changes through queries and alerts.

Installation

Installation

info

This integration requires an API key with Admin Read-only permissions on Feroot.

Configuration in Feroot

To create an API Key on Feroot:

1. Navigate to Settings > Account > Developer and click Create new API key.
2. Select the Admin Read-only role for the new key.
3. Once the key is created, access it from the List of API keys, and copy the key.

Data Volume Configuration

Control how much data is ingested from Feroot to manage storage and processing.

Data Filtering Options

Field	Type	Description	Default
Ingest Resolved Alerts	Boolean	Indicates whether to preserve entities for resolved alerts or to remove all resolved alerts from the graph.	false

How it affects data volume: When disabled (default), resolved alerts are removed from the graph, keeping only active alerts. Enabling this setting preserves all alerts including resolved ones, increasing the total number of alert entities stored.

In JupiterOne

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 an instance requires the following:

• The Account Name used to identify the Feroot 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.

• Lastly, your Feroot API Key.

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.

Data Model

Entities

The following entities are created:

Resources	Entity _type	Entity _class
Alert	feroot_alert	Finding
Inspector Project	feroot_project	Project
PageGuard Project	feroot_pageguard_project	Project
Project Folder	feroot_project_folder	Group
Target Domain	web_app_domain	Application
User	feroot_user	User
User Group	feroot_user_group	UserGroup

Relationships

The following relationships are created:

Source Entity _type	Relationship _class	Target Entity _type
feroot_project	MONITORS	web_app_domain
feroot_project	CONTAINS	feroot_pageguard_project
feroot_project	GENERATED	feroot_alert
feroot_project_folder	HAS	feroot_project
feroot_user_group	HAS	feroot_user
feroot_user_group	HAS	feroot_project_folder

Types

Feroot User

feroot_user inherits from User

---