Edgescan

Edgescan is a vulnerability management tool that provides continuous vulnerability scanning and threat intelligence. You can bring application, container, host, network and other security data from Edgescan into Brinqa to construct a unified view of your attack surface, thus strengthening your cybersecurity posture.

This document details the information you must provide for the connector to authenticate with Edgescan and how to obtain that information from Edgescan. See create a data integration for step-by-step instructions on setting up the integration.

Required connection settings

When setting up a data integration, select Edgescan from the Connector drop-down. If you cannot find the connector in the drop-down, make sure that you have installed it first. You must provide the following information to integrate Edgescan with Brinqa:

• Server URL: The Edgescan Server URL. The default URL is https://live.edgescan.com.

• API token: The API token associated with the Edgescan account, which must have permissions to log in to the API server and return data.

Generate an Edgescan API token

For the Edgescan connector to use the Edgescan API, you must generate an API token. To do so, follow these steps:

1. Log in to your organization's Edgescan portal as an administrator.

2. Click the user profile icon in the top right corner and select Account settings from the drop-down.

3. Locate the API tokens section, provide a label, and set an optional expiry date.

4. Click Create.

   Your new API key token displays. You can't view the token again after this. Copy and save it to a secure location.

   The API token inherits the permissions of the user who created it. Brinqa recommends generating the token from a user account with the Viewer User role and View permissions for the relevant assets or resources. This is the minimum role and permission set required to retrieve data from the Edgescan API without administrative privileges. For more information, see the Edgescan documentation for creating users and assigning permissions.

note

If you do not have permission to create an API token, contact your Edgescan administrator. For additional information, see the Edgescan documentation.

Additional settings

The Edgescan connector contains additional options for specific configuration:

• Page size: The maximum number of records to get per API request. The default setting is 100. It is not recommended to go over 100.

• Max retries: The maximum number of times that the integration attempts to connect to the Edgescan API before giving up and reporting a failure. The default setting is 5.

Types of data to retrieve

The Edgescan connector can retrieve the following types of data from the Edgescan API:

Table 1: Data retrieved from Edgescan

Connector Object	Required	Maps to Data Model
Application	Yes	Application
Container	Yes	Container
Host	Yes	Host
Network	No	Not mapped
Vulnerability	No	Vulnerability
Vulnerability Definition	No	Vulnerability Definition

info

The Edgescan connector does not currently support operation options for the types of data it retrieves.

For detailed steps on how to view the data retrieved from Edgescan in the Brinqa Platform, see How to view your data.

APIs

The Edgescan connector uses the Edgescan API v1. Specifically, it uses the following endpoints:

Table 2: Edgescan API Endpoints

Connector Object	API Endpoints
Application	GET /api/v1/assets
Container	GET /api/v1/assets
Host	GET /api/v1/hosts
Network	GET /api/v1/assets
Vulnerability	GET /api/v1/details
	GET /api/v1/details/{id}/request_responses
	GET /api/v1/vulnerabilities
Vulnerability Definition	GET /api/v1/definitions

Changelog

The Edgescan connector has undergone the following changes:

Table 3: Edgescan connector changelog

Version	Description	Date Published
3.0.0	Initial Integration+ release.	May 21st, 2025