[
  {
    "date": "2026-11-19",
    "title": "Google Cloud Daily Brief: 7 service updates",
    "summaryMarkdown": "### Application Integration\n- **Feature & Security Summary**: Security patch addressing Deserialization of Untrusted Data in execution parameter handling, effective September 22, 2026. Introduced to prevent remote code execution and data tampering risks in integration workflows; enhances input validation and serialization controls for compliance with secure coding standards. **Terraform Availability**: Supported in `hashicorp/google` provider (resource: `google_integration_connectors_connection`) from v4.50+, fully supported in v5.0+ - [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/integration_connectors)\n\n### Apigee\n- **Feature & Security Summary**: Security update mitigating CVE-2026-114938 (Bug ID 586658318) in Apigee X runtime. Addresses a high-severity vulnerability to protect API proxies and runtime environments from exploitation, strengthening zero-trust API management and regulatory compliance. **Terraform Availability**: Supported in `hashicorp/google` provider (resource: `google_apigee_instance`) from v4.0+, fully supported in v5.0+ - [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apigee_instance)\n\n### Cloud Service Mesh\n- **Feature & Security Summary**: Release of Cloud Service Mesh 1.31.3-asm.13 (Envoy v1.39.7-dev), 1.30.7-asm.13 (Envoy v1.38.10-dev), and 1.29.10-asm.8 (Envoy v1.37.10-dev) with CVE fixes and pilot-agent stability improvements. Delivers critical vulnerability remediations and enhanced observability for service-to-service communication, bolstering mTLS, authorization policies, and resilience in zero-trust architectures. **Terraform Availability**: Supported in `hashicorp/google` provider (resource: `google_gke_hub_feature`) from v1.29.10-asm.8, with latest features in v1.31.3-asm.13 - [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gke_hub_feature)\n\n### Dataflow\n- **Feature & Security Summary**: Eager watermark advancement GA for Streaming Engine jobs. Allows precise control over allowed lateness in windowed aggregations and stateful processing; introduced to improve pipeline correctness, reduce data loss risks, and support secure, compliant real-time analytics. **Terraform Availability**: Supported in `hashicorp/google` provider (resource: `google_dataflow_job`) from v4.50+, fully supported in v5.0+ - [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/dataflow_job)\n\n### Backup for GKE\n**Feature & Security Summary:** The addition of Backup for GKE resource types to Cloud Asset Inventory APIs was introduced to deliver centralized visibility, discovery, and governance of backup resources across an organization. It works by feeding GKE backup plans, backups, and restore plans into CAI feeds, enabling policy enforcement, audit logging, and compliance reporting. Key security/compliance value includes improved data protection posture, simplified regulatory audits, and prevention of shadow backup operations.\n**Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) using `google_gke_backup_backup_plan` (and related resources) since version 4.50+, with full compatibility in 5.0+. [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gke_backup_backup_plan)\n\n### Model Armor\n**Feature & Security Summary:** Support for custom organization policies to enforce Model Armor FloorSetting filters was introduced to strengthen responsible AI guardrails at the organization level. It works by allowing admins to define and enforce baseline protections against prompt injection, jailbreak attempts, and unsafe content via policy constraints that cannot be overridden by projects. Key security/compliance value includes proactive mitigation of AI-specific threats, consistent application of responsible AI principles, and alignment with governance frameworks.\n**Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) using `google_model_armor_floor_setting` since version 5.45.0. [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/model_armor_floor_setting)\n\n### Workbench\n**Feature & Security Summary:** Preparation of JupyterLab extension settings at build time along with installation of latest upstream dependency packages was introduced to reduce restart latency and improve reliability of JupyterLab 4 images. It works by baking configuration and dependencies into the image build pipeline, resulting in faster cold starts and more predictable runtime behavior. Key security/compliance value includes reduced exposure windows during restarts, consistent secure configurations, and easier maintenance of up-to-date dependency supply chains.\n**Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) using `google_notebooks_instance` since version 4.0+, with full compatibility in 5.0+. [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/notebooks_instance)",
    "updates": [
      {
        "serviceName": "Application Integration",
        "serviceId": "application-integration",
        "category": "Integration",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=application-integration#November_18_2026"
      },
      {
        "serviceName": "Apigee",
        "serviceId": "apigee",
        "category": "API Management",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=apigee-x#November_17_2026"
      },
      {
        "serviceName": "Cloud Service Mesh",
        "serviceId": "cloud-service-mesh",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-service-mesh#November_17_2026"
      },
      {
        "serviceName": "Dataflow",
        "serviceId": "dataflow",
        "category": "Data Analytics",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=dataflow#November_17_2026"
      },
      {
        "serviceName": "Backup for GKE",
        "serviceId": "gkebackup.googleapis.com",
        "category": "Backup and Recovery",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-asset-inventory#November_17_2026"
      },
      {
        "serviceName": "Model Armor",
        "serviceId": "modelarmor",
        "category": "AI and Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=model-armor#November_17_2026"
      },
      {
        "serviceName": "Workbench",
        "serviceId": "workbench",
        "category": "AI and Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=agent-platform-workbench#November_16_2026"
      }
    ]
  },
  {
    "date": "2026-11-18",
    "title": "Google Cloud Daily Brief: 9 service updates",
    "summaryMarkdown": "### Cloud Tasks\n- **Feature & Security Summary**: Support for migrating App Engine push queues to Cloud Tasks using the bundled services SDK is now GA. This simplifies modernization of legacy App Engine task queues to a fully managed, scalable queuing service with improved reliability, monitoring, and IAM-based access controls. Key security value includes least-privilege IAM integration, audit logging, and separation of queue management from application logic, enhancing compliance with SOC2, ISO 27001, and PCI-DSS. Terraform support available in `hashicorp/google` provider (resource: `google_cloud_tasks_queue`, versions 1.0+ / 5.0+, [documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_tasks_queue)).\n\n### App Engine\n- **Feature & Security Summary**: Support for migrating App Engine push queues to Cloud Tasks by updating the bundled services SDK is now in General Availability (GA) for Java standard environment. This update enables seamless transition without rewriting queue logic, reducing operational risk while inheriting Cloud Tasks security features such as encryption at rest, VPC Service Controls, and fine-grained IAM. Terraform support available in `hashicorp/google` provider (resource: `google_app_engine_application`, versions 1.0+ / 5.0+, [documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_application)).\n- **Feature & Security Summary**: Support for migrating App Engine push queues to Cloud Tasks by updating the bundled services SDK is now in General Availability (GA) for PHP standard environment. The GA release removes previous preview limitations, delivering consistent security posture across languages with centralized queue policy enforcement and comprehensive Cloud Audit Logs. Terraform support available in `hashicorp/google` provider (resource: `google_app_engine_application`, versions 1.0+ / 5.0+, [documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_application)).\n- **Feature & Security Summary**: GA support for migrating App Engine push queues to Cloud Tasks using the bundled services SDK (no code changes required). This capability accelerates secure workload modernization on Google Cloud by leveraging managed identity, automatic retries with exponential backoff, and dead-letter queue isolation for improved resilience and compliance. Terraform support available in `hashicorp/google` provider (resource: `google_app_engine_application`, versions 1.0+ / 5.0+, [documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_application)).\n\n### Access Context Manager\n- **Feature & Security Summary**: Extended session length for Workforce Identity Federation is now generally available (GA) for OAuth apps owned by Google Cloud projects. Sessions can be configured to last up to 90 days using project scopes. This feature was introduced to reduce frequent re-authentication friction for workforce users while maintaining strong identity controls; it works by allowing administrators to define longer-lived session durations at the project scope level, improving usability without sacrificing security boundaries. Key security/compliance value includes better alignment with enterprise SSO policies, reduced authentication fatigue, and support for regulated environments requiring tunable session lifetimes. **Terraform support**: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) since version 4.0+, with full compatibility in 5.0+; see [access_context_manager_access_level](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/access_context_manager_access_level).\n\n### BigQuery\n- **Feature & Security Summary**: GA support for cross-region dataset replication management and failover reservations via BigQuery REST API, plus GA of AI.RANK function. Introduced to enable resilient, multi-region analytics workloads with simplified disaster recovery orchestration; replication management allows declarative control of dataset copies across regions, while failover reservations ensure capacity during cutovers. The AI.RANK function adds native ranking capabilities for AI/ML-driven insights. Security/compliance value centers on improved data availability, auditability of replication events, and support for sovereignty and disaster-recovery compliance requirements. **Terraform support**: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) since version 4.0+, with full compatibility in 5.0+; see [bigquery_dataset](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_dataset).\n\n### Backup and DR\n- **Feature & Security Summary**: Support for automating resource protection for Compute Engine instances and disks at scale using auto-protection policies and resource labels is now GA. This capability was introduced to reduce manual operational overhead and ensure consistent backup coverage across large estates; it works by evaluating resource labels in real time to automatically enroll matching VMs and disks into protection plans. Key security/compliance value includes consistent data protection posture, reduced human error, and streamlined adherence to backup governance and recovery-time objectives. **Terraform support**: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) since version 4.50+, with full compatibility in 5.0+; see [backup_dr_backup_plan](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/backup_dr_backup_plan).\n\n### Cloud Monitoring\n- **Feature & Security Summary**: Ops Agent v2.72.0 - Logging pipelines now processed by Metric Agent service (duplicated logs expected during upgrade). The update was introduced to unify logging and metrics collection pipelines for improved efficiency and reduced agent footprint; the Metric Agent service now handles both workloads, with a temporary duplication of logs during the upgrade window to ensure continuity. Security/compliance value includes more reliable observability of security events, better correlation between logs and metrics, and strengthened monitoring of compliance-related audit trails. **Terraform support**: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) since version 3.50+, with full compatibility in 5.0+; see [monitoring_metric_descriptor](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/monitoring_metric_descriptor).\n\n### Daily Summary - November 2025\n\n#### Cloud Logging\n- **Feature & Security Summary**: Ops Agent v2.72.0+ now routes all supported logging pipelines through the Metric Agent service. This change was introduced to improve metric collection consistency, reduce agent complexity, and enable unified observability. During the upgrade a temporary period of log duplication is expected as both legacy and new pipelines may emit the same entries until the transition completes. From a security and compliance perspective this strengthens auditability by ensuring logs flow through a more reliable and centrally managed path, reducing blind spots and supporting consistent application of log-based metrics for security monitoring, alerting, and regulatory compliance (e.g., SOC 2, PCI-DSS, HIPAA). **Terraform support**: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) via `google_logging_metric` (and related resources) since version 2.0+, with full compatibility in 5.0+ ([provider documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/logging_metric)).",
    "updates": [
      {
        "serviceName": "Cloud Tasks",
        "serviceId": "cloudtasks",
        "category": "Application Integration",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-python#November_17_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "appengine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-java#November_17_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "appengine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-php#November_17_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "appengine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-go#November_17_2026"
      },
      {
        "serviceName": "Access Context Manager",
        "serviceId": "accesscontextmanager",
        "category": "Security and Identity",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=access-context-manager#November_17_2026"
      },
      {
        "serviceName": "BigQuery",
        "serviceId": "bigquery",
        "category": "Analytics",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigquery#November_17_2026"
      },
      {
        "serviceName": "Backup and DR",
        "serviceId": "backupdr",
        "category": "Backup and Disaster Recovery",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=backup-and-dr#November_17_2026"
      },
      {
        "serviceName": "Cloud Monitoring",
        "serviceId": "monitoring",
        "category": "Operations",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-monitoring#November_17_2026"
      },
      {
        "serviceName": "Cloud Logging",
        "serviceId": "logging",
        "category": "Operations",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-logging#November_17_2026"
      }
    ]
  },
  {
    "date": "2026-11-17",
    "title": "Google Cloud Daily Brief: 9 service updates",
    "summaryMarkdown": "### App Hub (Management Tools)\n**Feature & Security Summary:** App Hub now supports multi-regional applications in the us and eu multi-regions. This allows grouping of multi-regional and regional resources across regions within a single geographic boundary, simplifying management and improving resilience. The feature enhances compliance by enforcing geographic data residency boundaries. [Release Notes](https://docs.cloud.google.com/release-notes?product=app-hub#November_16_2026)\n\n**Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) via `google_apphub_application` resource since version 5.20.0 (fully supported in 5.35.0). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apphub_application)\n\n### Cloud Load Balancing (Networking)\n**Feature & Security Summary:** TLS post-quantum key exchange is now enabled by default (Phase 2) for Application Load Balancers and external proxy Network Load Balancers. This strengthens protection against future quantum computing attacks on TLS handshakes. Opt-out is available through SSL policy configuration, providing defense-in-depth for cryptographic agility and compliance with emerging post-quantum standards. [Release Notes](https://docs.cloud.google.com/release-notes?product=cloud-load-balancing#November_16_2026)\n\n**Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) via `google_compute_ssl_policy` resource since version 4.0+ (fully supported in 5.0+). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_ssl_policy)\n\n### Bigtable (Databases)\n**Feature & Security Summary:** New in-memory tier monitoring charts grouped by cluster/instance (Enterprise Plus Preview) and Bigtable migration agent skill for HBase migrations (Preview). These capabilities improve observability of memory usage and simplify secure, controlled migration from HBase, reducing operational risk and supporting compliance through better visibility and auditability. [Release Notes](https://docs.cloud.google.com/release-notes?product=bigtable#November_16_2026)\n\n**Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) via `google_bigtable_instance` resource since version 1.20.0 (fully supported in 5.48.0). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigtable_instance)\n\n### Batch (Compute)\n**Feature & Security Summary:** Instance flexibility for Batch jobs is now generally available. This enables improved resource scheduling across multiple machine types and better Spot VM utilization, increasing cost efficiency while maintaining workload isolation and security boundaries. [Release Notes](https://docs.cloud.google.com/release-notes?product=batch#November_16_2026)\n\n**Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) via `google_batch_job` resource since version 4.50+ (fully supported in 5.0+). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/batch_job)\n\n### Cloud Trace\n**Feature & Security Summary:** Cloud Trace now supports 200 views per trace scope with a project-to-_AllSpans default mapping for all stored trace data. This update was introduced to significantly increase visibility and analysis capacity for distributed tracing data, enabling teams to create more granular views without hitting previous limits. From a security and compliance perspective it improves auditability and observability of application behavior, helping detect anomalies, enforce least-privilege access to trace data, and maintain regulatory compliance through richer forensic capabilities.\n**Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) from version 3.50+ (recommended 5.0+). Resource: [`google_cloud_trace`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_trace).\n\n### Compute Engine\n**Feature & Security Summary:** Generally available capability to convert an automatically consumed reservation into a specifically targeted reservation (or vice-versa). The feature was introduced to provide workload flexibility when consumption patterns change, allowing organizations to optimize reserved capacity without recreating reservations. Security value includes tighter control over which projects or instances can consume reserved resources, supporting compliance with organizational segmentation and cost-governance policies.\n**Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) from version 4.0+ (recommended 5.0+). Resource: [`google_compute_reservation`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_reservation).\n\n### Cloud SQL for PostgreSQL\n**Feature & Security Summary:** Near real-time synchronization to Knowledge Catalog (instead of daily batch updates) when the integration is enabled on eligible instances. Introduced to deliver fresher metadata for data discovery and governance, reducing the window during which schema or metadata changes remain invisible to catalog consumers. Security and compliance benefits include accelerated detection of sensitive data, improved data-classification accuracy, and stronger alignment with privacy and regulatory requirements through timely metadata visibility.\n**Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) from version 4.50+ (recommended 5.0+). Resource: [`google_sql_database_instance`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance).\n\n### Cloud SQL for MySQL\n**Feature & Security Summary:** Near real-time sync of schema and metadata updates to Knowledge Catalog instead of daily batch updates. Users can toggle the integration off/on for existing instances to adopt the new behavior. The change was introduced to provide more timely metadata for governance tooling. Key security/compliance value lies in faster propagation of schema changes that may contain sensitive data definitions, enabling quicker policy enforcement, classification, and audit readiness.\n**Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) from version 4.0+ (recommended 5.0+). Resource: [`google_sql_database_instance`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance).\n\n### Dialogflow\n**Feature & Security Summary:** Google is migrating the mTLS client certificate authority for Dialogflow from Google Trust Services to SSL.com. This change is effective immediately, with a legacy fallback option available until December 1, 2026. The update enhances certificate management resilience and aligns with evolving PKI best practices, providing improved security posture, compliance with industry standards, and reduced dependency on a single CA provider while maintaining backward compatibility during the transition period.\n\n**Terraform Availability:** Not supported in the HashiCorp Google Terraform Provider (`hashicorp/google`). (N/A - see [dialogflow_cx_agent](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/dialogflow_cx_agent))",
    "updates": [
      {
        "serviceName": "App Hub",
        "serviceId": "apphub",
        "category": "Management Tools",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-hub#November_16_2026"
      },
      {
        "serviceName": "Cloud Load Balancing",
        "serviceId": "cloud-load-balancing",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-load-balancing#November_16_2026"
      },
      {
        "serviceName": "Bigtable",
        "serviceId": "bigtable",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigtable#November_16_2026"
      },
      {
        "serviceName": "Batch",
        "serviceId": "batch",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=batch#November_16_2026"
      },
      {
        "serviceName": "Cloud Trace",
        "serviceId": "cloudtrace",
        "category": "Operations",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-trace#November_16_2026"
      },
      {
        "serviceName": "Compute Engine",
        "serviceId": "compute",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=compute-engine#November_16_2026"
      },
      {
        "serviceName": "Cloud SQL for PostgreSQL",
        "serviceId": "cloudsql-postgresql",
        "category": "Database",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-sql-for-postgresql#November_16_2026"
      },
      {
        "serviceName": "Cloud SQL for MySQL",
        "serviceId": "cloudsql-mysql",
        "category": "Database",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-sql-for-mysql#November_16_2026"
      },
      {
        "serviceName": "Dialogflow",
        "serviceId": "dialogflow",
        "category": "AI and Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=dialogflow#November_16_2026"
      }
    ]
  },
  {
    "date": "2026-11-16",
    "title": "Google Cloud Daily Brief: 5 service updates",
    "summaryMarkdown": "### BigQuery\n**Feature & Security Summary:** Table-level data lineage in Knowledge Catalog for BigQuery pipelines is now GA, providing granular visibility into data flows and transformations. Additionally, the gemini-4-hydrogen model is now GA for BigQuery generative AI functions, enabling advanced AI-driven analytics. These capabilities were introduced to strengthen data governance, improve traceability for compliance audits, and deliver secure, governed AI insights directly within BigQuery. **Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) using `google_bigquery_dataset` and related resources (v4.0+ / v5.0+). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_dataset)\n\n### App Engine\n**Feature & Security Summary:** Direct VPC egress support for the App Engine standard environment is now GA, allowing applications to securely connect to VPC networks without additional proxies. The Migration hub also enables deploying an active version to Cloud Run (Preview). These updates were introduced to simplify secure networking, reduce attack surface by eliminating public internet exposure, and support compliant workload migrations. **Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) using `google_app_engine_application` and related resources (v4.0+ / v5.0+). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_application)\n\n### Cloud Logging\n**Feature & Security Summary:** SQL-based alerting policies for Observability Analytics query results are now GA. This allows monitoring of SQL query outputs with alerting policies, introduced to enable proactive security monitoring, anomaly detection, and compliance-driven observability directly from log and metric data. **Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) using `google_monitoring_alert_policy` (v4.0+ / v5.0+). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/monitoring_alert_policy)\n\n### Batch\n**Feature & Security Summary:** Jobs using TPUs are now generally available, with support for independent TPU VMs (single-host TPU slices) on machine types TPU7x (tpu7x-*), v6e (ct6e-*), and v5p (ct5p-*). Introduced to accelerate high-performance computing workloads while maintaining secure, isolated execution environments suitable for regulated AI/ML pipelines. **Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) using `google_batch_job` (v4.50+ / v5.0+). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/batch_job)\n\n### Cloud Monitoring\n**Feature & Security Summary:** SQL-based alerting policies for Observability Analytics query results are now GA. This capability was introduced to enable advanced, flexible alerting on complex log and trace data using standard SQL queries, significantly improving detection of security anomalies, compliance violations, and operational issues. It works by allowing users to define alerting conditions directly via SQL against Cloud Logging and Cloud Trace data through the Google Cloud console or the Cloud Monitoring API. **Key security/compliance value:** Provides precise, context-rich security monitoring and audit-ready alerting without custom code, reducing mean time to detect (MTTD) for threats and supporting regulatory compliance through auditable, query-driven policies.\n\n**Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) using the `google_monitoring_alert_policy` resource (available since v4.50+, fully supported in v5.0+). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/monitoring_alert_policy)",
    "updates": [
      {
        "serviceName": "BigQuery",
        "serviceId": "bigquery",
        "category": "Analytics",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigquery#November_12_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "appengine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-ruby#November_12_2026"
      },
      {
        "serviceName": "Cloud Logging",
        "serviceId": "logging",
        "category": "Operations",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-logging#November_12_2026"
      },
      {
        "serviceName": "Batch",
        "serviceId": "batch",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=batch#November_12_2026"
      },
      {
        "serviceName": "Cloud Monitoring",
        "serviceId": "monitoring",
        "category": "Operations",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-monitoring#November_12_2026"
      }
    ]
  },
  {
    "date": "2026-11-15",
    "title": "Google Cloud Daily Brief: 10 service updates",
    "summaryMarkdown": "As a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability:\n\n### Google Cloud Updates & Terraform Availability\n\n*   **API Keys API**: General Availability of the API Keys remote MCP server for use in AI applications. This update significantly enhances the security posture for AI workloads by providing a dedicated, managed control plane for API key lifecycle management. It ensures that API keys used by AI applications are securely provisioned, rotated, and monitored, thereby reducing the risk of unauthorized access or misuse and improving compliance for sensitive AI operations. Terraform support is available via the `google_apikeys_key` resource in the `hashicorp/google` provider, supported from version `4.84.0` up to `5.48.0+`. [Terraform Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apikeys_key).\n\n*   **Cloud Composer**: `pip` has been upgraded to `26.2.2` in Airflow `3.3.1`, `3.2.2`, and `2.11.1` images, incorporating crucial security fixes and stricter package installation rules. This is a vital update for supply chain security within data pipelines, mitigating risks associated with vulnerable Python packages. By enforcing stricter rules, it ensures that dependencies are installed securely and reliably, which is paramount for maintaining the integrity and compliance of data workflows orchestrated by Cloud Composer. Terraform support is available via the `google_composer_environment` resource in the `hashicorp/google` provider, supported from version `2.0+` up to `5.0+`. [Terraform Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/composer_environment).\n\n*   **Apigee**: Significant security enhancements include enhanced LLM proxy analytics for streaming SSE responses, improved WS-Security signature handling, hardened JavaCallout/Script/JavaScript and Jython policy sandboxes, OAuth 2.0 strict `redirect_uri` validation, and general infrastructure security updates. These updates collectively bolster API security, compliance, and observability. The hardened sandboxes reduce the attack surface for custom code execution, while strict OAuth 2.0 `redirect_uri` validation prevents common authorization code interception attacks. Improved WS-Security handling strengthens enterprise integration, and LLM proxy analytics provide better visibility into AI-driven API interactions. Terraform support is available via the `google_apigee_instance` resource in the `hashicorp/google` provider, supported from version `4.0+` up to `5.0+`. [Terraform Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apigee_instance).\n\n*   **App Engine**: General Availability (GA) for Direct VPC egress and Preview support for Migration Hub deployment to Cloud Run for App Engine standard environment Java. Direct VPC egress is a major security and networking enhancement, allowing App Engine applications to securely access resources within a Virtual Private Cloud (VPC) network without traversing the public internet. This simplifies network architecture, improves compliance by keeping traffic private, and significantly reduces the attack surface. The Migration Hub deployment to Cloud Run offers a modernized path for applications, potentially leveraging Cloud Run's inherent security features. Terraform support is available via the `google_app_engine_application` resource in the `hashicorp/google` provider, supported from version `4.0+` up to `5.0+`. [Terraform Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_application).\n\n# Google Cloud Security & IaC Daily Brief\n\nToday's Google Cloud updates focus on enhancing security posture through GKE version updates with critical OS patches, and improving network security and modernization paths for App Engine with Direct VPC Egress becoming Generally Available and simplified Cloud Run migrations.\n\n## Google Kubernetes Engine (GKE)\n*   **Feature & Security Summary**: New GKE versions are now available across Rapid, Regular, Extended, and No channels, including Alpha version 1.38.0-gke.5166000+preview. These updates are crucial as they incorporate updated Container-Optimized OS (COS) images with cumulative security fixes (e.g., `cos-133-19999-44-193` for GKE 1.37.2-gke.1325000). Regularly updating GKE clusters ensures that underlying operating systems are patched against known vulnerabilities, significantly reducing the attack surface and maintaining a strong security and compliance posture for containerized workloads. This proactive patching is a cornerstone of robust DevSecOps practices.\n*   **Terraform Availability**: Terraform support for GKE clusters is available via the `google_container_cluster` resource, supported since provider version `0.6.0` and up to `5.29.0`. [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/container_cluster).\n\n## App Engine\n\n### App Engine Standard Environment (PHP Runtime)\n*   **Feature & Security Summary**: Direct VPC egress is now Generally Available (GA), enabling App Engine standard applications to securely connect to resources within a Virtual Private Cloud (VPC) network via a Serverless VPC Access connector. This significantly enhances network isolation and compliance by ensuring outbound traffic remains private and does not traverse the public internet. Additionally, a new Preview feature allows direct migration of active App Engine standard versions to Cloud Run from the Migration Hub, simplifying modernization efforts without requiring source code access or application rebuilds. This streamlines the transition to a more secure and scalable serverless platform.\n*   **Terraform Availability**: Terraform support for managing the App Engine application itself is available via the `google_app_engine_application` resource, supported since provider version `4.0+` and up to `5.0+`. [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_application).\n\n### App Engine Standard Environment (Go Runtime)\n*   **Feature & Security Summary**: Direct VPC egress has reached General Availability (GA), allowing App Engine standard applications to establish private and secure connections to internal resources within a VPC network. This is achieved by routing outbound traffic through a Serverless VPC Access connector, which is vital for maintaining strict network segmentation and meeting compliance requirements. Furthermore, a new Preview feature facilitates deploying active App Engine standard versions directly to Cloud Run from the Migration Hub. This non-disruptive migration path, which avoids source code access or application rebuilding, empowers organizations to transition to Cloud Run's secure and scalable serverless container platform with minimal operational risk.\n*   **Terraform Availability**: Terraform support for managing App Engine standard environment versions, including potential configuration for VPC egress, is available via the `google_app_engine_standard_app_version` resource, supported since provider version `3.51.0` and up to `5.30.0`. [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_standard_app_version).\n\n### App Engine Standard Environment (Node.js Runtime)\n*   **Feature & Security Summary**: Direct VPC egress is now Generally Available (GA), providing App Engine standard applications with a secure and private communication channel to access internal VPC resources. This capability, enabled by Serverless VPC Access connectors, is fundamental for enforcing network security policies and ensuring data privacy by preventing sensitive traffic from being exposed to the public internet. Concurrently, a new Preview feature in the Migration Hub allows for the direct deployment of active App Engine versions to Cloud Run. This streamlined migration process requires no source code access or application rebuilds, making it an efficient and secure pathway for modernizing applications to leverage Cloud Run's fully managed, secure container environment.\n*   **Terraform Availability**: Terraform support for managing App Engine standard environment versions, including potential configuration for VPC egress, is available via the `google_app_engine_standard_app_version` resource, supported since provider version `3.69.0` and up to `5.30.0`. [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_standard_app_version).\n\n### Google Cloud Security & IaC Daily Briefing: Enhanced Auditability, Secure Connectivity, and Seamless Migration\n\nToday's Google Cloud updates bring significant advancements in security auditing, private network connectivity for serverless applications, and streamlined migration paths.\n\n*   **Essential Contacts: Enhanced Admin Activity Audit Logging**\n    *   **Feature & Security Summary**: Google Cloud's Essential Contacts v1 API now automatically generates Admin Activity audit logs (ADMIN_WRITE) for specific write operations: `CreateContact`, `UpdateContact`, `DeleteContact`, and `SendTestMessage`. This crucial enhancement complements existing Data Access audit logs, providing a more comprehensive and automatic audit trail for administrative actions related to managing essential contacts. This change is vital for security incident response, compliance adherence (e.g., GDPR, HIPAA), and maintaining accountability by ensuring that all modifications to critical contact information are logged. It reduces the risk of unauthorized changes going unnoticed, strengthening the overall security posture.\n    *   **Terraform Availability**: Supported by the `hashicorp/google` provider. While there isn't a direct `google_essential_contacts` resource for managing contacts, the related audit logging configuration can be managed. For configuring audit logs, the `google_project_iam_audit_config` resource is available from provider version `1.0.0` (latest `5.0.0`). [Terraform Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/project_iam_audit_config)\n\n*   **App Engine: Direct VPC Egress GA & Cloud Run Migration Hub**\n    *   **Feature & Security Summary**: App Engine standard environment (Python) now offers Generally Available (GA) 'Direct VPC egress'. This feature allows App Engine instances to securely send outbound traffic directly into a specified Virtual Private Cloud (VPC) network via a Serverless VPC Access connector. This enables private connectivity to internal resources like Cloud SQL, Compute Engine VMs, or on-premises networks (via VPN/Interconnect) without traversing the public internet, significantly enhancing network security and compliance. Additionally, a new feature in the Google Cloud console's 'Migration hub' simplifies the deployment of active App Engine standard environment versions directly to Cloud Run. This process requires no source code access or application rebuilding and does not impact live App Engine traffic, providing a streamlined path for modernization and leveraging Cloud Run's serverless container benefits.\n    *   **Terraform Availability**: Supported by the `hashicorp/google` provider. For managing App Engine standard environment versions, the `google_app_engine_standard_app_version` resource is available from provider version `3.50.0` (latest `5.30.0`). For configuring the Serverless VPC Access connector essential for Direct VPC egress, the `google_vpc_access_connector` resource is also available. [Terraform Documentation for App Engine Version](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_standard_app_version)",
    "updates": [
      {
        "serviceName": "API Keys API",
        "serviceId": "apikeys.googleapis.com",
        "category": "Security & Identity",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=api-keys-api#November_12_2026"
      },
      {
        "serviceName": "Cloud Composer",
        "serviceId": "composer",
        "category": "Data Analytics",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=managed-service-for-apache-airflow#November_13_2026"
      },
      {
        "serviceName": "Apigee",
        "serviceId": "apigee",
        "category": "API Management",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=apigee-x#November_13_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "appengine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-java#November_12_2026"
      },
      {
        "serviceName": "Google Kubernetes Engine",
        "serviceId": "gke",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-kubernetes-engine#November_13_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "appengine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-php#November_12_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "app-engine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-go#November_12_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "app-engine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-node-js#November_12_2026"
      },
      {
        "serviceName": "Essential Contacts",
        "serviceId": "essential-contacts",
        "category": "Security, Identity, & Compliance",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=resource-manager#November_13_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "app-engine",
        "category": "Serverless",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-python#November_12_2026"
      }
    ]
  },
  {
    "date": "2026-11-14",
    "title": "Google Cloud Daily Brief: 8 service updates",
    "summaryMarkdown": "As your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability:\n\n### BigQuery: Federated Queries to External Databases (Preview)\n\n*   **Feature & Security Summary**: BigQuery now offers federated queries to MySQL, Oracle, and PostgreSQL in Preview. This feature was introduced to enable data analysts and engineers to directly query external transactional databases from BigQuery without the need for complex ETL processes, simplifying data integration and reducing operational overhead. From a security and compliance perspective, this is highly valuable as it minimizes data movement and replication of sensitive information. Data remains in its source system, leveraging existing security controls (e.g., row-level security, data masking) and maintaining data sovereignty. Access is managed via BigQuery connections, which can be secured using Google Cloud IAM, ensuring granular control over who can access external data sources. This reduces the attack surface by limiting data proliferation and centralizing access management.\n*   **Terraform Availability**: Supported by the `hashicorp/google` provider via the `google_bigquery_connection` resource. First available in version `4.84+` and fully supported in `5.0+`. [https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_connection](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_connection)\n\n### Cloud Run: Ambient Networking with Managed Envoy Sidecar and Express Link (Preview)\n\n*   **Feature & Security Summary**: Cloud Run now supports ambient networking with a managed Envoy sidecar and Express Link integration in Preview. This update significantly enhances the networking capabilities for serverless applications, providing advanced traffic management, observability, and security features typically associated with service meshes, without the operational burden of manual sidecar injection. The managed Envoy sidecar automatically intercepts network traffic, enabling robust policy enforcement, mTLS for secure service-to-service communication, and enhanced observability for security monitoring. This strengthens the zero-trust security posture for serverless deployments by ensuring encrypted and authenticated communication within the application's network. Express Link further improves secure, private connectivity to other Google Cloud services, reducing exposure to the public internet and enhancing overall network isolation and compliance.\n*   **Terraform Availability**: Supported by the `hashicorp/google` provider via the `google_cloud_run_v2_service` resource (for Cloud Run V2 services). First available in version `4.0+` and fully supported in `5.0+`. [https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_v2_service](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_v2_service)\n\n### Bigtable: Access Pattern Analysis for Instances and Clusters (GA)\n\n*   **Feature & Security Summary**: Bigtable's access pattern analysis for instances and clusters is now Generally Available (GA). This feature was introduced to provide deep insights into how applications interact with Bigtable, helping users optimize schema design, identify hot spots, and improve performance and cost efficiency. While primarily a performance and optimization tool, understanding access patterns can indirectly contribute to security. By identifying unusual access spikes or patterns, it can help detect anomalous behavior that might indicate potential security incidents or data exfiltration attempts. Optimizing database design based on access patterns can also lead to more efficient data storage and retrieval, potentially reducing the attack surface by ensuring data is accessed only as needed and in expected ways.\n*   **Terraform Availability**: Supported by the `hashicorp/google` provider via the `google_bigtable_instance` resource (as this is a feature of the instance). First available in version `1.0+` and fully supported in `5.0+`. [https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigtable_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigtable_instance)\n\n### Cloud SQL for PostgreSQL: Enhanced Backups with DR Replica Support\n\n*   **Feature & Security Summary**: Cloud SQL for PostgreSQL now offers enhanced backups that support instances with disaster recovery (DR) replica instances. This critical update improves the resilience and recovery capabilities for PostgreSQL databases by allowing backup and DR backup plans to be associated directly with a primary instance that has a designated DR replica. This ensures that backup strategies fully account for DR replica setups, simplifying management and guaranteeing consistent data protection across both primary and DR environments. From a security and compliance standpoint, this is a significant enhancement for Business Continuity and Disaster Recovery (BCDR), a cornerstone of any robust security framework. It enables organizations to meet stringent Recovery Time Objective (RTO) and Recovery Point Objective (RPO) requirements, protect against data loss during regional outages, and satisfy regulatory mandates for data durability and availability. This simplifies the management of secure, recoverable data assets.\n*   **Terraform Availability**: Supported by the `hashicorp/google` provider via the `google_sql_database_instance` resource (where backup configurations are defined). First available in version `4.50+` and fully supported in `5.0+`. [https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance)\n\nAs a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability, focusing on security, compliance, and operational efficiency.\n\n### Google Cloud Updates and Terraform Availability\n\n*   **Cloud Quotas (General Availability)**\n    *   **Feature & Security Summary**: The Cloud Quotas service has reached General Availability (GA), providing a stable and supported platform for programmatic quota management. This allows users to view, request increases, and set preferences for Google Cloud service quotas via a reliable API with an SLA. From a security and compliance perspective, this enables robust resource governance, helps prevent service disruptions due to quota exhaustion, and facilitates automated adherence to organizational resource limits. Integrating quota management into automated workflows enhances operational stability and predictability.\n    *   **Terraform Availability**: Supported by `hashicorp/google` provider (first version `5.1.0`, latest `5.29.0`) via the `google_cloudquotas_quota_preference` resource. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloudquotas_quota_preference)\n\n*   **Cloud SQL for MySQL (Enhanced Backup Capabilities)**\n    *   **Feature & Security Summary**: Cloud SQL for MySQL now offers enhanced backup capabilities for instances with disaster recovery (DR) replica instances. Users can associate a Backup and DR backup plan directly with a primary Cloud SQL instance that has a designated DR replica. This significantly simplifies the management of backups for critical databases, ensuring that Recovery Point Objectives (RPOs) and Recovery Time Objectives (RTOs) can be met more effectively in disaster recovery scenarios. This update directly contributes to enhanced data resilience and improved business continuity.\n    *   **Terraform Availability**: While the `google_sql_database_instance` resource is supported, this specific enhanced backup capability for DR replicas is not yet directly exposed as a configurable argument within the `hashicorp/google` provider. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance)\n\n*   **Cloud SQL for SQL Server (Enhanced Backup Capabilities)**\n    *   **Feature & Security Summary**: Similar to MySQL, Cloud SQL for SQL Server now supports enhanced backups for instances with disaster recovery (DR) replica instances. This allows associating a Backup and DR backup plan directly with a primary Cloud SQL instance that includes a DR replica. This ensures consistent backup and recovery for the entire Cloud SQL setup, including its DR components, using the Backup and DR service. This is crucial for maintaining a robust data protection strategy, ensuring consistent recovery posture across primary and DR environments, and meeting stringent compliance and business continuity requirements.\n    *   **Terraform Availability**: The `google_sql_database_instance` resource is supported by `hashicorp/google` provider (first version `4.0.0`, latest `5.0.0`). While the instance itself can be managed, the direct association of the enhanced Backup and DR plan for DR replicas might require manual configuration or future provider updates. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance)\n\n*   **Looker (Multiple Enhancements including 2FA Enforcement)**\n    *   **Feature & Security Summary**: Looker has received several updates, notably including the automatic enablement of Google Group mirroring for simplified user management, Gemini usage billing for cost transparency, enhanced download metadata for better governance, and the General Availability of Sankey charts. **Crucially, default 2FA enforcement has been introduced.** This significantly enhances the security posture of Looker instances by requiring a second factor for authentication, drastically reducing the risk of unauthorized access due to compromised credentials. This aligns with security best practices and aids in compliance efforts.\n    *   **Terraform Availability**: Supported by `hashicorp/google` provider via the `google_looker_instance` resource. Specific versions for this feature are not explicitly detailed in the provider documentation, but the resource itself is available. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/looker_instance)",
    "updates": [
      {
        "serviceName": "BigQuery",
        "serviceId": "bigquery",
        "category": "Analytics",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigquery#November_13_2026"
      },
      {
        "serviceName": "Cloud Run",
        "serviceId": "cloud-run",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-run#November_13_2026"
      },
      {
        "serviceName": "Bigtable",
        "serviceId": "bigtable",
        "category": "Database",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigtable#November_13_2026"
      },
      {
        "serviceName": "Cloud SQL for PostgreSQL",
        "serviceId": "cloudsql-postgresql",
        "category": "Database",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-sql-for-postgresql#November_13_2026"
      },
      {
        "serviceName": "Cloud Quotas",
        "serviceId": "cloud-quotas",
        "category": "Management Tools",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=access-transparency#November_13_2026"
      },
      {
        "serviceName": "Cloud SQL for MySQL",
        "serviceId": "cloud-sql-mysql",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-sql-for-mysql#November_13_2026"
      },
      {
        "serviceName": "Cloud SQL for SQL Server",
        "serviceId": "cloud-sql-sql-server",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-sql-for-sql-server#November_13_2026"
      },
      {
        "serviceName": "Looker",
        "serviceId": "looker",
        "category": "Business Intelligence",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=looker#November_13_2026"
      }
    ]
  },
  {
    "date": "2026-11-12",
    "title": "Google Cloud Daily Brief: 9 service updates",
    "summaryMarkdown": "### Cloud Build\n**Feature & Security Summary:** When storing build logs in Cloud Storage, a user-owned, regional bucket is now used by default. This change was introduced to improve data locality, reduce cross-region egress costs, and strengthen compliance posture by ensuring logs remain under customer-controlled regional boundaries with customer-managed encryption keys. **Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) using `google_cloudbuild_trigger` (v5.0+, first supported in v4.0+). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloudbuild_trigger)\n\n### Apigee Edge\n**Feature & Security Summary:** Improved Edge UI performance when loading App Details or New App pages by fetching API products on demand. Fixed Analytics Error Code Analysis dashboard to properly include target timeout 504 responses under Proxy errors. Corrected dimension display formatting in the Analytics Custom Reports list view. These updates enhance operational efficiency and accuracy of security analytics for API traffic monitoring and error classification. **Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) using `google_apigee_organization` (v5.0+, first supported in v4.0+). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apigee_organization)\n\n### Google Kubernetes Engine\n**Feature & Security Summary:** Capacity buffers (active and standby) are now generally available for GKE Standard and Autopilot clusters on version 1.37.1-gke.3020000 or later, using the CapacityBuffer CRD to pre-provision compute capacity. This feature was introduced to improve workload resilience, enable faster scaling during demand spikes, and maintain security/compliance by ensuring capacity is available without compromising pod security policies or network controls. **Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) using `google_container_cluster` (v1.37). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/container_cluster)\n\n### Gemini Enterprise Agent Platform\n**Feature & Security Summary:** The CodeMender tool (v0.21.0) has received several updates including sandboxed build commands and patch refresh, read-only host toolchains and isolated caches, command environment isolation, and multiple bug fixes. CodeMender now supports the Gemini 4 Carbon model (Preview). The Agent Gateway for cross-cloud (Limited Preview) is introduced, extending Agent Platform governance to agents deployed on any CNCF-conformant Kubernetes cluster. This allows centralized governance by providing verifiable identities, registering agents and MCP servers, routing traffic through local proxies that enforce Model Armor safety policies, and sending logs/traces to Cloud Logging and Cloud Trace. These enhancements strengthen isolation, reproducibility, and cross-environment security controls for AI agents. **Terraform Availability:** Not currently supported in the HashiCorp Google Terraform Provider (`hashicorp/google`).\n\nAs a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability:\n\n*   **API Gateway: TLS 1.3 for Backend Connections**\n    *   **Feature & Security Summary:** This update significantly enhances the security posture of API Gateway by enabling TLS 1.3 for connections to backend services. TLS 1.3 is the latest and most secure version of the Transport Layer Security protocol, offering improved cryptographic algorithms, reduced handshake latency, and enhanced protection against known vulnerabilities compared to older TLS versions. This ensures that data in transit between API Gateway and its backend services is encrypted with the strongest available protocols, which is crucial for compliance with various security standards (e.g., PCI DSS, HIPAA) and protecting sensitive data. It was introduced to provide a more robust and efficient secure communication channel, aligning with best practices for data encryption in transit.\n    *   **Terraform Availability:** Supported by the `hashicorp/google` provider resource `google_api_gateway_gateway` from versions `4.0+` to `5.0+`. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/api_gateway_gateway)\n\n*   **Oracle Database@Google Cloud: Granular Identity Connector Control**\n    *   **Feature & Security Summary:** This update provides more granular control over the Identity Connector for Exadata VM Clusters and Exascale VM Clusters. Users can now opt to provision a cluster without the Identity Connector initially, and its status (enabled or disabled) can be modified at any point after cluster creation. This offers significant operational flexibility and security control. Organizations can defer Identity Connector integration or choose alternative identity management solutions if their security architecture dictates. The ability to enable/disable it post-creation allows for dynamic adjustments to identity management strategies without requiring cluster re-provisioning. From a security perspective, this granular control helps align the identity management configuration precisely with an organization's security policies, potentially reducing the attack surface by only enabling components when strictly necessary and integrating with existing, trusted identity providers. This enhances compliance by allowing more tailored configurations.\n    *   **Terraform Availability:** Supported by the `hashicorp/google` provider resource `google_oracle_database_at_google_cloud_exadata_vm_cluster` from versions `5.27.0` to `5.27.0`. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/oracle_database_at_google_cloud_exadata_vm_cluster)\n\n*   **BigQuery: Advanced Resource Governance and Data Transformation**\n    *   **Feature & Security Summary:** This update introduces three key features for BigQuery:\n        1.  **Project Caps (Scheduling Policies):** Now Generally Available (GA) for BigQuery Enterprise and Enterprise Plus editions, this feature allows users to define maximum slot usage and concurrency limits per project within a BigQuery reservation. This provides critical resource governance, preventing a single project from monopolizing reservation capacity. From a security and compliance perspective, it helps enforce resource isolation, preventing resource exhaustion attacks or accidental over-consumption that could lead to service degradation or unexpected costs. It's essential for multi-tenant environments to maintain service level agreements (SLAs) and fair usage policies.\n        2.  **Principal Property on Reservation Assignments:** Also GA for Enterprise and Enterprise Plus editions, users can now specify an optional `principal` property on BigQuery reservation assignments. This enables routing queries to specific reservations based on the identity (user, service account, or third-party identity) executing the job. This significantly enhances workload isolation and security. It's invaluable for multi-tenant architectures, regulatory compliance (e.g., isolating sensitive workloads to dedicated reservations), and cost attribution, ensuring that critical workloads executed by specific identities receive guaranteed resources and preventing unauthorized consumption.\n        3.  **`JSON_FLATTEN` Function:** A new SQL function, `JSON_FLATTEN`, is now GA. This function extracts all non-array values that are either directly within the input JSON value or are children of one or more consecutively nested arrays. While not directly a security feature, it simplifies the process of querying and analyzing complex JSON data structures in BigQuery, improving data usability and efficiency. This indirectly supports security by making it easier to analyze logs or other security-relevant data stored in JSON format, leading to more accurate and timely security analytics and reporting.\n    *   **Terraform Availability:** Supported by the `hashicorp/google` provider resource `google_bigquery_reservation_assignment` from versions `4.70.0` to `5.0.0`. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_reservation_assignment)\n\n*   **Vertex AI Workbench: Antigravity CLI with Security Controls**\n    *   **Feature & Security Summary:** The Antigravity CLI provides a terminal interface for Google Antigravity, an AI agent, available in Agent Platform Workbench instances running Debian 12 (workbench-instances-2603) or newer images. This significantly enhances productivity by allowing the AI agent to assist with creating, explaining, editing, checking, and running notebooks; creating custom Jupyter kernels; executing shell and Google Cloud commands (e.g., gcloud, bq); and writing notebook cell code. From a security perspective, the most critical aspect is the built-in security feature that *prompts for user approval before executing file edits or commands*. This mitigates the risk of an AI agent inadvertently or maliciously performing unauthorized actions, providing a crucial human-in-the-loop control. It ensures that powerful AI capabilities are wielded responsibly and securely, preventing potential data exfiltration, unauthorized code execution, or system modifications. The ability to disable it via metadata also allows for controlled deployment based on organizational security policies, helping maintain compliance by ensuring oversight of automated actions in sensitive environments.\n    *   **Terraform Availability:** Supported by the `hashicorp/google` provider resource `google_workbench_instance` from versions `4.0.0` to `5.0.0`. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/workbench_instance)\n\nAs a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability:\n\n### Google Distributed Cloud for bare metal\n\n**Feature & Security Summary:** This update, specifically version 1.34.1100-gke.125, significantly enhances the security posture of Google Distributed Cloud for bare metal. It was introduced to fortify the trust chain and integrity of system components and container base images. Key security improvements include the removal of distrusted eMudhra (emSign) and AAA Certificate Services root Certificate Authorities (CAs) and the implementation of mechanisms to reject compromised eMudhra intermediate CAs. This directly addresses potential supply chain vulnerabilities and strengthens the cryptographic trust within the cluster's internal communications and image verification processes. Furthermore, critical vulnerabilities have been patched, and operational issues like orphaned Kubernetes resources, snapshotting race conditions, and etcd member management have been resolved, leading to improved cluster stability and reliability. This update is crucial for maintaining a robust and compliant hybrid cloud environment, ensuring that on-premises GKE deployments meet stringent security standards.\n\n**Terraform Availability:** Fully supported in the `hashicorp/google-beta` provider. The primary resource for managing bare metal clusters is `gkeonprem_bare_metal_cluster`. Support was introduced in version `4.0.0` and is available in the latest version `5.0.0`. For detailed documentation, refer to the [Terraform Registry](https://registry.terraform.io/providers/hashicorp/google-beta/latest/docs/resources/gkeonprem_bare_metal_cluster).",
    "updates": [
      {
        "serviceName": "Cloud Build",
        "serviceId": "cloudbuild",
        "category": "Developer Tools",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-build#November_11_2026"
      },
      {
        "serviceName": "Apigee Edge",
        "serviceId": "apigee",
        "category": "API Management",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=apigee-edge-for-public-cloud#November_11_2026"
      },
      {
        "serviceName": "Google Kubernetes Engine",
        "serviceId": "gke",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-kubernetes-engine#November_11_2026"
      },
      {
        "serviceName": "Gemini Enterprise Agent Platform",
        "serviceId": "gemini-enterprise-agent-platform",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=gemini-enterprise-agent-platform#November_11_2026"
      },
      {
        "serviceName": "API Gateway",
        "serviceId": "apigateway",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=api-gateway#November_10_2026"
      },
      {
        "serviceName": "Oracle Database@Google Cloud",
        "serviceId": "oracle-database-at-google-cloud",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=oracle-database-google-cloud#November_11_2026"
      },
      {
        "serviceName": "BigQuery",
        "serviceId": "bigquery",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigquery#November_11_2026"
      },
      {
        "serviceName": "Vertex AI Workbench",
        "serviceId": "vertex-ai-workbench",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=agent-platform-workbench#November_10_2026"
      },
      {
        "serviceName": "Google Distributed Cloud for bare metal",
        "serviceId": "google-distributed-cloud-bare-metal",
        "category": "Hybrid & Multi-cloud",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-distributed-cloud-software-only-for-bare-metal#November_11_2026"
      }
    ]
  },
  {
    "date": "2026-11-11",
    "title": "Google Cloud Daily Brief: 8 service updates",
    "summaryMarkdown": "As a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability:\n\n*   **Model Armor: GA for Image Screening in Rich Text Documents**\n    *   **Feature & Security Summary:** Model Armor's General Availability for image screening addresses the critical need for content moderation within rich text documents (PDF, Word, Excel, PowerPoint). This feature works by extracting and analyzing embedded images, converting them into tokens for processing. From a security and compliance perspective, this is invaluable for preventing the dissemination of inappropriate, malicious, or sensitive visual content, thereby bolstering data governance and reducing the risk of data exfiltration through embedded media, which is crucial for maintaining regulatory compliance and data integrity.\n    *   **Terraform Availability:** Currently, direct Terraform support for Model Armor's image screening features is not available in the `hashicorp/google` provider. (Provider documentation: [https://registry.terraform.io/providers/hashicorp/google/latest/docs](https://registry.terraform.io/providers/hashicorp/google/latest/docs))\n\n*   **BigQuery: Advanced Graph Measures and Gemini-4-carbon AI Integration (GA)**\n    *   **Feature & Security Summary:** BigQuery significantly enhances its analytical and AI capabilities. The introduction of graph measures with AGG function and GRAPH_EXPAND multi-fact support empowers more complex data relationship analysis, crucial for identifying sophisticated patterns in security logs or audit trails. Furthermore, the General Availability of the Gemini-4-carbon model for generative AI functions directly within BigQuery allows for advanced data classification, anomaly detection, and automated compliance checks through SQL. This integration provides powerful tools for data security and governance, enabling proactive identification of risks and ensuring data integrity across vast datasets.\n    *   **Terraform Availability:** BigQuery core resources are well-supported. For managing datasets, tables, and other BigQuery components, the `google_bigquery_dataset` resource (and related resources) is available in the `hashicorp/google` provider, with support from version 5.10.0 up to the latest 5.35.0. (Provider documentation: [https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_dataset](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_dataset))\n\n*   **AlloyDB for PostgreSQL: GA of Smart Batching and Sentiment Analysis for AI Functions**\n    *   **Feature & Security Summary:** AlloyDB for PostgreSQL introduces General Availability for Smart batching for AI functions and Sentiment analysis (ai.analyze_sentiment) on PostgreSQL 17+ clusters, with smart batching enabled by default on PostgreSQL 18+. Smart batching optimizes AI function execution, improving performance for AI-driven database operations. Sentiment analysis directly within the database offers a powerful tool for security and compliance, enabling automatic monitoring of textual data (e.g., user comments, logs) to detect potential threats, inappropriate content, or policy violations. This enhances real-time data governance and risk management by providing immediate insights into data sentiment.\n    *   **Terraform Availability:** Core AlloyDB cluster and instance management is supported. The `google_alloydb_cluster` resource (and `google_alloydb_instance`) is available in the `hashicorp/google` provider, with support from version 4.0+ up to the latest 5.0+. (Provider documentation: [https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/alloydb_cluster](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/alloydb_cluster))\n\n*   **Vertex AI Search: 'Search-as-you-type' Feature for Dynamic Results**\n    *   **Feature & Security Summary:** Vertex AI Search introduces the 'Search-as-you-type' feature, which allows custom search apps to deliver dynamic, continuously updated lists of matching documents as a user types, rather than just suggesting query strings. This significantly improves user experience and efficiency in information retrieval. From a security and compliance standpoint, this feature can enhance the discoverability of critical information for internal audits, e-discovery, and ensuring users quickly access authorized data. However, robust access controls and data governance on the underlying data stores are paramount to prevent the inadvertent exposure of sensitive or unauthorized information through dynamic search results.\n    *   **Terraform Availability:** While Vertex AI Search has base resources like `google_vertex_ai_search_data_store` available in the `hashicorp/google` provider, the specific 'Search-as-you-type' feature configuration is not yet directly supported via Terraform. (Provider documentation: [https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/vertex_ai_search_data_store](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/vertex_ai_search_data_store))\n\n# Google Cloud Daily Brief: Security, AI, and Infrastructure Updates\n\nAs a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive summary of today's key Google Cloud updates and their Infrastructure as Code (IaC) availability.\n\n## Compute Engine\n*   **Feature & Security Summary**: Regional Managed Instance Groups (MIGs) now offer enhanced visibility into planned instance allocations across zones and machine types, allowing administrators to check instances waiting for capacity and configure alerts. This feature significantly improves capacity planning, resource optimization, and ensures application availability by providing proactive insights into resource provisioning. From a security and reliability perspective, this helps prevent service degradation due to capacity constraints and enables more resilient application deployments. Compute Engine records these details in Cloud Logging, aiding in auditability and operational insights. Terraform support is available via the `google_compute_region_instance_group_manager` resource in `hashicorp/google` provider versions `4.0+` (first) to `5.0+` (latest). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_region_instance_group_manager)\n\n## Google Cloud Vertex AI\n*   **Feature & Security Summary**: The General Availability of Gemini 4 Carbon and Gemini 4 Carbon for cyber marks a significant advancement in AI capabilities. Gemini 4 Carbon offers a unified 1,048,576-token input and output limit, supports long decodes, provides configurable thinking levels (LOW, MEDIUM, HIGH), includes implicit context caching, accepts Microsoft Office and OpenDocument file inputs, and supports Provisioned Throughput. Gemini 4 Carbon for cyber is a specialized defensive cybersecurity variant available through the Fairwind Program allowlist, offering targeted AI capabilities for threat detection and response. Additionally, CodeMender updates (v0.20.0) address bug fixes for patch application failures and improve scan error handling. The specialized 'for cyber' variant provides a critical security value by enabling advanced AI-driven defensive measures, while CodeMender improvements enhance the reliability of secure code analysis. Terraform support is available via the `vertex_ai_endpoint` resource in `hashicorp/google` provider versions `4.0.0` (first) to `5.0.0` (latest). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/vertex_ai_endpoint)\n\n## Cloud Identity and Access Management\n*   **Feature & Security Summary**: Several critical updates enhance IAM policy management and authentication mechanisms. The `gcloud agent-identity auth-providers` commands for `get-iam-policy`, `set-iam-policy`, `add-iam-policy-binding`, `remove-iam-policy-binding`, and `test-iam-permissions` are now GA, providing robust control over authentication provider IAM policies. New flags for `gcloud agent-identity auth-providers create` and `update` facilitate the configuration of Cross-App Access and Connector Reference auth providers, expanding options for secure federated identity scenarios. Cloud IAM's `gcloud iam workload-identity-pools create-cred-config` now supports certificate-bound OAuth 2.0 token exchanges and actor token delegation, significantly strengthening workload identity authentication. Other security-related updates include the GA promotion of Cloud Backup DR restore commands, the addition of `--enable-vulnerability-scanning` for Secure Source Manager repositories (crucial for DevSecOps), and the `gcloud spanner databases wait-for-reencryption` command for CMEK operations. Config Connector 1.160.0 also brings general improvements for managing GCP resources as Kubernetes objects. These updates collectively deliver stronger authentication, more granular access control, enhanced vulnerability management, and improved data encryption key operations, bolstering overall cloud security posture. Terraform support is available via the `google_iam_workload_identity_pool_provider` resource in `hashicorp/google` provider versions `4.0.0` (first) to `>= 5.0.0` (latest). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/google_iam_workload_identity_pool_provider)\n\n## Cloud Load Balancing\n*   **Feature & Security Summary**: Proxy Network Load Balancers now support SNI-based routing capabilities through the new TLSRoute API resource. This allows administrators to define routing rules that inspect the SNI hostname during the client's TLS handshake, directing traffic to specific backend services based on the matched hostname. A key security and architectural benefit is the support for TLS passthrough, meaning the TLS connection is not terminated at the load balancer. Instead, the encrypted traffic is forwarded directly to the backend service, which is responsible for TLS termination. This is crucial for maintaining end-to-end encryption, meeting compliance requirements, and enabling backend services to manage their own TLS certificates and keys, providing greater control and flexibility over the security chain. Terraform support is available via the `compute_region_tls_route` resource in `hashicorp/google` provider versions `4.38.0` (first) to `5.0.0` (latest). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_region_tls_route)",
    "updates": [
      {
        "serviceName": "Model Armor",
        "serviceId": "modelarmor",
        "category": "AI and Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=model-armor#November_10_2026"
      },
      {
        "serviceName": "BigQuery",
        "serviceId": "bigquery",
        "category": "Analytics",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigquery#November_10_2026"
      },
      {
        "serviceName": "AlloyDB for PostgreSQL",
        "serviceId": "alloydb",
        "category": "Database",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=alloydb-for-postgresql#November_09_2026"
      },
      {
        "serviceName": "Vertex AI Search",
        "serviceId": "vertex-ai-search",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=vertex-ai-search#November_10_2026"
      },
      {
        "serviceName": "Compute Engine",
        "serviceId": "compute",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=compute-engine#November_10_2026"
      },
      {
        "serviceName": "Google Cloud Vertex AI",
        "serviceId": "vertex-ai",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=gemini-enterprise-agent-platform#November_10_2026"
      },
      {
        "serviceName": "Cloud Identity and Access Management",
        "serviceId": "cloud-iam",
        "category": "Security, Identity, & Compliance",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-sdk#November_10_2026"
      },
      {
        "serviceName": "Cloud Load Balancing",
        "serviceId": "cloud-load-balancing",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-load-balancing#November_09_2026"
      }
    ]
  },
  {
    "date": "2026-11-10",
    "title": "Google Cloud Daily Brief: 7 service updates",
    "summaryMarkdown": "As your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability:\n\n### **Bigtable: Apache Avro Schema Bundles (Preview)**\n*   **Feature & Security Summary:** Bigtable now supports creating and managing Apache Avro schema bundles via the Google Cloud console and viewing definitions in Bigtable Studio (Preview). This enhancement was introduced to bolster data governance and interoperability. Avro schemas provide a robust, language-agnostic framework for defining data structures, ensuring data consistency, and simplifying data evolution. From a security and compliance perspective, well-defined schemas are critical for data validation, preventing malformed or unauthorized data from entering the system, and ensuring adherence to expected formats, which is vital for regulatory compliance and maintaining data integrity. Bigtable Studio's viewing capability further aids in auditing and understanding the structure of data within your Bigtable instances.\n*   **Terraform Availability:** Fully supported. You can manage Bigtable tables, which will implicitly support schema definitions, using the `google_bigtable_table` resource. Supported in `hashicorp/google` provider versions `5.35.0` and later. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigtable_table)\n\n### **Pathways on Cloud: General Availability on GKE**\n*   **Feature & Security Summary:** Pathways on Cloud is now generally available on GKE, offering resilient training, elastic scaling, hot-swapping, colocated sidecars, Shared Pathways Service, single-process profiling, and agentic debugging capabilities for TPU v5e, v5p, v6e, and TPU7x. This update marks a significant advancement in providing a more robust, scalable, and manageable infrastructure for advanced AI/ML training workloads. The emphasis on resilient training and elastic scaling directly contributes to operational security by ensuring workloads can withstand failures and dynamically adapt to demand, thereby reducing the risk of service disruption. Features like hot-swapping and agentic debugging improve reliability and enable quicker recovery from issues, which is paramount for maintaining the integrity and availability of high-value AI computations. While not a direct security feature, enhanced stability and manageability reduce the attack surface associated with misconfigurations or unpatched systems due to operational overhead.\n*   **Terraform Availability:** Supported for managing the underlying GKE clusters. The `google_container_cluster` resource can be used to provision and configure GKE clusters that can host Pathways on Cloud. Supported in `hashicorp/google` provider versions `4.50+` and later. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/container_cluster)\n\n### **Cloud Run: Vulnerability Assessment (Preview)**\n*   **Feature & Security Summary:** Cloud Run has introduced a preview release of Vulnerability Assessment. This capability empowers users to detect vulnerabilities and exposed secrets directly within the container images deployed to their Cloud Run services, jobs, and worker pools. This is a critical security enhancement, designed to provide developers and security teams with early and continuous visibility into potential security risks within their serverless container deployments. By identifying vulnerabilities (e.g., outdated libraries, known CVEs) and exposed secrets (e.g., hardcoded credentials) proactively, organizations can mitigate risks, enforce security policies, and significantly improve their overall security posture. This directly aligns with DevSecOps principles by integrating security scanning into the deployment pipeline, reducing the likelihood of vulnerable applications reaching production, and aiding compliance efforts.\n*   **Terraform Availability:** While Terraform can manage Cloud Run services via `google_cloud_run_v2_service`, this specific vulnerability assessment *feature* is a capability of the service itself and is not directly exposed as a configurable resource within the `hashicorp/google` provider at this time. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_v2_service)\n\n### **Anthos Config Management: Security Patch Update**\n*   **Feature & Security Summary:** Anthos Config Management has received a security patch, focusing on upgrading two key internal dependencies to address CVEs. Specifically, the `git-sync` dependency has been updated from v4.4.2 to v4.5.0, and the `Open Telemetry` image has been upgraded from 0.152.0 to 0.159.0. This update is purely for security and robustness, without introducing new user-facing functionalities. It was implemented to patch known vulnerabilities in these critical components, thereby enhancing the overall security posture of Anthos Config Management. `git-sync` is fundamental for synchronizing configurations from Git repositories, making any vulnerability a potential vector for unauthorized configuration changes or data exfiltration. Open Telemetry is used for observability, and patching it helps prevent potential exploits that could compromise monitoring data or introduce side-channel attacks. By upgrading these dependencies, Google ensures that ACM remains a secure and reliable platform for GitOps-driven configuration management, which is vital for maintaining compliance and preventing configuration drift that could introduce security gaps.\n*   **Terraform Availability:** This specific security patch for internal dependencies is managed by the Anthos Config Management service itself and is not directly configurable via Terraform. Terraform is used to manage the deployment and configuration of Anthos Config Management features (e.g., `google_gke_hub_feature`), but not the underlying service's internal patching. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gke_hub_feature)\n\n### Google Cloud Daily Brief: Concurrency Controls, API Gateway Security & IaC Updates\n\nAs a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's your daily summary of critical Google Cloud updates and their Infrastructure as Code (IaC) availability.\n\n---\n\n#### Analytics & Data\n\n*   **BigQuery: Pipeline Concurrency Control (GA)**\n    *   **Feature & Security Summary**: This new Generally Available (GA) feature allows users to define the maximum number of concurrently executed pipeline tasks during the creation or scheduling of a BigQuery pipeline. This was introduced to provide finer-grained control over resource allocation and parallel processing, preventing resource contention and ensuring predictable performance for data transformations. From a security and compliance perspective, managing concurrency is vital for maintaining service stability, preventing potential denial-of-service scenarios due to uncontrolled resource consumption, and ensuring that data processing adheres to operational resilience requirements.\n    *   **Terraform Availability**: Direct Terraform support for configuring BigQuery pipeline concurrency limits is not yet available in the `hashicorp/google` provider. While resources like `google_bigquery_data_transfer_config` exist for data transfers, this specific concurrency feature is not exposed.\n        *   Provider: `hashicorp/google`\n        *   Resource: N/A (for this specific feature)\n        *   Versions: N/A\n        *   [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_data_transfer_config)\n\n*   **Dataform: Workflow Concurrency Limits (GA)**\n    *   **Feature & Security Summary**: Dataform now supports defining a maximum limit for concurrent actions within a workflow execution or scheduled configuration. This feature is crucial for optimizing performance, managing resource allocation, and ensuring stability, particularly for complex data pipelines or when sharing BigQuery resources. By limiting concurrency, organizations can prevent excessive parallel processing that might lead to resource contention, rate limit issues with underlying services, or unexpected costs. This enhances operational security by preventing self-inflicted outages and ensuring predictable resource usage.\n    *   **Terraform Availability**: This feature is supported via the `hashicorp/google` provider.\n        *   Provider: `hashicorp/google`\n        *   Resource: `google_dataform_repository_workflow_config`\n        *   Versions: Supported since `4.67.0`, latest `4.67.0`.\n        *   [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/dataform_repository_workflow_config)\n\n---\n\n#### Networking\n\n*   **Apigee Edge Microgateway: Version 3.3.12 Release & Security Fixes**\n    *   **Feature & Security Summary**: Apigee Edge Microgateway version 3.3.12 is now available, bringing critical updates. Key changes include updated component versions (`microgateway` 3.3.12, `plugins` 3.3.9, `edgeauth` 3.2.2), revised Node.js support (now exclusively 22, 24, and 26; Node.js 20 support removed, 26 added), and modifications to the Docker image. The Docker image (`gcr.io/apigee-microgateway/edgemicro:3.3.12`) no longer includes `npm` and `npx`, requiring custom plugin dependencies to be installed *before* adding plugins to the container. Most importantly, this release addresses multiple critical security vulnerabilities (e.g., CVE-2026-12590, CVE-2026-14257, CVE-2026-111497). The Docker image is built on `node:24.22.1-trixie-slim` with Node.js fixes, and npm installations require upgrading Node.js runtime to specific patched versions (22.23.4, 24.22.1, or 26.12.1 or later). These security fixes are paramount for maintaining the integrity and confidentiality of API traffic, reducing the attack surface, and ensuring compliance with security best practices for API gateways. The Docker image changes promote a more secure build process by encouraging pre-installation of dependencies, mitigating potential runtime supply chain risks.\n    *   **Terraform Availability**: While Apigee Edge Microgateway itself doesn't have a dedicated Terraform resource for its configuration, its deployment targets (e.g., Cloud Run, GKE, Compute Engine) can be managed by Terraform. The provided Terraform support link refers to `google_cloud_run_service`, which could be used to deploy Apigee Edge Microgateway in a containerized environment.\n        *   Provider: `hashicorp/google`\n        *   Resource: `google_cloud_run_service` (for deployment target, not direct Microgateway configuration)\n        *   Versions: Supported since `1.0.0`, latest `5.0.0`.\n        *   [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_service)",
    "updates": [
      {
        "serviceName": "Bigtable",
        "serviceId": "bigtable",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigtable#November_09_2026"
      },
      {
        "serviceName": "Pathways on Cloud",
        "serviceId": "pathways-on-cloud",
        "category": "AI and Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=ai-hypercomputer#November_09_2026"
      },
      {
        "serviceName": "Cloud Run",
        "serviceId": "cloud-run",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-run#November_08_2026"
      },
      {
        "serviceName": "Anthos Config Management",
        "serviceId": "anthos-config-management",
        "category": "Management Tools",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=anthos-config-management#November_09_2026"
      },
      {
        "serviceName": "BigQuery",
        "serviceId": "bigquery",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigquery#November_09_2026"
      },
      {
        "serviceName": "Dataform",
        "serviceId": "dataform",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=dataform#November_09_2026"
      },
      {
        "serviceName": "Apigee Edge Microgateway",
        "serviceId": "apigee-edge-microgateway",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=apigee-edge-for-public-cloud#November_04_2026"
      }
    ]
  },
  {
    "date": "2026-11-09",
    "title": "Google Cloud Daily Brief: 5 service updates",
    "summaryMarkdown": "As your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive daily summary of the latest Google Cloud updates, focusing on their security implications and Infrastructure as Code (IaC) availability via the HashiCorp Google Terraform Provider.\n\n### Google Cloud Updates & Terraform Availability:\n\n*   **Agent Registry: Security Scanning, Governance, and CMEK Support**\n    *   **Feature & Security Summary:** The Agent Registry now includes security scanning and governance features for skills, enhancing the security posture of AI agents by allowing for vulnerability detection and policy enforcement. The introduction of Customer-Managed Encryption Keys (CMEK) support (in Preview) provides an additional layer of data protection for sensitive agent configurations, ensuring that data at rest is encrypted with keys managed by the customer. The General Availability (GA) of standalone Skill and SkillRevision resources further enables granular control and versioning of agent capabilities, which is crucial for auditing and maintaining a secure supply chain for AI components. These updates collectively improve the trustworthiness, compliance, and data security of AI agents deployed on Google Cloud.\n    *   **Terraform Availability:** Currently, there is no direct Terraform support for managing Agent Registry resources. For more information, refer to the [Google Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs).\n\n*   **Application Integration: Enhanced Service Account Impersonation Checks**\n    *   **Feature & Security Summary:** Google Cloud is enforcing the `iam.serviceAccounts.actAs` check for all Application Integration workflows, specifically when using scheduled or event triggers. This change mandates that the service account executing an integration must explicitly have the `iam.serviceAccounts.actAs` permission on any target service account it attempts to impersonate. This is a critical security enhancement that reinforces the principle of least privilege, preventing unauthorized service account impersonation and reducing the attack surface. It ensures that integrations can only perform actions with explicitly granted permissions, significantly improving the security and auditability of automated workflows. Existing integrations created before October 15, 2026, will be subject to this new behavior after January 15, 2027.\n    *   **Terraform Availability:** Supported. You can manage Application Integration connections using the `google_integration_connectors_connection` resource, available from provider version `4.50+` (latest `5.0+`). [Terraform `google_integration_connectors_connection` Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/integration_connectors_connection).\n\n*   **Cloud Asset Inventory: Visibility for KMS Key Access Justification Policies**\n    *   **Feature & Security Summary:** The Cloud Asset Inventory now publicly supports the `cloudkms.googleapis.com/KajPolicyConfig` resource type through its `SearchAllResources` and `SearchAllIamPolicies` APIs. This update provides security architects and compliance officers with unprecedented visibility into their Cloud KMS Key Access Justification (KAJ) policies. KAJ policies are crucial for controlling and auditing access to cryptographic keys, especially in highly regulated environments. By making these configurations discoverable via Cloud Asset Inventory, organizations can centralize auditing, enforce compliance standards, and quickly identify any misconfigurations or unauthorized changes to their key access justification policies, thereby strengthening their overall data protection strategy and regulatory adherence.\n    *   **Terraform Availability:** Supported. While `KajPolicyConfig` itself is not a direct Terraform resource, Cloud Asset Inventory feeds that can query such resources are manageable. You can manage Cloud Asset Inventory project feeds using the `google_cloud_asset_project_feed` resource, available from provider version `3.19.0` (latest `5.28.0`). [Terraform `google_cloud_asset_project_feed` Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_asset_project_feed).\n\n*   **Container-Optimized OS (COS): Critical Security Patches and Driver Updates**\n    *   **Feature & Security Summary:** Google has released significant updates for Container-Optimized OS (COS) images (cos-133-19999-44-193 and cos-121-18867-652-29), bringing crucial security and performance enhancements. Key updates include enabling PCI peer-to-peer direct memory access for 64k kernels, which can improve performance for specific workloads. Both image versions add support for NVIDIA driver v580.196.07, with cos-133-19999-44-193 also supporting v595.112.07 and upgrading `cos-gpu-installer` to v2.7.12. Most importantly, these updates address a wide array of security vulnerabilities (CVEs) across critical system components such as `cri-tools`, `containerd`, `docker`, `cos-extensions`, `guest-agent`, `cni-plugins`, `google-osconfig-agent`, `node-problem-detector`, and the Linux kernel itself. By patching these vulnerabilities and upgrading core libraries (e.g., `sqlite`, `nss`, `vim`), Google significantly bolsters the security posture of COS, reducing the risk of exploitation and ensuring a more robust and secure foundation for containerized workloads.\n    *   **Terraform Availability:** Supported. You can provision Compute Engine instances utilizing Container-Optimized OS images via the `google_compute_instance` resource, available from provider version `2.0.0` (latest `5.20.0`). [Terraform `google_compute_instance` Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_instance).\n\n## Google Cloud Security & IaC Daily Summary\n\nAs your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive overview of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability via HashiCorp Terraform.\n\n### AI & Machine Learning\n\n*   **Gemini Enterprise: Prepaid Credits for Enhanced Billing Flexibility**\n    *   **Feature & Security Summary:** This update introduces a significant shift in how Gemini Enterprise and associated AI developer tools are billed, moving towards a prepaid credit model for Pay-as-you-go editions and for usage exceeding quotas in other editions. The primary motivation is to offer greater cost control and predictability, eliminating traditional license fees for Pay-as-you-go and allowing users to pay only for actual consumption. Key functionalities include purchasing credits, tracking balances and transactions, and configuring auto-reload with optional monthly limits. Usage is automatically blocked if credits run out or monthly spend limits are hit, providing a robust mechanism for cost governance. Furthermore, AI developer tools can now be enabled on upgraded paid self-serve billing accounts with active Gemini Enterprise subscriptions, with usage paid via these credits. Users also gain access to detailed 30-day cost views and invoices for comprehensive financial oversight. From a security and compliance perspective, this feature enhances cost governance by preventing unexpected overspending, which is critical for budget adherence and preventing potential resource abuse. The automatic blocking of usage upon credit depletion acts as a safeguard against uncontrolled resource consumption, indirectly contributing to security by ensuring resources are not inadvertently exploited. The transparent cost and invoice monitoring provide essential audit trails for financial compliance.\n    *   **Terraform Availability:** Currently, there is no direct Terraform support for managing Gemini Enterprise prepaid credits, credit balances, or auto-reload configurations within the `hashicorp/google` provider. The provided `billing_account_iam` resource (`https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/billing_account_iam`) is for managing IAM policies on billing accounts, not for the specific credit management features of Gemini Enterprise. Support for these specific billing mechanisms is not available in any version of the provider at this time.",
    "updates": [
      {
        "serviceName": "Agent Registry",
        "serviceId": "agent-registry",
        "category": "AI and Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=agent-registry#November_06_2026"
      },
      {
        "serviceName": "Application Integration",
        "serviceId": "application-integration",
        "category": "Integration",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=application-integration#November_05_2026"
      },
      {
        "serviceName": "Cloud Asset Inventory",
        "serviceId": "cloud-asset-inventory",
        "category": "Management Tools",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-asset-inventory#November_06_2026"
      },
      {
        "serviceName": "Container-Optimized OS",
        "serviceId": "cos",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=container-optimized-os#November_05_2026"
      },
      {
        "serviceName": "Gemini Enterprise",
        "serviceId": "gemini-enterprise",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=gemini-enterprise#November_05_2026"
      }
    ]
  },
  {
    "date": "2026-11-07",
    "title": "Google Cloud Daily Brief: 8 service updates",
    "summaryMarkdown": "Good morning team, here's a comprehensive overview of the latest Google Cloud updates and their Terraform availability, focusing on security, compliance, and infrastructure as code.\n\n### **1. Cloud Trace: Data Residency and CMEK for Trace Buckets**\n\n*   **Feature & Security Summary**: Cloud Trace now supports reprovisioning of trace buckets to meet stringent data residency and Customer-Managed Encryption Keys (CMEK) requirements. This update is crucial for organizations operating under strict regulatory frameworks (e.g., GDPR, HIPAA) that mandate data localization and customer control over encryption keys. By allowing buckets to be reprovisioned to align with the organization's default observability bucket settings, it ensures that trace data, which can contain sensitive operational insights, adheres to defined geographic boundaries and is encrypted with keys managed by the customer. This significantly enhances the compliance posture and data sovereignty for critical observability data.\n*   **Terraform Availability**: Supported in the `hashicorp/google` provider. While the specific resource for 'trace bucket reprovisioning' is not explicitly named in the provided `terraformSupport` block, the service generally has support. The `terraformSupport` block indicates general Cloud Trace support from version `4.50+` (first) to `5.0+` (latest). For more details, refer to the [Cloud Trace provider documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_trace).\n\n### **2. Cloud Bigtable: Automated Daily Hot Backups (GA)**\n\n*   **Feature & Security Summary**: Cloud Bigtable has announced the General Availability (GA) of automated backup policy configuration for daily hot backups on SSD instances, complete with configurable retention. This is a critical enhancement for data resilience and disaster recovery. Automated daily hot backups minimize Recovery Point Objective (RPO) by ensuring frequent, consistent data snapshots with minimal performance impact on live instances. Configurable retention policies empower organizations to meet specific regulatory compliance requirements for data archival and retention, while also optimizing storage costs. This feature significantly strengthens the data protection strategy for Bigtable workloads.\n*   **Terraform Availability**: Supported in the `hashicorp/google` provider via the `google_bigtable_instance` resource. This feature is supported from version `4.0+` (first) to `5.0+` (latest). For more details, refer to the [Bigtable Instance provider documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigtable_instance).\n\n### **3. Artifact Registry: Assured Open Source Software Premium Tier Expansion**\n\n*   **Feature & Security Summary**: The Assured Open Source Software (AOSS) Premium tier now extends its support to Google Cloud regions and multi-regions for remote/proxy Artifact Registry repositories. This is a pivotal update for enhancing software supply chain security. AOSS provides curated, vulnerability-scanned, and signed open-source packages, mitigating risks associated with untrusted or compromised open-source dependencies. By expanding this coverage to regional and multi-regional proxy repositories, organizations can ensure that all their consumed open-source components, regardless of their origin or caching location, benefit from Google's rigorous security vetting. This directly contributes to a more secure software development lifecycle (SSDLC) and helps meet compliance standards requiring robust supply chain integrity.\n*   **Terraform Availability**: Supported in the `hashicorp/google` provider via the `google_artifact_registry_repository` resource. This feature is supported from version `4.0+` (first) to `5.0+` (latest). For more details, refer to the [Artifact Registry Repository provider documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/artifact_registry_repository).\n\n### **4. Cloud Load Balancing: IPv6 Frontend Configuration (GA)**\n\n*   **Feature & Security Summary**: Google Cloud Load Balancing now offers General Availability (GA) for frontend configuration to handle incoming IPv6 traffic across various regional and cross-region external/internal Application and Network Load Balancers. This update is essential for organizations transitioning to or operating in IPv6-enabled environments, addressing IPv4 address exhaustion and supporting modern network designs. From a security and operational standpoint, it ensures that critical load balancing functionalities, including traffic distribution, SSL termination, and WAF policies, can be consistently applied to both IPv4 and IPv6 traffic. This helps maintain a unified security posture across dual-stack deployments and supports compliance with IPv6 readiness mandates. To enable this, the associated proxy-only subnet must be configured with a `IPV4_IPV6` (dual-stack) type.\n*   **Terraform Availability**: Supported in the `hashicorp/google` provider. This feature is supported from version `3.4.0` (first) to `5.0.0` (latest). Relevant resources for configuring IPv6 frontends and dual-stack subnets would include `google_compute_forwarding_rule` (for load balancer frontend configuration) and `google_compute_subnetwork` (for setting the `stack_type` on proxy-only subnets). A specific provider documentation URL was not provided in the input.\n\nAs a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's your daily summary of critical Google Cloud updates and their IaC availability:\n\n### BigQuery: Enhanced Analytics, Model Governance, and Data Transfer Updates\n\n*   **Feature & Security Summary**: BigQuery introduces Graph capabilities and GQL support for on-demand pricing, significantly boosting its analytical power for connected datasets. A new custom organization policy (`constraints/bigquery.restrictModelOperations`) is in preview, enabling administrators to enforce granular controls over operations on BigQuery ML models. This is a crucial security enhancement for governing machine learning assets and ensuring compliance. Additionally, a breaking change for the BigQuery Data Transfer Service Shopify connector deprecates `legacyMode` and `permitSkuSharing` fields by January 31, 2027, requiring users to update configurations. \n    *   **Terraform Availability**: The custom organization policy for BigQuery models is supported via the `google_organization_policy` resource in the `hashicorp/google` provider, available from version `3.50.0` up to `5.28.0`. [Learn more](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/organization_policy).\n\n### Gemini Enterprise Agent Platform: Dedicated Memory Bank Management\n\n*   **Feature & Security Summary**: The Gemini Enterprise Agent Platform now features a dedicated Memory Bank page in the Google Cloud console. This update provides comprehensive management capabilities for memory banks, including creation (with Google-managed or Cloud KMS encryption), viewing, editing, and deletion. Users can inspect and filter memories (unstructured/structured), view revision history, and configure generation, retrieval, and retention policies. The platform also offers agent integration snippets and enhanced memory management controls for deployed agents. While not a direct security feature, the ability to manage encryption for memory banks is a key security control for sensitive AI data. \n    *   **Terraform Availability**: Direct Terraform support for managing Gemini Enterprise Agent Platform Memory Banks is currently not available in the `hashicorp/google` provider.\n\n### Config Controller: Underlying Config Connector Upgrade\n\n*   **Feature & Security Summary**: Config Controller has been updated to integrate Config Connector v1.159.0. This is an internal component upgrade that transparently enhances Config Controller's capabilities. Users will benefit from managing a broader set of Google Cloud resources, new features for existing resources, and general performance improvements and bug fixes inherited from the updated Config Connector version. This ensures that Config Controller remains a robust tool for declarative management of Google Cloud resources, aligning with DevSecOps principles by enabling consistent and auditable infrastructure as code. \n    *   **Terraform Availability**: Managing Config Controller instances is supported via the `google_config_controller_instance` resource in the `hashicorp/google` provider, available from version `4.40.0` up to `5.20.0`. [Learn more](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/config_controller_instance).\n\n### Apigee hybrid: Critical Stability and Security Patch Update\n\n*   **Feature & Security Summary**: This release for Apigee hybrid is a significant patch update focused on enhancing stability, reliability, and security. Key improvements include: correct processing of `HTTPS_PROXY` environment variables by `apigee-connect-agent` for egress, removal of compromised emSign and Comodo AAA Services roots from trust stores to bolster security, and a fix for incorrect `x-envoy-decorator-operation` header forwarding. The `apigee-redis` container has been updated to the Valkey engine (v8.1.10) while maintaining compatibility. Policy execution issues (e.g., `AssignMessage`, `OASValidation`) and Kubernetes configuration persistence problems have been resolved. A crucial security enhancement is the dynamic SSLContext rebuild for multi-certificate truststore changes, eliminating manual restarts. Most importantly, numerous security vulnerabilities (CVEs) have been addressed across a wide array of Apigee hybrid components, significantly improving the platform's overall security posture. \n    *   **Terraform Availability**: While `google_apigee_instance` exists for managing Apigee instances, specific configurations related to these detailed patch updates for Apigee hybrid components are generally managed within the Kubernetes cluster or via Apigee's own configuration mechanisms, and are not directly exposed as configurable resources in the `hashicorp/google` provider. [Learn more about Apigee instance management](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apigee_instance).",
    "updates": [
      {
        "serviceName": "Cloud Trace",
        "serviceId": "cloudtrace",
        "category": "Operations",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-trace#November_06_2026"
      },
      {
        "serviceName": "Cloud Bigtable",
        "serviceId": "bigtable",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigtable#November_06_2026"
      },
      {
        "serviceName": "Artifact Registry",
        "serviceId": "artifactregistry",
        "category": "DevOps",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=assured-open-source-software#November_06_2026"
      },
      {
        "serviceName": "Cloud Load Balancing",
        "serviceId": "cloud-load-balancing",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-load-balancing#November_06_2026"
      },
      {
        "serviceName": "BigQuery",
        "serviceId": "bigquery",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigquery#November_06_2026"
      },
      {
        "serviceName": "Gemini Enterprise Agent Platform",
        "serviceId": "gemini-enterprise-agent-platform",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=gemini-enterprise-agent-platform#November_06_2026"
      },
      {
        "serviceName": "Config Controller",
        "serviceId": "config-controller",
        "category": "Management Tools",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=config-controller#November_06_2026"
      },
      {
        "serviceName": "Apigee hybrid",
        "serviceId": "apigee-hybrid",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=apigee-hybrid#November_05_2026"
      }
    ]
  },
  {
    "date": "2026-11-06",
    "title": "Google Cloud Daily Brief: 9 service updates",
    "summaryMarkdown": "## Daily Google Cloud Security & IaC Update\\n\\nAs your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a summary of today's key updates, focusing on security, compliance, and Infrastructure as Code (IaC) availability.\\n\\n### 1. Model Armor: Enhanced CSAM Filter Controls\\n*   **Feature & Security Summary**: Google Cloud's Model Armor now offers granular control over its CSAM (Child Sexual Abuse Material) filter. This update allows users to enable or disable the filter and configure specific confidence levels (High, Medium and above, Low and above) directly within Model Armor templates and floor settings. This enhancement provides organizations with greater flexibility to align their AI models' content moderation with specific ethical guidelines, legal compliance requirements (e.g., GDPR, CCPA, child protection laws), and risk tolerance. By fine-tuning these settings, businesses can proactively mitigate legal and reputational risks associated with prohibited content, ensuring their AI systems operate responsibly and compliantly. This is a critical step towards more controllable and accountable AI deployments.\\n*   **Terraform Availability**: Terraform support is not yet available for Model Armor. Refer to the [Google Terraform Provider documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs) for future updates.\\n\\n### 2. Apigee Edge: Scheduled Control Plane Maintenance\\n*   **Feature & Security Summary**: Apigee Edge Public Cloud has announced its monthly scheduled maintenance window for control plane services. This routine operational activity is fundamental for maintaining the security, stability, and performance of the Apigee platform. Regular maintenance ensures that the underlying infrastructure and software components receive the latest security patches, bug fixes, and performance enhancements. This proactive approach is vital for minimizing vulnerabilities, preserving system integrity, and adhering to compliance standards that mandate consistent patching and system upkeep, thereby safeguarding the API ecosystem.\\n*   **Terraform Availability**: Terraform supports Apigee Edge organization management via the `google_apigee_organization` resource, available from provider version `2.0+` and fully supported in `5.0+`. See [Terraform Google Provider documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apigee_organization).\\n\\n### 3. API Gateway: Negative Backend Deadlines Reinstated\\n*   **Feature & Security Summary**: The deprecation of negative backend deadlines in API Gateway has been withdrawn. This reversal indicates a re-evaluation of the feature's utility, allowing for more flexible and efficient timeout management. Negative backend deadlines enable API Gateway to set a timeout for the backend service that is shorter than the overall request timeout. While not a direct security feature, this capability is crucial for system resilience and operational security. It helps prevent resource exhaustion and cascading failures by quickly terminating requests to slow or unresponsive backends, thereby maintaining the availability and performance of the API Gateway. This contributes to a more robust and predictable API infrastructure, essential for meeting service level agreements (SLAs) and preventing potential denial-of-service scenarios.\\n*   **Terraform Availability**: Terraform supports API Gateway configurations, including backend settings, via the `google_api_gateway_api_config` resource, available from provider version `4.0+` and fully supported in `5.0+`. See [Terraform Google Provider documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/api_gateway_api_config).\\n\\n### 4. Google SecOps: Case Activity Tagging\\n*   **Feature & Security Summary**: Google SecOps introduces 'Case activity tagging,' a new feature designed to significantly enhance the organization and efficiency of security incident response. Users can now add custom tags to various entries on the Case Wall, including activities, comments, tasks, and actions. This allows security teams to categorize and filter specific observations related to an incident, streamlining investigations. The ability to filter the Case Wall by these custom tags enables investigators to quickly focus on the most relevant information, accelerating analysis and resolution. This feature improves collaboration, provides better traceability of actions and decisions, and aids in demonstrating compliance with incident response frameworks (e.g., NIST, ISO 27001) by maintaining a clear, organized audit trail of the investigation process.\\n*   **Terraform Availability**: Terraform support for Google SecOps features, including case activity tagging, is not currently available in the `hashicorp/google` provider. Check future releases for potential integration.\n\n*   **Google Cloud Bigtable: Conversational Analytics & QueryData Tool (Preview)**\n    *   *Feature & Security Summary*: These new preview features enable users to interact with their operational data using natural language, leveraging the Conversational Analytics API and the QueryData tool. This aims to democratize data access, making it easier for a broader audience to derive insights without deep technical expertise. From a security and compliance perspective, while simplifying data exploration, it necessitates stringent IAM controls over access to these APIs and the underlying Bigtable instances to prevent unauthorized data exposure. Robust access management is crucial to maintain data confidentiality and integrity.\n    *   *Terraform Availability*: Direct Terraform support for these specific preview features (conversational analytics, QueryData tool) is not yet available in the `hashicorp/google` provider. Core Bigtable instance management is supported via `google_bigtable_instance` (e.g., [Bigtable Instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigtable_instance)).\n*   **Cloud Run: Ephemeral Disk (General Availability)**\n    *   *Feature & Security Summary*: Cloud Run's ephemeral disk is now Generally Available, providing temporary, instance-specific storage. This feature is crucial for applications requiring local scratch space for caching, temporary file processing, or intermediate results that do not need to persist beyond the instance's lifecycle. From a security standpoint, ephemeral disks enhance data hygiene by automatically purging data upon instance termination, significantly reducing the risk of sensitive data persistence and aiding compliance with data retention policies.\n    *   *Terraform Availability*: Supported. Configuration for ephemeral disks within Cloud Run services is available via the `google_cloud_run_v2_service` resource in the `hashicorp/google` provider, specifically within the `template.volumes` and `template.containers.volume_mounts` blocks. Support is available from version `4.0+`, with the latest features in `5.0+`. [Cloud Run v2 Service](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_v2_service).\n*   **BigQuery: Conversational Analytics Expansion & Metadata Management Shift**\n    *   *Feature & Security Summary*: Conversational analytics in BigQuery has expanded to the `asia-northeast1` (Tokyo) region, enabling natural language querying for regional users, similar to the Bigtable update. More significantly, the BigQuery Metadata curation console page has been deprecated, with users now directed to Google Cloud Data Catalog for all data governance activities. This shift centralizes metadata management, offering a unified platform for discovery, profiling, and quality management across Cloud Storage and BigQuery. This is a critical enhancement for data security and compliance, providing better visibility, control, and auditability of data assets, essential for regulations like GDPR and HIPAA.\n    *   *Terraform Availability*: While core BigQuery dataset management is well-supported via `google_bigquery_dataset` (available from `1.0.0`, latest `5.20.0+`), direct Terraform resources for conversational analytics or the explicit deprecation of the metadata console are not applicable. Data Catalog resources, such as `google_data_catalog_entry_group` or `google_data_catalog_entry`, would be used for managing the new recommended metadata governance approach. [BigQuery Dataset](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_dataset).\n*   **Security Command Center: Data Security Posture Management (DSPM) Deprecation**\n    *   *Feature & Security Summary*: The Data Security Posture Management (DSPM) feature within Security Command Center has been deprecated for new Google Cloud organizations, with existing users having until February 1, 2027, for full shutdown. This strategic shift requires organizations to proactively identify and implement alternative detection capabilities to maintain their data security posture. As a DevSecOps Lead, this necessitates an immediate review of current security controls and a plan to transition to new solutions to ensure continuous compliance and robust data protection.\n    *   *Terraform Availability*: As DSPM is being deprecated, there is no specific Terraform resource for its management or enablement. General Security Command Center configurations are managed through resources like `google_scc_organization_notification_config` or `google_scc_source`, but these do not directly address the deprecated DSPM feature.\n\n### Google Cloud Daily Security Brief: Vertex AI Enhancements for Genomic Data Streaming\n\nAs a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive summary of today's key Google Cloud updates and their Infrastructure as Code (IaC) availability.\n\n---\n\n#### **Vertex AI: AlphaGenome-004 Streaming & Genomic Modality Enhancements**\n\nVertex AI's AlphaGenome (alphagenome-004) has been updated to support unified HTTP/2 gRPC streaming and chunked binary protobuf HTTP streaming on the Gemini Enterprise Agent Platform. This significant enhancement allows for the efficient, low-latency transfer of compressed binary tensor chunks directly over gRPC (port 8081) and chunked binary protobuf payloads over HTTP (port 8080). This capability is crucial for high-throughput genomic analysis, applying across all seven DnaModelService methods and 11 genomic modalities, specifically reducing latency for 1 MB track predictions. The update also enables concurrent multi-variant evaluation for in silico saturation mutagenesis without HTTP gateway timeouts, improving operational efficiency for complex genomic research. From a security and compliance perspective, these streaming capabilities enhance data integrity during transit by reducing potential error surfaces and ensuring reliable delivery of sensitive genomic information. The improved performance and reliability are vital for regulated environments where timely and accurate processing of critical data is paramount. Furthermore, the retention of AlphaGenome-003 ensures backward compatibility, allowing for a controlled and secure transition for existing deployments. Model fold selection is now also supported across both gRPC and HTTP clients via the unified `alphagenome_cloud_sdk` Python SDK.\n\n**Terraform Availability:** Direct Terraform support for these specific AlphaGenome-004 streaming and genomic modality features is currently **not available**. While the `hashicorp/google` provider includes resources like `google_vertex_ai_endpoint` for managing Vertex AI endpoints, the granular control over these new streaming protocols and DnaModelService methods is not yet exposed. Users would typically manage the underlying Vertex AI infrastructure, and then configure these specific model runtime behaviors via SDKs or API calls.\n*   **Provider:** `hashicorp/google`\n*   **Resource (related):** `google_vertex_ai_endpoint`\n*   **Latest Version Support:** N/A (for these specific features)\n*   **First Version Support:** N/A (for these specific features)\n*   **Provider Documentation:** [Vertex AI Endpoint Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/vertex_ai_endpoint)",
    "updates": [
      {
        "serviceName": "Model Armor",
        "serviceId": "modelarmor",
        "category": "AI and Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=model-armor#November_05_2026"
      },
      {
        "serviceName": "Apigee Edge",
        "serviceId": "apigee",
        "category": "API Management",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=apigee-edge-for-public-cloud#November_05_2026"
      },
      {
        "serviceName": "API Gateway",
        "serviceId": "apigateway",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=api-gateway#November_04_2026"
      },
      {
        "serviceName": "Google SecOps",
        "serviceId": "google-secops",
        "category": "Security, Identity, & Compliance",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-secops#November_05_2026"
      },
      {
        "serviceName": "Google Cloud Bigtable",
        "serviceId": "bigtable",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigtable#November_04_2026"
      },
      {
        "serviceName": "Cloud Run",
        "serviceId": "cloud-run",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-run#November_04_2026"
      },
      {
        "serviceName": "BigQuery",
        "serviceId": "bigquery",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigquery#November_05_2026"
      },
      {
        "serviceName": "Security Command Center",
        "serviceId": "security-command-center",
        "category": "Security, Identity, & Compliance",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=security-command-center#November_05_2026"
      },
      {
        "serviceName": "Vertex AI",
        "serviceId": "vertex-ai",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=gemini-enterprise-agent-platform#November_04_2026"
      }
    ]
  },
  {
    "date": "2026-11-05",
    "title": "Google Cloud Daily Brief: 8 service updates",
    "summaryMarkdown": "As your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive summary of today's key Google Cloud updates and their Infrastructure as Code (IaC) availability:\n\n*   **AlloyDB for PostgreSQL**: This update introduces direct Iceberg access (Preview), syncing data from BigQuery (GA), and AlloyDB Express (Preview). These features enhance AlloyDB's capabilities for integrated analytics and high-performance operational workloads. Direct Iceberg access enables unified data lake integration, streamlining data governance and potentially reducing data movement, which improves data integrity and security posture by centralizing access control. Syncing data from BigQuery ensures data consistency across analytical and operational stores, critical for compliance and accurate reporting. AlloyDB Express offers specialized performance profiles, crucial for sensitive, high-throughput applications requiring stringent SLAs and consistent performance for security operations. Terraform support is available via the `google_alloydb_cluster` resource, supported from provider version `4.0.0` to `5.45.0+`. [Terraform Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/alloydb_cluster)\n\n*   **Cloud SQL for SQL Server**: The new Read pool autoscaling (GA) feature allows automatic adjustment of read replica capacity based on CPU usage and/or client connections. This is crucial for maintaining application availability and performance under varying loads, directly supporting business continuity and meeting RTO/RPO objectives. By preventing performance degradation, it indirectly supports compliance requirements for system availability and reliable data access. Terraform support is available via the `google_sql_database_instance` resource, supported from provider version `4.50+` to `5.0+`. [Terraform Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance)\n\n*   **API Gateway**: Streaming gateways can now securely call Google Cloud APIs, such as `aiplatform.googleapis.com`, using service-account access tokens for `*.googleapis.com` and `*.vertexai.goog` hosts. This significantly enhances the security posture by leveraging Google's IAM for fine-grained access control to backend services. It ensures that API Gateway acts as a secure front-door, authenticating and authorizing requests to internal GCP APIs using established service identity, thereby reducing the risk of unauthorized access and improving auditability. Terraform support is available via the `google_api_gateway_gateway` resource, supported from provider version `4.0+` to `5.0+`. [Terraform Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/api_gateway_gateway)\n\n*   **Cloud Storage**: A critical new feature allows pausing the permanent deletion of objects that have been soft-deleted from a Cloud Storage bucket. When enabled, this setting prevents objects from being irrevocably removed even after their configured `softDeletePolicy.retentionDuration` has expired. This provides administrators with additional time to restore soft-deleted objects, offering a critical safety net against accidental or malicious deletions. This functionality is configured as part of the bucket's `softDeletePolicy` and complements the existing soft delete retention duration, allowing for a more flexible and robust data recovery strategy. This is a vital security and compliance feature, significantly enhancing data recoverability and acting as an extended recovery window for soft-deleted data. It directly supports compliance requirements for data retention, e-discovery, and disaster recovery, mitigating the impact of human error or insider threats, and adding a layer of protection against ransomware or malicious deletion attempts. Terraform support is available via the `google_storage_bucket` resource, supported from provider version `5.1.0` to `5.1.0+`. [Terraform Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/storage_bucket)\n\nToday's Google Cloud updates bring significant enhancements across security, operations, and database management, with a strong focus on hardening infrastructure and streamlining administrative experiences. As a DevSecOps Lead and Terraform Specialist, I've analyzed these updates for their security implications and Infrastructure as Code (IaC) availability.\n\n- **Apigee Operator for Kubernetes v1.1.2**: This update introduces critical security enhancements by upgrading several core internal libraries, including Netty, Jackson, Jetty, Vert.x, and Guava. These upgrades collectively address numerous CVEs, substantially improving the overall security posture and stability of the Apigee Operator. This proactive patching is vital for maintaining a secure API gateway environment. Terraform support: Not currently available in the `hashicorp/google` provider.\n\n- **Google SecOps - Consolidated Settings and Navigation**: The platform now features a unified 'Settings' menu, replacing separate SIEM and SOAR settings. This new menu is logically organized into Administration, Access Management, Investigation, Detection, and Data Management categories, complemented by an updated left navigation. This streamlines the user experience and improves operational efficiency. Crucially, permissions are strictly enforced via Cloud IAM, with Cloud IAM Viewer and Editor roles gaining read-only access to specific SOAR settings, enhancing visibility for broader teams while maintaining robust access control. Terraform support: Not currently available in the `hashicorp/google` provider.\n\n- **Google Distributed Cloud (software only) for VMware - Security & Stability Enhancements**: Version 1.35.700-gke.124 delivers significant security and stability improvements. Key updates include the removal of distrusted eMudhra (emSign) and AAA Certificate Services root CAs from system components, container base images, Container-Optimized OS (COS), and Ubuntu node/admin workstation images. This action mitigates risks associated with compromised certificate authorities. The release also includes fixes for various vulnerabilities and resolves issues such as excessive audit logging traffic and cluster upgrade failures. This update is critical for maintaining a hardened hybrid cloud environment. Terraform support: Available via `google_gkeonprem_vmware_cluster` in the `hashicorp/google` provider (latest version, e.g., 5.x.x). [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gkeonprem_vmware_cluster).\n\n- **AlloyDB for PostgreSQL - Default to PostgreSQL Major Version 18**: New AlloyDB for PostgreSQL clusters will now default to PostgreSQL major version 18 upon provisioning if no specific version is declared. This ensures that new deployments automatically benefit from the latest performance, security, and feature enhancements offered by PostgreSQL 18, promoting best practices for database deployments. Terraform support: While the `google_alloydb_cluster` resource exists for managing AlloyDB clusters, this specific update regarding the *defaulting* of new clusters to PostgreSQL major version 18 is not directly configurable or managed as a default behavior via the `hashicorp/google` provider. [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/alloydb_cluster).",
    "updates": [
      {
        "serviceName": "AlloyDB for PostgreSQL",
        "serviceId": "alloydb",
        "category": "Database",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=alloydb-for-postgresql#November_04_2026"
      },
      {
        "serviceName": "Cloud SQL for SQL Server",
        "serviceId": "cloudsql-sqlserver",
        "category": "Database",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-sql-for-sql-server#November_04_2026"
      },
      {
        "serviceName": "API Gateway",
        "serviceId": "apigateway",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=api-gateway#November_03_2026"
      },
      {
        "serviceName": "Cloud Storage",
        "serviceId": "cloud-storage",
        "category": "Storage",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-storage#November_04_2026"
      },
      {
        "serviceName": "Apigee",
        "serviceId": "apigee",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=apigee-operator-for-kubernetes#November_04_2026"
      },
      {
        "serviceName": "Google SecOps",
        "serviceId": "google-secops",
        "category": "Security, Identity, & Compliance",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-secops#November_04_2026"
      },
      {
        "serviceName": "Google Distributed Cloud (software only) for VMware",
        "serviceId": "gdc-vmware",
        "category": "Hybrid & Multi-cloud",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-distributed-cloud-software-only-for-vmware#November_04_2026"
      },
      {
        "serviceName": "AlloyDB for PostgreSQL",
        "serviceId": "alloydb",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=alloydb-for-postgresql#November_03_2026"
      }
    ]
  },
  {
    "date": "2026-11-04",
    "title": "Google Cloud Daily Brief: 7 service updates",
    "summaryMarkdown": "As a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's your daily summary of critical Google Cloud updates and their IaC implications:\n\n*   **Cloud Service Mesh: Authorization Policies (Preview)**\n    *   **Feature & Security Summary**: This update introduces the ability to configure fine-grained authorization policies (`GCPAuthzPolicy`) on Cloud Service Mesh sidecars within GKE environments. It enables namespace and workload-level `allow/deny` rules, significantly enhancing the zero-trust security posture for microservices. Furthermore, it supports external authorization delegation via `GCPAuthzExtension`, allowing integration with existing identity and access management systems. This feature was introduced to provide more granular control over service-to-service communication, reducing the attack surface and aiding in compliance with stringent access control requirements. By enforcing authorization at the sidecar level, it ensures that only authorized workloads can communicate, even within the same mesh.\n    *   **Terraform Availability**: Supported. The HashiCorp Google Terraform Provider (`hashicorp/google`) can manage related features, typically through the `google_gke_hub_feature` resource. Support ranges from provider version `1.29.10-asm.0` to `1.31.3-asm.3`. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gke_hub_feature)\n\n*   **Knowledge Catalog: Knowledge Studio (Preview)**\n    *   **Feature & Security Summary**: Knowledge Studio in Knowledge Catalog is now available in Preview, offering interactive context graphs, automated enrichment tasks, and context sets specifically designed for AI agent grounding. This feature was introduced to improve the discoverability, understanding, and governance of enterprise data, particularly in the context of building and deploying AI agents. By providing richer metadata and contextual relationships, it helps ensure that AI models are grounded in accurate and relevant information, which is crucial for responsible AI development and preventing data misuse. From a security and compliance perspective, enhanced data cataloging and lineage improve data governance, making it easier to track data usage and enforce policies.\n    *   **Terraform Availability**: Not directly supported. There is no specific Terraform resource in the `hashicorp/google` provider to manage Knowledge Studio features at this time. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs)\n\n*   **AlloyDB for PostgreSQL: AI-powered SQL Query Tuning (Preview)**\n    *   **Feature & Security Summary**: AlloyDB for PostgreSQL now includes AI-powered SQL query tuning, exposed through the `ai.tune_sql` function (requiring `google_ml_integration` extension v1.6.2+). This capability leverages an LLM, combined with query execution plans, database schemas, and runtime statistics, to analyze SQL queries. It identifies performance bottlenecks and generates actionable recommendations, including query rewrites, index creation, statistics updates, GUC flag adjustments, and `ANALYZE`/`VACUUM` operations. This feature was introduced to automate and optimize database performance, reducing the manual effort required for tuning and ensuring applications run efficiently. While not a direct security feature, optimized database performance contributes to operational resilience and can prevent resource exhaustion, which could otherwise be exploited or lead to service degradation. It ensures the database operates optimally, indirectly supporting the availability and reliability of services.\n    *   **Terraform Availability**: Not directly supported. While AlloyDB instances can be managed via Terraform (e.g., `google_alloydb_instance`), the specific AI-powered SQL query tuning feature is not exposed as a configurable resource within the `hashicorp/google` provider at this time. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/alloydb_instance)\n\n*   **Google Cloud Vertex AI: Global Gemini 3.x Model Deployment**\n    *   **Feature & Security Summary**: This update enables users to leverage the Model Registry `models:copy` API to replicate fine-tuned Gemini 3.x models into the global region. Once copied, these models can be deployed to global serving endpoints, facilitating low-latency inference requests from diverse geographical locations. Inference requests are then routed directly to the `aiplatform.googleapis.com` endpoint, ensuring broad accessibility and performance for Gemini 3.x models. This feature was introduced to enhance the global reach and responsiveness of AI applications powered by Gemini models. From a security and compliance perspective, it allows organizations to deploy models closer to their users, potentially addressing data residency requirements and reducing latency for sensitive inference operations. It also ensures consistent and secure model deployment and serving across different regions.\n    *   **Terraform Availability**: Supported. The HashiCorp Google Terraform Provider (`hashicorp/google`) can manage Vertex AI endpoints, which are crucial for deploying these models. The relevant resource is `google_vertex_ai_endpoint`. Support ranges from provider version `4.10.0` to `5.20.0`. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/vertex_ai_endpoint)\n\n## Google SecOps\n\n*   **Feature & Security Summary**: Google SecOps has deprecated the `ListCaseEvents` API endpoint, replacing it with `ListCaseEvidenceData`. This change aims to provide a more precise and efficient way to retrieve evidence data related to security cases. From a security and compliance perspective, this update ensures that security operations teams have access to the most relevant and accurate evidence for incident response, forensic analysis, and audit trails. By streamlining evidence retrieval, it enhances the integrity and speed of security investigations, which is crucial for maintaining a strong security posture and meeting regulatory requirements. **Terraform Availability**: As of the latest information, direct Terraform support for managing specific Google SecOps API endpoints like `ListCaseEvents` or `ListCaseEvidenceData` is not available in the `hashicorp/google` provider. This typically means API interactions for such granular features are handled via custom scripts or client libraries rather than declarative IaC. Provider Resource Names: N/A, Latest Version Support: N/A, First Version Support: N/A, Provider Documentation: N/A.\n\n## Oracle Database@Google Cloud\n\n*   **Feature & Security Summary**: Oracle Database@Google Cloud now introduces 'Database Connections', enabling users to directly connect to their Oracle databases and execute SQL statements. This feature significantly streamlines database operations and integration within the Google Cloud ecosystem. From a security standpoint, while enhancing usability, it underscores the critical need for robust Identity and Access Management (IAM) controls, network segmentation, and encryption for all database connections. Ensuring least privilege access and monitoring connection attempts will be paramount to prevent unauthorized access and maintain data confidentiality and integrity. **Terraform Availability**: Currently, the `hashicorp/google` Terraform provider does not offer direct resources for managing 'Database Connections' within Oracle Database@Google Cloud. Infrastructure provisioning for the underlying Oracle Database@Google Cloud service itself might be available, but this specific feature is not exposed via IaC. Provider Resource Names: N/A, Latest Version Support: N/A, First Version Support: N/A, Provider Documentation: N/A.\n\n## Vertex AI\n\n*   **Feature & Security Summary**: Vertex AI's Model Armor now offers template-specific exclusion rules for streaming sanitization (StreamSanitizeUserPrompt and StreamSanitizeModelResponse) in Preview. These rules, leveraging dictionary and regular expression matching, are designed to mitigate false-positive detections for prompt injection, jailbreak detection, and other responsible AI filters. This significantly improves the precision of Model Armor's protective capabilities. From a DevSecOps perspective, this enhancement is critical for building more resilient and trustworthy AI applications. By reducing false positives, it allows security teams to focus on genuine threats, thereby improving operational efficiency, reducing alert fatigue, and ensuring the reliable and ethical deployment of AI models. **Terraform Availability**: As of the current release, there is no direct Terraform resource within the `hashicorp/google` provider to configure these specific template-specific exclusion rules for Vertex AI's streaming sanitization. Management of such granular AI safety features often relies on API calls or SDKs rather than declarative IaC. Provider Resource Names: N/A, Latest Version Support: N/A, First Version Support: N/A, Provider Documentation: N/A.",
    "updates": [
      {
        "serviceName": "Cloud Service Mesh",
        "serviceId": "cloud-service-mesh",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-service-mesh#November_02_2026"
      },
      {
        "serviceName": "Knowledge Catalog",
        "serviceId": "knowledge-catalog",
        "category": "Data Management",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=knowledge-catalog#November_02_2026"
      },
      {
        "serviceName": "AlloyDB for PostgreSQL",
        "serviceId": "alloydb-for-postgresql",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=alloydb-for-postgresql#November_02_2026"
      },
      {
        "serviceName": "Google Cloud Vertex AI",
        "serviceId": "vertex-ai",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=gemini-enterprise-agent-platform#November_02_2026"
      },
      {
        "serviceName": "Google SecOps",
        "serviceId": "google-secops",
        "category": "Security, Identity, & Compliance",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-secops#November_02_2026"
      },
      {
        "serviceName": "Oracle Database@Google Cloud",
        "serviceId": "oracle-database-at-google-cloud",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=oracle-database-google-cloud#November_03_2026"
      },
      {
        "serviceName": "Vertex AI",
        "serviceId": "vertex-ai",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=model-armor#November_02_2026"
      }
    ]
  },
  {
    "date": "2026-11-03",
    "title": "Google Cloud Daily Brief: 10 service updates",
    "summaryMarkdown": "As your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability:\n\n### Google Cloud Updates & Terraform Availability:\n\n*   **Backup and DR: Automated Resource Protection GA**\n    *   **Feature & Security Summary:** This update brings General Availability (GA) for automating resource protection for Compute Engine instances and disks at scale using auto-protection policies and resource labels. This is a significant enhancement for disaster recovery and operational resilience. By leveraging labels, organizations can ensure consistent backup coverage for critical assets, reducing manual overhead and the risk of human error. From a security and compliance perspective, automated and policy-driven backups are fundamental for data integrity, ransomware recovery, and meeting RTO/RPO objectives, ensuring business continuity. This proactive approach strengthens the overall security posture by guaranteeing data availability and recoverability.\n    *   **Terraform Availability:** Terraform support is currently not available for managing Backup and DR auto-protection policies directly within the `hashicorp/google` provider. Users should monitor the [Terraform Google Provider documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs) for future updates.\n\n*   **App Engine: Python 3.15 Runtime Preview**\n    *   **Feature & Security Summary:** App Engine now offers support for the Python 3.15 runtime in Preview. This update allows developers to leverage the latest features, performance improvements, and crucial security patches available in the newest Python version. Adopting modern runtimes is vital for maintaining secure applications, as newer versions often include fixes for known vulnerabilities, improved dependency management, and enhanced language security features. This helps in building more robust, efficient, and secure serverless applications.\n    *   **Terraform Availability:** Terraform supports App Engine application management via the `google_app_engine_application` resource, available from provider version `2.0+` and fully compatible with `5.0+`. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_application).\n\n*   **Apigee: EKM Health Monitoring with Cloud Logging**\n    *   **Feature & Security Summary:** Apigee now includes EKM (External Key Management) health monitoring with Cloud Logging integration for health checks and alerting on EKM-related issues. This is a critical security enhancement, providing deep visibility into the operational status of your external key management systems. For DevSecOps teams, this means proactive detection and rapid response to potential issues with key availability, rotation, or access, which are paramount for maintaining the confidentiality and integrity of API traffic and sensitive data. Automated alerting through Cloud Logging ensures that any EKM-related security incidents or operational disruptions are immediately flagged, enabling swift remediation and strengthening compliance with key management policies.\n    *   **Terraform Availability:** Terraform supports Apigee environment configuration, including aspects that would interact with EKM settings, via the `google_apigee_environment` resource, available from provider version `4.0+` and fully compatible with `5.0+`. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apigee_environment).\n\n*   **BigQuery: Enhanced Observability and Data Engineering Agent Support GA**\n    *   **Feature & Security Summary:** BigQuery now has GA support for monitoring data agents with Google Cloud Observability, alongside Data Engineering Agent support for BigQuery AI/ML/object functions in Dataform SQLX. The GA support for monitoring data agents provides comprehensive insights into the health and performance of data pipelines, which is crucial for identifying anomalies, potential data exfiltration attempts, or unauthorized data access. The Data Engineering Agent support within Dataform SQLX streamlines the development and deployment of advanced analytics and machine learning workflows, ensuring that data transformations and AI/ML models are built, governed, and managed securely. This enhances data integrity, auditability, and operational security for critical data assets, allowing for secure and compliant data processing and advanced analytics.\n    *   **Terraform Availability:** Terraform supports BigQuery dataset management via the `google_bigquery_dataset` resource, available from provider version `4.0+` and fully compatible with `5.0+`. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_dataset).\n\n### Google Cloud Updates: Enhanced Security & Modern Runtimes\\n\\nAs a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability.\\n\\n---\\n\\n#### Cloud NGFW: Advanced Malware Sandbox (WildFire) Integration GA\\n*   **Feature & Security Summary**: This update introduces the General Availability (GA) of advanced malware sandbox (WildFire) integration within the Cloud NGFW Enterprise tier. This was introduced to provide a deeper, more dynamic layer of threat detection beyond traditional signature-based methods. It works by leveraging machine learning and behavioral sandboxing to analyze suspicious traffic and files in an isolated environment, identifying zero-day threats and polymorphic malware before they can impact your network. The key security value lies in its proactive defense capabilities, significantly enhancing network perimeter security, reducing the attack surface, and aiding compliance with stringent security standards requiring advanced threat protection.\\n*   **Terraform Availability**: Supported via `hashicorp/google` provider, resource `google_compute_firewall`. First supported in version `4.50+`, with latest support in `5.0+`. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_firewall)\\n\\n#### Cloud Run functions: Python 3.15 Runtime Support (Preview)\\n*   **Feature & Security Summary**: Cloud Run functions now support the Python 3.15 runtime in Preview. This update allows developers to utilize the latest features, performance improvements, and standard library updates offered by Python 3.15 for their serverless functions. It was introduced to keep pace with language advancements and provide developers with modern tools. From a security perspective, using newer runtimes often means benefiting from the latest security patches and improvements within the language ecosystem, reducing the attack surface from older, potentially vulnerable versions and promoting a more secure development lifecycle.\\n*   **Terraform Availability**: Supported via `hashicorp/google` provider, resource `google_cloudfunctions2_function`. First supported in version `4.84.0`, with latest support in `5.48.0`. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloudfunctions2_function)\\n\\n#### Google App Engine: Python 3.15 Runtime Support in Flexible Environment (Preview)\\n*   **Feature & Security Summary**: The App Engine flexible environment now supports the Python 3.15 runtime in Preview. This enables developers to deploy applications leveraging Python 3.15's new language features, standard library updates, and performance enhancements. This was introduced to offer App Engine users the benefits of the latest Python version, ensuring their applications can be built with modern, efficient, and secure language constructs. The key security value is the ability to build applications on a more current and actively maintained runtime, which typically includes critical security fixes and performance optimizations, thereby reducing exposure to known vulnerabilities.\\n*   **Terraform Availability**: Supported via `hashicorp/google` provider, resource `google_app_engine_flexible_app_version`. Version support is N/A. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_flexible_app_version)\\n\\n#### Cloud Run: Python 3.15 Runtime Support (Preview)\\n*   **Feature & Security Summary**: Cloud Run now offers Python 3.15 runtime support in Preview for containerized applications. This allows developers to build and deploy their serverless containers using the newest Python language features and libraries, enhancing application performance and developer productivity. This update was introduced to provide Cloud Run users with access to the latest Python ecosystem advancements. From a security standpoint, utilizing Python 3.15 helps ensure applications are built on a more secure and performant foundation, benefiting from the latest security patches and reducing the risk associated with older, less maintained language versions.\\n*   **Terraform Availability**: Supported via `hashicorp/google` provider, resource `google_cloud_run_service`. First supported in version `4.0.0`, with latest support in `5.20.0`. [Documentation Link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_service)\n\n## Daily Google Cloud Security & IaC Summary\n\nAs your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive overview of today's key Google Cloud updates and their corresponding Infrastructure as Code (IaC) availability via the HashiCorp Google Terraform Provider.\n\n---\n\n### 1. Datastream Regional Expansion\n\n*   **Feature & Security Summary:** Datastream has expanded its global footprint, now available in the `africa-south1` (Johannesburg) and `asia-southeast3` (Bangkok) regions. This expansion is crucial for organizations requiring data residency within these geographies, enabling them to leverage Datastream for real-time change data capture (CDC) and replication workflows closer to their data sources and destinations. From a security and compliance perspective, this directly addresses data residency requirements (e.g., GDPR, local regulations) by minimizing cross-border data transfers and reducing data transit risks. It allows for the establishment of robust, compliant data pipelines that keep sensitive data within specified sovereign boundaries, enhancing overall data governance and reducing latency for critical data operations. Terraform support is available via the `google_datastream_stream` resource, supported from provider version `4.1.0` and fully compatible with `5.30.0`. [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/datastream_stream).\n\n### 2. Cloud Load Balancing Enhancements: Distributed Tracing & mTLS Relaxations\n\n*   **Feature & Security Summary:** Cloud Load Balancing introduces two significant updates for Application Load Balancers: Distributed tracing with Cloud Trace (Preview) and mTLS validation relaxations (GA). The introduction of distributed tracing with Cloud Trace provides deep observability into request flows, allowing security architects and SREs to pinpoint latency issues, identify anomalous behavior, and trace the full lifecycle of a request across microservices. This is invaluable for incident response, forensic analysis, and ensuring compliance by providing a clear audit trail. The mTLS validation relaxations, now Generally Available, offer greater flexibility in configuring mutual TLS. While the term 'relaxation' might suggest reduced security, it typically means more granular control to accommodate diverse client environments (e.g., legacy systems, specific IoT devices) without compromising the core security posture. It allows for tailored mTLS policies, ensuring strong client authentication and data integrity where critical, while providing operational agility. This enhances the zero-trust security model by ensuring authenticated and encrypted communication between clients and the load balancer. Terraform support for configuring Application Load Balancers, including aspects related to forwarding rules, is available via `google_compute_forwarding_rule` and related resources, supported from provider version `4.50+` and compatible with `5.0+`. [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_forwarding_rule).",
    "updates": [
      {
        "serviceName": "Backup and DR",
        "serviceId": "backupdr",
        "category": "Backup and Disaster Recovery",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=backup-and-dr#November_02_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "appengine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-python#November_02_2026"
      },
      {
        "serviceName": "Apigee",
        "serviceId": "apigee",
        "category": "API Management",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=apigee-x#November_02_2026"
      },
      {
        "serviceName": "BigQuery",
        "serviceId": "bigquery",
        "category": "Analytics",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigquery#November_02_2026"
      },
      {
        "serviceName": "Cloud NGFW",
        "serviceId": "cloud-ngfw",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-ngfw#November_02_2026"
      },
      {
        "serviceName": "Cloud Run functions",
        "serviceId": "cloud-run-functions",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-run-functions#November_02_2026"
      },
      {
        "serviceName": "Google App Engine",
        "serviceId": "app-engine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-flexible-environment-python#November_02_2026"
      },
      {
        "serviceName": "Cloud Run",
        "serviceId": "cloud-run",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-run#November_02_2026"
      },
      {
        "serviceName": "Datastream",
        "serviceId": "datastream",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=datastream#November_02_2026"
      },
      {
        "serviceName": "Cloud Load Balancing",
        "serviceId": "load-balancing",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-load-balancing#November_02_2026"
      }
    ]
  },
  {
    "date": "2026-11-01",
    "title": "Google Cloud Daily Brief: 6 service updates",
    "summaryMarkdown": "As a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability:\n\n### Daily Google Cloud Security & IaC Update\n\n*   **Secure Source Manager: Vulnerability Scanning for Dependencies**\n    *   **Feature & Security Summary:** This update introduces vulnerability scanning for dependencies within Secure Source Manager, a critical enhancement for software supply chain security. It was introduced to proactively identify known vulnerabilities in the third-party libraries and components used in your source code. By integrating scanning directly into the source management lifecycle, it helps developers and security teams detect and remediate security flaws early, significantly reducing the attack surface and ensuring compliance with secure development practices. This works by analyzing project dependencies against comprehensive vulnerability databases, providing actionable insights to maintain a robust security posture for your applications.\n    *   **Terraform Availability:** Supported. The `hashicorp/google` provider supports Secure Source Manager instances via the `google_secure_source_manager_instance` resource, available from version `5.10.0` up to `5.25.0`. [Learn more about `google_secure_source_manager_instance`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/secure_source_manager_instance)\n\n*   **Google Cloud Datastream: Integration with Knowledge Catalog (GA)**\n    *   **Feature & Security Summary:** Google Cloud Datastream now offers General Availability (GA) for its integration with Knowledge Catalog. This integration was introduced to enhance data governance, discoverability, and understanding of data replication and synchronization pipelines. It works by automatically ingesting metadata from Datastream streams\u2014including stream definitions, source/destination details, and schema information\u2014into Google Cloud Data Catalog. The key security and compliance value lies in providing a centralized, searchable catalog of streaming data assets, which improves data lineage tracking, facilitates compliance audits, and ensures better data quality and trust across the organization by making data replication processes transparent and governable.\n    *   **Terraform Availability:** Not directly supported for this specific integration feature. While the base `datastream_stream` resource exists, the integration with Knowledge Catalog is not yet exposed as a configurable attribute within the `hashicorp/google` provider. [Learn more about `datastream_stream`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/datastream_stream)\n\n*   **Google SecOps: General Availability for SAP Environments**\n    *   **Feature & Security Summary:** The GA release of Google SecOps for SAP marks a significant step in securing critical SAP landscapes. This offering was introduced to provide specialized security monitoring, threat detection, and automated response capabilities tailored for SAP environments, addressing their unique security challenges. It works by enabling log ingestion from diverse SAP deployments (RISE, self-managed, on-premises, other clouds), leveraging new SAP-specific YARA-L threat detection rules, and introducing automated security responses and containment actions via SAP RFC Gateway and SOAR playbooks (currently in Preview). The key security and compliance value is a dramatically improved ability to detect and respond to threats targeting sensitive SAP applications and data, ensuring business continuity and regulatory compliance.\n    *   **Terraform Availability:** Supported. While not directly named 'Google SecOps for SAP', related Chronicle (Google SecOps backend) feed configurations can be managed using the `google_chronicle_feed` resource in the `hashicorp/google` provider, available from version `5.0.0` up to `5.11.0`. [Learn more about `google_chronicle_feed`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/chronicle_feed)\n\n*   **Google Cloud Storage: Storage Intelligence Advisor Security & Compliance Findings (Preview)**\n    *   **Feature & Security Summary:** The Storage Intelligence advisor in Google Cloud Storage now offers security and compliance findings in Preview, specifically focusing on identifying and remediating encryption policy violations. This feature was introduced to empower users to proactively identify Cloud Storage buckets containing objects that do not comply with configured default Customer-Managed Encryption Key (CMEK) policies or enforced encryption rules. It works by scanning and highlighting non-compliant objects, then providing mechanisms to re-encrypt them. The key security and compliance value is ensuring a consistent and robust encryption posture for data at rest, preventing potential data exposure due to misconfigurations, and aiding organizations in meeting stringent regulatory requirements for data encryption.\n    *   **Terraform Availability:** Not directly supported for this specific feature. While the base `storage_bucket` resource allows configuration of CMEK and encryption policies, the Storage Intelligence advisor's findings and remediation suggestions are not yet exposed as configurable resources or data sources within the `hashicorp/google` provider. [Learn more about `storage_bucket`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/storage_bucket)\n\n### Google Cloud Spanner\n**Feature & Security Summary**: The latest update to Google Cloud Spanner introduces several key features for JSONB and JSON data types: (1) Equality and Ordering Comparisons \u2013 Spanner now supports direct equality and ordering comparisons on JSONB and JSON values; (2) GROUP BY and ORDER BY Support \u2013 JSONB and JSON values can be used directly in GROUP BY and ORDER BY clauses without requiring conversion; (3) CAST(expression AS JSON) \u2013 In GoogleSQL, users can convert other data types to JSON using the CAST function; (4) Implicit Coercion \u2013 Spanner can implicitly coerce non-JSON values to JSON for direct comparison; (5) Search Index Acceleration \u2013 Search indexes can now accelerate equality comparisons (= or IN) on JSONB/JSON columns and subpaths, significantly improving query performance. These enhancements were introduced to simplify JSON-centric application development, reduce query complexity, and deliver substantial performance gains while maintaining Spanner\u2019s strong consistency and compliance posture for regulated workloads handling semi-structured data. **Terraform Availability**: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) via `google_spanner_instance` and `google_spanner_database` resources since v1.0.0 (latest support in v5.0.0). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/spanner_instance_database)\n\n### Gemini Enterprise Agent Platform\n**Feature & Security Summary**: Two major Generally Available capabilities were released. 'Inference request metadata logging' generates privacy-preserving Cloud Logging entries for each inference request, capturing only metadata (model, region, token counts, latency, error codes, etc.) without prompts or responses. Activation via console or REST API also enables 1-second resolution metrics and enhanced observability dashboards; custom headers allow usage attribution for analytics. The 'Computer use tool' introduces robust Human-in-the-Loop (HITL) safety governance, allowing developers to configure confirmation policies and administrators to enforce organization-wide guardrails via the new `configurableComputerUseToolSafetyPolicies` Organization Policy constraint. These features were introduced to improve model observability, operational transparency, and centralized safety/compliance controls for AI agents handling sensitive or high-risk actions. **Terraform Availability**: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) via the `google_organization_policy` resource since v3.5.0 (latest support in v5.28.0). [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/organization_policy)",
    "updates": [
      {
        "serviceName": "Secure Source Manager",
        "serviceId": "securesourcemanager",
        "category": "Developer Tools",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=secure-source-manager#October_30_2026"
      },
      {
        "serviceName": "Google Cloud Datastream",
        "serviceId": "datastream",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=datastream#October_30_2026"
      },
      {
        "serviceName": "Google SecOps",
        "serviceId": "google-secops",
        "category": "Security, Identity, & Compliance",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=sap-on-google-cloud#October_30_2026"
      },
      {
        "serviceName": "Google Cloud Storage",
        "serviceId": "cloud-storage",
        "category": "Storage",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-storage#October_30_2026"
      },
      {
        "serviceName": "Google Cloud Spanner",
        "serviceId": "cloud-spanner",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=spanner#October_30_2026"
      },
      {
        "serviceName": "Gemini Enterprise Agent Platform",
        "serviceId": "gemini-enterprise-agent-platform",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=gemini-enterprise-agent-platform#October_30_2026"
      }
    ]
  },
  {
    "date": "2026-10-31",
    "title": "Google Cloud Daily Brief: 9 service updates",
    "summaryMarkdown": "## Google Cloud Daily Security & IaC Update\n\nAs your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive summary of today's key updates, focusing on their security implications and Infrastructure as Code (IaC) availability.\n\n### 1. BigQuery: Apache Arrow Format for Query Results (Preview)\n*   **Feature & Security Summary**: This update introduces support for retrieving BigQuery query results directly in Apache Arrow format. This was introduced to significantly accelerate data retrieval for analytical workloads, particularly beneficial for data scientists and machine learning engineers who need efficient, in-memory columnar data processing. By reducing serialization and deserialization overhead, it streamlines data pipelines. From a security and compliance perspective, while not a direct security feature, faster data processing enables quicker security analytics, threat detection, and compliance reporting by accelerating data ingestion into other tools. Data remains within BigQuery's robust security model, ensuring governance and access controls are maintained.\n*   **Terraform Availability**: Supported via the `hashicorp/google` provider, primarily through the `google_bigquery_job` resource for managing query execution. This feature is supported in provider versions `5.0+`, with initial support from `4.0+`. [Terraform Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_job)\n\n### 2. Apigee hybrid: Critical Security & Stability Fixes\n*   **Feature & Security Summary**: Apigee hybrid has received crucial updates addressing several security and stability issues. Key fixes include resolving a regression where `apigee-connect-agent` ignored `HTTPS_PROXY` settings, which is vital for ensuring all outbound traffic adheres to organizational network security policies and passes through required proxies for inspection and control. Compromised emSign/Comodo roots have been removed from trust stores, significantly enhancing supply chain security by preventing potential man-in-the-middle attacks and ensuring only trusted certificates are recognized. Additionally, corrections were made to `x-envoy-decorator-operation` header forwarding and LLM token quota flow variable assignment, improving API gateway reliability. Most importantly, multiple CVEs in core Apigee hybrid containers have been patched, directly reducing the attack surface and mitigating known vulnerabilities. These updates are critical for maintaining a strong security posture, compliance with network policies, and overall platform integrity for hybrid API deployments.\n*   **Terraform Availability**: Management of Apigee organizations and related configurations is supported by the `hashicorp/google` provider using the `google_apigee_organization` resource. This update's underlying platform fixes are reflected in provider version `1.16.13`, with initial support from `1.0`. [Terraform Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apigee_organization)\n\n### 3. Google Cloud SQL: Enhanced Backup Plan Modification\n*   **Feature & Security Summary**: This new feature for Cloud SQL enables users to modify existing backup plans with greater flexibility. Specifically, it allows for updating settings such as backup rules (e.g., frequency, time) and adjusting the maximum custom on-demand retention periods. This was introduced to provide more granular control and adaptability for data recovery strategies, aligning with evolving business requirements and regulatory compliance. From a security and compliance perspective, this enhancement directly contributes to improved data resilience and disaster recovery capabilities. Granular control over backup policies helps organizations meet stringent Recovery Point Objective (RPO) and Recovery Time Objective (RTO) targets, and ensures compliance with data retention regulations by allowing precise configuration of backup schedules and retention periods for sensitive data.\n*   **Terraform Availability**: Cloud SQL instance configurations, including backup settings, are managed via the `hashicorp/google` provider using the `google_sql_database_instance` resource. This feature is supported in provider versions `5.20.0`, with initial support from `4.0.0`. [Terraform Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance)\n\n### 4. Cloud Run: GPU-Enabled Jobs (Preview)\n*   **Feature & Security Summary**: Cloud Run now supports running jobs with GPUs enabled for up to 12 hours (Preview). This expansion was introduced to enable Cloud Run to handle compute-intensive workloads that benefit significantly from GPU acceleration, such as machine learning inference, data processing, and scientific simulations, within a serverless and managed environment. From a security and compliance standpoint, while the feature itself is about compute capability, it allows organizations to execute high-performance, specialized workloads securely within Cloud Run's isolated and managed infrastructure. This means GPU-accelerated tasks benefit from Cloud Run's inherent security features, including container isolation, built-in IAM integration for fine-grained access control, and automatic patching, ensuring that sensitive data processing occurs in a controlled and secure environment without the operational overhead of managing underlying infrastructure.\n*   **Terraform Availability**: Cloud Run jobs are managed using the `hashicorp/google` provider via the `google_cloud_run_v2_job` resource. This feature is supported in provider versions `5.0+`, with initial support from `4.0+`. [Terraform Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_v2_job)\n\nAs a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's your comprehensive daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability:\n\n### Google Cloud Updates & Terraform Availability (October 30, 2026)\n\n*   **Google Cloud Bigtable - Knowledge Catalog Integration GA**\n    *   **Feature & Security Summary**: This update introduces the general availability (GA) of Bigtable's integration with Knowledge Catalog. This was introduced to significantly enhance metadata management and data asset visibility for Bigtable users. It allows for the discovery and search of specific Bigtable data assets, including authorized views, logical views, and continuous materialized views, directly within Knowledge Catalog. This capability centralizes the discovery of Bigtable's granular data structures alongside its instances and tables. From a security and compliance perspective, this integration provides a unified view of data assets, making it easier to track, audit, and govern sensitive data. It improves data lineage understanding, aids in compliance reporting by centralizing metadata, and helps enforce data access policies by providing better context on data usage. This is a critical step towards robust data governance and meeting regulatory requirements.\n    *   **Terraform Availability**: This specific integration for discovering Bigtable views within Knowledge Catalog is not directly exposed as a dedicated resource in the `hashicorp/google` Terraform provider. While `google_bigtable_instance` and `google_bigtable_table` manage Bigtable resources, and `google_data_catalog_entry_group`, `google_data_catalog_entry`, `google_data_catalog_tag_template` manage Data Catalog components, the direct linkage for *discovering Bigtable views* is a service-level integration rather than a configurable IaC resource. Therefore, direct Terraform support for this specific integration is not available. (Supported: false, Latest Version: N/A, First Version: N/A, Provider Doc: N/A)\n\n*   **Cloud SQL for PostgreSQL - Updated Time Zone Rules**\n    *   **Feature & Security Summary**: This update addresses time zone rules for specific Canadian provinces/territories, reflecting permanent standard offsets. This was introduced to ensure the accuracy and consistency of time-sensitive data within Cloud SQL for PostgreSQL instances. Incorrect time zone handling can lead to data integrity issues, misaligned timestamps, and potential compliance violations, especially for applications dealing with financial transactions, logging, or scheduling across different regions. The update, available in PostgreSQL maintenance release `*.R20260712.01_44` or later, ensures that all time-based operations and data storage accurately reflect the local time, preventing operational discrepancies and supporting reliable auditing and reporting.\n    *   **Terraform Availability**: Cloud SQL for PostgreSQL instances are managed by the `google_sql_database_instance` resource. While the specific maintenance release is applied by Google Cloud, Terraform can manage the instance configuration, including `database_version` and `settings.maintenance_window` to ensure instances are eligible for updates. (Supported: true, Latest Version: 5.0+, First Version: 4.0+, Resource: `google_sql_database_instance`, Provider Doc: [https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance))\n\n*   **Cloud SQL for MySQL - Updated Time Zone Rules**\n    *   **Feature & Security Summary**: Similar to PostgreSQL, this update details a correction to Cloud SQL for MySQL's internal time zone rules to accurately reflect permanent standard daylight offsets across Alberta, British Columbia, Manitoba, and Northwest Territories. This is crucial for maintaining data integrity and preventing discrepancies in time-sensitive operations, which could impact compliance, reporting, and application logic. The updated rules are supported in Cloud SQL for MySQL maintenance release `*.R20260726.00_36` or later. An alternative mitigation involves configuring the `default_time_zone` database flag to a fixed numeric offset, which can be applied without an instance restart, though applying the maintenance release is the recommended long-term solution for comprehensive accuracy.\n    *   **Terraform Availability**: Cloud SQL for MySQL instances are managed using the `google_sql_database_instance` resource. The `settings.database_flags` argument can be used to configure the `default_time_zone` flag if the alternative mitigation is chosen. Maintenance windows can also be managed via `settings.maintenance_window`. (Supported: true, Latest Version: 4.80.0, First Version: 1.0.0, Resource: `google_sql_database_instance`, Provider Doc: [https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance))\n\n*   **Cloud SQL for SQL Server - Time Zone Lag Resolution**\n    *   **Feature & Security Summary**: This announcement addresses a critical operational issue where Cloud SQL for SQL Server instances configured with specific Canadian time zones (Pacific Standard Time, Mountain Standard Time, Central Standard Time) would incorrectly observe a one-hour lag after November 1, 2026. This issue could lead to significant data integrity problems, incorrect scheduling, and compliance failures for applications relying on accurate timestamps. The recommended fix involves updating the instance's time zone setting to a corresponding Windows time zone with a fixed UTC offset (e.g., 'Pacific Standard Time' to 'Yukon Standard Time' for British Columbia). This proactive measure ensures precise timekeeping, preventing data corruption and maintaining the reliability of time-sensitive operations and audit trails.\n    *   **Terraform Availability**: Cloud SQL for SQL Server instances are managed by the `google_sql_database_instance` resource. The `settings.time_zone` argument within this resource can be used to configure the instance's time zone, allowing for the recommended fix to be applied via IaC. (Supported: true, Latest Version: 5.0.0, First Version: 1.0.0, Resource: `google_sql_database_instance`, Provider Doc: [https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance))\n\n### AlloyDB for PostgreSQL\n**Feature & Security Summary:** The enhancement improves operational experience for Advanced Query Insights on AlloyDB for PostgreSQL. For clusters running PostgreSQL 18 or newer, modifications to settings such as `query_string_length` and enabling active query analysis can now be performed without requiring an instance restart. This change reduces downtime, increases administrative agility, and maintains strong observability for query performance and security analysis. For clusters on PostgreSQL 17 or earlier, a restart is still required. The feature strengthens compliance and security posture by enabling faster tuning of query insights without interrupting workloads. **Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) via `google_alloydb_cluster` resource (query_insights_config block) since version 4.30.0. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/alloydb_cluster#query_insights_config)",
    "updates": [
      {
        "serviceName": "BigQuery",
        "serviceId": "bigquery",
        "category": "Analytics",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigquery#October_30_2026"
      },
      {
        "serviceName": "Apigee hybrid",
        "serviceId": "apigee-hybrid",
        "category": "API Management",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=apigee-hybrid#October_30_2026"
      },
      {
        "serviceName": "Google Cloud SQL",
        "serviceId": "cloud-sql",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=backup-and-dr#October_30_2026"
      },
      {
        "serviceName": "Cloud Run",
        "serviceId": "cloud-run",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-run#October_30_2026"
      },
      {
        "serviceName": "Google Cloud Bigtable",
        "serviceId": "bigtable",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigtable#October_30_2026"
      },
      {
        "serviceName": "Cloud SQL for PostgreSQL",
        "serviceId": "cloudsql-postgresql",
        "category": "Database",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-sql-for-postgresql#October_30_2026"
      },
      {
        "serviceName": "Cloud SQL for MySQL",
        "serviceId": "cloud-sql-mysql",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-sql-for-mysql#October_30_2026"
      },
      {
        "serviceName": "Cloud SQL for SQL Server",
        "serviceId": "cloud-sql-sql-server",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-sql-for-sql-server#October_30_2026"
      },
      {
        "serviceName": "AlloyDB for PostgreSQL",
        "serviceId": "alloydb-postgresql",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=alloydb-for-postgresql#October_30_2026"
      }
    ]
  },
  {
    "date": "2026-10-27",
    "title": "Google Cloud Daily Brief: 30 service updates",
    "summaryMarkdown": "# Daily Google Cloud Updates Summary (October 26, 2026)\n\n## Service Updates\n\n- **Cloud Database Migration Service**: The update introduces heterogeneous conversion workspaces via importing database schema metadata files from Cloud Storage. It was introduced to simplify Oracle and SQL Server to PostgreSQL/AlloyDB migrations by removing the need for direct network connectivity to the source database during schema conversion. This reduces the network attack surface, supports zero-trust architectures, and aids compliance in restricted environments by limiting direct database exposure. Terraform support appended: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) v4.75.0+ with the [`google_database_migration_service_conversion_workspace`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/database_migration_service_conversion_workspace) resource.\n\n- **Apigee X**: Addresses Model Context Protocol (MCP) tool argument placement so that OpenAPI 'in: header' parameters are sent as request headers and 'in: cookie' parameters are sent in the Cookie header (instead of incorrectly to the query string). 'in: query' and 'in: path' are unchanged; for tool calls with cookies the Cookie header is limited to declared parameters only. Introduced to correct transmission behavior for security and correctness; existing proxies retain legacy behavior until redeployed. Key security/compliance value is proper handling of sensitive headers/cookies to prevent leakage, injection, or auth bypass risks. Terraform support appended: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) via the [`google_apigee_instance`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apigee_instance) resource (version support N/A for this specific feature).\n\n- **Compute Engine**: Delivers a patch for an incorrect authorization vulnerability per the GCP-2026-073 security bulletin. Introduced to eliminate unauthorized access paths; it works by correcting auth logic and promotes hardened IAM roles, encryption defaults, and organizational policy enforcement. Key security/compliance value includes least-privilege controls, reduced attack surface, and alignment with regulatory requirements for secure VM management. Terraform support appended: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) since v1.0.0 (latest v5.15.0) with the [`google_compute_instance`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_instance) resource.\n\n- **Gemini Enterprise Agent Platform**: Enables toggling of user intent matching for semantic governance policies via the `sgpUserIntentMatching` key (default enabled) in authorization extension metadata; logs now report `sgpUserIntentMatchingMode`. Disabling reduces protection against indirect prompt injection. Introduced to offer policy flexibility with visibility into evaluation mode. Key security/compliance value is tunable AI safety controls (keep enabled for maximum prompt-injection defense in agent workflows). Terraform support appended: Not currently supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) (N/A); related support via the [`google_dialogflow_cx_agent`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/dialogflow_cx_agent) resource.\n\n# Google Cloud Daily Security and IaC Summary\n\n**Date:** October 26, 2026\n\n**Overview:** As a Google Cloud Security Architect and Terraform Specialist, this daily summary analyzes today's feature updates with emphasis on security implications, compliance benefits, and Infrastructure as Code (IaC) readiness using the HashiCorp Google Terraform Provider (`hashicorp/google`). All listed services are covered individually.\n\n## Updates\n\n- **Agent Platform Workbench** (Category: AI and Machine Learning): Feature & Security Summary: This update was introduced to proactively mitigate risks from outdated libraries by delivering security vulnerability fixes and dependency updates for certifi, pip, and CA certificates. It works by refreshing the workbench runtime environment to incorporate patched components that prevent certificate-related exploits and supply-chain attacks. Key security/compliance value: Significantly reduces the attack surface for AI/ML development environments and supports adherence to standards such as SOC 2, ISO 27001, and secure software development frameworks. Terraform support: Supported in `hashicorp/google` provider since v4.5.0 (latest v6.0.0) - [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs).\n\n- **BigQuery** (Category: Data Analytics): Feature & Security Summary: Python user-defined functions (UDFs) now support volume mounts to access dependency files from Cloud Storage directly; introduced in Preview to simplify complex analytics workflows and eliminate the need to embed large dependency files within UDF code. It works by allowing GCS paths to be mounted into the UDF execution context at runtime. Key security/compliance value: Enables finer-grained IAM-based access controls on Cloud Storage buckets holding dependencies, reducing code duplication risks and supporting data governance policies by keeping sensitive assets outside the query logic. Terraform support: Not yet supported in the HashiCorp Google Terraform Provider (`hashicorp/google`); see related `google_bigquery_routine` resource at [BigQuery Routine](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_routine).\n\n- **Oracle Database@Google Cloud** (Category: Analytics & Data): Feature & Security Summary: General availability of the remote MCP server adds tools to create/manage Database Connections and execute SQL via the `database_connection_executesql` function; introduced to streamline operations and enable direct integration with modern AI technologies such as LLMs and AI-enabled platforms. It works by exposing secure, abstracted interfaces for interaction with Oracle resources without exposing raw connection details. Key security/compliance value: Facilitates auditable, IAM-controlled access patterns for AI-to-database interactions, reducing credential exposure risks and aiding compliance in regulated hybrid database environments. Terraform support: Not currently supported in the HashiCorp Google Terraform Provider (`hashicorp/google`).\n\n- **Google SecOps** (Category: Security, Identity, & Compliance): Feature & Security Summary: Users can now resize inline images directly within rich-text comments on the Case Wall by entering rich-text mode, inserting images, and dragging resize handles; introduced to improve usability and visual documentation during security investigations. It works through enhancements to the comment editor UI. Key security/compliance value: Improves the fidelity of incident records and forensic artifacts on the Case Wall, supporting more effective threat analysis, audit readiness, and knowledge retention within security operations centers. Terraform support: Not currently supported in the HashiCorp Google Terraform Provider (`hashicorp/google`).\n\nAs your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability:\n\n### AI and Machine Learning\n\n*   **Model Armor (GA)**\n    *   **Feature & Security Summary**: This update introduces a critical enhancement to data residency compliance for AI models. Model Armor now enforces the `constraints/modelarmor.managed.requireTemplateDataResidencyCompliance` managed Organization Policy Service constraint by default. This prevents users from inadvertently setting `data_residency_compliant` to `false` or clearing the 'Enforce data residency' option when creating or updating a template, unless explicitly disabled by an Organization Policy Administrator. This feature significantly strengthens data governance and ensures AI model templates adhere to specified residency requirements, reducing the risk of non-compliance. \n    *   **Terraform Availability**: Supported via the `hashicorp/google` provider. You can manage this organization policy using the `google_org_policy_policy` resource, available from version `5.10.0` up to `5.27.0`. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/google_org_policy_policy)\n\n*   **Vertex AI Workbench**\n    *   **Feature & Security Summary**: Vertex AI Workbench has received important security and stability updates. This includes installing the latest packages from upstream dependencies like `certifi`, `pip`, and `conda ca-certificates`, addressing multiple reported security vulnerabilities in bundled packages. Additionally, it fixes issues related to dataset/table search and Jupyter Server terminal configuration. These updates are crucial for maintaining a secure development environment, mitigating known vulnerabilities in common data science tools, and ensuring the integrity of your AI/ML workflows.\n    *   **Terraform Availability**: Supported via the `hashicorp/google` provider. Vertex AI Workbench instances can be provisioned and managed using the `google_notebooks_instance` resource, available from version `4.80.0` up to `5.25.0`. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/notebooks_instance)\n\n### Compute\n\n*   **App Engine flexible environment (.NET Runtimes)**\n    *   **Feature & Security Summary**: This is a critical security maintenance update for the App Engine flexible environment, specifically targeting .NET runtimes and underlying operating system packages. Affected .NET runtimes include .NET 6 (updated to 6.0.428), .NET 8 (updated to 8.0.415), and .NET 10 (updated to 10.0.100). Furthermore, the `google-22`, `google-22-full`, `google-24`, and `google-24-full` base OS stacks have received security patches. While core functionality remains unchanged, users **must rebuild and redeploy** their applications to apply these patches. This update is vital for mitigating known security vulnerabilities and ensuring your applications run on a hardened, compliant environment.\n    *   **Terraform Availability**: Supported via the `hashicorp/google` provider. App Engine flexible environment application versions can be managed using the `google_app_engine_flexible_app_version` resource, available from version `4.0.0` up to `~> 5.0`. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_flexible_app_version)\n\n*   **Google App Engine flexible environment (Java Runtimes)**\n    *   **Feature & Security Summary**: Similar to the .NET update, this announcement details important security updates for specific Java runtimes and underlying operating system packages in the App Engine flexible environment. Affected Java versions are 17.0.20_101, 21.0.12_101.0.LTS, and 25.0.5_8.0.LTS. The underlying OS packages for the `google-22`, `google-22-full`, `google-24`, and `google-24-full` stacks have also been updated with security patches. These are not new feature releases but critical security patches requiring user action (rebuild and redeploy) to ensure applications run on secure, updated environments. This proactive patching is essential for maintaining a strong security posture and protecting against potential exploits.\n    *   **Terraform Availability**: Supported via the `hashicorp/google` provider. App Engine flexible environment application versions can be managed using the `google_app_engine_flexible_app_version` resource, available from version `1.0.0` up to `5.0.0`. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_flexible_app_version)\n\n# Google Cloud Daily Security Summary: App Engine Runtime & OS Updates (Oct 2026)\n\nGoogle Cloud has issued critical security patches across App Engine flexible environment runtimes and base OS stacks. These updates address vulnerabilities in language-specific runtimes and underlying OS images (e.g., google-22, google-24 families). They were introduced to reduce exposure to known exploits, strengthen the security posture, and support compliance by ensuring patched dependencies. Updates take effect only after users rebuild artifacts and redeploy services. Below is a dedicated entry for every update in the list.\n\n* **App Engine (Compute)**: Feature & Security Summary: Go runtime patches and updated base OS stacks (google-22, google-24) for security. Introduced to mitigate vulnerabilities in the Go runtime and OS layers; works by providing new base images that require application rebuild and redeploy. Key security/compliance value includes reduced attack surface and adherence to latest patch levels. Terraform support: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) (first supported v3.50.0, latest v5.27.0) - [app_engine_flexible_app_version](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_flexible_app_version).\n\n* **Google App Engine (Compute)**: Feature & Security Summary: The announcement details security updates for specific PHP runtime patch versions: PHP 8.2.35, PHP 8.3.36, PHP 8.4.27, and PHP 8.5.12. These updates are critical for maintaining the security posture of applications running on the App Engine flexible environment. Furthermore, the underlying operating system packages for the 'google-22', 'google-22-full', 'google-24', and 'google-24-full' stacks have also received security patches. The core functionality updated is the security hardening of the runtime environment itself, requiring users to rebuild and redeploy their applications to leverage these updated dependencies. Terraform support: Not supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) (N/A) - reference [app_engine_flexible_app_version](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_flexible_app_version).\n\n* **App Engine (Serverless)**: Feature & Security Summary: Security patches for Node.js runtimes and underlying OS packages in App Engine flexible environment stacks. Introduced to close vulnerabilities in Node.js and base OS components; requires rebuild/redeploy to activate the hardened stacks. Delivers key security/compliance value by keeping runtimes current and minimizing exposure to threats. Terraform support: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) (first supported v3.50.0, latest v5.27.0) - [app_engine_flexible_app_version](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_flexible_app_version).\n\n* **Google App Engine (Compute)**: Feature & Security Summary: This announcement details security updates for specific Ruby runtime versions available in the App Engine flexible environment: Ruby 3.3.12, 3.4.11, and 4.0.7. Additionally, the underlying operating system packages for the 'google-22', 'google-22-full', 'google-24', and 'google-24-full' stacks have been updated. These are not new features but critical security patches to existing runtimes and base images. To benefit from these updates, users must rebuild their application artifacts and redeploy their App Engine flexible environment services. This action will ensure that new deployments utilize the patched runtime and OS images provided by Google. Terraform support: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) (first supported v3.0.0, latest v5.20.0) - [app_engine_flexible_app_version](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_flexible_app_version).\n\n### Daily Google Cloud Security & IaC Summary\\n\\nToday's updates focus heavily on critical security patches for various App Engine runtimes and underlying operating system stacks, emphasizing the importance of keeping applications up-to-date to mitigate vulnerabilities. As a DevSecOps Lead, these updates highlight the continuous need for robust CI/CD pipelines that can quickly rebuild and redeploy applications to incorporate the latest security fixes.\\n\\n---\\n\\n### App Engine (Java Standard Environment)\\n\\n*   **Feature & Security Summary**: Google has released critical security updates for specific Java runtime versions (Java 17.0.20_101, Java 21.0.12_101.0.LTS, and Java 25.0.5_8.0.LTS) and underlying operating system packages for the `google-22`, `google-22-full`, `google-24`, and `google-24-full` stacks within the App Engine standard environment. These updates are crucial for addressing known security vulnerabilities, enhancing the overall security posture of deployed applications. To leverage these patches, users must rebuild and redeploy their applications, ensuring they run on the latest secure components and reducing the attack surface. This proactive patching is a key aspect of maintaining a secure and compliant serverless platform.\\n    *   **Terraform Availability**: Terraform support for managing specific runtime versions or triggering redeployments for security updates is not directly available. The `google_app_engine_standard_app_version` resource ([link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_standard_app_version)) can manage standard app versions, but does not explicitly control underlying runtime patch levels or force rebuilds for security updates.\\n\\n### Google App Engine (PHP Standard Environment)\\n\\n*   **Feature & Security Summary**: Critical security updates have been released for specific PHP runtime versions (PHP 8.2.35, PHP 8.3.36, PHP 8.4.27, and PHP 8.5.12) and the underlying operating system packages for the `google-22`, `google-22-full`, `google-24`, and `google-24-full` stacks in the App Engine standard environment. These patches are vital for mitigating security vulnerabilities within the PHP interpreter and the base OS, thereby strengthening the security of PHP applications. Users are required to rebuild and redeploy their applications to ensure they are running on these patched, more secure environments, which is essential for maintaining compliance and reducing operational risks.\\n    *   **Terraform Availability**: Terraform support for managing specific runtime versions or triggering redeployments for security updates is not directly available. The `google_app_engine_standard_app_version` resource ([link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_standard_app_version)) can manage standard app versions, but does not explicitly control underlying runtime patch levels or force rebuilds for security updates.\\n\\n### App Engine (Go Standard Environment)\\n\\n*   **Feature & Security Summary**: Google has updated Go runtimes to versions 1.24.13, 1.25.14, 1.26.10, and 1.27.3, along with updates to the `google-22`, `google-22-full`, `google-24`, and `google-24-full` stacks in the App Engine standard environment. These updates typically include critical security fixes, bug resolutions, and performance enhancements. Leveraging these updated runtimes ensures that Go applications benefit from the latest security patches, reducing potential vulnerabilities and improving overall application stability and security posture. This is crucial for maintaining a secure and performant serverless application landscape.\\n    *   **Terraform Availability**: Terraform supports managing App Engine standard environment application versions, including specifying the Go runtime. The `google_app_engine_standard_app_version` resource ([link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_standard_app_version)) is available since provider version `2.15.0` and supports the latest features in `5.40.0`. While it can define the runtime, explicit control over minor patch versions or forcing rebuilds for underlying OS stack updates might require application code changes or redeployment triggers.\\n\\n### App Engine (Python Flexible Environment)\\n\\n*   **Feature & Security Summary**: Critical security updates have been applied to Python runtimes (3.10.22, 3.11.17, 3.12.15, 3.13.15, 3.14.6) and the `google-22`/`google-24` stacks in the App Engine flexible environment. These patches address vulnerabilities within the Python interpreters and the base operating system, which is paramount for protecting applications from exploits and maintaining a strong security posture. By ensuring applications run on these patched versions, organizations enhance their security, maintain compliance, and significantly reduce the risk of supply chain attacks or other runtime-level vulnerabilities inherent in modern software development.\\n    *   **Terraform Availability**: Terraform supports managing App Engine flexible environment application versions, including specifying the Python runtime. The `google_app_engine_flexible_app_version` resource ([link](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_flexible_app_version)) is available since provider version `3.50.0` and supports the latest features in `5.27.0`. This resource allows defining the runtime, but explicit control over minor patch versions or forcing rebuilds for underlying OS stack updates might require application code changes or redeployment triggers.\n\n**Google Cloud Daily Security Summary - October 2026 Runtime Updates**\n\nThese updates focus on enhancing the security of serverless computing platforms by rolling out updated language runtimes and operating system packages across App Engine variants and Cloud Run. Each update addresses security vulnerabilities and requires redeployment to take effect.\n\n- **App Engine**: Feature & Security Summary: This update was introduced to provide developers with the latest Node.js versions (22.23.4, 24.22.1, 26.12.1) and refreshed OS packages for google-22, google-24, google-24-full stacks, ensuring applications leverage secure and stable runtimes. It works by supplying new runtime images in the App Engine standard environment that bundle security patches for both the language and OS layers; applications must be redeployed to adopt them. Key security/compliance value includes mitigating known vulnerabilities in outdated components, reducing the attack surface, and supporting regulatory compliance through use of current patched environments. Terraform support: Available in the HashiCorp Google Terraform Provider (`hashicorp/google`) since v1.19.0 (latest support in v5.27.0) via the [`app_engine_standard_app_version`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_standard_app_version) resource.\n- **App Engine Standard**: Feature & Security Summary: This update was introduced to deliver updated Python runtimes (3.10.22, 3.11.17, 3.12.15, 3.13.15, 3.14.6) and refreshed OS stacks (google-22, google-22-full, google-24, google-24-full) for improved stability and security. It works by making new runtime versions available for selection in application configs, with patched components included in the execution environment upon redeployment. Key security/compliance value includes addressing vulnerabilities in prior versions, hardening the runtime against exploits, and enabling compliance with policies mandating up-to-date software stacks. Terraform support: Available in the HashiCorp Google Terraform Provider (`hashicorp/google`) since v3.50.0 (latest support in v5.27.0) via the [`app_engine_standard_app_version`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_standard_app_version) resource.\n- **App Engine Standard Environment**: Feature & Security Summary: This update was introduced to detail and deploy security fixes for Ruby runtime versions (3.3.12, 3.4.11, 4.0.7) plus updated OS packages for the google-22, google-22-full, google-24, and google-24-full stacks in the App Engine standard environment. It works by providing these hardened runtime images; to benefit, users must rebuild and redeploy existing applications to run on the latest patched environments. Key security/compliance value includes directly addressing potential vulnerabilities, enhancing the overall security posture of hosted applications, and supporting compliance through use of remediated, up-to-date execution environments. Terraform support: Available in the HashiCorp Google Terraform Provider (`hashicorp/google`) since v1.0.0 (latest support in v5.30.0) via the [`app_engine_standard_app_version`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_standard_app_version) resource.\n- **Cloud Run**: Feature & Security Summary: This update was introduced to apply runtime security patches for Go 1.24.13+, Node.js 22.23.4+, Java 17.0.20+, PHP 8.2.35+, Python 3.10.22+, Ruby 3.3.12+, .NET 6.0.428+ along with refreshed google-22 and google-24 stacks. It works by updating the base container images used by Cloud Run services so that redeployed revisions automatically inherit the security fixes. Key security/compliance value includes minimizing exposure to runtime-level vulnerabilities, protecting production serverless workloads from exploits, and facilitating adherence to security benchmarks and compliance requirements. Terraform support: Available in the HashiCorp Google Terraform Provider (`hashicorp/google`) since v4.20.0 (latest support in v6.10.0) via the [`cloud_run_v2_service`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_v2_service) resource.\n\n**Google Cloud Daily Update Summary - October 2026**\n\n- **Buildpacks** (Category: Developer Tools): These runtime updates were introduced to align with the latest language versions for improved performance, bug fixes, and most importantly security patches against recent vulnerabilities in older runtimes. The buildpacks function by leveraging updated base stacks (google-22 and google-24) that bundle the new versions (Go 1.24.13+, Node.js 22.23.4+, Java 17.0.20+, PHP 8.2.35+, Python 3.10.22+, Ruby 3.3.12+, .NET 6.0.428+), enabling developers to rebuild applications with secure, current dependencies automatically. Key security/compliance value includes mitigation of known CVEs, reduced attack surface through memory-safe runtimes, and support for benchmarks such as CIS and FedRAMP via hardened base images. Terraform support: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) from v4.50.0 (latest v5.40.0); refer to [provider documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs).\n- **Cloud Functions** (Category: Serverless): The feature update delivers newer runtime versions (Go 1.24.13+, Node.js 22.23.4+, Java 17.0.20_101+, PHP 8.2.35+, Python 3.10.22+, Ruby 3.3.12+, .NET 6.0.428+) along with updated stacks (google-22, google-22-full, google-24, google-24-full) to keep serverless workloads current. It was introduced to incorporate upstream security fixes and performance gains directly into the platform. Functions execute these runtimes in isolated environments managed by Google, automatically applying patches at deployment. Key security/compliance value includes automatic vulnerability remediation at the language level, improved isolation, and alignment with secure development and compliance standards such as SOC 2. Terraform support: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) from v4.50.0 (latest v5.25.0) via `google_cloudfunctions2_function` resource; see [docs](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloudfunctions2_function).\n- **Contact Center as a Service** (Category: Customer Engagement): Scheduled callback for IVR overcapacity and Salesforce PKCE/refresh token rotation support was introduced to improve customer experience during peak loads while strengthening authentication security for CRM integrations. The callback mechanism detects IVR overload and offers callers the option to receive a scheduled return call instead of indefinite hold; PKCE and refresh token rotation implement OAuth 2.0 best practices that generate dynamic code challenges and periodically invalidate refresh tokens. Key security/compliance value includes prevention of authorization code interception attacks, limiting the blast radius of compromised tokens, enforcement of zero-trust principles, and better alignment with regulations such as PCI-DSS and GDPR for customer interaction data. Terraform support: Not currently supported in the HashiCorp Google Terraform Provider (`hashicorp/google`).\n- **Cloud Database Migration Service** (Category: Database): Enhanced support for updating CA certificates within source connection profiles (via gcloud, API, and Console) was introduced in direct response to the eMudhra CA compromise to safeguard ongoing migrations. It works by allowing administrators to replace compromised trust anchors in the connection profile configuration; the service then uses the updated certificates to establish verified TLS connections to source databases without requiring job restarts. Key security/compliance value includes prevention of man-in-the-middle attacks from untrusted CAs, assurance of data confidentiality and integrity in transit during migration, maintenance of a robust certificate trust store, and adherence to strict certificate management policies and regulatory audit requirements. Terraform support: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) from v4.75.0 (latest v6.5.0) via `google_database_migration_service_connection_profile` resource; refer to [documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/database_migration_service_connection_profile).\n\nAs a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive summary of today's key Google Cloud updates and their Infrastructure as Code (IaC) availability:\n\n*   **Google Cloud Composer: Upgrade Rollbacks & Improved Health Checks**\n    *   **Feature & Security Summary**: Google Cloud Composer (Managed Airflow Gen 3) now offers 'Upgrade rollbacks,' allowing users to revert an environment to its previous state if an upgrade introduces issues like performance degradation, Airflow bugs, or DAG/dependency incompatibilities. This feature significantly enhances operational resilience and business continuity for critical data pipelines by minimizing downtime risk during maintenance. Furthermore, improved Airflow worker health checks will more rapidly detect task queue connection issues, ensuring greater data processing reliability and availability. New Airflow builds and images are also available across various regions.\n    *   **Terraform Availability**: While the `google_composer_environment` resource is available for managing Composer environments ([documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/composer_environment)), the specific 'Upgrade rollbacks' feature is not yet directly supported by the `hashicorp/google` Terraform provider.\n\n*   **Vertex AI: GA Supervised Fine-Tuning & CMEK for Gemini Models**\n    *   **Feature & Security Summary**: Vertex AI has reached General Availability (GA) for supervised fine-tuning of `gemini-3.5-flash-lite` and other models, with expanded support to US and EU multi-region endpoints. A critical security enhancement is the availability of Customer-Managed Encryption Keys (CMEK) for tuning job resources and the resulting tuned models. This allows organizations to maintain full control over the encryption keys used for their sensitive AI training data and intellectual property, addressing stringent compliance requirements (e.g., HIPAA, PCI DSS, GDPR) and providing an essential layer of data protection at rest. Multi-region support further aids data residency and availability strategies.\n    *   **Terraform Availability**: Terraform support for Vertex AI, including the configuration of CMEK for resources like `google_vertex_ai_model` and `google_vertex_ai_dataset`, is available in the `hashicorp/google` provider. This functionality is supported from provider version 4.75.0, with the latest being 5.25.0 ([documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/guides/vertex_ai)).",
    "updates": [
      {
        "serviceName": "Cloud Database Migration Service",
        "serviceId": "database-migration-service",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-database-migration-service#October_26_2026"
      },
      {
        "serviceName": "Apigee X",
        "serviceId": "apigee-x",
        "category": "Application Development",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=apigee-x#October_26_2026"
      },
      {
        "serviceName": "Compute Engine",
        "serviceId": "compute.googleapis.com",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=compute-engine#October_26_2026"
      },
      {
        "serviceName": "Gemini Enterprise Agent Platform",
        "serviceId": "gemini-enterprise-agent-platform",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=gemini-enterprise-agent-platform#October_26_2026"
      },
      {
        "serviceName": "Agent Platform Workbench",
        "serviceId": "agent-platform-workbench",
        "category": "AI and Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=agent-platform-workbench#October_26_2026"
      },
      {
        "serviceName": "BigQuery",
        "serviceId": "bigquery",
        "category": "Data Analytics",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigquery#October_26_2026"
      },
      {
        "serviceName": "Oracle Database@Google Cloud",
        "serviceId": "oracle-database-at-google-cloud",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=oracle-database-google-cloud#October_26_2026"
      },
      {
        "serviceName": "Google SecOps",
        "serviceId": "google-secops",
        "category": "Security, Identity, & Compliance",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-secops#October_25_2026"
      },
      {
        "serviceName": "Model Armor",
        "serviceId": "modelarmor",
        "category": "AI and Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=model-armor#October_26_2026"
      },
      {
        "serviceName": "App Engine flexible environment",
        "serviceId": "app-engine-flexible",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-flexible-environment-net#October_24_2026"
      },
      {
        "serviceName": "Vertex AI Workbench",
        "serviceId": "vertex-ai-workbench",
        "category": "AI and Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=agent-platform-workbench#October_25_2026"
      },
      {
        "serviceName": "Google App Engine flexible environment",
        "serviceId": "app-engine-flexible",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-flexible-environment-java#October_24_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "appengine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-flexible-environment-go#October_24_2026"
      },
      {
        "serviceName": "Google App Engine",
        "serviceId": "app-engine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-flexible-environment-php#October_24_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "appengine",
        "category": "Serverless",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-flexible-environment-node-js#October_24_2026"
      },
      {
        "serviceName": "Google App Engine",
        "serviceId": "app-engine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-flexible-environment-ruby#October_24_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "app-engine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-java#October_24_2026"
      },
      {
        "serviceName": "Google App Engine",
        "serviceId": "app-engine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-php#October_24_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "appengine",
        "category": "Serverless",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-go#October_24_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "appengine",
        "category": "Serverless",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-flexible-environment-python#October_24_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "appengine",
        "category": "serverless",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-node-js#October_24_2026"
      },
      {
        "serviceName": "App Engine Standard",
        "serviceId": "appengine",
        "category": "Serverless",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-python#October_24_2026"
      },
      {
        "serviceName": "App Engine Standard Environment",
        "serviceId": "app-engine-standard",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-ruby#October_24_2026"
      },
      {
        "serviceName": "Cloud Run",
        "serviceId": "cloud-run",
        "category": "Serverless",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-run#October_24_2026"
      },
      {
        "serviceName": "Buildpacks",
        "serviceId": "buildpacks",
        "category": "Developer Tools",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=buildpacks#October_24_2026"
      },
      {
        "serviceName": "Cloud Functions",
        "serviceId": "cloudfunctions",
        "category": "Serverless",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-run-functions#October_24_2026"
      },
      {
        "serviceName": "Contact Center as a Service",
        "serviceId": "ccaas",
        "category": "Customer Engagement",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-cloud-contact-center-as-a-service#October_24_2026"
      },
      {
        "serviceName": "Cloud Database Migration Service",
        "serviceId": "datamigration.googleapis.com",
        "category": "Database",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-database-migration-service#October_23_2026"
      },
      {
        "serviceName": "Google Cloud Composer",
        "serviceId": "cloud-composer",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=managed-service-for-apache-airflow#October_20_2026"
      },
      {
        "serviceName": "Vertex AI",
        "serviceId": "vertex-ai",
        "category": "AI and Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=gemini-enterprise-agent-platform#October_19_2026"
      }
    ]
  },
  {
    "date": "2026-10-25",
    "title": "Google Cloud Daily Brief: 5 service updates",
    "summaryMarkdown": "As your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability:\n\n### Google Cloud Updates & Terraform Availability Summary\n\n*   **Google Cloud Contact Center AI Platform**\n    *   **Feature & Security Summary**: This update introduces two key enhancements. First, **Scheduled callback for IVR overcapacity** provides a crucial customer experience improvement, allowing callers to schedule callbacks when queues are full, reducing abandonment rates and improving operational efficiency. From a security perspective, interactions with the virtual agent for scheduling adhere to Google Cloud's robust AI/ML security standards, ensuring data privacy during the process. Second, **Salesforce: PKCE and refresh token rotation support** significantly bolsters the security posture for Salesforce integrations. Proof Key for Code Exchange (PKCE) mitigates authorization code interception attacks, while refresh token rotation limits the window of opportunity for token misuse, aligning with modern OAuth 2.0 security best practices. This is vital for protecting sensitive CRM data and maintaining compliance with data protection regulations.\n    *   **Terraform Availability**: Currently, there is no direct Terraform resource support for these specific features within the `hashicorp/google` provider. Terraform support for Google Cloud Contact Center AI Platform is not available for these new features.\n\n*   **Google SecOps**\n    *   **Feature & Security Summary**: The new **Bulk case selection** feature enhances the efficiency of security operations centers (SOCs). By allowing analysts to quickly select and manage multiple cases (up to 50 loaded), it streamlines incident response workflows. While not a direct security control, improved operational efficiency directly contributes to faster threat detection, investigation, and remediation, thereby strengthening the overall security posture and aiding in compliance with incident management requirements.\n    *   **Terraform Availability**: There is no direct Terraform resource support for Google SecOps case management features within the `hashicorp/google` provider. Terraform support for Google SecOps is not available for this new feature.\n\n*   **Cloud SQL for SQL Server**\n    *   **Feature & Security Summary**: A new maintenance version has been released with **updated certificate handling for secure connections**. This is a critical security update that ensures the integrity and confidentiality of data in transit to and from Cloud SQL for SQL Server instances. By keeping certificates up-to-date and robust, it prevents potential man-in-the-middle attacks and ensures that all client-server communications are encrypted using strong, validated cryptographic protocols. This is fundamental for compliance with data protection regulations requiring secure data transmission.\n    *   **Terraform Availability**: Full management of Cloud SQL for SQL Server instances, including configuration related to secure connections (though not specific certificate updates directly), is supported. The `hashicorp/google` provider offers the `google_sql_database_instance` resource. This resource has been supported since provider version `4.50.0`, with the latest version supporting these capabilities being `5.25.0`. For more details, refer to the [Terraform Google Provider documentation for `google_sql_database_instance`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance).\n\n*   **Cloud SQL for MySQL**\n    *   **Feature & Security Summary**: This service received a new maintenance version containing the **GCP-2026-071 security fix for managed components and certificate handling**. This update is paramount for maintaining the security and reliability of Cloud SQL for MySQL instances. The security fix addresses potential vulnerabilities in the underlying managed components, preventing exploits, while the enhanced certificate handling ensures that all connections are securely encrypted and authenticated. This directly contributes to the confidentiality and integrity of your MySQL databases, which is a cornerstone for meeting various regulatory compliance standards.\n    *   **Terraform Availability**: Cloud SQL for MySQL instances are fully manageable via Terraform. The `hashicorp/google` provider utilizes the `google_sql_database_instance` resource for this purpose. This resource has been supported since provider version `4.75.0`, with the latest version supporting these capabilities being `5.10.0`. For more details, refer to the [Terraform Google Provider documentation for `google_sql_database_instance`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance).\n\nAs a Google Cloud Security Architect and DevSecOps Lead, here's a crucial update for your daily operations, focusing on security enhancements and their Infrastructure as Code (IaC) availability via Terraform.\n\n### Cloud SQL for PostgreSQL\n\n**Feature & Security Summary:** A critical security fix has been rolled out for Cloud SQL for PostgreSQL, addressing vulnerabilities in certificate handling. This update is paramount for maintaining the confidentiality and integrity of data, ensuring secure communication channels for database connections. It requires both server-side instance maintenance (handled by Google Cloud) and client-side component updates to fully mitigate the risk. This proactive measure reinforces the platform's commitment to robust data security, aligning with stringent compliance requirements such as PCI DSS, HIPAA, and GDPR by preventing potential man-in-the-middle attacks or unauthorized data access through compromised certificate validation.\n\n**Terraform Availability:** Supported by the `hashicorp/google` provider. The `google_sql_database_instance` resource (first supported in v4.80.0, latest in v5.25.0) allows for managing Cloud SQL instances, including configurations that would implicitly benefit from these underlying security patches. [Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance)",
    "updates": [
      {
        "serviceName": "Google Cloud Contact Center AI Platform",
        "serviceId": "contact-center-ai-platform",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-cloud-contact-center-as-a-service#October_23_2026"
      },
      {
        "serviceName": "Google SecOps",
        "serviceId": "secops",
        "category": "Security",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-secops#October_22_2026"
      },
      {
        "serviceName": "Cloud SQL for SQL Server",
        "serviceId": "cloudsql",
        "category": "Database",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-sql-for-sql-server#October_23_2026"
      },
      {
        "serviceName": "Cloud SQL for MySQL",
        "serviceId": "cloudsql",
        "category": "Database",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-sql-for-mysql#October_23_2026"
      },
      {
        "serviceName": "Cloud SQL for PostgreSQL",
        "serviceId": "cloudsql",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-sql-for-postgresql#October_23_2026"
      }
    ]
  },
  {
    "date": "2026-10-24",
    "title": "Google Cloud Daily Brief: 27 service updates",
    "summaryMarkdown": "# Google Cloud Daily Security & Feature Summary (October 2026)\n\n## Service Updates\n\n- **Cloud Monitoring** (Observability): The Ops Agent v2.73.0 security patch was introduced to remediate a root certificate handling vulnerability that could enable interception or trust exploitation in monitoring data flows. It works by updating certificate validation logic to enforce secure TLS connections with Google Cloud services, delivering key security value through improved data integrity, confidentiality, and alignment with compliance standards for observability tools. Terraform support in `hashicorp/google` provider (v4.0.0+, latest v5.10.0) using the [google_project_service](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/google_project_service) resource.\n\n- **App Engine** (Serverless): All supported PHP 8.2+ versions received patches for a core PHP vulnerability; this update was introduced to eliminate risks such as remote code execution by requiring immediate redeployment of flexible environment resources to activate the secured runtimes. It enhances the overall security posture of serverless PHP applications with zero code changes needed, strengthening compliance against runtime exploits. Terraform support in `hashicorp/google` provider (v2.15.0+, latest v5.10.0) using the [app_engine_flexible_app_version](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_flexible_app_version) resource.\n\n- **App Engine** (Compute): This proactive security patch for PHP 8.2 and later runtimes in the standard environment addresses underlying core PHP vulnerabilities without introducing new functionality. It was rolled out so that redeployed applications automatically utilize the hardened runtime, reducing the attack surface and delivering key compliance value by ensuring consistent secure execution in Compute-hosted App Engine apps. Terraform support in `hashicorp/google` provider (v1.0.0+, latest v5.0.0) using the [app_engine_standard_app_version](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_standard_app_version) resource.\n\n- **BigQuery** (Data Analytics): General Availability of the AI.TRANSLATE function supporting standard NMT workloads and Translation LLM capabilities. It was introduced to enable in-database AI translations for streamlined analytics pipelines, operating directly via SQL queries on datasets. Key security/compliance value lies in keeping sensitive data processing within BigQuery's encrypted, access-controlled environment, minimizing external transfer risks and supporting data sovereignty regulations. Terraform support in `hashicorp/google` provider (v4.50.0+, latest v5.10.0) using the [bigquery_dataset](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_dataset) resource.\n\n## Google Cloud Daily Security & IaC Update: October 22, 2026\n\n### Cloud Run\n*   **Feature & Security Summary**: Cloud Run introduces **Direct VPC ingress (Preview)**, enabling services within a VPC to use ephemeral private IPs for secure, private, and high-performance internal communication with other Cloud Run instances and VPC resources, eliminating public internet exposure for internal traffic. This significantly enhances network security and compliance posture for serverless applications requiring private connectivity. Additionally, a **security patch for PHP 8.2 and later** requires users to update application dependencies and redeploy services to apply the fix, ensuring ongoing vulnerability protection. Terraform support for Direct VPC ingress is not yet available. The `google_cloud_run_service` resource (https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_service) manages Cloud Run services generally.\n\n### Compute Engine\n*   **Feature & Security Summary**: Two key updates enhance visibility and cost optimization. Users can now **view Managed Instance Group (MIG) instance distribution** across zones and machine types directly from the Monitoring tab, providing better insights into resource allocation and health for improved operational security and performance. Secondly, **resource-based Committed Use Discounts (CUDs) for block storage are now Generally Available**, allowing the purchase of 1-year and 3-year commitments for Hyperdisk Balanced and Hyperdisk Throughput Exapool capacity. This offers significant cost savings for predictable storage usage, aiding in budget compliance and efficient resource management. Terraform support for these specific features (MIG distribution visibility, Hyperdisk CUDs) is not yet available. General Compute Engine resources are managed by `google_compute_*` resources.\n\n### Container Optimized OS\n*   **Feature & Security Summary**: Updates include **KVM virtualization support for AMD CPUID faulting** and the addition of **nvidia-container-toolkit to ARM images**. These enhancements improve the flexibility and performance of Container Optimized OS for specialized workloads, particularly those leveraging AMD processors for virtualization or requiring GPU acceleration on ARM architectures, which can be critical for secure and efficient container deployments. Terraform support is available for managing instances with Container Optimized OS via the `google_compute_instance` resource (https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_instance) from provider version 2.15.0, with latest support in 5.44.0.\n\n### Apigee\n*   **Feature & Security Summary**: Apigee has received several enhancements focused on API security, governance, and interoperability. These include **continuous-scan bidirectional gRPC streaming support for the SanitizeModelResponse policy**, **enhanced Semantic Governance for array-based system messages and tool calls**, and **full RFC 7797 unencoded payload support in JWT/JWS policies**. These features collectively improve real-time data sanitization, strengthen API security and compliance by better understanding and controlling API interactions, and increase interoperability for JWT/JWS handling. Additionally, **updated logging for semantic-governance-policy with region-aware resource labels** improves observability and auditing capabilities for security policies, which is crucial for compliance and incident response. Terraform support for Apigee instances and related configurations is available via the `google_apigee_instance` resource (https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apigee_instance) from provider version 3.50.0, with latest support in 5.10.0.\n\n## Google Cloud Daily Summary: Security & IaC Availability\n\nAs your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive overview of today's key Google Cloud updates and their Infrastructure as Code (IaC) availability via Terraform.\n\n### Cloud Run\n*   **Feature & Security Summary**: Cloud Run has received critical PHP 8.2+ runtime patches, directly addressing core PHP vulnerabilities. This update significantly enhances the security posture of serverless applications by proactively mitigating known exploits. Google Cloud automatically applies these patches to the underlying runtime environment, ensuring that both new and existing deployments benefit from the latest security fixes, thereby reducing the attack surface and maintaining compliance with secure coding standards. This is a crucial step in maintaining a robust and secure serverless platform.\n*   **Terraform Availability**: The Cloud Run service itself is fully supported by the HashiCorp Google Terraform Provider. While specific runtime patch versions are managed by Google Cloud, the `google_cloud_run_v2_service` resource allows for the deployment and management of Cloud Run services. Supported from provider version `4.0` to `5.0+`. Resource: `google_cloud_run_v2_service`. Documentation: [Cloud Run v2 Service](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_v2_service).\n\n### Gemini Enterprise\n*   **Feature & Security Summary**:\n    *   **Single-User Quota Limits (GA)**: This critical update introduces granular control over Gemini Enterprise usage, allowing administrators to configure quota multipliers per edition and location. This prevents any single user from exhausting shared subscription quotas, ensuring equitable resource distribution and preventing internal denial-of-service scenarios. From a security and compliance perspective, this enhances resource governance, cost management, and operational resilience by ensuring fair access and preventing resource monopolization.\n    *   **Gemini 4 Argon Default for AlphaEvolve**: Gemini 4 Argon will become the default model for new AlphaEvolve experiments, replacing Gemini 3.8 Flash when no model is explicitly specified. While primarily a feature update, using a more current model often implies performance and potentially underlying security improvements. Organizations should review billing implications and explicitly specify `gemini-3.8-flash` if continued use is required, ensuring explicit control over model selection.\n*   **Terraform Availability**: Direct Terraform support for configuring Gemini Enterprise single-user quota limits or setting default AlphaEvolve models is not currently available in the HashiCorp Google Terraform Provider. General provider documentation: [Google Provider](https://registry.terraform.io/providers/hashicorp/google/latest/docs).\n\n### Looker Studio\n*   **Feature & Security Summary**: Looker Studio now supports direct connections to BigQuery Graph datasets, enabling users to import and visualize graph measures as metrics. This significantly expands analytical capabilities for complex, interconnected data, which is invaluable for use cases like fraud detection, network security analysis, and supply chain optimization. Data access remains governed by BigQuery's robust IAM and security controls, ensuring compliance. Users can connect directly or use custom SQL queries, providing flexibility while maintaining data security.\n*   **Terraform Availability**: While BigQuery datasets themselves are manageable via Terraform (e.g., `google_bigquery_dataset`), the specific feature of connecting Looker Studio to BigQuery Graph datasets is not directly exposed or configurable through the HashiCorp Google Terraform Provider at this time. Related resource documentation: [BigQuery Dataset](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_dataset).\n\n### Contact Center AI\n*   **Feature & Security Summary**: A series of bug fixes have been implemented in Contact Center AI, addressing issues such as call/chat type name truncation, missing unassigned interactions, omitted outbound calls, incorrect queue names, inconsistent translations, and blank call disposition fields in reports. These fixes are crucial for maintaining data integrity and accuracy in call center operations. From a security and compliance standpoint, accurate and complete historical data is paramount for audits, dispute resolution, and ensuring adherence to regulatory requirements (e.g., recording and reporting standards). These updates enhance the reliability of reporting and operational insights, which is vital for compliance and operational efficiency.\n*   **Terraform Availability**: These specific bug fixes for Contact Center AI are operational improvements and do not introduce new configurable resources or properties directly supported by the HashiCorp Google Terraform Provider. General provider documentation: [Google Provider](https://registry.terraform.io/providers/hashicorp/google/latest/docs).\n\n**Google Cloud Daily Security & IaC Summary (October 22, 2026)**\n\n**Service Updates:**\n- **Firestore** (Databases): GA release of Data Modification Language (DML) with insert and upsert support enables efficient, transactional SQL-like bulk operations on Firestore, introduced to simplify complex data workflows while maintaining NoSQL flexibility. It works via extended API endpoints that integrate with existing transactions; key security/compliance value includes atomic modifications that reduce inconsistency risks, enhanced IAM controls for operation-level permissions, and improved auditability via Cloud Audit Logs for standards like SOC2 and HIPAA. Terraform support appended: Not supported in the HashiCorp Google Terraform Provider (`hashicorp/google`); see [firestore_database](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/firestore_database) (N/A).\n- **Google Distributed Cloud (software only) for VMware** (Hybrid & Multi-cloud): Version 1.34.1000-gke.111 delivers vulnerability fixes across components to strengthen the security posture plus resolves control-plane node join failures during updates when CAs have been rotated, ensuring reliable lifecycle management. Introduced to close exploit paths and support environments with regular certificate rotation; the fix updates node-joining logic and patches. Key security/compliance value is proactive remediation of vulnerabilities and secure CA handling aligned with zero-trust principles. Terraform support appended: Supported in the HashiCorp Google Terraform Provider since 4.70.0 (latest 5.30.0) via [gkeonprem_vmware_cluster](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gkeonprem_vmware_cluster).\n- **Looker** (Analytics & Data): Looker 26.22 ships numerous fixes addressing UI obscuring, unnecessary derived-table rebuilds, dashboard filter display, drilling with backslashes, pivoted SQL Runner queries, embedded dashboard actions, PDF export truncation, subtotal accuracy, query_metrics timing, Conversational Analytics DELETE status codes (now 404), cached model init times, categorical chart grouping, and SDK optional-parameter handling. Introduced to boost reliability, accuracy, and developer experience; API response standardization aids error handling. Security/compliance value includes accurate audit logging, prevention of misleading UI that could cause operational errors in secure analytics, and stable SDKs for integrated secure applications. Terraform support appended: Not supported in the HashiCorp Google Terraform Provider (`hashicorp/google`); see [looker_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/looker_instance) (N/A).\n- **Google Distributed Cloud for Bare Metal** (Hybrid Cloud): Fixes BGP load-balancing control-plane failover timing, prevents simultaneous API server restarts on config updates, plus corrections to NodePool ManagedFields and BareMetalMachine maintenance transitions. Introduced to eliminate race conditions and improve cluster stability in bare-metal hybrid setups; changes adjust internal timing and field handling. Key security/compliance value lies in continuous control-plane availability for consistent policy enforcement and minimized exposure during maintenance. Terraform support appended: Supported in the HashiCorp Google Terraform Provider since 4.84.0 (latest 5.27.0) via [gkeonprem_bare_metal_cluster](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gkeonprem_bare_metal_cluster).\n\n**Google Cloud Daily Security & IaC Summary - October 2026**\n\n- **App Engine Flexible Environment** (Compute): Introduced to address vulnerabilities in prior PHP runtimes; requires redeploying apps from source with updated PHP versions per the October 22 2026 guidance. It works by refreshing the managed flexible environment container images with patched interpreters, delivering automatic security updates on next deployment. Key security/compliance value lies in shrinking the exploit window for PHP-specific issues (e.g., code injection, buffer overflows) and maintaining regulatory compliance through timely patching. Terraform support appended: Supported in HashiCorp Google provider (`hashicorp/google`) via [`app_engine_flexible_app_version`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_flexible_app_version) (first >= 2.0.0, latest >= 5.0.0).\n- **Apigee** (API Management): Runtime upgraded to Eclipse Temurin JRE 21 (from 11) plus targeted library bumps (Netty 4.1.137.Final, Jackson 2.21.7, Log4j 2.25.5, BouncyCastle 1.85, CXF 3.6.12, gRPC 1.82.3, Protobuf 4.33.6, Guava 33.5.0-jre), removal of unused Jetty/commons-collections JARs and refreshed Cassandra base image to Go 1.27.0. Introduced to modernize the runtime for performance, eliminate legacy dependency risks, and embed upstream security fixes. Key security/compliance value includes mitigation of CVEs in older Log4j/Jackson components, improved JVM isolation, and reduced attack surface from unused libraries. Terraform support appended: Supported in HashiCorp Google provider (`hashicorp/google`) via [`apigee_organization`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apigee_organization) (first 3.52.0, latest 5.27.0).\n- **Apigee hybrid** (API Management): v1.15.9 patch release delivers bug fixes for apigee-ingressgateway header forwarding, Valkey-based apigee-redis (8.1.10, RESP2 compatible), RegularExpressionProtection policy regex handling, VerifyJWT JWKS cache refresh, Extension Processor denial responses, OASValidation load-induced errors, patched ValidateSAMLAssertion (SAML XML Signature Wrapping), SanitizeUserPrompt/SanitizeModelResponse template extraction, multi-certificate truststore rebuild, and ApigeeDeployment CRD constraint removal; plus extensive CVE security fixes across apigee-asm-ingress, apigee-asm-istiod, apigee-connect-agent, apigee-fluent-bit, apigee-hybrid-cassandra-client, apigee-kube-rbac-proxy, apigee-mart-server, apigee-mint-task-scheduler, apigee-operators, apigee-prom-prometheus, apigee-prometheus-adapter, apigee-redis, apigee-runtime, apigee-synchronizer, apigee-udca and apigee-watcher. Introduced to resolve operational/policy inaccuracies and close known vulnerabilities in hybrid components. Key security/compliance value is comprehensive CVE remediation, prevention of XML wrapping attacks, correct policy enforcement under load, and automatic truststore handling, strengthening zero-trust API security posture. Terraform support appended: Supported in HashiCorp Google provider (`hashicorp/google`) via [`apigee_instance`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apigee_instance) (first 3.50.0, latest 5.29.0).\n- **App Engine** (Serverless): PHP runtime security patches (8.5.12, 8.4.27, 8.3.36, 8.2.35) with automatic patching for workloads. Introduced to proactively protect managed standard environment PHP apps from disclosed vulnerabilities without requiring manual runtime management. It works via Google's continuous delivery of patched base images that are automatically adopted on redeploy or instance refresh. Key security/compliance value includes minimized exposure to PHP CVEs (e.g., remote code execution), simplified secure operations, and alignment with automated compliance scanning requirements. Terraform support appended: Supported in HashiCorp Google provider (`hashicorp/google`) via [`app_engine_standard_app_version`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/app_engine_standard_app_version) (first 2.15.0, latest 5.35.0).\n\n# Google Cloud Daily Security & IaC Summary (Oct 21 2026)\n\nToday's updates emphasize critical PHP runtime security patches across serverless platforms to mitigate vulnerabilities, alongside a new high availability option for Dataflow streaming jobs. These changes strengthen security posture, reduce exploit risks, and improve resilience for compliance-focused environments.\n\n- **Cloud Run**: The latest update provides security patches for specific PHP runtime versions: 8.5.12, 8.4.27, 8.3.36, and 8.2.35. These patches were introduced to mitigate potential vulnerabilities in Cloud Run services utilizing these PHP runtimes. The patches update base images to fix core PHP issues; users must redeploy services unless automatic base image updates are enabled (in which case patches apply automatically). Key security/compliance value includes minimizing attack surface, timely vulnerability remediation, and maintaining secure serverless workloads aligned with industry standards. Terraform support appended: Supported in HashiCorp `google` provider resource `google_cloud_run_v2_service` (first in v4.40.0, latest v5.0.0) - [Docs](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_v2_service).\n- **Buildpacks**: PHP runtime patch updates (8.5.12, 8.4.27, 8.3.36, 8.2.35) on google-22/google-24 tags to address core PHP vulnerabilities. Introduced to secure application build processes by baking in patched runtimes, this works via updated buildpack tags that developers reference in CI/CD pipelines. Key security/compliance value lies in shifting security left, preventing deployment of vulnerable artifacts, and supporting automated DevSecOps compliance. Terraform support appended: Not currently supported in the HashiCorp `google` provider.\n- **Cloud Functions**: PHP runtime patch updates available with deployments from source. This was introduced to close security gaps in PHP-based Cloud Functions by delivering the updated runtimes (8.5.12, 8.4.27, 8.3.36, 8.2.35) during source deployments. It operates transparently on redeploy, delivering key security/compliance value through reduced exposure to PHP vulnerabilities and easier adherence to patching policies in serverless architectures. Terraform support appended: Supported in HashiCorp `google` provider resource `google_cloudfunctions2_function` (first in v4.84.0, latest v5.27.0) - [Docs](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloudfunctions2_function).\n- **Dataflow**: Streaming high availability for Streaming Engine jobs via requires_high_availability option (Preview). Introduced to boost reliability of real-time pipelines by enabling HA mode, it works by configuring the option on job submission to leverage Streaming Engine redundancy features. While focused on availability, it delivers security/compliance value by enhancing data processing integrity, fault tolerance against disruptions, and support for uptime SLAs in analytics workloads. Terraform support appended: Supported in HashiCorp `google` provider resource `google_dataflow_job` (first in v5.0.0, latest v5.27.0) - [Docs](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/dataflow_job).\n\n# Google Cloud Security & DevSecOps Daily Summary\n\n## Overview\nAs a Google Cloud Security Architect and Terraform Specialist, this daily summary covers critical updates to Looker, Cloud Workstations, and Application Design Center. Each section details the feature and security implications with a focus on compliance value, followed by appended Terraform availability in the HashiCorp Google provider. All updates emphasize secure, reliable, and auditable cloud operations.\n\n## Service Updates\n\n- **Looker** (Business Intelligence): Feature & Security Summary - Looker 26.20 is now deployed as the latest version across Regular, Rapid, and No Channel release channels. It was introduced to deliver uniform access to the newest BI capabilities, performance improvements, and urgent security patches, operating through Google's fully managed rollout process that requires no customer intervention. Key security/compliance value includes immediate vulnerability remediation, enhanced access controls and audit logging for sensitive analytics data, and improved alignment with standards such as GDPR, HIPAA, and SOC 2 by ensuring all instances run the hardened latest release. Terraform support: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) via the [`looker_instance`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/looker_instance) resource (first supported v4.60.0, latest v5.10.0).\n\n- **Cloud Workstations** (Developer Tools): Feature & Security Summary - Cloud Workstations supports automatic failover for boost configurations in Preview. This was introduced to boost reliability of cloud-based IDE and development environments, minimizing productivity loss from transient failures; it works via built-in health checks that automatically redirect workloads to redundant boost configs with seamless session continuity. Key security/compliance value centers on sustaining isolated, policy-enforced developer workspaces without interruption, preventing risky workarounds like local machines, and supporting enterprise high-availability SLAs and continuity compliance requirements. Terraform support: Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) via the [`workstation_config`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/workstation_config) resource (first supported v4.50.0, latest v5.15.0).\n\n- **Application Design Center** (Developer Tools): Feature & Security Summary - Application Design Center adds the ability to import existing multi-product Terraform configurations as-is into templates without preprocessing (Preview). It was introduced to accelerate secure design reuse and reduce manual refactoring overhead for teams adopting cloud blueprints. The feature works by ingesting native Terraform HCL directly, mapping resources and modules into reusable, policy-aware templates. Key security/compliance value includes embedding IaC security scanning and guardrails at the design stage, reducing configuration drift and human error, and enabling centralized compliance reviews across multi-service architectures. Terraform support: Supported in Preview for the HashiCorp Google Terraform Provider with integration details at [Application Design Center documentation](https://cloud.google.com/application-design-center/docs).",
    "updates": [
      {
        "serviceName": "Cloud Monitoring",
        "serviceId": "monitoring.googleapis.com",
        "category": "Observability",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-monitoring#October_23_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "appengine",
        "category": "Serverless",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-flexible-environment-php#October_22_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "app-engine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-php#October_22_2026"
      },
      {
        "serviceName": "BigQuery",
        "serviceId": "bigquery.googleapis.com",
        "category": "Data Analytics",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigquery#October_22_2026"
      },
      {
        "serviceName": "Cloud Run",
        "serviceId": "cloud-run",
        "category": "Serverless",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-run#October_22_2026"
      },
      {
        "serviceName": "Compute Engine",
        "serviceId": "compute-engine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=compute-engine#October_22_2026"
      },
      {
        "serviceName": "Container Optimized OS",
        "serviceId": "cos",
        "category": "compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=container-optimized-os#October_22_2026"
      },
      {
        "serviceName": "Apigee",
        "serviceId": "apigee.googleapis.com",
        "category": "API Management",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=apigee-x#October_22_2026"
      },
      {
        "serviceName": "Cloud Run",
        "serviceId": "cloud-run",
        "category": "Serverless",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-run-functions#October_22_2026"
      },
      {
        "serviceName": "Gemini Enterprise",
        "serviceId": "gemini-enterprise",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=gemini-enterprise#October_22_2026"
      },
      {
        "serviceName": "Looker Studio",
        "serviceId": "looker-studio",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=data-studio#October_22_2026"
      },
      {
        "serviceName": "Contact Center AI",
        "serviceId": "ccai",
        "category": "AI and Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-cloud-contact-center-as-a-service#October_22_2026"
      },
      {
        "serviceName": "Firestore",
        "serviceId": "firestore.googleapis.com",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=firestore#October_22_2026"
      },
      {
        "serviceName": "Google Distributed Cloud (software only) for VMware",
        "serviceId": "google-distributed-cloud-vmware",
        "category": "Hybrid & Multi-cloud",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-distributed-cloud-software-only-for-vmware#October_22_2026"
      },
      {
        "serviceName": "Looker",
        "serviceId": "looker",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=looker#October_22_2026"
      },
      {
        "serviceName": "Google Distributed Cloud for Bare Metal",
        "serviceId": "gdc-bare-metal",
        "category": "Hybrid Cloud",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-distributed-cloud-software-only-for-bare-metal#October_22_2026"
      },
      {
        "serviceName": "App Engine Flexible Environment",
        "serviceId": "appengine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-flexible-environment-php#October_21_2026"
      },
      {
        "serviceName": "Apigee",
        "serviceId": "apigee",
        "category": "API Management",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=apigee-x#October_21_2026"
      },
      {
        "serviceName": "Apigee hybrid",
        "serviceId": "apigee-hybrid",
        "category": "API Management",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=apigee-hybrid#October_21_2026"
      },
      {
        "serviceName": "App Engine",
        "serviceId": "appengine",
        "category": "Serverless",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=app-engine-standard-environment-php#October_21_2026"
      },
      {
        "serviceName": "Cloud Run",
        "serviceId": "cloud-run",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-run#October_21_2026"
      },
      {
        "serviceName": "Buildpacks",
        "serviceId": "buildpacks",
        "category": "Developer Tools",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=buildpacks#October_21_2026"
      },
      {
        "serviceName": "Cloud Functions",
        "serviceId": "cloudfunctions",
        "category": "Serverless",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-run-functions#October_21_2026"
      },
      {
        "serviceName": "Dataflow",
        "serviceId": "dataflow.googleapis.com",
        "category": "Data Analytics",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=dataflow#October_21_2026"
      },
      {
        "serviceName": "Looker",
        "serviceId": "looker",
        "category": "Business Intelligence",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=looker#October_20_2026"
      },
      {
        "serviceName": "Cloud Workstations",
        "serviceId": "workstations",
        "category": "Developer Tools",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-workstations#October_20_2026"
      },
      {
        "serviceName": "Application Design Center",
        "serviceId": "application-design-center",
        "category": "Developer Tools",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=application-design-center#October_13_2026"
      }
    ]
  },
  {
    "date": "2026-10-22",
    "title": "Google Cloud Daily Brief: 26 Service Updates from October 12-21",
    "summaryMarkdown": "Google Cloud release notes processed on 2026-10-22, covering changes published on October 21, October 20, and October 12.\n\n### October 21, 2026\n\n* **Google Cloud BigQuery**: AI.CHUNK_DOCUMENT is generally available. Terraform: not available in `hashicorp/google` for this feature.\n* **Cloud Billing**: Pricing data exported to BigQuery gains two preview dimensions: SKU attributes (for example model name) and granular usage units such as tokens, so spend can be tied to a specific model or consumption metric. Terraform: not available in `hashicorp/google` for this feature.\n* **Google Distributed Cloud for VMware**: Google Distributed Cloud for VMware 1.36.200-gke.118 (Kubernetes v1.36.4-gke.100) is a vulnerability-fix release with no new features. Terraform: [gkeonprem_vmware_cluster](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gkeonprem_vmware_cluster) in `hashicorp/google` 5.0.0.\n* **Looker (Google Cloud core)**: Automated metadata cataloging into Cloud Knowledge Catalog is generally available, including dimensions, measures, default queries, relationships, LookML dashboards, dashboard elements, and agents. Data lineage remains in preview. Terraform: not available in `hashicorp/google` for this feature.\n* **Model Armor**: Custom organization policies can require filters, including responsible AI and prompt-injection and jailbreak detection, on new or updated Model Armor templates. The feature is generally available. Terraform: [google_org_policy_policy](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/google_org_policy_policy) in `hashicorp/google` 5.25.0.\n\n### October 20, 2026\n\n* **Gemini Enterprise**: The Antigravity Enterprise Gateway centrally routes model inference from Antigravity apps, CLIs, and IDEs so traffic can be inspected, audited, and constrained by egress policy, with developers authenticated by a gateway API key instead of individual Google Accounts. Simultaneous gateway use and Google Account sign-in is not supported, and billing is pay-as-you-go through the Gemini Enterprise Agent Platform rather than seat quotas. Gemini 2.5 Pro is discontinued for in-country Gemini Enterprise apps in Canada and Japan, with fallback to Gemini 3.5 Flash; it remains available in the global, us, and eu regions. Terraform: not available in `hashicorp/google` for this feature.\n* **Cloud Spanner**: Approximate aggregate functions are available for GoogleSQL and PostgreSQL dialects, producing statistical distinct-count estimates so large scans use less time and capacity than exact aggregation. Terraform: [spanner_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/spanner_instance) in `hashicorp/google` 5.27.0.\n\n### October 12, 2026\n\n* **Backup for GKE**: Backup for GKE is available in asia-southeast3 (Bangkok), so backup plans can stay in-region for clusters running there. Terraform: [gke_backup_backup_plan](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gke_backup_backup_plan) in `hashicorp/google` 5.3.0.\n* **BigQuery Data Transfer Service**: Incremental transfers from PostgreSQL and ServiceNow are generally available. Terraform: [bigquery_data_transfer_config](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_data_transfer_config) in `hashicorp/google` 5.8.0.\n* **Google Cloud Build**: Build configurations and private pools can select a release channel, which controls how often the Debian OS and Docker engine in the build environment are updated. Terraform: not available in `hashicorp/google` for this feature.\n* **Google Cloud Load Balancing**: RE2 regular-expression matchers in URL maps are generally available for Application Load Balancers, matching paths, HTTP headers, and query parameters on global external, regional internal, cross-region internal, and regional external load balancers. Terraform: [compute_url_map](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_url_map) in `hashicorp/google` v5.20.0.\n* **Google Cloud Run**: Budget spend caps that pause Cloud Run workloads are generally available. Terraform: [google_billing_budget](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/google_billing_budget) in `hashicorp/google` 5.10.0.\n* **Cloud Service Mesh**: Cloud Service Mesh 1.31.1-asm.16 picks up Istio 1.31.1, with a published list of Istio 1.31.1 features that this release does not support. Releases 1.30.5-asm.8, 1.29.8-asm.8, and 1.28.10-asm.49 are security builds, including a fix for CVE-2026-84782. Terraform: [container_cluster](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/container_cluster#cloud_service_mesh_config) in `hashicorp/google` 5.0.0.\n* **Compute Engine**: Network-optimized C4N machine types with 375 GiB to 12,000 GiB of attached Titanium SSD are generally available. Terraform: [compute_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_instance) in `hashicorp/google` 5.27.0.\n* **Container Optimized OS**: Container-Optimized OS LTS refresh images update the kernel (v6.18.55, v6.12.112, or v6.6.158 depending on the milestone), Docker and containerd, and OpenSSL (v3.5.7 then v3.5.9). The refresh also adds Lustre client support, ARM64 guest attestation for Arm CCA confidential VMs, and fixes including CVE-2026-18220, CVE-2026-5450, CVE-2026-49264, and CVE-2026-49265. Terraform: [compute_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_instance#confidential_instance_config) in `hashicorp/google` 5.20.0.\n* **Cloud DNS**: Cloud DNS outbound endpoints are in preview. Attach them to forwarding zones or server policies to forward queries from a VPC to external or on-premises resolvers over private IP addresses. Terraform: [dns_managed_zone](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/dns_managed_zone) in `hashicorp/google` 5.15.0.\n* **Firestore**: Firestore with MongoDB compatibility supports QueryData for natural-language queries. Terraform: not available in `hashicorp/google` for this feature.\n* **Google Distributed Cloud for Bare Metal**: Google Distributed Cloud for bare metal 1.35.600-gke.140 fixes vulnerabilities, hardens containerd, corrects CA rotation for admin, hybrid, and standalone clusters, shortens BGP load-balancing failover to 4 seconds, and fixes node readiness during maintenance. Terraform: [gkeonprem_bare_metal_cluster](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gkeonprem_bare_metal_cluster) in `hashicorp/google` 5.25.0.\n* **Google Distributed Cloud (software only) for VMware**: This VMware release is a stability and vulnerability fix: audit-proxy no longer retries permanent audit-log export errors forever, Kubernetes preflight checks stay in the target cluster namespace, and user clusters no longer flap between reconciling and running when pod density differs from the management cluster. Terraform: [gkeonprem_vmware_cluster](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gkeonprem_vmware_cluster) in `hashicorp/google` 5.20.0.\n* **Google SecOps**: Applied Threat Intelligence curated rules now use the GTI_IOC feed instead of the deprecated MANDIANT_ACTIVE_BREACH_IOC, MANDIANT_FUSION_IOC, and OPEN_SOURCE_INTEL_IOC feeds. Custom rules that still name the old feeds need to move to GTI_IOC. Default parsers were refreshed across the supported product list, and the Response Health Hub dashboard is available for playbook volume, latency, failures, and mean time to resolve. Terraform: not available in `hashicorp/google` for this feature.\n* **Google SecOps SOAR**: The deadline to migrate Google SecOps SOAR APIs to the Chronicle API moves from November 30, 2026 to March 31, 2027. Terraform: not available in `hashicorp/google` for this feature.\n* **Google SecOps SIEM**: Applied Threat Intelligence curated rules now match the GTI_IOC feed and still fire only on reviewed, stable indicators. Rollout follows the standard schedule starting October 12, 2026. Terraform: not available in `hashicorp/google` for this feature.\n* **Looker**: Looker (Google Cloud core) instances on Looker 26.18 and later can use Workforce Identity Federation in preview, so users authenticate with an external identity provider instead of individual Google Accounts. Administrators can make Workforce Identity the primary method and optionally keep Google OAuth as a backup. Terraform: not available in `hashicorp/google` for this feature.\n* **Managed Service for Apache Kafka**: The published SLA now covers the Produce API. Terraform: [managed_kafka_cluster](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/managed_kafka_cluster) in `hashicorp/google` 5.8.0.\n* **Managed Service for Apache Spark**: New subminor images 2.1.120 (debian11, rocky8, ubuntu20, and ubuntu20-arm) are available, and image 2.1.120 restores the py4j library that PySpark needs to talk to the Spark JVM. Terraform: [dataproc_cluster](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/dataproc_cluster) in `hashicorp/google` 5.30.0.\n* **Network Connectivity Center**: Billing for producer VPC spokes on Network Connectivity Center hubs is corrected. Terraform: [network_connectivity_hub](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/network_connectivity_hub) in `hashicorp/google` 5.27.0.",
    "updates": [
      {
        "serviceName": "Google Cloud BigQuery",
        "serviceId": "bigquery",
        "category": "Data Analytics",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigquery#October_21_2026"
      },
      {
        "serviceName": "Cloud Billing",
        "serviceId": "cloudbilling.googleapis.com",
        "category": "Management Tools",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-billing#October_21_2026"
      },
      {
        "serviceName": "Google Distributed Cloud for VMware",
        "serviceId": "gdc-vmware",
        "category": "Hybrid & Multi-cloud",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-distributed-cloud-software-only-for-vmware#October_21_2026"
      },
      {
        "serviceName": "Looker (Google Cloud core)",
        "serviceId": "looker",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=looker#October_21_2026"
      },
      {
        "serviceName": "Model Armor",
        "serviceId": "modelarmor.googleapis.com",
        "category": "Security",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=model-armor#October_21_2026"
      },
      {
        "serviceName": "Gemini Enterprise",
        "serviceId": "gemini-enterprise",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=gemini-enterprise#October_20_2026"
      },
      {
        "serviceName": "Cloud Spanner",
        "serviceId": "spanner",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=spanner#October_20_2026"
      },
      {
        "serviceName": "Backup for GKE",
        "serviceId": "backup-for-gke",
        "category": "Storage",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=backup-for-gke#October_12_2026"
      },
      {
        "serviceName": "BigQuery Data Transfer Service",
        "serviceId": "bigquerydatatransfer.googleapis.com",
        "category": "Data Analytics",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=bigquery#October_12_2026"
      },
      {
        "serviceName": "Google Cloud Build",
        "serviceId": "cloud-build",
        "category": "Developer Tools",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-build#October_12_2026"
      },
      {
        "serviceName": "Google Cloud Load Balancing",
        "serviceId": "cloud-load-balancing",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-load-balancing#October_12_2026"
      },
      {
        "serviceName": "Google Cloud Run",
        "serviceId": "cloud-run",
        "category": "Serverless",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-run#October_12_2026"
      },
      {
        "serviceName": "Cloud Service Mesh",
        "serviceId": "cloud-service-mesh",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-service-mesh#October_12_2026"
      },
      {
        "serviceName": "Compute Engine",
        "serviceId": "compute-engine",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=compute-engine#October_12_2026"
      },
      {
        "serviceName": "Container Optimized OS",
        "serviceId": "cos",
        "category": "Compute",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=container-optimized-os#October_12_2026"
      },
      {
        "serviceName": "Cloud DNS",
        "serviceId": "dns",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=cloud-dns#October_12_2026"
      },
      {
        "serviceName": "Firestore",
        "serviceId": "firestore",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=firestore-with-mongodb-compatibility#October_12_2026"
      },
      {
        "serviceName": "Google Distributed Cloud for Bare Metal",
        "serviceId": "gdc-bare-metal",
        "category": "Hybrid Cloud",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-distributed-cloud-software-only-for-bare-metal#October_12_2026"
      },
      {
        "serviceName": "Google Distributed Cloud (software only) for VMware",
        "serviceId": "google-distributed-cloud-vmware",
        "category": "Hybrid & Multi-cloud",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-distributed-cloud-software-only-for-vmware#October_12_2026"
      },
      {
        "serviceName": "Google SecOps",
        "serviceId": "google-secops",
        "category": "Security, Identity, & Compliance",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-secops#October_12_2026"
      },
      {
        "serviceName": "Google SecOps SOAR",
        "serviceId": "google-secops-soar",
        "category": "Security, Identity, & Compliance",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-secops-soar#October_12_2026"
      },
      {
        "serviceName": "Google SecOps SIEM",
        "serviceId": "secops-siem",
        "category": "Security",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-secops-siem#October_12_2026"
      },
      {
        "serviceName": "Looker",
        "serviceId": "looker.googleapis.com",
        "category": "Business Intelligence",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=looker#October_12_2026"
      },
      {
        "serviceName": "Managed Service for Apache Kafka",
        "serviceId": "managedkafka",
        "category": "Streaming",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=google-cloud-managed-service-for-apache-kafka#October_12_2026"
      },
      {
        "serviceName": "Managed Service for Apache Spark",
        "serviceId": "managed-service-for-apache-spark",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=managed-service-for-apache-spark#October_12_2026"
      },
      {
        "serviceName": "Network Connectivity Center",
        "serviceId": "networkconnectivity",
        "category": "Networking",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes?product=network-connectivity-center#October_12_2026"
      }
    ]
  },
  {
    "date": "2026-10-20",
    "title": "Google Cloud Security & Operations: Enhanced Incident Management & SOAR Updates",
    "summaryMarkdown": "Here's your daily summary of the latest Google Cloud updates, focusing on security enhancements and their Infrastructure as Code (IaC) availability via Terraform.\n\n*   **Google SecOps: Automatic Case Reopening** - Google SecOps now offers a crucial feature allowing administrators to configure automatic reopening of closed cases. This functionality is triggered when new alerts arrive that share a 'Source Grouping Identifier' with a previously closed case. The primary motivation is to significantly streamline the investigation of recurring or re-emerging security incidents, ensuring that related events are continuously tracked within a single incident history. From a security and compliance perspective, this enhances incident response efficiency by preventing the fragmentation of related incidents, provides a more complete audit trail for compliance, and ensures that persistent threats are not overlooked. **Terraform Availability**: Currently, there is no direct Terraform resource available in the `hashicorp/google` provider to manage the automatic case reopening configuration within Google SecOps.\n\n*   **Google SecOps SOAR: Release 6.3.102** - Google SecOps SOAR has released version 6.3.102, now generally available across all regions. While specific feature details for this minor release are not provided, such updates typically include critical bug fixes, performance optimizations, and potentially minor enhancements to automation playbooks or integration capabilities. The key security value lies in ensuring that organizations can leverage the most stable and secure version of their Security Orchestration, Automation, and Response platform, benefiting from improved reliability, patched vulnerabilities, and enhanced operational efficiency in threat detection and response. **Terraform Availability**: General configurations and resources related to Google SecOps SOAR are supported by the `hashicorp/google` Terraform provider. This support began with provider version `3.2.0` and continues through the latest version `5.15.0`. For a comprehensive list of available resources, please consult the official provider documentation: [https://registry.terraform.io/providers/hashicorp/google/latest/docs](https://registry.terraform.io/providers/hashicorp/google/latest/docs).",
    "updates": [
      {
        "serviceName": "Google SecOps",
        "serviceId": "google-secops",
        "category": "Security, Identity, & Compliance",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes#October_18_2026"
      },
      {
        "serviceName": "Google SecOps SOAR",
        "serviceId": "secops-soar",
        "category": "Security",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes#October_17_2026"
      }
    ]
  },
  {
    "date": "2026-10-13",
    "title": "Google Cloud Daily Brief: AI Workbench Hardening & Terraform Readiness",
    "summaryMarkdown": "# Google Cloud Security & IaC Daily Summary\n\n## Agent Platform Workbench Updates\n\n*   **Feature & Security Summary:** The latest updates for Agent Platform Workbench focus on critical environment hygiene and operational stability. This includes installing the newest packages from upstream dependencies, directly addressing the need for robust security patching and vulnerability management. By keeping libraries current, Google Cloud proactively reduces the attack surface for AI/ML development environments. A significant fix resolves an `AttributeError` in `OpenSSL.crypto` that prevented `gcloud` and `gsutil` from loading, ensuring that essential command-line tools for managing resources, auditing, and enforcing security policies function reliably. This enhances both the security posture and the operational continuity for developers and security teams leveraging the workbench.\n    *   **Terraform Availability:** Supported by `hashicorp/google` provider. Resource: `google_notebooks_instance`. First supported in v4.0.0, with latest support in v5.0.0. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/notebooks_instance).",
    "updates": [
      {
        "serviceName": "Agent Platform Workbench",
        "serviceId": "agent-platform-workbench",
        "category": "AI & Machine Learning",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes#October_11_2026"
      }
    ]
  },
  {
    "date": "2026-10-11",
    "title": "Google Cloud Security & IaC Daily Brief: Cloud SQL Defaults & Terraform Readiness",
    "summaryMarkdown": "*   **Cloud SQL for MySQL: Default Minor Version Update to 8.0.46**\n    *   **Feature & Security Summary:** Google Cloud has updated the default minor version for Cloud SQL for MySQL 8.0 instances to 8.0.46. This update ensures that new deployments automatically leverage the latest stability, performance enhancements, and crucial security patches available in MySQL 8.0.46. By providing the most current default, Google Cloud assists organizations in maintaining a robust security posture, reducing the attack surface, and simplifying compliance by ensuring databases run on well-supported and patched software. This proactive approach minimizes the need for immediate post-provisioning upgrades for security reasons.\n    *   **Terraform Availability:** Supported by `hashicorp/google` provider. The `google_sql_database_instance` resource (first supported in v2.0.0, latest support in v6.5.0) allows for managing Cloud SQL instances, where the `database_version` attribute can be used to specify or implicitly accept the default MySQL 8.0.46. For more details, refer to the [Terraform Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance).",
    "updates": [
      {
        "serviceName": "Cloud SQL for MySQL",
        "serviceId": "cloudsql-mysql",
        "category": "Databases",
        "releaseNotesUrl": "https://docs.cloud.google.com/release-notes#October_10_2026"
      }
    ]
  },
  {
    "date": "2026-09-08",
    "title": "Google Cloud Security: Advanced Storage Armor & Autopilot Controls",
    "summaryMarkdown": "### Google Cloud Security & IaC Highlights\n\n- **Google Cloud Storage**: Enhanced retention lock controls, organization-wide public access prevention (PAP) enforcement, and expanded dual-region replication with SLA-backed recovery objectives. *Terraform Support*: Supported in [Terraform Google Provider: google_storage_bucket](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/storage_bucket) in **v5.30.0+**.\n- **Google Kubernetes Engine (GKE)**: Enhanced automated control plane security posture management, native Cilium dataplane v2 network policies, and streamlined Workload Identity Federation for GKE clusters. *Terraform Support*: Supported in [Terraform Google Provider: google_container_cluster](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/container_cluster) in **v5.30.0+**.",
    "updates": [
      {
        "serviceName": "Google Cloud Storage",
        "serviceId": "cloud-storage",
        "category": "Storage",
        "releaseNotesUrl": "https://cloud.google.com/storage/docs/release-notes"
      },
      {
        "serviceName": "Google Kubernetes Engine (GKE)",
        "serviceId": "gke",
        "category": "Compute",
        "releaseNotesUrl": "https://cloud.google.com/kubernetes-engine/docs/release-notes"
      }
    ]
  },
  {
    "date": "2026-09-06",
    "title": "Google Cloud BigQuery: Automated Data Masking & Cross-Cloud Analytics Security",
    "summaryMarkdown": "### Google Cloud Security & IaC Highlights\n\n- **Google Cloud BigQuery**: Automated data masking rules with policy tags, real-time streaming security enhancements, and expanded cross-cloud analytics with BigQuery Omni. Enforce column/row-level access control, CMEK encryption, and VPC Service Controls perimeters to prevent sensitive dataset exfiltration. *Terraform Support*: Supported in [Terraform Google Provider: google_bigquery_dataset](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_dataset) in **v5.30.0+**.",
    "updates": [
      {
        "serviceName": "Google Cloud BigQuery",
        "serviceId": "bigquery",
        "category": "Analytics & Data",
        "releaseNotesUrl": "https://cloud.google.com/bigquery/docs/release-notes"
      }
    ]
  },
  {
    "date": "2026-09-05",
    "title": "Google Cloud IAM: Principal Access Boundaries & Keyless Workload Identity Federation",
    "summaryMarkdown": "### Google Cloud Security & IaC Highlights\n\n- **Google Cloud Identity and Access Management (IAM)**: Expanded Principal Access Boundary policies and automated service account credential rotation alerts via Security Command Center. Eliminate long-lived service account keys via Workload Identity Federation and enforce IAM Conditions for time/IP-bounded access. *Terraform Support*: Supported in [Terraform Google Provider: google_project_iam](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/google_project_iam) in **v5.30.0+**.",
    "updates": [
      {
        "serviceName": "Google Cloud Identity and Access Management (IAM)",
        "serviceId": "cloud-iam",
        "category": "Security, Identity, & Compliance",
        "releaseNotesUrl": "https://cloud.google.com/iam/docs/release-notes"
      }
    ]
  },
  {
    "date": "2026-09-04",
    "title": "Google Cloud KMS: Automated Key Rotation & Multi-Region HSM Hardening",
    "summaryMarkdown": "### Google Cloud Security & IaC Highlights\n\n- **Google Cloud Key Management Service (Cloud KMS)**: Automated crypto key rotation schedule enhancements, Cloud HSM multi-region support, and expanded integration with Security Command Center. Separate key administration from key usage via distinct IAM roles and enforce VPC Service Controls around cryptographic operations. *Terraform Support*: Supported in [Terraform Google Provider: google_kms_crypto_key](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/kms_crypto_key) in **v5.30.0+**.",
    "updates": [
      {
        "serviceName": "Google Cloud Key Management Service (Cloud KMS)",
        "serviceId": "cloud-kms",
        "category": "Security, Identity, & Compliance",
        "releaseNotesUrl": "https://cloud.google.com/kms/docs/release-notes"
      }
    ]
  }
]