Key Points:  

  • Corellium solutions are now deployable in public preview on Google Cloud C4A metal instances 
  • Teams can validate mobile, automotive, and embedded systems through ARM virtualization, without relying on physical hardware 
  • Run testing directly in existing Google Cloud environments with no additional infrastructure 
  • Scale across hundreds of configurations without maintaining device fleets 
  • Support long-term compliance requirements like UNR155 without physical labs 

Corellium is now in public preview on Google Cloud Axion  

The shift to cloud-first is no longer a prediction, it is the operating model for most organizations building software at scale. Yet many of these organizations develop software that runs on dedicated custom hardware that bears little resemblance to servers in the cloud, limiting their ability to fully adopt a cloud-first methodology. 

Corellium security validation solutions, including Viper and Falcon are now available in public preview on Google Cloud Axion C4A bare metal instances, giving teams a way to validate software across mobile, automotive and embedded systems in a cloud-first environment. Teams can run validation directly in their existing Google Cloud environments without relying on physical infrastructure that slows development. 

For more complex systems, Corellium Atlas makes it possible to recreate and test full environments, from kernel-level firmware to user-facing applications like Android Auto, without maintaining costly physical infrastructure. 

Why physical hardware is slowing teams down 

The challenge is not a lack of testing tools. It is a lack of access.  

Physical hardware introduces friction at every stage of the process. Teams coordinate access to limited devices, maintain inventory across versions and decide which scenarios to test based on what is available rather than what is needed.  

The result is predictable: 

  • Delays in validation when required configurations are unavailable 
  • Incomplete coverage across versions and environments 
  • Increased operational overhead to maintain hardware fleets 
  • Inconsistent results across teams working in different locations 

This problem becomes more pronounced as systems grow more complex, and release cycles accelerate. 

Beyond Automotive: Mobile, Embedded and IoT Validation 

Automotive highlights the issue, but the challenge exists well beyond vehicles.  

Mobile applications, embedded systems and connected devices all require access to real operating environments to validate behavior and security. As these systems become more software-defined, the number of possible configurations increases. Hardware-based testing models cannot keep pace with that growth. 

The result is a widening gap between how software is built and how it is validated. 

How Cloud-Based Virtualization Replaces Physical Device Fleets 

Instead of relying on physical devices, teams are shifting toward validation platforms that give them a virtual lab they can control and scale. 

Corellium makes that possible by allowing teams to recreate real systems in the cloud and validate how software behaves under real conditions. 

Teams can: 

  • Spin up environments on demand instead of waiting for hardware 
  • Test across multiple configurations at the same time 
  • Validate changes earlier in the development cycle 
  • Run consistent tests across distributed teams 

This cloud-first methodology frees testing from access limitations and transforms it into something that scales with development and keeps up with how modern software is built. 

System-Level Validation for Automotive and Embedded Platforms 

For teams working beyond individual applications, validation needs to happen at the system level. 

Corellium Atlas supports this by enabling teams to recreate full environments – from low-level kernel and firmware components to user-facing interfaces like Android Auto and QNX infotainment systems. These environments include everything needed to validate how software behaves across the full stack. 

With Atlas, teams can: 

  • Recreate full system stacks across different hardware generations 
  • Run software at the speed of real silicon without physical devices 
  • Replace large physical test fleets with scalable virtual environments 
  • Execute validation across multiple configurations simultaneously 
  • Test software before physical hardware is available 

This allows teams to validate interactions across components and identify issues that would not surface in isolated testing environments. 

Corellium on Google Cloud Axion: Arm-Based Validation at Scale 

Before this expansion, running Corellium required specialized Arm-based bare-metal infrastructure that was only available from a limited number of cloud providers. 

For teams already operating on Google Cloud, that meant deploying Corellium required additional infrastructure outside their current environment. With public preview support for Google Cloud Axion C4A metal instances, that barrier is removed. Teams can deploy Corellium directly within their existing Google Cloud environments today, with general availability expected following Google Cloud Next. 

“The public preview availability of Corellium on Google Cloud Axion C4A metal instances reflects growing demand for Arm-based infrastructure to support complex development and security workloads,” said Florian Haubner, Industry Architect Lead Automotive at Google Cloud. “We’re excited to support Cellebrite’s Corellium platform as it brings scalable, system-level validation to Google Cloud customers across mobile, embedded, and automotive environments.” 

