Onspring
The Onspring Connector integrates with the Onspring platform to synchronize security findings and exception requests. You can bring finding and exception request data from Onspring into Brinqa to gain 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 Onspring and how to obtain that information from Onspring. 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 Onspring from the Connector dropdown. If you cannot find the connector in the dropdown, make sure that you have installed it first. You must provide the following information to authenticate Onspring with Brinqa:
- Onspring server URL: The URL for your Onspring server.
- Onspring API Key: The API key used to authenticate with the Onspring API.
Generate Onspring API keys
For instructions on how to generate an API key, refer to the Onspring API Documentation or contact your Onspring administrator.
Additional settings
The Onspring 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.
- Parallel requests: The maximum number of parallel API requests. The default setting is 4.
- Maximum retries: The maximum number of times that the integration attempts to connect to the Onspring API before giving up and reporting a failure. The default setting is 5.
Types of data to retrieve
The Onspring connector can retrieve the following types of data from the Onspring API:
Table 1: Data retrieved from Onspring
| Connector Object | Required | Maps to Data Model |
|---|---|---|
| Exception Request | Yes | None |
| Finding | Yes | None |
The Onspring 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 Onspring in the Brinqa Platform, see How to view your data.
Attribute mappings
Expand the sections below to view the mappings between the source and the Brinqa data model attributes.
Exception Request
Attributes for this model are derived dynamically from the Onspring API based on the fields defined in the "Exception Requests" application.
Table 2: Exception Request attribute mappings
| Source Field Name | SDM Attribute |
|---|---|
(Application Fields) | (DYNAMIC FIELDS) |
| Generated (Sync timestamp) | LAST_CAPTURED |
recordId | UID |
Finding
Attributes for this model are derived dynamically from the Onspring API based on the fields defined in the "Findings" application.
Table 3: Finding attribute mappings
| Source Field Name | SDM Attribute |
|---|---|
(Application Fields) | (DYNAMIC FIELDS) |
| Generated (Sync timestamp) | LAST_CAPTURED |
recordId | UID |
APIs
The Onspring connector uses the Onspring API. Specifically, it uses the following endpoints:
Table 4: Onspring API Endpoints
| Connector Object | API Endpoint |
|---|---|
| Exception Request | GET /Records/appId/{appId} |
PUT /Records/ | |
| Finding | GET /Records/appId/{appId} |
Changelog
The Onspring connector has undergone the following changes:
This connector is part of a bundled release with other connectors from the same vendor. If a version shows "No change", it means that the connector version was updated for consistency as part of the bundle, but no functional changes were made to this specific connector. You can update to or skip this version without affecting your existing configuration.
Table 5: Onspring Changelog
| Version | Description | Date Published |
|---|---|---|
| 3.0.0 | Initial Integration+ release. | TBD |