本頁提供 Google SecOps 資訊主頁管理總覽。你可以使用動態饋給管理 UI 或動態饋給管理 API 建立及管理動態饋給。
動態饋給管理 UI 是以動態饋給管理 API 為基礎建構而成。您可以使用 Google SecOps 資料動態饋給，從下列來源將記錄資料擷取至 Google SecOps 執行個體：
Google SecOps 支援的 Cloud Storage 服務，例如 Google Cloud Storage 和 Amazon S3
Google SecOps 支援的第三方資料來源，並透過 API 存取，例如 Microsoft 365
可使用 HTTP(S) 要求直接存取的檔案
支援 HTTPS 推送擷取的來源，例如 Webhook、Pub/Sub 和 Amazon Data Firehose。您可以透過這些來源的 HTTPS 端點推送記錄。
你建立的每個動態饋給都包含資料來源類型和記錄類型。
Google Cloud Storage、第三方 API 和可透過 HTTP 存取的檔案都是來源類型。Google Security Operations 支援的每種資料來源類型，也支援特定記錄類型。舉例來說，如果是 Google Cloud Storage 來源類型，Google SecOps 支援 Carbon Black 記錄類型和許多其他類型。支援的記錄類型清單因來源類型而異。
建立動態饋給時，請根據記錄類型指定來源類型、記錄類型、必要權限、驗證詳細資料和其他資訊。Google SecOps 的安全設計包括將使用者憑證 (例如您提供的憑證，讓 Google SecOps 資訊主動從第三方 API 擷取記錄資料) 儲存在 Secret Manager 中。
如果 Google SecOps 為記錄類型提供預設剖析器，系統會以 Google SecOps 統合資料模型 (UDM) 格式和原始記錄格式儲存擷取的記錄資料。
支援的來源類型和記錄類型
Google SecOps 支援下列來源類型：
動態饋給來源類型
說明
第三方 API
從第三方 API 擷取資料。
Pub/Sub
使用 Pub/Sub 推送訂閱項目擷取資料。
Google Cloud Storage
從 Google Cloud Storage 值區擷取資料。
Amazon Data Firehose
使用 Amazon Data Firehose 擷取資料。
Amazon S3
從 Amazon Simple Storage Service 值區擷取資料。
Amazon SQS
從 Amazon Simple Queue Service 佇列擷取資料，該佇列的項目指向儲存在 S3 中的檔案
Azure Blobstore
從 Azure Blob 儲存體擷取資料。
HTTP(S)
從可透過 HTTP(S) 要求存取的檔案擷取資料。請勿使用這個來源類型與第三方 API 互動。使用 Google SecOps 支援的第三方 API API動態饋給來源類型。
Webhook
使用 HTTPS Webhook 擷取資料。
您可以透過下列幾種方式查看支援的記錄類型清單：
Google SecOps 使用者介面：如要瞭解如何查看各來源類型支援的記錄類型清單，請參閱「新增動態饋給」。
[[["容易理解","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-09-04 (世界標準時間)。"],[[["\u003cp\u003eGoogle SecOps feed management allows ingestion of log data from various sources, including Cloud Storage services, third-party APIs, HTTP(S) accessible files, and HTTPS push sources.\u003c/p\u003e\n"],["\u003cp\u003eEach feed consists of a data source type and a log type, with examples of source types including Google Cloud Storage, third-party APIs, and HTTP(S) files, each supporting specific log types.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating a feed, users specify source type, log type, required permissions, and authentication details, with user credentials securely stored in Secret Manager.\u003c/p\u003e\n"],["\u003cp\u003eIf a default parser is available for the log type, ingested data is stored in both Google SecOps Unified Data Model (UDM) and raw log format.\u003c/p\u003e\n"],["\u003cp\u003eSupported log types can be viewed through the Google SecOps UI, the API reference documentation, or the Feed Schema API.\u003c/p\u003e\n"]]],[],null,["# Feed management overview\n========================\n\nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n\nThis page provides an overview of Google SecOps feed management.\nYou can create and manage feeds using the feed management UI or the feed management API.\n\nThe feed management UI is built on the feed management API. You can use Google SecOps\ndata feeds to ingest log data into your Google SecOps instance from the following sources:\n\n- Cloud Storage services that are supported by Google SecOps, such as Google Cloud Storage and Amazon S3\n- Third-party data sources that are supported by Google SecOps and accessed through API, such as Microsoft 365\n- Files accessible directly using HTTP(S) requests\n- Sources that support HTTPS push ingestion, such as webhooks, Pub/Sub, and Amazon Data Firehose. You can push logs using an HTTPS endpoint from these sources.\n\nEach feed that you create is composed of a data *source type* and a *log type*.\nGoogle Cloud Storage, third-party APIs, and HTTP-accessible files are examples\nof source types. For each data source type that Google SecOps supports, Google SecOps\nalso supports specific log types. For example, for the Google Cloud Storage source type,\nGoogle SecOps supports the Carbon Black log type and many others. The list of\nsupported log types varies by source type.\n\nWhen you create a feed, you specify the source type, log type, required permissions,\nauthentication details, and other information that is based on the log type. As part\nof its security design, Google SecOps stores user credentials (for example,\ncredentials that you provide so that a Google SecOps\nfeed can ingest log data from a third-party API) in [Secret Manager](/secret-manager).\n\nIf Google SecOps provides a [default parser](/chronicle/docs/ingestion/parser-list/supported-default-parsers)\nfor the log type, then the ingested log data is stored in both Google SecOps\nUnified Data Model (UDM) format and raw log format.\n\nSupported source types and log types\n------------------------------------\n\n| **Note:** To restrict access using Google Cloud public IP range, open a support ticket.\n\nGoogle SecOps supports the following source types: \n\nThere are several ways to view a list of supported log types:\n\n- **Google SecOps UI** : For information about how to view the list of supported\n log types for each source type, see [Add a feed](/chronicle/docs/administration/feed-management#add-new-feed).\n\n- **API reference documentation** : To view a list of supported log types for third-party API\n feeds, see [Configuration by log type](/chronicle/docs/reference/feed-management-api#api-log-types).\n\n- **Feed Schema API** : To view log types for any source type, you can also use the\n [Feed Schema API](/chronicle/docs/reference/feed-management-api#feed-schema-api-reference).\n\n| **Note:** The log types listed in third-party endpoints in the Feed UI are not listed in any other Cloud Storage options like AWS S3, AWS SQS, Google Cloud Storage, and Azure Blob Store.\n\nWhat's next\n-----------\n\n- Learn how to [create and manage feeds using the feed management UI](/chronicle/docs/administration/feed-management).\n- Learn how to [create and manage feeds using the Feed management API](/chronicle/docs/reference/feed-management-api).\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
