service perimeter

Related topics

• service perimeter is part of VPC Service Controls From the official documentation: “Learn how to set up a service perimeter using VPC Service Controls.”
• VPC Service Controls configures service perimeter From the official documentation: “VPC Service Controls lets you set up a service perimeter to guard against data exfiltration.”
• service perimeter secures Artifact Registry From the official documentation: “2. Add the Container Registry or Artifact Registry service to the list of services you want to protect using the service perimeter.”
• folder works with service perimeter From the official documentation: “When you specify a folder as a protected resource when you [create a perimeter](/vpc-service-controls/docs/create-service-perimeters), VPC Service Controls includes all resources within that folder, such as projects and nested folders.”
• host project is part of service perimeter From the official documentation: “**Note:** If you're using [Shared VPC](/vpc/docs/shared-vpc), then you must include the [host project](/vpc-service-controls/docs/troubleshooting#shared_vpc) in a service perimeter along with any projects that belong to the Shared VPC.”
• metrics scope is part of service perimeter From the official documentation: “Using VPC Service Controls, you can add a [metrics scope](/monitoring/settings) to a Service Perimeter that protects Cloud Monitoring resources and services from requests originating outside the perimeter.”
• service perimeter secures Artifact Analysis From the official documentation: “# Protect Artifact Analysis in a service perimeter”
• service perimeter secures BigQuery From the official documentation: “Dataform and BigQuery must be restricted by the same VPC Service Controls service perimeter.”
• service perimeter secures Cloud Monitoring From the official documentation: “Using VPC Service Controls, you can add a [metrics scope](/monitoring/settings) to a Service Perimeter that protects Cloud Monitoring resources and services from requests originating outside the perimeter.”
• service perimeter secures Cloud Storage From the official documentation: “Additionally, the Google Cloud console interface for the BigQuery and Cloud Storage services that you protected with the perimeter might become partially or fully inaccessible.”
• service perimeter secures Compute Engine From the official documentation: “This tutorial shows you how to protect Compute Engine using a service perimeter and troubleshoot an ingress violation to allow authorized access to Compute Engine.”
• service perimeter secures Database Center From the official documentation: “First, you select the Database Center project that you want the service perimeter to protect, and then you create and manage the service perimeter.”
• service perimeter secures host project From the official documentation: “The service perimeter `perimeter-1` protects the entire host project and service projects.”
• service perimeter works with VPC network From the official documentation: “For information about VPC networks limitations when you use VPC networks in service perimeters, see [VPC network limitations](/vpc-service-controls/docs/vpc-perimeters-management#limitations).”
• service perimeter secures VPC network From the official documentation: “This perimeter protects the VPC network `VPC1` and the service project `service-project-1`.”
• service perimeter works with VPC Service Controls From the official documentation: “Protect resources and data by [creating a service perimeter](/vpc-service-controls/docs/create-service-perimeters) with VPC Service Controls.”
• 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: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• Cloud Run works with Cloud SQL From the official documentation: “Connecting from Cloud Run (fully managed) to Cloud SQL”
• Cloud SQL works with Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
• Artifact Analysis works with Artifact Registry From the official documentation: “Artifact Analysis scans new images when they're uploaded to Artifact Registry.”
• Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
• Cloud SQL works with GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• Cloud Logging works with Cloud SQL From the official documentation: “Database Migration Service and Cloud SQL use Cloud Logging.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Storage works with Compute Engine From the official documentation: “For example, you can create a service account that your Compute Engine instances use to access objects stored in Cloud Storage buckets.”
• VPC Service Controls secures Artifact Registry From the official documentation: “If your VPC Service Controls settings are blocking access to Artifact Registry, you must add the Artifact Registry service to the service perimeter of your VPC Service Controls.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Logging works with Security Command Center From the official documentation: “Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• Artifact Analysis secures Cloud Run From the official documentation: “To identify and mitigate security risks in the container images, use Artifact Analysis to automatically run vulnerability scans.”
• Artifact Analysis works with VPC Service Controls From the official documentation: “VPC Service Controls provides support for Artifact Analysis.”
• Artifact Registry works with GKE From the official documentation: “In the next tutorial, you deploy those images from the Artifact Registry repository to a GKE cluster:”
• Artifact Registry works with Security Command Center From the official documentation: “Security Command Center integrates these AI findings with Artifact Registry vulnerabilities and IAM analysis for a comprehensive view of your fleet.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Private Google Access From the official documentation: “Private Google Access lets you access BigQuery without using public IPs.”
• BigQuery works with Security Command Center From the official documentation: “Security Command Center supports discovery and inventory of BigQuery datasets.”
• Cloud Logging is an alternative to Cloud Storage From the official documentation: “Instead, they are routed to either Cloud Storage (recommended) or Cloud Logging, depending on your organization's configuration.”
• Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• Cloud Monitoring works with Cloud SQL From the official documentation: “You can also get more details by viewing the Cloud Monitoring logs for your Cloud SQL destination instance.”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Cloud Run works with VPC network From the official documentation: “Send outbound traffic from Cloud Run directly to a VPC network with low latency and high throughput.”
• Cloud SQL works with Database Center From the official documentation: “Database Center supports Cloud SQL for MySQL, Cloud SQL for PostgreSQL, and AlloyDB.”
• metrics scope is part of Cloud Monitoring From the official documentation: “Monitoring organizes itself around metrics scopes that let you view and monitor metrics for one or more Google Cloud projects.”
• VPC Service Controls secures Compute Engine From the official documentation: “To further protect your Compute Engine resources, you can protect them using [VPC Service Controls](/vpc-service-controls/docs/overview).”
• Artifact Analysis secures Artifact Registry From the official documentation: “Turn on Artifact Analysis, which allows for security scanning, for your Artifact Registry repository.”
• Artifact Analysis works with Cloud Storage From the official documentation: “Artifact Analysis stores your SBOMs in Cloud Storage in your Google Cloud project.”
• Artifact Registry works with Cloud Logging From the official documentation: “Artifact Registry sends the following types of audit log data to Cloud Logging:”