Brinqa Integration

The Bitsight Connector enables Brinqa users to seamlessly ingest Bitsight asset, company, and security data into the Brinqa Platform. It provides pre‑built mappings to Brinqa’s Data Model, making data consolidation and risk analysis fast and reliable. 

Key Benefits

• Security context enrichment
  Add asset- and company-level security rating data to existing Brinqa analytics workflows.
   
• Accelerated deployment
  Out-of-the-box Integration+ mappings eliminate manual schema configuration.
   
• Customizable data retrieval
  Control data volume through settings like page size, parallel requests, and maximum retries.

Integration Capabilities

The connector leverages the following Bitsight API endpoints:

• Asset Data via /ratings/v2/portfolio and /ratings/v1/companies/{portfolio}/assets
• Company Ratings via /ratings/v2/portfolio
• Findings via /ratings/v1/companies/{portfolioId}/findings and /ratings/v2/portfolio

It ingests:

• Asset entities mapped to Host
• Company entities linked to Company model
• Finding entities formatted as Violation model 

Prerequisites

Before configuring the integration, ensure:

1. Connector Installation
   • Locate Bitsight under Integrations → Connectors A–F in the Brinqa UI
   • Click Install, then Use to configure
      
2. API Credentials
   • Bitsight API URL: default to https://api.bitsighttech.com/
   • Valid Bitsight API token (generated via the Bitsight portal)
      
3. Connector Settings
   • Page size: max 100 (default 100)
   • Parallel requests: default 4
   • Maximum retries: default 5
   • Optional: enable Skip certificate verification as needed

Configuration & Setup Steps

1. In Brinqa, navigate to Integrations → Connectors, select Bitsight, and click Install.
2. Once installed, click Use and enter:
   • API URL
   • API token
   • Desired connector options (page size, parallel requests, etc.)
3. Save and enable the connector.
4. Create a scheduled sync via Integration > Data Sources.
5. Monitor ingest status and review imported data via Brinqa’s UDM entities for Hosts, Companies, and Violations.

For additional details see Brinqa documentation : https://docs.brinqa.com/docs/connectors/bitsight/

Data Flow

• Inbound: Brinqa pulls data from Bitsight APIs into the platform.
• Channelled into: UDM tables — Host, Company, Violation.
• Unified with other connectors for enriched risk analytics.

Operational Options

Use connector options to refine data syncs:

• portfolioIds: restrict imports to specific Bitsight portfolio IDs (comma-separated).
• Adjust page size, parallelism, retries, and certificate settings as needed.

Troubleshooting & Tips

• Too many parallel requests or large page sizes may trigger API rate limits.
• To filter vendors, specify portfolioIds consistently across Company and related queries.
• Connector updates (like type mismatches or improved performance) are listed in the changelog.