This expansion applies across the Corellium platform, including mobile application validation, vulnerability research, and system-level testing for automotive and embedded systems. 

Axion C4A provides the performance required for these workloads. Automotive systems, for example, rely on technologies such as Android Auto and QNX that depend on accurate system-level behavior. Running these environments on Arm-based infrastructure ensures that validation reflects how software will perform in production. 

Compliance and Long-Term Automotive Cybersecurity Validation 

Regulatory requirements are shifting how teams approach testing. 

Frameworks like UN Regulation No. 155 (UNR155) require automotive manufactures (OEMs) to implement rigorous Cybersecurity Management Systems (CSMS) validation of software security across the lifecycle of a vehicle, which can extend for more than a decade. This is not a one-time certification exercise. It is an ongoing process that must keep pace with updates and changes. 

To meet these requirements, teams need validation environments that are: 

  • Repeatable across time and versions 
  • Scalable across multiple configurations 
  • Consistent across teams and locations 

Physical hardware introduces variability and operational overhead that make this difficult to sustain. 

By moving validation into controlled environments, teams can maintain consistency and produce evidence that supports audits and regulatory expectations. 

What scalable validation looks like in practice 

When hardware is no longer a constraint, validation becomes part of the development workflow rather than a bottleneck at the end. 

Teams can: 

  • Validate new builds as soon as they are available 
  • Run large-scale testing across configurations without additional setup 
  • Identify issues earlier when they are easier to fix 
  • Standardize validation processes across teams 

This leads to more predictable outcomes, stronger coverage, and reduced risk as systems move toward release. 

From Investigations to Proactive Security Validation 

Corellium, part of the Cellebrite portfolio, expands the platform beyond device investigations into security validation. 

Cellebrite has built its leadership around helping organizations access and analyze digital evidence after an incident. Corellium extends that capability earlier in the lifecycle, giving teams a way to validate how software behaves before issues reach production. 

With this expansion, organizations can move beyond investigating what happened and start validating what could happen. Teams can test mobile applications, automotive systems and embedded environments running on Arm in controlled, scalable environments that reflect real-world conditions. 

The addition of Google Cloud Axion C4A metal instance (in public preview) removes one of the biggest barriers to making that shift. Teams can now run validation directly in the environments where their systems already operate. 

This connects two sides of the same problem. Investigation provides visibility into incidents. Validation provides confidence before they occur. 

Together, they give organizations a more complete approach to managing risk across modern, software-defined systems.  

Learn how Corellium supports mobile, automotive and embedded systems. 

Frequently Asked Questions (FAQ):  

What is Corellium Atlas?  

Corellium Atlas is a system-level validation platform that enables teams to recreate complete hardware environments — including vehicle systems, embedded platforms, and complex multi-component architectures — in the cloud. Atlas allows teams to validate how software behaves across the full stack without relying on physical infrastructure, supporting use cases from automotive cybersecurity testing to embedded device validation. 

What is Google Cloud Axion?  

Google Cloud Axion is Google’s custom Arm-based processor that powers its C4A bare metal instances. It is designed to run performance intensive workloads directly on Arm architecture without virtualization overhead, making it well suited for environments that require high fidelity and system level accuracy. For Corellium, Axion enables teams to run mobile, automotive, and embedded validation workloads in the cloud with the same behavior and performance as real devices, without relying on physical hardware. 

Why is physical hardware a bottleneck in automotive software testing?  

Physical vehicles and hardware environments are expensive to maintain, slow to provision, and difficult to scale. Testing across multiple models, configurations, and software versions requires large fleets, which limits coverage and delays development cycles. 

Is this only for automotive testing?  

No. While automotive is a strong use case, Corellium supports any Arm-based system. This includes mobile applications, embedded systems, IoT devices, and other complex software environments. Teams use Corellium to validate how software behaves at the system level, identify vulnerabilities, and generate evidence across a wide range of use cases. 

How does Corellium help automotive teams scale testing?  

Corellium virtualizes Arm-based systems, allowing teams to recreate complete vehicle environments in the cloud. This enables parallel testing across hundreds of configurations without relying on physical vehicles or lab infrastructure. 

How does this support compliance requirements like UNR155?  

Corellium enables continuous validation across software lifecycles, allowing teams to test, document, and prove security controls over time without the limitations of physical testing environments. 

Share this post