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 the following prerequisites:
Google Security Operations instance.
Privileged access to ThreatConnect.
Configure API User on ThreatConnect
Sign in to ThreatConnect.
Go to Settings>Org Settings.
Go to the Membership tab in the Organization Settings.
Click Create API User.
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.
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.
Click Save.
Set up feeds
To configure a feed, follow these steps:
Go to SIEM Settings>Feeds.
Click Add New Feed.
On the next page, click Configure a single feed.
In the Feed name field, enter a name for the feed; for example, ThreatConnect Logs.
Select Third Party API as the Source type.
Select the ThreatConnect as the log type.
Click Next.
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.
Click Next.
Review the feed configuration in the Finalize screen, and then click Submit.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eThis content describes how to collect and ingest ThreatConnect IOC logs into Google Security Operations (SecOps), utilizing a parser that transforms the data into the Unified Data Model (UDM) format.\u003c/p\u003e\n"],["\u003cp\u003eThe process requires privileged access to both Google SecOps and ThreatConnect, followed by configuring an API user within ThreatConnect to generate necessary authentication credentials.\u003c/p\u003e\n"],["\u003cp\u003eThe configuration of an API user involves defining roles such as "Api User" or "Exchange Admin," setting user details, and saving the generated Access ID and Secret Key for later use in Google SecOps.\u003c/p\u003e\n"],["\u003cp\u003eSetting up a feed in Google SecOps involves specifying the ThreatConnect log source, providing the API credentials and instance details, and defining parameters such as Owners and Asset namespace for the log ingestion.\u003c/p\u003e\n"],["\u003cp\u003eThe ThreatConnect parser is able to handle various types of IOC's such as Host, Address, File, and URL, and will map them to the UDM equivalent while categorizing the threats based on keywords found within the log data.\u003c/p\u003e\n"]]],[],null,["# Collect ThreatConnect IOC logs\n==============================\n\nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n| **Note:** This feature is covered by [Pre-GA Offerings Terms](https://chronicle.security/legal/service-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 SecOps Technical Support Service guidelines](https://chronicle.security/legal/technical-support-services-guidelines/) and the [Google SecOps Service Specific Terms](https://chronicle.security/legal/service-terms/).\n\nThis 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.\n\nBefore you begin\n----------------\n\nEnsure that you have the following prerequisites:\n\n- Google Security Operations instance.\n- Privileged access to ThreatConnect.\n\nConfigure API User on ThreatConnect\n-----------------------------------\n\n1. Sign in to ThreatConnect.\n2. Go to **Settings** \\\u003e **Org Settings**.\n3. Go to the **Membership** tab in the **Organization Settings**.\n4. Click **Create API User**.\n5. Fill out the fields on the API User Administration window:\n\n - **First Name**: enter the API user's first name.\n - **Last Name**: enter the API user's last name\n - **System Role** : select the **Api User** or **Exchange Admin** System role.\n\n | **Note:** Available System roles for API users include the following: \n | 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. \n | Exchange Admin: API users with this role can use all ThreatConnect v2 and v3 API endpoints, including the v3 AP.\n - **Organization Role**: select the API user's Organization role.\n - **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.\n - **Disabled**: click the checkbox to disable an API user's account in the event that the Administrator wants to retain log integrity.\n - Copy and save the **Access ID** and **Secret Key**.\n6. Click **Save**.\n\nSet up feeds\n------------\n\nTo configure a feed, follow these steps:\n\n1. Go to **SIEM Settings** \\\u003e **Feeds**.\n2. Click **Add New Feed**.\n3. On the next page, click **Configure a single feed**.\n4. In the **Feed name** field, enter a name for the feed; for example, **ThreatConnect Logs**.\n5. Select **Third Party API** as the **Source type**.\n6. Select the **ThreatConnect** as the log type.\n7. Click **Next**.\n8. Specify values for the following input parameters:\n - **Username**: enter the ThreatConnect Access ID to authenticate as.\n - **Secret**: enter the ThreatConnect Secret Key for the specified user.\n - **API Hostname** : Fully Qualified Domain Name (FQDN) of your ThreatConnect instance (for example, `\u003cmyinstance\u003e.threatconnect.com`).\n - **Owners**: all owner names, where the owner identifies a collection of IOCs.\n9. Click **Next**.\n10. Review the feed configuration in the **Finalize** screen, and then click **Submit**.\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]