GCP News - 2026-08-18
2026-08-18
最終更新: 2026-08-27 21:31:31 JST
Google Cloud Release Notes
August 18, 2026
- Link: https://docs.cloud.google.com/release-notes#August_18_2026
- Published: 2026-08-18 16:00:00
- Fetched: 2026-08-27 21:31:25
詳細を表示
App Engine standard environment Java
Feature
Support for migrating from the App Engine Images service to Cloud Run is in General Availability (GA).
App Engine standard environment Python
Feature
Support for migrating from the App Engine Images service to Cloud Run is in General Availability (GA).
BigQuery
Feature
The default per-project limit of user-specific reservation assignments has been increased from 10 to 100.
Gemini Enterprise
Feature
Gemini Enterprise: Show new team member announcements on the app home page
Gemini Enterprise can display new team member announcement cards on the app home page to welcome people who recently joined the organization. Users see people who recently joined their part of the organization.
This feature is generally available (GA). For more information, see Show new team member announcements.
Feature
Gemini Enterprise: Gemini 3.6 Flash available in US and EU multi-regions
Gemini 3.6 Flash is generally available in the us and eu multi-regions, and
an allowlist is no longer required to use Gemini 3.6 Flash in the us
multi-region.
To make Gemini 3.6 Flash available to users in the Gemini Enterprise app,
administrators must turn on the Gemini 3.6 Flash feature toggle in the
Google Cloud console.
If an administrator previously turned on the Gemini 3.6 Flash toggle for
an app in the us or eu multi-region and accepted the out-of-region routing
warning, traffic for that app automatically routes to the app's location
(us or eu). No action is required.
In regions where the model is not supported, administrators can still enable
the model by acknowledging a warning that traffic routes to the global
endpoint, which does not support regional data residency.
For more information, see:
- Manage features on the web app
- Data residency for Gemini Enterprise Standard and Plus Editions and Gemini Notebook Enterprise
Feature
Gemini Enterprise: Access and configure AI developer tools
AI developer tools is generally available (GA) for Gemini Enterprise Standard, Plus, and Pay-as-you-go editions with an invoiced Cloud Billing account. This launch includes access to Antigravity 2.0, Antigravity CLI, and Android Studio.
Key capabilities of AI developer tools include the following:
- Administrative controls: Turn on or turn off AI developer tools, configure security policies (such as file access and terminal command execution), and manage model availability in the Google Cloud console.
- Usage metrics dashboard: Monitor developer adoption, active users, token consumption, and API call volumes with integrated Cloud Monitoring and logging.
You can manage access to AI developer tools using a custom IAM role.
For more information, see the following:
- AI developer tools overview
- Configure AI developer tools settings
- Create custom roles for AI developer tools
- View AI developer tools metrics
Gemini Enterprise Agent Platform
Feature
CodeMender updates: Model support
This release introduces updates to CodeMender:
- Gemini 3 Flash removal: Gemini 3 Flash (
gemini-3-flash-preview) is no longer supported as a model backend for CodeMender. CodeMender supports Gemini 3.5 Flash (default) and Gemini 3.1 Pro Preview.
For more information, see Specifying the model.
Google Kubernetes Engine
Change
For node pools running on GKE versions 1.36.3-gke.1480000 and later, the minimum supported boot disk size is 15 GB. For earlier versions, the minimum supported boot disk size is 12 GB.
Google SecOps
Feature
[Spotlight Feature] Evaluate threat coverage and generate rules with the Detection Engineering Agent
This feature is in public preview. You can now evaluate and strengthen your Google SecOps security posture against emerging threats using the Detection Engineering Agent. This AI-powered assistant helps you extract threat intelligence and automatically draft YARA-L detection rules, drastically improves time-to-value for custom security automation and accelerating risk mitigation. The agent is accessible using Model Context Protocol (MCP) tools operated by compatible AI clients (such as Google Antigravity or Claude Code). For more information, see Evaluate threat coverage with the Detection Engineering Agent.
Feature
[Spotlight Feature] Event simulation for detection coverage evaluation
This feature is in public preview. You can now programmatically deliver realistic threat sequences into the live ingestion pipeline using event simulation. Event simulation provides a full-funnel detection coverage evaluation framework embedded directly within Google SecOps, enabling detection engineering and SOC teams to verify the entire detection lifecycle—from UDM normalization to multi-event correlation and alerting—while preserving production SOC workflows.
As a core capability of the Detection Engineering Agent (DEA) architecture, event simulation connects Google SecOps MCP tools with AI assistance (such as Gemini) to automate threat intel processing, synthetic telemetry generation, and YARA-L 2.0 rule coverage evaluation.
For more information, see Use event simulation for detection coverage evaluation.
Looker
Announcement
The latest versions in the Looker (Google Cloud core) release channels are beginning deployment as follows:
- Latest version in the Rapid channel: Looker 26.14
- Latest version in the Regular channel: Looker 26.12
- Latest version in the No Channel channel: Looker 26.14
NetApp Volumes
Announcement
Google Cloud NetApp Volumes is now Canada Controlled Goods (CCG) compliant for the Standard, Premium, and Extreme service levels. For more information, see Compliance.
Google Cloud Blog (AI & ML)
Building operational resilience with agentic AI in financial services
- Link: https://cloud.google.com/blog/topics/financial-services/building-operational-resilience-with-agentic-ai-in-financial-services/
- Published: 2026-08-18 23:00:00
- Fetched: 2026-08-27 21:31:31
詳細を表示
For financial institutions, operational resilience has long been embedded in regulatory and supervisory expectations — to say nothing of the high expectations of consumers. With the implementation of the European Union’s Digital Operational Resiliency Act (DORA), those expectations have become even more stringent, with more explicit, harmonized, and evidence-driven requirements. Firms must now demonstrate that their critical business services and supporting digital infrastructures can withstand disruption, support coordinated response, and recover with control.
To meet these conditions, Deutsche Bank developed an AI-powered agentic resilience platform that modernized its regulatory tabletop resilience exercises at scale and turned manual preparation into context-aware and evidence-ready simulations grounded in actual operational data. The platform builds enterprise context from architecture, data flows, logs, incident history, alerting signals, and operational telemetry to generate scenarios, simulated operational evidence, structured session records, and regulator-ready artifacts.
At many large banks with operations that span interdependent applications, data flows, and third-party services, this is a critical and even existential shift. Across financial services, supervisory expectations are evolving and as they do, banks’ tabletop exercises must reflect their production dependencies, real operating conditions, and compliance with consistent evidence standards more directly.
As Deutsche Bank considered how to successfully and efficiently make this shift at scale, it looked to its long-time partner, Google Cloud, and its growing suite of agentic AI tools.
From tabletop exercises to resilience intelligence
With its agentic resilience platform, DB has been able to transform its tabletop exercises from manual preparation to a continuous intelligence model. And it’s been able to extend the same agentic layer to root-cause analysis when real operational context is needed.
This means that every scenario it runs is based on real enterprise signals. The platform can then reflect true system dependencies, failure patterns, and business impact instead of relying on static inputs that are more likely to return assumptions than real-time insights.
By using Gemini Enterprise Agent Platform, DB has been able to migrate this operational context into structured scenarios with clear timelines, decision points, and expected responses. This has ensured that each exercise is grounded in real system behavior that produces consistent, audit-ready evidence that meets regulatory expectations.
Dual orchestration for control and flexibility
In order to deliver both regulator-grade control and operational flexibility, DB’s platform introduced a dual-orchestration architecture that separates workflows into two complementary execution models.
First, for regulator-aligned execution, the bank is using LangGraph to ensure that it generates every scenario through a traceable, deterministic process — with clear lineage from input context to output — that supports the auditability required for supervisory review.
Next, for its adaptive and investigative scenarios, DB is using Google Agent Development Kit (ADK) to enable agent-driven coordination. This approach allows the bank’s platform to dynamically analyze conditions and generate responses without predefined execution paths.
<div class="article-module h-c-page">
<div class="h-c-grid">
<figure class="article-image--large
h-c-grid__col
h-c-grid__col--6 h-c-grid__col--offset-3
">
<img alt="image1" src="https://storage.googleapis.com/gweb-cloudblog-publish/images/image1_dbc2MvR.max-1000x1000.png" />
</a>
<figcaption class="article-image__caption "><p>Figure 1. Architecture for context assembly, orchestration, and scenario generation.</p></figcaption>
</figure>
</div>
</div>
With this architectural separation, the platform can combine governed execution with adaptive investigation while preserving a common intelligence layer. The same agents and tools can reason over architecture, data-flow diagrams, logs, and code artifacts across tabletop scenario generation and related incident-analysis workflows. Importantly, this supports a consistent resilience model across both planned exercises and real operational events.
Deutsche Bank’s objective with this platform was to engineer a resilience model for critical financial systems that meets regulatory expectations — even within highly complex, distributed environments. By linking dynamically generated scenarios to real business context and combining governed orchestration with adaptive analysis, the platform has given us an intelligent, continuously adaptive model for operational resilience.” – Sanjay Tripathi, Managing Director, Global Head of Surveillance Technology & Compliance Cloud & AI Transformation Lead, Deutsche Bank
Powering generation and governance with Google Cloud
Google Cloud’s suite of agentic tools is providing the foundation for scaling Deutsche Bank’s platform across its many governed, enterprise-grade resilience workflows. Here’s how:
-
Cloud Run supports elastic execution of scenario and evidence-generation services.
-
Gemini Enterprise Agent Platform transforms operational context into structured resilience scenarios.
-
Google ADK enables adaptive agent coordination.
-
Cloud SQL provides durable persistence for scenarios, session artifacts, and review records.
Collectively, these services give DB support for the traceable generation, controlled execution, and persistent evidence record required for compliance review and continuous improvement.
Scalable, evidence-ready resilience testing
Every scenario generated by Deutsche Bank’s platform drives a structured tabletop session for the teams that run response, escalation, and recovery. Because these exercises are grounded in real enterprise context, they reflect operational reality while also strengthening consistency across teams and creating audit-ready evidence that meets regulatory expectations. For institutions that operate under DORA or similar frameworks, this makes it easier to demonstrate controlled, coordinated, and disciplined response at scale.
This model is now being applied across multiple DB portfolios, which is helping the bank establish more consistent and scalable resilience paradigms and a replicable blueprint for the broader financial sector.
In this model, root-cause analysis acts as the feedback loop between real incidents and future resilience testing. The resulting insights from production events can inform future tabletop scenarios, while exercise outcomes can strengthen response playbooks, escalation paths, and recovery readiness.
All of this extends the platform’s value from planned resilience exercises to real operational events while keeping scenario-based resilience testing as the primary use case.
As adoption expands, this platform brings consistency by embedding Google Cloud’s methodology for context-aware resilience. It eliminates fragmented manual approaches and establishes a cross-functional, AI-informed operating model across the bank.
Toward resilience intelligence
The bank’s next step is to extend this approach into a broader resilience intelligence layer, which is possible because it can deploy the same patterns to support playbook refinement, recovery-readiness assessments, and continuous validation of controls against evolving system conditions.
For financial institutions, this is a strategic shift. As systems become more distributed and regulatory expectations more demanding, banks must move from periodic resilience testing to continuous, intelligence-driven capabilities. At Deutsche Bank, Google Cloud is making that transition simple across the organization.
Learn more about Google Cloud’s methodology for context-aware resilience in this article.