Cloud Next Generation Firewall

Related topics

• Cloud Next Generation Firewall depends on Certificate Authority Service From the official documentation: “Cloud NGFW uses [Certificate Authority Service](/certificate-authority-service) to generate intermediate certificate authorities (CAs).”
• firewall endpoint is part of Cloud Next Generation Firewall From the official documentation: “To enable Advanced malware sandbox in your network, you must set up multiple Cloud Next Generation Firewall (Cloud NGFW) components, including firewall endpoints, security profiles, and security profile groups.”
• Cloud Audit Logs works with Cloud Next Generation Firewall From the official documentation: “This document describes audit logging for Cloud Next Generation Firewall. Google Cloud services generate audit logs that record administrative and access activities within your Google Cloud resources. For more information about Cloud Audit Logs, see the following:”
• Cloud Next Generation Firewall depends on Certificate Manager From the official documentation: “Cloud NGFW uses [Certificate Manager](/certificate-manager/docs/overview) to create trust configs.”
• Cloud Next Generation Firewall works with Google SecOps From the official documentation: “This document provides guidance on how to integrate Palo Alto Next Gen Firewall with Google Security Operations.”
• Cloud Next Generation Firewall secures VPC network From the official documentation: “Cloud Next Generation Firewall (Cloud NGFW) governs traffic that passes through the VPC network.”
• firewall policy is part of Cloud Next Generation Firewall From the official documentation: “This page describes how to troubleshoot common issues that you might encounter when setting up Cloud Next Generation Firewall (Cloud NGFW) policies for Virtual Private Cloud (VPC) networks with the remote direct memory access (RDMA) over converged ethernet (RoCE) network profile.”
• intrusion detection and prevention service is part of Cloud Next Generation Firewall From the official documentation: “Intrusion detection and prevention service is offered as part of Cloud Next Generation Firewall Enterprise capabilities.”
• tags configures Cloud Next Generation Firewall From the official documentation: “Create resource tags to govern Cloud Next Generation Firewall rules”
• TLS inspection is part of Cloud Next Generation Firewall From the official documentation: “To learn more about TLS inspection in Cloud NGFW, see [TLS inspection overview](/firewall/docs/about-tls-inspection).”
• Cloud Storage works with Google SecOps From the official documentation: “Configure a feed in Google SecOps to ingest from Google Cloud Storage”
• Cloud SQL works with Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Certificate Authority Service works with Certificate Manager From the official documentation: “To integrate CA Service with Certificate Manager, follow these steps:”
• Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
• Identity and Access Management works with tags From the official documentation: “You can use tags and IAM conditions to conditionally grant role bindings to users in your hierarchy.”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• Certificate Authority Service works with Cloud Key Management Service From the official documentation: “CA Service is automatically configured to use Cloud Key Management Service for generating, storing, and utilizing CA signing keys.”
• 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.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• Certificate Authority Service works with Cloud Storage From the official documentation: “For a Google-managed Cloud Storage bucket, CA Service creates a Google-managed bucket in the same location as the CA.”
• Cloud Audit Logs works with Cloud Key Management Service From the official documentation: “Cloud Audit Logs for Cloud KMS in the Activity stream read like generic logs, and are not easily read by a human.”
• Cloud Audit Logs works with Cloud Storage From the official documentation: “Use Cloud Audit Logs to generate logs for API operations performed in Cloud Storage.”
• Cloud Key Management Service works with Cloud SQL From the official documentation: “Cloud KMS integrates with Cloud SQL.”
• VPC Service Controls secures Cloud SQL From the official documentation: “VPC Service Controls perimeters protect the Cloud SQL Admin API.”
• Certificate Authority Service depends on Cloud Key Management Service From the official documentation: “The CA then issues a certificate using the corresponding key in Cloud KMS to sign the certificate digest.”
• Certificate Authority Service works with VPC Service Controls From the official documentation: “Yes, CA Service supports VPC Service Controls.”
• Cloud SQL works with tags From the official documentation: “This page describes Google Cloud tags and how to use them with Cloud SQL.”
• Cloud SQL works with VPC network From the official documentation: “This zone is associated with the VPC network that's used to connect to the Cloud SQL instance through the Private Service Connect endpoint.”
• Google SecOps depends on Cloud Storage From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
• Identity and Access Management works with VPC Service Controls From the official documentation: “VPC Service Controls perimeters and Identity and Access Management (IAM) roles work together.”
• Certificate Authority Service works with Google SecOps From the official documentation: “This document provides guidance on how to integrate Symantec Content Analysis with Google SecOps.”
• Certificate Authority Service works with Identity and Access Management From the official documentation: “For information about how and which permissions are evaluated for each method, see the Identity and Access Management documentation for Certificate Authority Service.”
• 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.”
• Certificate Manager works with tags From the official documentation: “Certificate Manager uses the following resources that support Resource Manager tags:”
• Cloud Audit Logs works with Google SecOps From the official documentation: “Enable Cloud Audit Logs and configure the export of Cloud Audit Logs to Google SecOps.”
• 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 Key Management Service works with Google SecOps From the official documentation: “To control your encryption keys, you can use CMEKs in Cloud KMS with CMEK-integrated services, including Google SecOps, as follows:”
• Cloud Key Management Service depends on Identity and Access Management From the official documentation: “Whatever the mechanism, Cloud KMS resolves the provided credential to identify the principal (the entity which is authenticated and is authorizing the request), and calls IAM to see whether the principal is authorized to make the request and whether an audit log is written.”
• Cloud Key Management Service works with Identity and Access Management From the official documentation: “The Cloud KMS platform is integrated with [IAM](/iam/docs/overview) and [Cloud Audit Logs](/logging/docs/audit) so that you can manage permissions on individual keys and audit how they are used.”
• Cloud Key Management Service works with VPC Service Controls From the official documentation: “If you want your Dataproc Metastore service to run inside a [VPC Service Controls](/dataproc-metastore/docs/vpc-sc) perimeter, you must add the Cloud Key Management Service (Cloud KMS) API to the perimeter.”
• Cloud SQL depends on Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Cloud SQL works with Google SecOps From the official documentation: “This document describes how fields of Cloud SQL context logs map to Google Security Operations Unified Data Model (UDM) fields.”
• Cloud SQL works with VPC Service Controls From the official documentation: “Make sure that you configure VPC Service Controls so that the project that hosts the CA Service CA pool and CA<br>and the project that hosts Cloud SQL belong to the same service perimeter.”
• firewall endpoint is part of intrusion detection and prevention service From the official documentation: “Cloud NGFW intrusion detection and prevention service works by creating Google-managed zonal firewall endpoints that use packet intercept technology to transparently inspect the workloads for the configured threat signatures and protect them against threats.”
• firewall endpoint works with VPC network From the official documentation: “Associating a firewall endpoint with your VPC networks lets you help protect your VM instances and inspect traffic across multiple networks in the same zone without deploying separate inspection appliances.”
• firewall policy works with VPC network From the official documentation: “Remove the association between the firewall policy and the VPC network.”
• Google SecOps works with Identity and Access Management From the official documentation: “Test connectivity to the Identity and Access Management service with parameters provided at the integration configuration page in the Google Security Operations Marketplace tab.”
• Google SecOps works with Secure Web Proxy From the official documentation: “This document explains how to export and ingest Secure Web Proxy into Google Security Operations using Cloud Storage.”
• Google SecOps works with VPC Service Controls From the official documentation: “Configure Google Security Operations with VPC Service Controls so that Google SecOps can access resources and services outside its service perimeter.”
• Identity and Access Management secures Certificate Authority Service From the official documentation: “CA Service uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management secures Certificate Manager From the official documentation: “Understand the Identity and Access Management (IAM) predefined roles and permissions required to securely manage and control access to your Certificate Manager (2nd gen) resources.”
• Identity and Access Management secures Cloud Audit Logs From the official documentation: “IAM permissions and roles determine your ability to access audit logs data in the [Logging API](/logging/docs/reference/v2/rest), the [Logs Explorer](/logging/docs/view/logs-explorer-interface), and the [Google Cloud CLI](/logging/docs/reference/tools/gcloud-logging).”
• Identity and Access Management secures Cloud Key Management Service From the official documentation: “If you need to prevent a user from using a Cloud KMS resource during the time needed for propagation of an eventually consistent operation, remove the Identity and Access Management (IAM) permission for the resource.”
• Identity and Access Management secures Secure Web Proxy From the official documentation: “Secure Web Proxy uses Identity and Access Management (IAM) for authorization.”
• 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.”
• TLS inspection is part of Secure Web Proxy From the official documentation: “Secure Web Proxy provides an integrated TLS inspection service that lets you intercept and decrypt HTTPS traffic.”
• VPC Service Controls secures Certificate Manager From the official documentation: “VPC Service Controls provides additional security for Certificate Manager to help mitigate the risk of data exfiltration.”