feed

Related topics

• feed is part of Google SecOps From the official documentation: “Configure a feed in Google SecOps”
• feed is part of Google Security Operations From the official documentation: “### Configure a feed in Google SecOps”
• feed works with Pub/Sub From the official documentation: “After creating a feed, you receive notifications through [Pub/Sub](/pubsub/docs) whenever the specified assets change.”
• API key configures feed From the official documentation: “Create an API key for the webhook feed”
• BigQuery works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze BigQuery data.”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
• Cloud Storage works with Google SecOps From the official documentation: “Configure a feed in Google SecOps to ingest from Google Cloud Storage”
• Google SecOps depends on API key From the official documentation: “Chronicle requires an API key for authentication.”
• Pub/Sub works with Secret Manager From the official documentation: “Receive notifications via Pub/Sub when Secret Manager resources change.”
• Pub/Sub works with Sensitive Data Protection From the official documentation: “Watch the Pub/Sub topic until the DLP job finishes”
• BigQuery is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Cloud Storage works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze a file on GCS.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• API key secures Google SecOps From the official documentation: “Chronicle requires an API key for authentication. Create a restricted API key in the Google Cloud Console.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Security Command Center works with Sensitive Data Protection From the official documentation: “Sending Sensitive Data Protection scan results to Security Command Center”
• service account is part of Google SecOps From the official documentation: “Each Google SecOps instance has a unique service account.”
• BigQuery works with Google SecOps From the official documentation: “Google SecOps exports the following categories of data to your BigQuery project:”
• Cloud Storage works with Google Security Operations From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
• BigQuery works with Google Security Operations From the official documentation: “This document explains how to integrate BigQuery with Google Security Operations.”
• BigQuery works with Security Command Center From the official documentation: “Security Command Center supports discovery and inventory of BigQuery datasets.”
• Cloud Storage works with service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
• Google SecOps depends on Cloud Storage From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
• Google SecOps works with Security Command Center From the official documentation: “This document explains how to integrate Security Command Center with Google Security Operations.”
• Google SecOps depends on service account From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket. You must grant this service account access to your bucket.”
• Pub/Sub works with Security Command Center From the official documentation: “This page explains how to use the Security Command Center API to enable finding notifications for Pub/Sub.”
• Pub/Sub works with service account From the official documentation: “5. Creates a service account to represent the Pub/Sub subscription identity.”
• Secret Manager works with service account From the official documentation: “The service account can access the secret data.”
• API key works with Google SecOps From the official documentation: “Google SecOps requires an API key for authentication. Create a restricted API key in the Google Cloud Console.”
• API key secures Google Security Operations From the official documentation: “- `API_KEY`: the API key to authenticate to Google Security Operations.”
• API key is an alternative to service account From the official documentation: “For Cloud Translation - Basic, you can send authenticated requests by using API keys or service accounts.”
• BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
• BigQuery works with service account From the official documentation: “The service account can be used by services, such as Cloud Run, to read and modify data in the BigQuery dataset.”
• Cloud Storage is an alternative to Secret Manager From the official documentation: “Your provisioning tools might need to be adapted to use Google Cloud Storage or Secret Manager to read such custom configuration lists.”
• Google SecOps works with Pub/Sub From the official documentation: “This document explains how to integrate Pub/Sub with Google Security Operations.”
• Google SecOps works with Secret Manager From the official documentation: “As part of its security design, Google SecOps stores user credentials (for example, credentials that you provide so that a Google SecOps feed can ingest log data from a third-party API) in [Secret Manager](/secret-manager).”
• Google SecOps depends on Security Command Center From the official documentation: “Google SecOps requires [Security Command Center](/security-command-center/docs/security-command-center-overview) (Standard or Premium) for asset metadata ingestion.”
• Google SecOps is an alternative to Security Command Center From the official documentation: “Verify that you can correlate various events across your systems. Consider tools such as Google SecOps or Security Command Center.”
• Google SecOps works with Sensitive Data Protection From the official documentation: “You can export your Sensitive Data Protection data to Google SecOps.”
• Google Security Operations works with Secret Manager From the official documentation: “This document explains how to integrate Secret Manager with Google Security Operations.”
• Google Security Operations works with Security Command Center From the official documentation: “A typical deployment consists of Security Command Center and the Google Security Operations feed configured to send logs to Google Security Operations.”
• Google Security Operations works with Sensitive Data Protection From the official documentation: “This document explains how to ingest Forcepoint DLP logs to Google Security Operations using Bindplane.”
• Secret Manager secures API key From the official documentation: “When using API keys for authentication to Google Cloud, you can securely store your API keys with the [Secret Manager](/secret-manager/docs/overview) service of Google Cloud.”
• Security Command Center secures BigQuery From the official documentation: “Security Command Center analyzes various logs for potential threats that affect BigQuery resources.”
• Security Command Center secures Cloud Storage From the official documentation: “Security Command Center analyzes various logs for potential threats that affect Cloud Storage resources.”
• Sensitive Data Protection secures BigQuery From the official documentation: “To help meet compliance requirements, use Sensitive Data Protection to inspect your BigQuery tables and to help protect your sensitive data.”
• service account depends on Cloud Storage From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket. You must grant this service account access to your bucket.”