// Security Advisory Triage

Google Application Integration extends actAs requirement to legacy integrations

Google Cloud security bulletins · published 2026-11-11 19:37 UTC
ACTION NEEDED MITIGATE SECURITYAPI
WHAT CHANGEDGoogle Cloud bulletin GCP-2026-068 updated 5 November 2026. Starting 15 January 2027 (UTC), Application Integration will require iam.serviceAccounts.actAs permission on the run-as service account to publish or test ALL integrations, including those created before 15 October 2026. Previously this requirement applied only to new integrations created on or after 15 October 2026.
WHY IT MATTERSExisting integrations created before 15 October 2026 that lack the actAs permission will fail to publish or test after the deadline. This affects scheduled and event triggers specifically.
WHAT TO DOAudit integrations created before 15 October 2026. Grant iam.serviceAccounts.actAs permission on each integration's run-as service account before 15 January 2027. See the bulletin's linked preparation guide for the exact permission grant procedure. Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-068.
Model-reported confidence 95% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 ## GCP-2026-068
 https://docs.cloud.google.com/support/bulletins/index#gcp-2026-068
-2026-11-04T19:14:32.553485+00:00
+2026-11-05T20:44:29.684252+00:00
 
-Published: 2026-10-14Updated: 2026-10-24Description
+Published: 2026-10-14Updated: 2026-11-05Description
 
 Description
 Severity
@@
 What should I do?
 No customer action to resolve this vulnerability is required.
 This vulnerability was patched on August 27, 2026.
-To improve security against authorization vulnerabilities,
-starting October 15, 2026, Application Integration
-requires the iam.serviceAccounts.actAs permission on the
-run-as service account for any new integrations. Existing integrations
-and their new versions are unaffected.For more information, see
+Application Integration helps to enhance security against
+authorization vulnerabilities by requiring the
+iam.serviceAccounts.actAs permission on the run-as service
+account to publish or test an integration. Integrations created on or
+after October 15, 2026, must have a run-as service account to publish or
+test scheduled or event triggers. Starting January 15, 2027 (UTC), this
+requirement also applies to existing integrations created before
+October 15, 2026. For more information, see
 Prepare for upcoming authorization changes.
 What vulnerabilities are being addressed?
 An authenticated user could escalate privileges and impersonate a
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningNew enforcement deadline for existing integrations changes what platform leads must do by January 2027.
signalsfuture enforcement date added: January 15, 2027 · requirement scope expanded: now applies to existing integrations · behavioral change: new deadline for legacy integrations · cloud control plane service affected: Application Integration · managed runtime policy change affecting customer workloads
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)