Thomas Kurian now owns the most consequential integration assignment of his tenure at Google Cloud. On March 11, 2026, Google completed its $32 billion purchase of Wiz, the cloud-security company it agreed to acquire a year earlier. Wiz joined Google Cloud while retaining its brand, products and commitment to protect workloads across Amazon Web Services, Microsoft Azure and Google Cloud.
That last promise is the operating thesis, not a courtesy to existing customers. Enterprises rarely run on one cloud. Their security teams need a common view of identities, data, code and misconfigurations across providers. Wiz built its growth by presenting itself as an independent layer above those estates. Google bought that customer trust along with the technology. If integration turns Wiz into a mechanism for steering workloads toward Google, the acquisition can lose the quality that justified its price.
Kurian has already shown that he can turn Google Cloud from a technically admired challenger into a scaled enterprise supplier. Artificial intelligence has accelerated that work. The next phase is harder because it combines product architecture, channel conflict, culture and capital allocation. He must make Wiz valuable to Google without making it less credible to customers whose largest cloud relationship may be elsewhere.
Security is becoming Google Cloud’s distribution layer
Google Cloud entered 2026 with momentum. Alphabet reported that customers were adopting its AI infrastructure and applications rapidly, large contracts were increasing and cloud profitability was expanding. The company expected a growing share of its machine-learning computing capacity to serve external cloud customers rather than only Google’s consumer products. That shift makes enterprise trust more important than model benchmarks.
Security can deepen every part of the relationship. A customer experimenting with generative AI needs to know where sensitive data sits, which model or agent can access it, whether code has created a new exposure and how activity changes at runtime. Wiz’s security graph maps relationships across cloud resources. Combined with Google’s threat intelligence, incident-response capabilities and AI infrastructure, it can become an entry point to broader cloud conversations.
The commercial opportunity is attractive because security budgets can be more durable than experimental AI spending. Cloud customers may delay an application migration, but they cannot ignore a critical exposure. A security platform also reaches chief information-security officers, boards and audit committees, expanding Google Cloud’s access beyond infrastructure teams.
Yet distribution cuts both ways. Google’s sales organisation can place Wiz in front of far more enterprises and partners. It can bundle services, align incentives and use existing contracts to reduce procurement friction. Those advantages become liabilities if salespeople treat Wiz mainly as a wedge for Google Cloud consumption. Kurian should measure how much Wiz grows on rival clouds, not merely how much Google Cloud revenue follows a Wiz deployment.
Neutrality must be visible in product decisions
Multi-cloud neutrality is not established by a press release. Customers will test it through release cadence, depth of integrations and access to data. Wiz must continue supporting new services from AWS and Azure quickly, even when those services compete directly with Google. Its risk models should apply comparable scrutiny across providers. Its dashboards should not make Google environments easier to remediate while leaving rival workloads with weaker automation.
Organisational design matters. Wiz needs product authority, engineering resources and a route to Kurian that does not depend entirely on Google Cloud’s infrastructure priorities. Retaining the brand helps, but independence requires budget and decision rights. Compensation for account teams should reward protecting the customer’s full estate. Partner programmes should include consultancies and security vendors that have deep ties to AWS and Microsoft.
Data governance will draw close attention. Security telemetry can reveal an enterprise’s architecture, vulnerabilities and operating patterns. Google must define strict boundaries around how Wiz data is used, particularly for training models, improving unrelated services or informing competitive sales. Customers should receive clear controls, retention policies and auditability. The burden is higher because Google operates advertising, productivity, developer and cloud businesses under one parent.
Regulators may also examine whether bundling disadvantages independent security vendors. Google can reduce those concerns by preserving open interfaces and allowing customers to export findings, integrate competing tools and procure Wiz separately. Kurian does not need to sacrifice cross-selling. He needs to demonstrate that the cross-sell comes from product value rather than contractual pressure or technical lock-in.
The price raises the standard for integration
At $32 billion, Wiz is not a feature acquisition. It is larger than any previous deal completed by Google and creates a demanding return threshold. The purchase price reflects scarce growth, enterprise distribution and a belief that cloud security will be central to the AI era. Google must convert those expectations into revenue without forcing changes that slow the company it bought.
The first risk is talent. Wiz’s founders and senior engineers created a fast product culture outside a large corporate structure. Retention packages can keep people for a period, but autonomy, mission and speed determine whether they continue building. Google’s review processes, privacy obligations and infrastructure standards can improve reliability while also lengthening decisions. Kurian must identify which controls are essential and which can be adapted.
The second risk is portfolio complexity. Google Cloud already sells Security Operations, threat intelligence and Mandiant services. Wiz overlaps with some functions and complements others. Customers need a simple explanation of which platform handles posture, detection, response and application security. Duplicated products create internal competition and raise integration costs. A rushed consolidation, however, can break workflows or alienate customers.
The third risk is accounting disguised as strategy. Bundled contracts can make revenue attribution look successful even if users are not expanding or renewing Wiz on its merits. Kurian should focus on net retention, module adoption, time to remediation and cross-cloud coverage. Security outcomes matter more than the number of licences attached to a cloud agreement.
Alphabet has the balance sheet to absorb a long investment cycle. That does not remove discipline. The acquisition should eventually improve customer acquisition, increase security revenue and strengthen Google Cloud’s position in large accounts. It should also produce evidence that Google can manage a major enterprise software asset after years of relying mainly on internally built products.
AI agents make the integration more urgent
Enterprise AI is moving from assistants that generate text to agents that can call tools, change systems and execute workflows. Each additional permission creates a new security path. Traditional inventories organised around servers or applications are insufficient when an agent can combine identities, data stores and external services dynamically.
Wiz has been extending its platform across AI infrastructure and agentic systems. Google can connect that context with Gemini, its developer platform and its security operations tools. The strategic prize is a control layer that lets enterprises deploy agents while continuously evaluating what they can see and do. If Google makes security native to the development process, it can compete on safe deployment rather than raw model capability alone.
That opportunity also intensifies conflicts. A security platform must be willing to flag unsafe configurations in Google’s own AI services with the same clarity it applies elsewhere. It should support customers that use rival models and agent frameworks. The credibility of its recommendations depends on separating assurance from cloud promotion.
Kurian can establish that separation through published product commitments, customer councils and transparent service-level measures. He can retain independent routes for responsible disclosure and allow Wiz researchers to criticise weaknesses across the market. Those practices will sometimes create uncomfortable conversations inside Google. They are part of the value of owning a trusted security company.
Success will be measured outside Google Cloud
The obvious integration scorecard includes revenue growth, renewals and adoption across Google Cloud accounts. A stronger one tracks whether AWS- and Azure-heavy customers deepen their use of Wiz after the acquisition. If they do, Google will have proved that it can own a neutral enterprise platform. If they reduce exposure or demand contractual protections, the market will be signalling that the brand promise is not enough.
Kurian should also watch partner behaviour. Systems integrators, managed-security providers and software vendors will decide whether Wiz remains a platform around which they can build. Continued investment by that ecosystem can multiply Google’s reach. Consolidation into a closed bundle would narrow it.
The acquisition gives Google Cloud a chance to become the company enterprises trust to secure heterogeneous computing, not simply another provider defending its own perimeter. That is a more valuable position in an AI market where customers will combine models, chips and clouds. It is also more difficult to maintain because every commercial incentive pulls toward the parent platform.
Customer concentration deserves attention as well. A few very large contracts can create apparent momentum while giving buyers significant negotiating power. Kurian should broaden adoption among regulated mid-sized companies, where simple deployment and independent assurance matter. That would make Wiz less dependent on a small group of strategic accounts and provide a wider test of whether Google’s distribution adds durable value.
Thomas Kurian has spent years convincing enterprises that Google Cloud understands their operating needs. Wiz puts that claim under a sharper test. The $32 billion return will not come from making Wiz look more like Google. It will come from using Google’s resources to make Wiz stronger everywhere, including on infrastructure Google does not control.
