Logo
Cybersecurity

Cloud Misconfigurations Are Still the Leading Cause of Breaches: Here Is How to Stay Ahead

ITSEC Asia, Indonesia's leading cybersecurity company, breaks down why cloud misconfiguration still outranks malware and zero day exploits as the most common way organizations get breached, and what actually needs to change before the next incident.

ITSEC AsiaITSEC Asia
|
Agu 07, 2026
Cloud Misconfigurations Are Still the Leading Cause of Breaches: Here Is How to Stay Ahead

Introduction


How many storage buckets, IAM roles, or API endpoints in your organization's cloud environment could you confidently say are configured correctly right now. Most security leaders cannot answer that with certainty, and that uncertainty is precisely what attackers count on. Recent industry research puts the picture in sharp focus. Verizon's Data Breach Investigations Report ties fifteen percent of breaches directly to cloud misconfiguration, while separate analysis from SentinelOne finds that ninety five percent of cloud security failures trace back to human error rather than a flaw in the platform itself. Gartner has been saying the same thing for years, projecting that through 2026, ninety nine percent of cloud security failures will be the customer's fault, not the provider's. ITSEC Asia, Indonesia's leading cybersecurity company, works with organizations across Indonesia, Singapore, Australia, and the UAE that are racing to modernize their infrastructure, and the pattern is consistent everywhere. Teams move fast to ship to the cloud, and the governance needed to secure that environment quietly falls behind.


Source: Cloud Security Statistics 2026: Key Data and Trends


Why Misconfiguration Still Beats Malware as the Number One Entry Point


Attackers do not need custom malware or a zero day exploit when a storage bucket is sitting open to the public internet or an identity role has far more privilege than it should. That is what makes misconfiguration such a persistent problem, it demands almost nothing from the attacker beyond a scanner and a bit of patience.

  • Roughly a third of cloud incidents originate from exposed storage buckets or unsecured databases that were left open during migration or testing and never locked back down before going live.
  • Misconfigured identity permissions were found to be a factor in as many as seventy five percent of cloud breach investigations conducted in 2024 and 2025.
  • Identity misconfiguration tends to be more dangerous than an exposed bucket precisely because it grants persistent, often undetected access that lets an attacker move laterally once inside, rather than a single exposed dataset that gets flagged the moment someone notices it.
  • The average cloud misconfiguration related breach is now estimated at 4.3 million dollars, a figure that climbed roughly seventeen percent year over year as breaches spanning multiple cloud environments proved consistently more expensive to contain than single environment incidents.

The financial weight behind these numbers is exactly why misconfiguration keeps outranking more sophisticated attack methods on every major threat list, it is cheap for an attacker to find and expensive for everyone else to clean up.


Source: 50 Cloud Misconfiguration Statistics for 2025 to 2026 · Cloud Misconfiguration: The Number One Cause of Data Breaches in 2025


The Risk Looks Different, and More Urgent, in Indonesia


Indonesian enterprises are not immune to this pattern, and in some respects the local conditions make it sharper. Banking, telecommunications, government, and e-commerce organizations have shifted critical workloads to public and hybrid cloud faster than many have built the internal expertise to secure them.

  • Development teams under pressure to deploy quickly often skip formal security review, leaving storage, networking, and identity settings sitting at default or overly permissive states.
  • Indonesia's National Cyber and Crypto Agency recorded more than fifty six million data exposures affecting hundreds of stakeholders in its most recent national landscape report, alongside billions of recorded attacks tracked through 2025.
  • Indonesia's Personal Data Protection Law requires data controllers to notify both affected individuals and the Data Protection Authority within seventy two hours of discovering a personal data protection failure, and the law's extraterritorial reach means organizations outside Indonesia can still be held accountable if they mishandle the data of Indonesian citizens.
  • Seventy percent of misconfigurations globally are estimated to remain undetected for weeks or months before anyone finds them, a timeline that leaves almost no margin against Indonesia's seventy two hour notification window.

Taken together, these numbers point to the same conclusion, the technical exposure and the regulatory clock are now moving at the same speed, and an organization that is slow on one will almost certainly be caught out on the other.


Source: Cloud Misconfiguration Risks for Indonesian Enterprises, IndoSec · 50 Cloud Breach Statistics for 2025 to 2026


What Staying Ahead Actually Requires


Closing this gap is less about buying another tool and more about treating configuration as something that needs continuous verification rather than a one time setup step. Cloud security posture management platforms that continuously assess configurations against recognized benchmarks give teams the visibility to catch drift before an attacker's scanner does, but the tooling only works if it is paired with a remediation workflow that prioritizes findings by exploitability and data sensitivity, rather than a dashboard nobody acts on. Just as important is where security sits in the development process itself. Waiting until an application is in production to review its cloud configuration is already too late, since a single insecure Infrastructure as Code template can silently replicate the same open port or excessive permission across dozens of environments before anyone notices. Building secure defaults into that template from the start, and validating identity permissions against the principle of least privilege before deployment rather than after, is what actually shifts an organization from reacting to breaches to preventing them. None of this requires exotic technology, it requires the discipline to check consistently rather than assume the last audit still holds true.


