Detectify
Visualize Detectify scan reports and monitor changes through queries and alerts.
- Installation
- Data Model
- Types
- Release Notes
Installation
The integration connects directly to the Detectify REST API to obtain application scan assets, reports, and findings. By default, it only ingests findings from the past 30 days. If you have an Enterprise Plan with Detectify, the configuration can be changed to ingest findings from the latest scan reports.
Configuration in Detectify
You will need a Detectify API key to allow the integration to make REST API calls. The API-keys tab is only visible to team Admins, so you must have admin permissions for the team to create the key.
-
In Detectify, open the user menu and go to Team settings, then select the API-keys tab.
-
Click Generate API key and, if desired, give the key a name or description in the modal.
-
On professional and enterprise plans, you can optionally configure Setting Permissions for the key or require a message signature (secret key). These controls are not required for the integration.
-
The key is shown only once. Copy it and store it in a safe place — you will paste it into JupiterOne. API keys can be reviewed and managed later from the API keys page.
For more detail, see Detectify's guide to setting up the API.
Configuration in JupiterOne
To install the Detectify integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Detectify. Click New Instance to begin configuring your integration.
Creating an instance requires the following:
-
The Account Name used to identify the Detectify account in JupiterOne. Ingested entities will have this value stored in
tag.AccountNamewhen theAccountNametoggle is enabled. -
A Description to assist in identifying the integration instance, if desired.
-
A Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration. -
Your Detectify API Key, configured for read access, generated in the steps above.
Click Create once all values are provided to finalize the integration.
Data Volume Configuration
The Detectify integration provides configuration options to control the volume of data ingested into JupiterOne:
| Field | Description | Default | Options |
|---|---|---|---|
| Get findings from the latest scans | When enabled, the integration pulls findings only from the latest scan reports. When disabled, the integration pulls all findings from the last 30 days. Requires an Enterprise Plan from Detectify. | Disabled (pulls findings from the last 30 days) | Enable to pull only the latest scan findings (requires Enterprise Plan) |
Data Model
The JupiterOne vulnerability management and scanner integration is built on this high level data model:
Vendor - HOSTS -> Account
Account - PROVIDES -> Service (*)
Service - SCANS or TESTS -> <Entity> (*)
<Entity> - HAS -> Finding
(*) Examples:
Service(E.g., SAST, DAST, IAST, MAST, PenTest, etc.)<Entity>(E.g., Application, Host, or Device)
Optionally, the following is added when each scan/assessment/report is also tracked by the integration:
Service - PERFORMS -> Assessment
Assessment - IDENTIFIED -> Finding
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 |
|---|---|---|
| Account | detectify_account | Account |
| Asset (Domain) | web_app_domain | Application |
| Asset (Subdomain) | web_app_endpoint | ApplicationEndpoint |
| Finding | detectify_finding | Finding |
| Scan Profile | detectify_scan_profile | Configuration |
| Service | detectify_service | Service |
| User | detectify_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
detectify_account | PROVIDES | detectify_service |
detectify_account | HAS | web_app_domain |
detectify_account | HAS | detectify_user |
detectify_service | SCANS | web_app_domain |
web_app_domain | HAS | web_app_endpoint |
web_app_domain | HAS | detectify_scan_profile |
web_app_endpoint | HAS | detectify_finding |
Detectify Finding
detectify_finding inherits from Finding
| Property | Type | Description | Specifications |
|---|---|---|---|
category * | string | null | ||
cvss2Score * | number | null | ||
cvss2Vector * | string | null | ||
cvss31Score * | number | null | ||
cvss31Vector * | string | null | ||
cvss3Score * | number | null | ||
cvss3Vector * | string | null | ||
details * | array | null | ||
endpoint * | string | null | ||
references * | array | null | ||
score * | number | null | ||
vector * | string | null |
Detectify User
detectify_user inherits from User
| Property | Type | Description | Specifications |
|---|---|---|---|
authentication | string | ||
createdOn | number | ||
lastLoginOn | number | ||
role | string | ||
userToken | string |
Release Notes
- 2025-06-06 — Added CVSS v2, v3, and v3.1 score and vector properties to Detectify finding entities for vulnerability severity assessment.