[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-04-02 UTC。"],[[["This 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."],["The process requires privileged access to both Google SecOps and ThreatConnect, followed by configuring an API user within ThreatConnect to generate necessary authentication credentials."],["The 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."],["Setting 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."],["The 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."]]],[]]