Skip to main content

ThreatConnect

ThreatConnect is a Threat Intelligence Platform (TIP) that aggregates and operationalizes threat intelligence. You can bring group and indicator data from ThreatConnect into Brinqa to enrich your attack surface with threat-intelligence context, thus strengthening your cybersecurity posture.

This document details the information you must provide for the connector to authenticate with ThreatConnect and how to obtain that information from ThreatConnect. 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 ThreatConnect 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 ThreatConnect with Brinqa:

  • Server URL: The ThreatConnect server URL.

  • Access ID: The API Access ID associated with the ThreatConnect account, which must have permissions to access the API and return data.

  • Secret Key: The API Secret Key associated with the Access ID.

The connector authenticates using HMAC-SHA256 request signing. It signs every API request with your Access ID and Secret Key, so no token exchange or session is required.

Additional settings

The ThreatConnect 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 the lesser of 4 or the number of available CPU cores.
  • Skip certificate verification: Select this option to allow for untrusted certificates. Only enable this for development or testing environments.

Types of data to retrieve

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

Table 1: Data retrieved from ThreatConnect

Connector ObjectRequiredMaps to Data Model
GroupNoNot mapped
IndicatorNoNot mapped
info

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

For the connector objects that are not mapped, you must define the mappings yourself. See Data Consolidation for additional information.

For detailed steps on how to view the data retrieved from ThreatConnect 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.

Group

Table 2: Group attribute mappings

Source Field NameSDM Attribute
GroupResource.assignments[].user.userNameASSIGNED_TO
GroupResource.bodyBODY
GroupResource.createdBy.userNameCREATED_BY
GroupResource.documentDateAddedDOCUMENT_DATE_ADDED
GroupResource.documentTypeDOCUMENT_TYPE
GroupResource.dueDateDUE_DATE
GroupResource.escalatedESCALATED
GroupResource.escalationDateESCALATION_DATE
GroupResource.eventDateEVENT_DATE
GroupResource.fileNameFILE_NAME
GroupResource.fileSizeFILE_SIZE
GroupResource.fileTextFILE_TEXT
GroupResource.fileTypeFILE_TYPE
GroupResource.firstSeenFIRST_SEEN
GroupResource.fromFROM
GroupResource.statusGROUP_STATUS
GroupResource.typeGROUP_TYPE
GroupResource.headerHEADER
Generated (sync capture timestamp)LAST_CAPTURED
GroupResource.nameNAME
GroupResource.overdueOVERDUE
GroupResource.ownerNameOWNER
GroupResource.passwordPASSWORD
GroupResource.publishDatePUBLISHED_DATE
GroupResource.remindedREMINDED
GroupResource.reminderDateREMINDER_DATE
GroupResource.signatureDateAddedSIGNATURE_DATE_ADDED
GroupResource.dateAddedSOURCE_CREATED_DATE
GroupResource.lastModifiedSOURCE_LAST_MODIFIED
GroupResource.subjectSUBJECT
GroupResource.idUID
GroupResource.webLinkURL
GroupResource.xidXID
Indicator

Table 3: Indicator attribute mappings

Source Field NameSDM Attribute
IndicatorResource.activeACTIVE
IndicatorResource.activeLockedACTIVE_LOCKED
IndicatorResource.addressADDRESS
IndicatorResource.asNumberAS_NUMBER
IndicatorResource.blockBLOCK
IndicatorResource.confidenceCONFIDENCE
IndicatorResource.descriptionDESCRIPTION
IndicatorResource.dnsActiveDNS_ACTIVE
IndicatorResource.associatedGroups[].idGROUP_IDS
IndicatorResource.hashtagHASHTAG
IndicatorResource.hostNameHOST_NAME
IndicatorResource.ipIP
IndicatorResource.keyNameKEY_NAME
Generated (sync capture timestamp)LAST_CAPTURED
IndicatorResource.md5MD5
IndicatorResource.mutexMUTEX
IndicatorResource.ownerNameOWNER
IndicatorResource.privateFlagPRIVATE_FLAG
IndicatorResource.ratingRATING
IndicatorResource.sha1SHA1
IndicatorResource.sha256SHA256
IndicatorResource.sizeSIZE
IndicatorResource.sourceSOURCE
IndicatorResource.dateAddedSOURCE_CREATED_DATE
IndicatorResource.lastModifiedSOURCE_LAST_MODIFIED
IndicatorResource.subjectSUBJECT
IndicatorResource.summarySUMMARY
IndicatorResource.textTEXT
IndicatorResource.threatAssessConfidenceTHREAT_ASSESS_CONFIDENCE
IndicatorResource.threatAssessRatingTHREAT_ASSESS_RATING
IndicatorResource.threatAssessScoreTHREAT_ASSESS_SCORE
IndicatorResource.typeTYPE
IndicatorResource.idUID
IndicatorResource.userAgentStringUSER_AGENT
IndicatorResource.valueNameVALUE_NAME
IndicatorResource.valueTypeVALUE_TYPE
IndicatorResource.webLinkURL
IndicatorResource.whoisActiveWHO_IS_ACTIVE

APIs

The ThreatConnect connector uses the ThreatConnect REST API v3. Specifically, it uses the following endpoints:

Table 4: ThreatConnect REST API Endpoints

Connector ObjectAPI Endpoint
GroupGET /api/v3/groups
IndicatorGET /api/v3/indicators

Changelog

The ThreatConnect connector has undergone the following changes:

Table 5: ThreatConnect connector changelog

VersionDescriptionDate Published
3.0.0Improvements
- Upgraded to the latest Brinqa connector framework, modernizing how ThreatConnect groups and indicators are modeled and synchronized.
- Indicator records now include their 'associated group IDs' and 'ThreatAssess rating, confidence, and score', which were not previously retrieved from ThreatConnect.
- Date fields (date added, last modified, first seen, event date, due/escalation/reminder dates, publish date, etc.) are now stored as proper timestamps rather than raw numbers, improving filtering and reporting.
Bug Fixes
- Group and indicator synchronization no longer fails when ThreatConnect returns a user record without an identifier (for example, on a group's 'created by' or an indicator's associated groups).
Migration Required
- 'Group' and 'Indicator': the attribute model has changed (date fields are now timestamps, the attribute set has been updated, and additional indicator data is captured). Re-sync both object types after upgrading so existing records pick up the new structure.
June 3rd, 2026