Is Cloud Infrastructure More Complex Than We Think?

Cloud complexity is increasing due to multiple stakeholders and fragmented processes. A recent Volkswagen breach highlights the risks of misconfigurations, particularly those introduced by third-party vendors.

January 11, 2026
5 Minute Read

In my previous post, I talked about how cloud security has become a reactive game - issues only being addressed after they are detected in production. At first glance, it seems there’s a solution in the form of “shift-left” practices - scanning IaC templates and managing configurations before deployment. However, these methods often assume a level of simplicity in cloud environments that just is not common in the real world.

Infrastructure as Code (IaC) was supposed to simplify and standardize cloud deployments, but only 13% of organizations have fully matured their IaC programs. Many still rely on manual processes, “ClickOps” or partial automation that are prone to countless misconfigurations. This complexity is compounded by the number of stakeholders touching the cloud environment: DevOps teams, IT departments, third-party vendors, and even M&A-driven “sub-organizations” operating under the same corporate umbrella. Each one adds a new layer, a new tool, and opens the door to misconfiguration.

The result? A lot more than just theoretical risk. Take the December 2024 incident at Volkswagen: a significant data breach exposed sensitive information including vehicle locations, customer information, and operational details on roughly 800,000 electric vehicles, all traced back to a cloud misconfiguration managed by a third-party provider. In cases like this, organizations relying on external vendors have limited control over their own security posture, leaving them exposed. Reactive cloud security measures and traditional CSPM approaches simply weren’t enough to prevent this incident. But then, what security approach could possibly work when an external vendor holds the keys to your cloud kingdom?

Isn’t it time we rethink cloud security entirely? Instead of resolving problems post-deployment, perhaps we need a truly proactive strategy - one that aligns with the realities of modern, multi-stakeholder, hyper-scaled cloud environments. If we don’t adapt now, we risk chasing one misconfiguration after another, never pausing to address the root cause: complexity itself.

‍

About
Ariel Litmanovich

Ariel Litmanovich is Co-Founder & CTO of Aryon Security, the Cloud Security Enforcement Platform that prevents cloud risks by enforcing policy before deployment. At Matzov, the IDF's elite cybersecurity unit, he led the military's transition to the cloud and designed its secure cloud infrastructure.

Read more articles by author →

Notes & Sources

  1. Is Something Missing in Cloud Security? https://lnkd.in/dKmUGTAj
  2. ‍StackGen 2025 Report https://lnkd.in/d2M6ySQ
  3. ‍Volkswagen Breach https://lnkd.in/dfD7gD4e

‍

Continue reading

Map showing Aryon's enforcement point between the starting pin and CSPM and CNAPP
November 18, 2026
Josh Thorngren

Cloud Security Intent Enforcement: Stop Risk Before It Exists

SACR's new CISO's Guide defines Cloud Security Intent Enforcement (CSIE) as its own layer of cloud security. What it means, where it sits next to your CNAPP, and how Aryon maps to it.

November 16, 2026
Abel Morales

From the Frontlines: Why SecOps and Incident Response Need Prevention in the Cloud

In the incidents I handled, the adversary rarely needed a zero-day. They only needed one setting to be wrong. In the cloud, that setting can expose an entire data store, sometimes for just a few minutes, and attackers now move faster than detection can: the average breakout takes 29 minutes, the fastest 27 seconds. Here is what I saw from the frontlines, and why SecOps and incident response teams should start with prevention.

November 9, 2026
Ariel Litmanovich
Yair Ladizhensky
Josh Thorngren

The Regulator Did Not Fine Them for the Bug

885 million mortgage documents were open to anyone who could change a digit in a web address, and the company’s own security team had found the flaw five months before a journalist reported it. Yet when New York’s financial regulator brought its first-ever cybersecurity enforcement action, it did not fine First American for the bug. It asked whether the company’s environment was under control. That is the question every Part 500 examination comes back to.

November 2, 2026
Vlad Babiuk
Tom Tsabar

Shipping and Maritime: A Cyber Incident Is Now a Hazardous Condition

As of July 2025, the US Coast Guard treats a cyber incident as a hazardous condition, in the same regime as a fire or a grounding. In shipping, that is not a compliance footnote. It recognizes what an attack actually takes away: not records, but the ability to operate.

October 26, 2026
Josh Thorngren
Vlad Babiuk

Healthcare: The Most Expensive Sector to Get Wrong

Healthcare faces the highest data breach costs of any industry, averaging $6.64 million per incident in 2026. As cloud adoption accelerates, misconfigurations threaten patient data, HIPAA compliance, and critical clinical operations. Discover why detection alone isn't enough and how preventive cloud security stops risky configurations before deployment-without disrupting patient care.

‍

October 19, 2026
Tair Lahayani
Tom Tsabar

Exploiting Cloud Misconfigurations, Part 2: How Attackers Discover Cloud Resources

The first thing an attacker needs is a target, so an attack naturally begins with resource discovery. During discovery, the attacker builds and expands a database of resource identifiers. These resources are then checked periodically for exploitable conditions. A resource may be discovered long before an opportunity to exploit it arises.

Ready to take your first proactive step?