SysReptor
Penetration Testing- Overview
- Setup
- Data & mappings
- Operations & API
- Changelog
The SysReptor connector integrates with SysReptor, an open-source penetration test reporting and collaboration platform. It synchronizes pentest findings and a deduplicated library of pentest finding definitions derived from those findings.
SysReptor stores findings under pentest projects, and the shape of each finding's data object is
defined per project type. The connector enumerates projects, walks each project's findings, and
reads the owning project type's finding_fields so that any organization-specific custom finding
fields are surfaced automatically as connector attributes.
Data retrieved from SysReptor
| Connector Object | Required | Maps to Data Model |
|---|---|---|
| Pentest Finding | Yes | Pentest Finding |
| Pentest Finding Definition | Yes | Pentest Finding Definition |
Model relationships
For detailed steps on how to view the data retrieved from SysReptor in the Brinqa Platform, see How to view your data.
Connection settings
When setting up a data integration, select SysReptor from the Connector dropdown and provide the following:
| Setting | Required | Default | Description |
|---|---|---|---|
| API URL | Yes | — | SysReptor base URL (e.g. https://sysreptor.example.com) |
| API token | Yes | — | SysReptor API token used as a Bearer token for authentication |
| Max retries | No | 5 | Maximum number of retries for failed API requests |
Authentication
SysReptor authenticates with a personal API token supplied as a Bearer token.
Endpoint
| Method | URL |
|---|---|
GET | {url}/api/v1/pentestprojects |
Request Headers
| Header | Value |
|---|---|
Authorization | Bearer <apiToken> |
Accept | application/json |
Usage
Every API request includes the bearer token:
Authorization: Bearer <apiToken>
The connection test issues a GET /api/v1/pentestprojects request and treats any non-2xx
response as an authentication/connectivity failure.
How to obtain SysReptor credentials
Obtain the required credentials (url, apiToken) from your SysReptor administrator or the SysReptor admin console, then enter them in the connection settings above.
Attribute mappings
Expand the sections below to view the mappings between the source and the Brinqa data model attributes:
Pentest Finding
| Source Field Name | SDM Attribute |
|---|---|
Finding.assignee.name (fallback username) | ASSIGNEE |
Finding.created | FIRST_FOUND |
Finding.data.* | custom |
Finding.data.affected_components | TARGETS |
Finding.data.recommendation | RECOMMENDATION |
Finding.data.retest_status (fallback Finding.status) | PROVIDER_STATUS |
Finding.data.title | NAME |
Finding.data.title | TYPE |
Finding.id | UID |
Finding.project | PROJECT |
Finding.status | WORKFLOW_STATUS |
Finding.updated | LAST_FOUND |
| normalized PROVIDER_STATUS | SOURCE_STATUS |
| sync time | LAST_CAPTURED |
Pentest Finding Definition
| Source Field Name | SDM Attribute |
|---|---|
| derived from SEVERITY | SEVERITY_SCORE |
Finding.data.cvss | CVSS_V3_VECTOR, CVSS_V3_BASE_SCORE, CVSS_V3_SEVERITY, … |
Finding.data.description | DESCRIPTION |
Finding.data.references | REFERENCES |
Finding.data.root_cause | CATEGORIES |
Finding.data.root_cause | TAGS |
Finding.data.summary | SUMMARY |
Finding.data.title | UID |
Finding.data.title | NAME |
| normalized SOURCE_SEVERITY | SEVERITY |
severity from data.cvss | SOURCE_SEVERITY |
| sync time | LAST_CAPTURED |
Operations & API
Expand each connector object to see its operation options, delta-sync behavior, and the API it uses. See connector operation options for how to apply operation options (keys and values are case-sensitive).
Pentest Finding
Operation options
This object does not support any operation options.
Delta sync
The connector README does not document sync behavior for this object.
API
- Type: REST endpoint · Endpoint:
GET /api/v1/pentestprojects/{id}/findings/
Pentest Finding Definition
Operation options
This object does not support any operation options.
Delta sync
The connector README does not document sync behavior for this object.
API
- Type: REST endpoint · Endpoint:
GET /api/v1/pentestprojects/{id}/findings/
Changelog
The SysReptor connector has undergone the following changes:
| Version | Description | Migration Steps |
|---|---|---|
| 3.0.0 | Overview The SysReptor connector integrates with SysReptor to synchronize penetration test findings and a deduplicated library of finding definitions (including severity ratings and CVSS metrics). Category: Penetration Testing Models | N/A |