Source: Cloud Misconfiguration Risks for Indonesian Enterprises, IndoSec


Build the Habit of Checking, Not Just the Habit of Deploying


The organizations that avoid becoming another statistic in next year's breach report are not the ones with the most advanced infrastructure, they are the ones that treat cloud configuration as something that gets checked continuously rather than assumed correct. ITSEC Asia has spent more than a decade working alongside organizations across Indonesia, Singapore, Australia, and the UAE to close exactly this gap between rapid cloud adoption and the governance needed to secure it, and Bronyx, ITSEC Asia's AI powered continuous penetration testing platform, was built around the same principle this article keeps returning to, that a misconfiguration left unvalidated is only a matter of time before someone else finds it first.


Visit bronyx.ai to see how continuous, AI-powered penetration testing works, or reach the ITSEC Asia team directly at itsec.asia/contact to talk through what a real evaluation should look like for your organization.

Share this post

You may also like

What Is Cloud Security? A First Introduction for Modern Enterprises
Cybersecurity

What Is Cloud Security? A First Introduction for Modern Enterprises

INTRODUCTION: CLOUD ADOPTION IS ACCELERATING, SO ARE THE RISKS Cloud computing has been part of enterprise IT for years, but the risk landscape around it is changing faster than ever. As organizations embrace AI, remote work, and digital transformation, cloud environments have become the backbone of business operations and a prime target for attackers. Today, breaches are no longer limited to traditional data centers. Misconfigured cloud resources, stolen credentials, and unmanaged identities are now among the most common root causes of security incidents. This is why understanding what cloud security is and what it is not matters deeply for enterprises today. At its core, cloud security refers to the policies, technologies, configurations, and responsibilities that protect cloud-based systems, data, and services. This concept is inseparable from how cloud computing itself is defined:an on demand, shared,and externally managed computing model, as outlined in the NIST [https://csrc.nist.gov/pubs/sp/800/145/final]Cloud Computing Definition (SP 800-145), where responsibility is inherently distributed between the provider and the user. WHAT IS CLOUD COMPUTING? A SIMPLE ENTERPRISE PERSPECTIVE Cloud computing is not

ITSEC AsiaITSEC Asia
|
Feb 12, 2026 — 7 minutes read
€100 Million. One Third-Party Breach. How Far Can Trusted Access Reach?
Cybersecurity

€100 Million. One Third-Party Breach. How Far Can Trusted Access Reach?

A cyberattack against French banking group Crédit Mutuel Arkéa has exposed the financial consequences of compromised third-party access. On 5 November 2026, Reuters reported that approximately €100 million ($112.61 million) was missing following fraudulent transactions carried out using an account belonging to the bank. [1] The bank had initially disclosed the attack on 4 November. In a subsequent clarification, Arkéa said attackers entered through the platform of one of its service providers, reaching the bank directly. It explicitly denied that its online banking subsidiary Fortuneo was the entry point. Customer accounts were not involved and customer assets remained unaffected. Some transfers were temporarily delayed while the bank contained the incident and secured its operations. The final financial impact was still being assessed. [2][3] The incident raises an uncomfortable question for financial institutions: how much authority does an external service provider have inside the systems it connects to? The French incident is not the only recent warning. On 4 November, India's Computer Emergency Response Team (CERT-In) issued an updated warning about an active

ITSEC AsiaITSEC Asia
|
Nov 06, 2026 — 4 minutes read
The Cybersecurity Talent Pipeline Needs More Than More Graduates
Cybersecurity

The Cybersecurity Talent Pipeline Needs More Than More Graduates

Cybersecurity has no shortage of reasons to attract new talent. There are technical roles, policy roles, incident response, digital forensics, security engineering, governance and an expanding set of jobs around AI. Yet access to those paths isn’t evenly distributed. ITU’s Her CyberTracks programme puts a specific number against the problem: women accounted for 22% of the global cybersecurity workforce in 2025. ITU also identifies unequal access to training, a lack of strong female role models and limited awareness of cybersecurity career options among barriers to greater participation. ITU [https://www.itu.int/en/ITU-D/Cybersecurity/Pages/Skills-Development/Her-CyberTracks.aspx?utm_source=chatgpt.com] The programme’s fourth edition, running from May to October 2026, is designed around that gap. It combines technical and policy training with mentorship, networking and practical exercises. Its Asia-Pacific regional training is scheduled for 12–16 October in Bangkok. ITU [https://www.itu.int/en/ITU-D/Cybersecurity/Pages/Skills-Development/Her-CyberTracks.aspx?utm_source=chatgpt.com] The useful lesson for workforce planning is simple: talent development needs an ecosystem around the learner. TRAINING GETS PEOPLE STARTED. MENTORSHIP HELPS THEM STAY. A cybersecurity course can teach someone how incident response works. It can’t automatically show them what a career in incident response

ITSEC AsiaITSEC Asia
|
Okt 09, 2026 — 3 minutes read

Receive weekly
updates on new posts

Subscribe