Collect ThreatConnect IOC logs

Supported in:

Google SecOps SIEM

Note: This feature is covered by Pre-GA Offerings Terms of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the Google Security Operations Technical Support Service guidelines and the Google Security Operations Service Specific Terms.

This parser extracts IOC data from ThreatConnect JSON logs and transforms it into the UDM format. It handles various IOC types such as Host, Address, File, and URL, mapping fields like confidence scores, descriptions, and entity details to their corresponding UDM equivalents, and categorizes threats based on keywords within the log data.

Before you begin

• Ensure that you have a Google Security Operations instance.
• Ensure that you have privileged access to ThreatConnect.

Configure API User on ThreatConnect

1. Sign in to ThreatConnect.
2. Go to Settings > Org Settings.
3. Go to the Membership tab in the Organization Settings.
4. Click Create API User.

5. Fill out the fields on the API User Administration window:

   • First Name: enter the API user's first name.
   • Last Name: enter the API user's last name
   • System Role: select the Api User or Exchange Admin System role.
   Note: Available System roles for API users include the following:
   Api User: API users with this role can use all ThreatConnect v2 and v3 API endpoints, with the exception of the v3 API TC Exchange™ administration endpoints.
   Exchange Admin: API users with this role can use all ThreatConnect v2 and v3 API endpoints, including the v3 AP.
   • Organization Role: select the API user's Organization role.
   • Include in Observations and False Positives: select the checkbox to allow data provided by the API user to be included in observation and false-positive counts.
   • Disabled: click the checkbox to disable an API user's account in the event that the Administrator wants to retain log integrity.
   • Copy and save the Access ID and Secret Key.

6. Click Save.

Configure a feed in Google SecOps to ingest ThreatConnect logs

1. Go to SIEM Settings > Feeds.
2. Click Add new.
3. In the Feed name field, enter a name for the feed (for example, ThreatConnect Logs).
4. Select Third Party API as the Source type.
5. Select the ThreatConnect as the log type.
6. Click Next.
7. Specify values for the following input parameters:
   • Username: enter the ThreatConnect Access ID to authenticate as.
   • Secret: enter the ThreatConnect Secret Key for the specified user.
   • API Hostname: Fully Qualified Domain Name (FQDN) of your ThreatConnect instance (for example, <myinstance>.threatconnect.com).
   • Owners: all owner names, where the owner identifies a collection of IOCs.
   • Asset namespace: the asset namespace.
   • Ingestion labels: the label applied to the events from this feed.
8. Click Next.
9. Review the feed configuration in the Finalize screen, and then click Submit.

Need more help? Get answers from Community members and Google SecOps professionals.