本文档介绍了如何使用 API 将 Recorded Future IOC 日志注入到 Google Security Operations。解析器会将 JSON 格式的数据转换为统一数据模型 (UDM)。它会提取 IOC 详细信息,将其映射到 UDM 字段,根据严重程度对威胁进行分类,并使用时间戳和供应商信息丰富数据。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],null,["# Collect Recorded Future 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 document explains how to ingest Recorded Future IOC logs to Google Security Operations using an API. The parser transforms the data in JSON format into a unified data model (UDM). It extracts IOC details, maps them to UDM fields, categorizes threats based on criticality, and enriches the data with timestamps and vendor information.\n\nBefore you begin\n----------------\n\nMake sure you have the following prerequisites:\n\n- Google SecOps instance\n- Privileged access to a Recorded Future **Enterprise** account\n\nAcquire the Recorded Future API token\n-------------------------------------\n\n1. Sign in to [Recorded Future](https://app.recordedfuture.com/).\n2. Click your **avatar** in the top-right corner and select **User Settings**.\n3. In the navigation menu, click **API Access**.\n4. Click **Generate New API Token**.\n5. Copy the long string that appears (for example `RF-1234567890abcdef...`).\n - You can create more than one key; Provide a descriptive name such as **Google SecOps**.\n6. Copy and save the token in a secure location. The API token is not displayed again.\n\nSet up feeds\n------------\n\n1. Go to **SIEM Settings \\\u003e Feeds**.\n2. Click **+ Add New Feed**.\n3. In the **Feed name** field, enter a name for the feed (for example, `Recorded Future IOC`).\n4. Select **Third Party API** as the **Source type**.\n5. Select the **Recorded Future** log type.\n6. Click **Next**.\n7. Specify values for the following input parameters:\n - **Authentication HTTP Header**\n - `X-RFToken:\u003cyour-api_key\u003e`\n - Make sure to replace `\u003cyour-api_key\u003e` with the actual key copied in the previous step.\n - **Asset namespace** : The [asset namespace](/chronicle/docs/investigation/asset-namespaces).\n - **Ingestion labels**: The label applied to the events from this feed.\n8. Click **Next**.\n9. Review the feed configuration in the **Finalize** screen, and then click **Submit**.\n\nUDM Mapping Table\n-----------------\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]