Clarification: August 5, 2026 release note for Melbourne and Seoul

In Melbourne (australia-southeast2) and Seoul (asia-northeast3), only the Sensitive Data Protection filter is supported when data residency is enforced. To use other Model Armor features in these regions, disable data residency enforcement in the template.

For information about available Model Armor features for each region, see Supported features by region.

Filter version v3 will be promoted to the Stable alias on or before September 25, 2026. On the same date, filter versions v1 and v2 transition to Legacy status and retire on November 29, 2026.

If your templates use the Stable alias, they will automatically upgrade to v3 when it is promoted. If your templates use explicit version numbers (v1 or v2), migrate them to v3 or the Stable alias before November 29, 2026.

For more information, see Set the filter version for a template.

You can disable data residency enforcement for in-use and in-transit data in Model Armor templates. Disabling data residency enforcement allows cross-jurisdictional routing to enable Model Armor features that are otherwise unavailable in limited-support regions. Data at rest remains compliant with data residency requirements.

For more information, see Set data residency compliance and Data residency and endpoints.

Model Armor supports screening prompts and responses up to 65,536 tokens (262,144 characters) for prompt injection and jailbreak detection, responsible AI, and child sexual abuse material (CSAM) filters. Model Armor scans only the first 256 URLs found in prompts and responses.

For more information, see Token system limits.

Model Armor supports data residency compliance for in-use and in-transit data in the following regions:

• Melbourne (australia-southeast2)
• Seoul (asia-northeast3)

To maintain data residency compliance, these regions have limited feature support. For more information about data residency enforcement in Model Armor, see Data residency and endpoints.

For information about available Model Armor features for each region when using templates, see Supported features by region.

A clarification for this release note is provided in the September 4, 2026 release note.

Filter version v3 will be promoted to the Stable alias on August 31, 2026. On the same date, filter versions v1 and v2 transition to Legacy status and retire on November 29, 2026.

If your templates use the Stable alias, they automatically upgrade to v3 on August 31, 2026. If your templates use explicit version numbers (v1 or v2), migrate them to v3 or Stable before November 29, 2026. For more information, see Set the filter version for a template.

The responsible AI safety filter for the hate speech, harassment, sexually explicit, and dangerous content categories has been upgraded to improve detection accuracy and reduce the rate of false positives.

Streaming sanitization for text is generally available (GA). For more information, see Sanitize streaming text prompts.

Model Armor supports data residency in-use and in-transit compliance in Japan (asia-northeast1) and the United Kingdom (europe-west2). These regions have limited feature support. For more information, see Data residency.

You can select the modality (text, images, or both) when creating a Model Armor template in the Google Cloud console. Image modality is supported in the us and eu multi-regions. This feature is in Preview. For more information, see Image screening.

Model Armor supports screening images within prompts and responses. This feature extends Model Armor's protection capabilities to multimodal inputs, helping you detect and mitigate risks associated with image content in your AI applications. This feature is in Preview. For more information, see Image screening.

You can enable Model Armor on an Agent Gateway resource to apply your organization's content security guardrails to prompts and responses that pass through the gateway. This feature is generally available (GA).

For more information, see Integrate Model Armor with Agent Gateway.

Model Armor supports data residency in-use compliance in Singapore (asia-southeast1). This region has limited feature support. Filter version v3 under the Latest alias is available in asia-southeast1 and it includes an updated prompt injection and jailbreak detection filter to improve accuracy and reduce false positives. For more information, see Data residency.

Filter version v3 under the Latest alias is available in asia-south1 and northamerica-northeast2. This version includes an updated prompt injection and jailbreak detection filter to improve accuracy and reduce false positives.

Model Armor supports data residency in-use compliance in Mumbai (asia-south1) and Toronto (northamerica-northeast2). This compliance lets you meet regional data locality requirements when using Model Armor in these regions. For more information, see Data residency.

Model Armor supports multiple filter versions, allowing you to choose the version that best suits your needs for stability and access to the latest features. You can configure versions within your templates using version numbers or aliases such as Latest, Stable, and Legacy. For more information, see Set the filter version for a template.

A new filter version, v3, is available under the Latest alias. v3 features an updated prompt injection and jailbreak detection filter. This new model has been trained to:

• Significantly reduce false positives.
• Provide improved detection and mitigation against various attack vectors.

Model Armor supports streaming sanitization for text. You can process user prompts and model responses more efficiently for large inputs and low-latency scenarios by sending text to the Model Armor API as a stream of chunks. This feature is in Preview. For more information, see Sanitize streaming text prompts.

Model Armor is available in Gemini Enterprise Agent Platform and integrates with Agent Gateway to provide enhanced security and governance for your AI agent interactions. This integration lets you enforce Model Armor's AI safety and security policies directly on gateway traffic.

To screen AI agents for content security risks and block violations, configure Model Armor on the gateways that govern your agents. You can then do the following:

• Monitor content security insights from Model Armor on the Agent Platform Security page in the Google Cloud console.
• View Model Armor trace spans.

This feature is in Preview. For more information, see Integrate with Agent Gateway.

Feature

Model Armor integration with Google and Google Cloud MCP servers is in General Availability.

The level of detail provided in the virusDetails field of the Antivirus filter scan results has been updated. To enhance security and align with data handling policies, responses no longer include specific names of security vendors or threat signatures. Instead, generalized placeholders are used when a threat is detected. This change does not affect the efficacy of the Antivirus filter's detection capabilities.

Model Armor is FedRAMP High compliant.

Feature

Model Armor can sanitize data passed in as rich documents that have specific metadata labels. To use this feature, create a custom metadata label infoType in Sensitive Data Protection. Use the custom infoType in an advanced Sensitive Data Protection configuration in your Model Armor template.

Prompt injection and jailbreak detection was improved to reduce the rate of false positives and false negatives.

Model Armor is available in the following regions:

• asia-northeast1 (Japan)
• asia-northeast3 (South Korea)
• europe-southwest1 (Madrid)
• europe-west9 (Paris)
• northamerica-northeast2 (Canada)

For more information, see Locations.

The malicious URL detection and responsible AI safety filters are fixed to improve detection accuracy and reduce the rate of false positives.

Model Armor is available in the australia-southeast2 (Melbourne) region. For more information, see Model Armor Locations.

For non-English requests, the translation process was enhanced to improve service availability and processing efficiency.

The behavior of multi-language detection for text prompts and model responses has changed.

Previously, if you specified the source language in your sanitization request, Model Armor compared the specified language with the automatically detected language. If the specified and detected languages differed, Model Armor skipped the request.

With this change, if you specify the source language, Model Armor uses that language to evaluate the request. It no longer attempts to automatically detect the language.

The error messages returned by the Sensitive Data Protection detector have been modified to exclude internal details. If a transient or internal quota error occurs, you will receive the message: Error occurred while processing sensitive data detection. Please try again.

The prompt injection and jailbreak detection filter for the Mumbai (asia-south1) and Singapore (asia-southeast1) regions is upgraded to improve detection accuracy and reduce the rate of false positives.

You can configure Model Armor floor settings for Google-managed Model Context Protocol (MCP) servers to define baseline safety and security filters. This feature is in Preview.

You can also configure Cloud Logging for sanitization operations. The Model Armor floor settings perform these operations on traffic to and from Google-managed MCP servers and Gemini Enterprise Agent Platform models.

You can configure Model Armor to enhance the security of your agentic AI applications that interact with Google Cloud Model Context Protocol (MCP) servers. This feature is in Preview. For configuration details, see Model Armor integration with Google Cloud MCP servers.