Secure Web Proxy

Related topics

• Cloud NAT is an alternative to Secure Web Proxy From the official documentation: “To allow VMs to access the internet, use Secure Web Proxy if the traffic can be downloaded over HTTP(S) and you want to implement identity controls. Otherwise, use Cloud NAT.”
• Private Service Connect works with Secure Web Proxy From the official documentation: “Deploying Secure Web Proxy with Private Service Connect involves the following steps:”
• Admin Activity audit logs is part of Secure Web Proxy From the official documentation: “Secure Web Proxy writes two types of audit logs: Admin Activity audit logs and Data Access audit logs.”
• Certificate Manager works with Secure Web Proxy From the official documentation: “before you can configure a Secure Web Proxy gateway, you create one or more Certificate Manager certificates for the gateway to use.”
• Cloud Audit Logs works with Secure Web Proxy From the official documentation: “Cloud Audit Logs for Secure Web Proxy tracks the following activities and changes:”
• Cloud Logging works with Secure Web Proxy From the official documentation: “Secure Web Proxy integrates with Cloud Logging to record metrics and transaction logs.”
• Cloud Monitoring works with Secure Web Proxy From the official documentation: “Cloud Monitoring API metrics help you observe the performance, health, and usage of your Secure Web Proxy instances.”
• Compute Engine works with Secure Web Proxy From the official documentation: “Configure Secure Web Proxy to route all network traffic and ensure the routing complies with regulatory standards for Compute Engine instances and Google Kubernetes Engine (GKE) clusters.”
• Data Access audit logs is part of Secure Web Proxy From the official documentation: “Secure Web Proxy writes two types of audit logs: Admin Activity audit logs and Data Access audit logs.”
• GKE works with Secure Web Proxy From the official documentation: “Configure Secure Web Proxy to route all network traffic and ensure the routing complies with regulatory standards for Compute Engine instances and Google Kubernetes Engine (GKE) clusters.”
• global access is part of Secure Web Proxy From the official documentation: “When you enable global access for a Secure Web Proxy instance, clients can connect from *any* region, not only the region where the proxy is deployed.”
• Secure Web Proxy depends on Certificate Authority Service From the official documentation: “If you <a href="/secure-web-proxy/docs/enable-tls-inspection">enable TLS inspection</a> for your proxy, then you must also include the <a href="/certificate-authority-service/docs/reference/rest">Certificate Authority Service API</a> (<code>privateca.googleapis.com</code>) in…”
• Secure Web Proxy depends on Certificate Manager From the official documentation: “If you provision your proxy with a <a href="/certificate-manager/docs/certificates">certificate</a>, then you must also include the Certificate Manager API (<code>certificatemanager.googleapis.com</code>) in your service perimeter.”
• Secure Web Proxy secures Compute Engine From the official documentation: “Configure Secure Web Proxy to route all network traffic and ensure the routing complies with regulatory standards for Compute Engine instances and Google Kubernetes Engine (GKE) clusters.”
• Secure Web Proxy secures GKE From the official documentation: “Configure Secure Web Proxy to route all network traffic and ensure the routing complies with regulatory standards for Compute Engine instances and Google Kubernetes Engine (GKE) clusters.”
• VPC Service Controls secures Secure Web Proxy From the official documentation: “VPC Service Controls provides additional security for Secure Web Proxy to help mitigate the risk of data exfiltration.”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Certificate Authority Service works with Cloud Service Mesh From the official documentation: “Configure Cloud Service Mesh to use CA Service”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• Data Access audit logs is part of Cloud Audit Logs From the official documentation: “You need to turn on [Data Access audit logs](/logging/docs/audit#data-access) for login tracking.”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Admin Activity audit logs is part of Cloud Audit Logs From the official documentation: “The following types of audit logs are available for Assured OSS: - Admin Activity audit logs”
• Cloud SQL works with Private Service Connect From the official documentation: “You can use Private Service Connect to connect to a Cloud SQL instance from multiple VPC networks.”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• Cloud SQL works with Compute Engine From the official documentation: “Create a Compute Engine VM Instance to host a sample web app that connects to Cloud SQL.”
• Private Google Access is an alternative to Private Service Connect From the official documentation: “Private Service Connect to access Google APIs is an alternative to using Private Google Access or the public domain names for Google APIs.”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
• Certificate Authority Service works with Certificate Manager From the official documentation: “To integrate CA Service with Certificate Manager, follow these steps:”
• Cloud Logging works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh stores the dry-run results to Cloud Logging in the following labels:”
• Cloud Monitoring works with Cloud Service Mesh From the official documentation: “Mesh telemetry is no longer automatically ingested into Cloud Monitoring.”
• 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 Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• Cloud Service Mesh works with VPC Service Controls From the official documentation: “You can now use VPC Service Controls with Cloud Service Mesh.”
• BigQuery works with Gemini Enterprise Agent Platform From the official documentation: “The BigQuery dataset stores all versions for the associated Gemini Enterprise Agent Platform dataset.”
• Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
• Cloud Service Mesh depends on Certificate Authority Service From the official documentation: “Cloud Service Mesh service security depends on the CA Service integration with GKE.”
• Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
• Certificate Authority Service works with GKE From the official documentation: “Cloud Service Mesh service security depends on the CA Service integration with GKE.”
• Certificate Authority Service works with Cloud SQL From the official documentation: “Cloud SQL hosts and manages the root CA and subordinate server CAs on Google Cloud Certificate Authority Service (CA Service).”
• Cloud Audit Logs works with VPC Service Controls From the official documentation: “VPC Service Controls integrate with Cloud Audit Logs to monitor access to the control plane.”
• Cloud NAT is an alternative to Private Google Access From the official documentation: “If you disable public IP addresses, you must set up Private Google Access or Cloud NAT on your network.”
• Cloud Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• Cloud SQL works with GKE From the official documentation: “[From an application running on GKE](/sql/docs/postgres/connect-kubernetes-engine)”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Service Mesh works with Compute Engine From the official documentation: “You can run applications on the following platforms and adopt them into a global service mesh that Cloud Service Mesh configures. | Feature | Supported | | --- | --- | | Compute Engine virtual machine (VM) instances | ✔ |”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• Private Service Connect works with VPC Service Controls From the official documentation: “VPC Service Controls that use Private Service Connect”
• VPC Service Controls secures Cloud SQL From the official documentation: “VPC Service Controls perimeters protect the Cloud SQL Admin API.”
• VPC Service Controls secures Gemini Enterprise Agent Platform From the official documentation: “The API for Agent Platform can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
• Admin Activity audit logs works with GKE From the official documentation: “Admin Activity audit logs are automatically enabled for GKE clusters.”
• Certificate Authority Service works with VPC Service Controls From the official documentation: “Yes, CA Service supports VPC Service Controls.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “If a log entry matches the filter of the alerting policy, then Cloud Logging extracts labels and forwards the data to Cloud Monitoring.”
• Cloud Logging works with Private Google Access From the official documentation: “Cloud Logging captures all API requests made from VM instances in subnets that have Private Google Access enabled.”
• Cloud Monitoring works with Cloud NAT From the official documentation: “Metrics for Cloud NAT are batched and exported to Monitoring every one minute.”
• Cloud Monitoring works with Compute Engine From the official documentation: “Many Google services like Compute Engine send telemetry to Cloud Monitoring.”
• Cloud NAT works with Compute Engine From the official documentation: “A Cloud NAT gateway provides outgoing connectivity for Compute Engine virtual machine (VM) instances without external IP addresses.”