Skip to main content

Validation Agent

Security Testing

The Validation Agent connector integrates with the Brinqa Validation Agent API and synchronizes validation runs — the record of an agent attempting to independently reproduce or disprove a finding on a target asset. Each record carries the run's status, its verdict (for example exploitable, remediated, inconclusive), the rationale behind that verdict, the finding and asset it was run against, the timing of the run, and — when a run does not finish — why it failed.

The connector syncs a single model, Validation, onto the Validation UDM. The endpoint returns the full run history, so a finding that has been validated more than once contributes one record per run, each keyed by its own validation id.

Data retrieved from Validation Agent​

Connector ObjectRequiredMaps to Data Model
ValidationYesValidation

Model relationships​

note

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

warning

A create starts a real validation run and spends the tenant's quota. It is not idempotent, so the connector sends it exactly once and never retries it, unlike the sync's reads.

note

The one exception is a 401, which the API returns before processing the request: the create is sent again once, with a renewed access token.