Cloud security incidents now affect 80% of organizations every year. If your business runs cloud-connected systems, from data infrastructure to access control and surveillance cameras, you’re likely already inside that statistic. Here’s what the latest cloud security statistics actually tell you, and what to do about it.
Key Takeaways
- 80% of companies experienced a cloud security breach in the past year — making cloud incidents routine rather than exceptional.
- Misconfigurations remain the primary driver of cloud security breaches, and Gartner estimates that 99% of cloud failures stem from customer error rather than provider shortcomings.
- The average US data breach now costs $10.22 million, nearly 2.3x the global average of $4.44 million.
- Only 8% of organizations encrypt 80% or more of their cloud data, despite 54% of cloud-stored data being classified as sensitive.
- Shadow AI adds $670,000 in additional breach costs per incident—and most security budgets don’t account for them.
- Cloud-connected physical security systems — cameras, access control, intercoms — are now part of your cloud attack surface, a gap that most cloud security statistics roundups ignore entirely.
What Do the Cloud Security Statistics Say: Data, Insights, & Market Size
Most organizations no longer ask whether to use the cloud — they’re already in it. The question now is whether their cloud security strategy has kept pace.
1. The global cloud security market is on track to reach $148.3 billion by 2032
It was valued at $20.54 billion in 2022 (Exabeam). That’s a nearly 7x increase in a decade — driven by the scale of cloud adoption and the cost of securing it.
2. Breach rates have remained near-universal despite rising security budgets
Global cloud security budgets are projected to cross $40 billion in 2025. Yet 80% of organizations still experienced a breach in the past year. More spending isn’t the same as more protection.
3. Cloud Security Data Snapshot
| Metric | Statistic | Source |
|---|---|---|
| Companies experiencing a cloud breach (past year) | 80% | Spacelift, 2026 |
| Organizations in hybrid/multi-cloud environments | 88% | Fortinet, 2026 |
| Cloud breaches involving human error (misconfigurations) | 82% | SentinelOne |
| Average global data breach cost | $4.44 million | IBM, 2025 |
| Average US data breach cost | $10.22 million | IBM, 2025 |
| Organizations lacking AI governance policies | 63% | IBM, 2025 |
| Cloud data that is classified as sensitive | 54% | Thales, 2025 |
| Organizations encrypting 80%+ of cloud data | 8% | Thales, 2025 |
| Average breach detection + containment time | 241 days | IBM, 2025 |
| Cloud security market projected value by 2032 | $148.3 billion | Exabeam |
How Common Are Cloud Security Breaches?
Cloud security breaches are no longer exceptional events. They are now the baseline risk for any organization running cloud infrastructure.
4. 80% of companies experienced a serious cloud security incident in the past year
That’s according to Spacelift/SentinelOne. Over a rolling 18-month window, 83% of organizations encountered at least one breach or incident. More than 60% reported security incidents specifically tied to public cloud usage in 2024, a figure that increased 10% year-over-year.
5. Cloud intrusion attempts jumped 75% from 2022 to 2023
By Q1 2025, organizations were facing approximately 1,925 cyber attacks per week (SentinelOne). Attack frequency shows no sign of slowing — 71% of business leaders reported a high rise in attack frequency in 2025-2026.
6. 45% of all data breaches now occur in cloud environments
That makes cloud the dominant breach category globally. This reflects both the concentration of high-value data in cloud systems and the security maturity gap many organizations carry into the cloud.
7. 88% of government agencies cite cloud misconfiguration as their top security concern
Healthcare, finance, and government are consistently the highest-impact sectors (Exabeam). This is particularly relevant for organizations working under SLED (State, Local, and Education) contracts, where cloud security failures carry not just financial consequences but regulatory and procurement implications.
8. Healthcare has averaged $7.42 million per breach for 14 consecutive years
Despite a 24% year-over-year cost reduction, healthcare remains the most heavily impacted industry (IBM, 2025). No industry is insulated, but healthcare, financial services, and government carry the highest per-incident costs.
What Does a Cloud Security Breach Cost and Its Financial Impact?
The headline breach cost figures are well-known. The layered picture is more important.
9. The global average data breach cost fell to $4.44 million in 2025
That’s the first decline in five years, driven largely by faster AI-assisted threat detection (IBM, 2025). That progress, however, is unevenly distributed across geographies.
10. The average US breach cost hit a record $10.22 million in 2025
That’s nearly 2.3x the global average. US organizations are moving in the opposite direction from the global trend, driven by steeper regulatory fines and escalating detection costs (IBM/CyberScoop, 2025).
11. Multi-environment breaches are the most expensive, averaging $5.05 million
The type of cloud environment significantly affects breach cost:
| Storage Environment | Average Breach Cost | Average Detection Time |
|---|---|---|
| On-premises only | $4.01 million | 217 days |
| Public cloud | $4.18 million | 251 days |
| Private cloud | $4.68 million | 247 days |
| Multi-environment (public + private + on-premises) | $5.05 million | 276 days |
Every additional environment adds both cost and time to the detection of a breach. Multi-environment breaches are both the most expensive and the hardest to see.
12. Recovery after containment averages 100+ days
The headline breach cost figure understates total damage. Nearly two-thirds of breached organizations were still recovering at the time of IBM’s 2025 annual report — meaning the financial and operational impact extends well beyond initial detection.
13. Shadow AI adds $670,000 in additional breach costs per incident
Organizations using unsanctioned AI tools face compounding exposure: 65% of shadow AI breaches result in compromised PII, compared to 53% in standard incidents (IBM, 2025). Most security budgets don’t account for this category at all.
14. 32% of cloud assets sit idle and unmonitored
Each neglected asset carries an average of 115 unresolved vulnerabilities (Orca Security, 2025). These forgotten resources — often running outdated operating systems — become entry points that organizations haven’t budgeted to address.
15. AI and automation can save organizations $1.9 million per breach
IBM’s 2025 data found that organizations that extensively use AI and automation in their security operations also reduced their breach lifecycle by 80 days. Technical controls, not training programs, are what actually move the needle.
How Does Multi-Cloud and Hybrid Cloud Adoption Affect Security?
88% of organizations now operate in hybrid or multi-cloud environments (Fortinet, 2026). Multi-cloud is no longer a strategic choice for most — it’s the operational baseline. And it creates cloud security challenges that single-environment thinking doesn’t solve.
16. 56% of organizations struggle to secure data consistently across multi-cloud environments
69% can’t maintain uniform security controls across cloud service providers (Exabeam). Every additional cloud introduces configuration variance, visibility gaps, and the potential for policy drift that compounds misconfiguration risk.
17. Only 42% of cloud engineers believe they own cloud security, but only 19% of security teams agree
That accountability gap (Exabeam) is where misconfigurations proliferate undetected. When neither group fully owns the security posture, vulnerabilities fall through the cracks between teams.
18. 79% of organizations use more than one cloud provider
This directly multiplies misconfiguration risk. Each provider has different default settings, different IAM models, and different compliance requirements. Managing them consistently requires deliberate policy architecture that most lean security teams don’t have the capacity to maintain manually.
19. Poorly configured network infrastructure amplifies every cloud security vulnerability above it
Network infrastructure is the foundation on which cloud environments run. Inadequate segmentation, weak edge access controls, and unmonitored lateral movement paths all increase exposure. Understanding how enterprise network security intersects with cloud security posture is increasingly important as cloud computing continues to expand.
What Are the Biggest Cloud Security Breaches on Record?
Real-world breach cases illustrate the pattern: most large-scale cloud failures aren’t the result of sophisticated zero-day exploits. They’re misconfigurations, credential theft, and third-party access failures.
20. Capital One (2019) — 100M+ records exposed via misconfigured S3 bucket
A former AWS employee exploited default public access settings to access personal information, credit scores, and banking details for over 100 million customers. Capital One paid over $150 million in fines and settlements. The root cause wasn’t a sophisticated attack — it was a configuration default that was never changed.
21. Toyota (2023) — 260,000 customer records exposed through human error alone
Toyota misconfigured a cloud environment, exposing customer data with no external attack involved. It was a pure human error in the setup process — exactly the scenario Gartner projects accounts for 99% of cloud security failures.
22. Marks & Spencer (2025) — £300M+ in losses from a third-party credential compromise
A vendor credential compromise resulted in estimated losses of £300 million, operational shutdowns, and months of disrupted cloud services. The breach underscored how third-party access to cloud systems creates indirect exposure that internal security measures alone can’t cover.
23. AT&T (2024) — 73M records exposed through a third-party cloud service provider
Stolen credentials gave attackers access to a third-party cloud service provider, exposing 73 million customer records, including social security numbers, business financial records, and account data. The breach originated entirely outside AT&T’s direct infrastructure.
These cases reinforce the same pattern: identity and access management failures, cloud misconfigurations, and third-party vulnerabilities are the root causes—not exotic attacks.
What Are the Most Exploited Cloud Vulnerabilities and Misconfigurations?
Security researchers and incident responders consistently document the same configuration gaps across security breaches:
24. Overpermissive IAM policies are the most common entry point
Identity and access management gaps mean more than half of global organizations don’t have sufficient restrictions placed on privileged accounts. Once attackers obtain any valid credential, overpermissive access lets them move laterally through the environment without triggering alerts.
25. Exposed access keys and API credentials are weaponized within hours
Threat actors scan for exposed keys in code repositories, CI/CD pipelines, and public cloud storage services within hours of exposure. Static, long-lived access keys are particularly dangerous — rotating to short-lived credentials with IP restrictions significantly reduces this risk. Properly managing encryption keys is equally critical, as exposed cryptographic credentials can give attackers access to otherwise-protected data in the cloud.
26. Missing alert configurations leave defenders blind
Most CSPM tools and cloud providers generate alerts for misconfiguration and anomalous activity. But alert fatigue and disconnected tooling mean many defenders never see these signals until after a breach occurs — a fixable gap that requires deliberate configuration, not additional software.
27. 9% of publicly accessible cloud storage services contain sensitive data
That’s according to Tenable’s 2025 Cloud Security Risk Report. That’s a fraction of total cloud storage — but the scale of cloud computing makes the absolute number enormous. Publicly exposed storage buckets remain one of the most widespread and preventable vulnerabilities.
28. 32% of cloud infrastructure sits idle and unmonitored — with 115 vulnerabilities per asset
Each neglected asset carries an average of 115 unresolved vulnerabilities (Orca Security, 2025). These assets often run outdated operating systems, go unpatched for 6 months or more, and remain outside the visibility of security teams.
29. Proper network installation reduces the configuration drift that attackers exploit
The professional network installation process matters here. When network infrastructure is properly documented, consistently configured, and systematically maintained, the underlying environment that cloud services run on is far less likely to harbor the vulnerabilities that enable lateral movement.
What Security Risks Come With Cloud Services and Cloud Storage?
Cloud storage risks often live in two categories that are easy to underestimate: sensitive data exposure and physical security systems as cloud endpoints.
30. 54% of data stored in the cloud is classified as sensitive, but only 8% of organizations encrypt it adequately
That’s up from 47% the prior year (Thales, 2025). Despite that, only 8% of organizations encrypt 80% or more of their cloud data. Encrypting data at rest and in transit remains one of the most underpracticed security measures in cloud environments.
31. Cloud-connected physical security systems are an underappreciated attack surface
Surveillance cameras, cloud access control systems, and intercoms are now endpoint devices within an organization’s cloud environment. Each one is a potential entry point if not properly configured and maintained. Edge devices such as cameras and IoT sensors are identified as emerging cyber threats in 2025 security trend reports.
32. A breach in the cloud layer can compromise physical access integrity
For organizations operating cloud-based access control systems, such as those managing credential issuance, door access, and audit trails, the security posture of the cloud platform directly affects the physical security integrity. A breach can expose access logs, disable entry controls, or allow credential manipulation. This is why evaluating the cybersecurity architecture of cloud security solutions, not just their hardware, matters.
Understanding enterprise security architecture in the context of cloud-connected physical systems is increasingly relevant for facility managers and IT directors making vendor selection decisions.
How Are Organizations Approaching Cloud Security Audits and Compliance?
Cloud security audits are standard practice in regulated industries, but the data suggests compliance frameworks often lag the threat environment.
33. 54% of organizations struggle with consistent compliance across cloud environments
Multi-cloud complexity means policies enforced in one environment may not transfer to another (Exabeam) — a particular challenge in hybrid cloud environments where on-premises and cloud infrastructure interact. Each cloud service provider has its own compliance tooling and default configurations.
34. NDAA compliance extends to the cloud infrastructure underlying security hardware
For SLED organizations, compliance requirements carry unique weight. NDAA (National Defense Authorization Act) compliance restricts the use of certain foreign-manufactured security equipment in government-funded facilities. Cloud-connected security systems fall within this framework — meaning the cloud infrastructure underlying a camera or access control system must meet the same compliance standards as the hardware itself.
35. 88% of government agencies cite cloud misconfiguration as their top security concern
Agencies operating under procurement vehicles like CMAS, PEPPM, or GSA Schedules face added scrutiny, where a documented security failure can affect contract standing (Exabeam). This makes misconfiguration prevention a procurement risk, not just a technical one.
36. Cloud security audits should prioritize these five areas
Organizations conducting cloud security audits should focus on: IAM policy review, API access logging, encryption posture, third-party vendor access controls, and completeness of asset inventory — including decommissioning neglected cloud resources that often carry the highest unresolved vulnerability counts.
Which Industries Are Most Vulnerable to Cloud Security Breaches?
No industry is immune, but exposure levels and financial impact vary significantly based on data sensitivity, regulatory environment, and cloud adoption maturity.
| Industry | Avg. Breach Cost | Primary Risk Drivers |
|---|---|---|
| Healthcare | $7.42 million | PHI exposure, HIPAA fines, high cloud adoption |
| Financial Services | $6.1 million | PII and financial records, PCI DSS, and regulatory fines |
| Government/Public Sector | $2.6 million (direct) + significant indirect costs | Misconfiguration, NDAA compliance exposure, procurement risk |
| Education | Rising | Weak IAM, underfunded security teams, and student records |
| Retail/Ecommerce | $3.5 million | Payment data, high transaction volume, third-party integrations |
| Media/Utilities | High | Access-related vulnerabilities are behind 83% of breaches in these sectors (IDC/Ermetic) |
| Technology | Elevated | IP theft at $178/record; AI-related breach exposure |
Healthcare has topped the IBM breach cost rankings for 14 consecutive years. Government and education buyers face an added layer of risk: cloud security failures can jeopardize business continuity and procurement standing under programs like CMAS, PEPPM, and GSA Schedules — consequences that go beyond financial damage to operations.
What Are the Most Common Cloud Security Threats?
Phishing and Credential Theft
Phishing remains the dominant initial access vector. 69% of organizations experienced phishing-based identity security incidents in 2024 (Exabeam). Credential theft and stolen secrets are now the fastest-growing cloud infrastructure attack tactics, cited by 68% of security professionals (Thales, 2025).
Leaked credentials were the initial access point in 65% of cloud breaches analyzed by RSAC researchers (2025). Once attackers have valid credentials, they often walk through open doors created by cloud misconfigurations rather than needing to force their way in.
AI is accelerating this threat. AI-driven phishing is projected to account for more than 42% of all global intrusions by the end of 2026 (SentinelOne). Deepfake-based social engineering — voice cloning and synthetic impersonation — is now operationally viable and increasingly used in targeted attacks on organizations with high-value cloud access.
Misconfiguration
Misconfiguration is both the most common and most preventable cloud security failure. 23% of cloud security incidents stem directly from misconfigurations (SentinelOne/IBM). 82% of those misconfigurations are caused by human error, not software flaws (SentinelOne).
The most common forms include: IAM misconfigurations with over-permissive access, insecure API keys, publicly exposed storage buckets, unencrypted backups, and missing alert configurations. Each creates an entry point that can sit dormant for months before discovery.
72% of cloud environments have publicly exposed PaaS databases lacking sufficient access controls (Wiz, 2025). Most organizations do not discover this exposure until after a breach.
Ransomware
Ransomware has followed data into the cloud. Cloud intrusion attempts tied to ransomware activity jumped significantly in 2024-2025, with over 2,200 ransomware incidents globally in Q1 2025 alone (SentinelOne).
Ransomware attacks now cost an average of $5.08 million per incident — higher than the global average breach cost — because of combined data loss, operational disruption, and ransom negotiation overhead (IBM, 2025). The number of organizations refusing to pay ransoms grew from 59% to 63% year-over-year, but that does not reduce the recovery burden.
API and Application Vulnerabilities
APIs are the connective tissue of cloud infrastructure. 31% of cloud data breaches involve API exploitation (SentinelOne, 2026). Broken authentication, excessive permissions, and missing rate limiting make APIs prime targets — particularly in multi-cloud environments, where API traffic is difficult to monitor across cloud service providers consistently.
62% of organizations using cloud AI services have at least one vulnerable AI package, and 93% have at least one privileged Kubernetes service account (Orca Security, 2025). As AI workloads expand, the API attack surface grows with them.
What Is Zero Trust Security?
Zero Trust is a security model built on the principle of “never trust, always verify.” Rather than assuming that anything within the network perimeter is safe, a zero-trust security architecture requires continuous verification of identity, context, and device posture for every access request — regardless of its origin.
Why Does It Matter for the Cloud?
In traditional on-premises environments, the network perimeter was a meaningful security boundary. In cloud and hybrid environments, that perimeter does not exist in the same way. Users, devices, and applications access resources from anywhere, across multiple providers, often through third-party integrations.
81% of organizations have fully or partially implemented a Zero Trust model (TechMagic, 2025). Adoption is accelerating because it directly addresses the identity and access failures that sit behind most cloud breaches.
For government and SLED buyers, Zero Trust aligns with federal security mandates and is increasingly expected in infrastructure assessments. Cloud access control systems with built-in MFA, role-based access, and audit trail capabilities — like those from Brivo — provide a practical Zero Trust layer for physical access environments.
How Does Network Infrastructure Affect Cloud Security?
Cloud security does not exist in isolation. The physical network infrastructure carrying data between on-premises environments and cloud services is part of the attack surface.
Improperly configured network infrastructure increases cloud exposure in several specific ways:
- Weak network segmentation allows lateral movement between zones that should be isolated from one another.
- Unmonitored network access points create blind spots where cloud credentials can be captured.
- Poor documentation of physical network topology makes it harder to trace unauthorized access paths.
- Outdated cabling and switching infrastructure can limit the ability to implement modern security controls, such as network access control (NAC) or traffic inspection.
Cross-environment breaches — spanning physical network, private cloud, and public cloud infrastructure — average $5.05 million and take 276 days to detect (IBM, 2025). The longer detection time correlates directly with reduced visibility across the full path data travels.
Professional network installation benefits include structured documentation, standardized configurations, and compliance-ready infrastructure — all of which simplify both security enforcement and audit processes. When network infrastructure is installed correctly from the ground up, it creates a more defensible environment for the cloud services running on top of it.
For organizations running government facility network infrastructure, this layered approach to security — from physical cabling through cloud configuration — is particularly relevant given the compliance requirements involved.
What New Cloud Security Threats Should Organizations Watch For?
AI-Powered Attacks
AI is improving both sides of the security equation — but attackers are moving fast. 16% of breaches in 2025 involved attackers using AI tools, primarily for phishing campaigns and deepfake impersonation (IBM, 2025).
AI-driven phishing is becoming more convincing and harder to detect through traditional indicators. Voice cloning and synthetic video are being used to impersonate executives and IT personnel, bypassing human judgment checks that organizations have historically relied on. Deepfake-related unpreparedness among C-suite security leaders jumped from 6% to 28% between 2024 and 2025 (Viking Cloud).
Shadow AI and Ungoverned AI Systems
Shadow AI — AI tools adopted by employees without IT or security approval — was a factor in 20% of breaches studied in IBM’s 2025 report. Breaches involving shadow AI carried an additional $670,000 in average costs.
63% of breached organizations lacked AI governance policies. Among those with policies, fewer than half had approval processes for AI deployments, and 61% lacked technology to enforce them (IBM, 2025). The governance gap is where shadow AI thrives: employees adopting AI tools that process sensitive data, with no visibility into what is uploaded or how it is retained.
Post-Quantum Encryption
Quantum computing represents a forward-looking threat to current encryption standards. While large-scale quantum attacks on production systems are not yet operational, the security community is already preparing. CISA has published post-quantum security guidance for federal agencies, and forward-looking cloud security architectures are beginning to incorporate quantum-resistant cryptographic standards.
Supply Chain Attacks
Third-party integrations, SaaS vendors, and open-source components introduce indirect cyber threats that organizations cannot control solely through their own security controls. The Marks & Spencer breach in 2025 traced back to a third-party vendor whose credentials were compromised. The SolarWinds-pattern attack method — compromising software that trusted parties deploy — remains a high-threat vector.
30% of data breaches involve data distributed across multiple environments, often due to supply chain and third-party exposure (IBM, 2025). Organizations need vendor access controls, third-party security assessments, and monitoring of API integrations to limit exposure from partners and software vendors.
Also read:
- Warehouse Automation Statistics
- Data Center Construction Statistics
- Video Conferencing Statistics IT Directors Need to Know
FAQs
How do cloud security statistics differ between public and private cloud deployments?
Cloud deployments are more frequently targeted but are cheaper to breach. 27% of organizations using public cloud services experienced a security incident in 2024 — up 10% year-over-year. Public cloud breaches average $4.18 million and take approximately 251 days to detect and contain.
Private cloud breaches are less frequent but more expensive: $4.68 million on average, with a 247-day detection timeline. The additional cost reflects the complexity of private cloud environments, which often involve more customization and less standardized tooling.
The most expensive scenario is multi-environment deployment — combining public cloud, private cloud, and on-premises systems. These breaches average $5.05 million and take 276 days to detect and contain, the longest timeline of any configuration (IBM, 2025).
The practical implication: complexity is the most reliable predictor of breach cost and detection difficulty. Every environment added requires deliberate cloud security posture management to prevent it from becoming a blind spot.
How often do cloud attacks occur globally?
Attack volume is accelerating across every metric. In Q1 2025, organizations faced approximately 1,925 attacks per week — roughly 275 attacks per day (SentinelOne). Globally, there were over 2,200 ransomware incidents in Q1 2025 alone.
Cloud infrastructure attacks are climbing 21% year-over-year, with identity breaches and misconfigurations accounting for the largest share. Nearly three-quarters (71%) of business leaders observed a significant rise in cyberattacks during 2025–2026, and 66% of security leaders admitted they are not confident in their real-time cloud threat detection and response capabilities (SentinelOne, 2026).
The mean time to identify and contain a breach is 241 days — a 9-year low, driven by improved AI detection tools. However, that still represents nearly eight months of potential exposure. Organizations that do not use continuous monitoring are operating with a significant detection gap.
How does NDAA compliance intersect with cloud security for government buyers?
The NDAA (National Defense Authorization Act) restricts the use of security equipment from certain foreign manufacturers in federal facilities and federally funded projects. This restriction applies not only to physical hardware but also to the cloud infrastructure that underlies it.
For government and SLED buyers, this means evaluating cloud security vendors requires assessing both the device and the platform. A cloud-managed access control or surveillance system from an NDAA-compliant manufacturer — like Verkada or Brivo — provides regulatory compliance and a security architecture in which the cloud backend is managed by the vendor, reducing the customer-side misconfiguration risk, which accounts for 99% of cloud failures (Gartner).
Organizations pursuing government contracts under CMAS, PEPPM, or GSA Schedules should treat NDAA compliance as a cloud security criterion, not just a hardware procurement checkbox.
In Summary
Recent cloud security statistics paint a consistent picture: breaches are near universal, most are preventable, and the cost of inaction is rising faster in the US than anywhere else in the world. The most dangerous threats are not sophisticated zero-day exploits — they are misconfigured buckets, overpermissive access policies, and forgotten cloud assets running 115 unresolved vulnerabilities each.
The organizations doing best are those using AI-assisted detection tools, implementing a zero-trust security architecture incrementally, choosing cloud vendors that assume greater security responsibility on their end, and building on network infrastructure that was designed and documented correctly from the start.
For businesses running cloud-connected security systems — cameras, access control, intercoms — the cloud security posture of your vendor selection is part of your security strategy. Choosing NDAA-compliant, vendor-managed platforms reduces your exposure on the side of the equation that matters most: the customer-controlled configuration layer, where most data breaches originate.
If you are evaluating your cloud security infrastructure or need professionally installed, properly configured network and security systems, contact us to discuss your project.
References
- https://www.ibm.com/reports/data-breach
- https://www.fortinet.com/resources/reports/cloud-security
- https://orca.security/lp/2025-state-of-cloud-security-report/
- https://cpl.thalesgroup.com/cloud-security-research
- https://www.sentinelone.com/cybersecurity-101/cloud-security/cloud-security-statistics/
- https://spacelift.io/blog/cloud-security-statistics
- https://www.exabeam.com/explainers/cloud-security/61-cloud-security-statistics-you-must-know-in-2025/
- https://www.rsaconference.com/library/blog/cloud-misconfigurations-still-the-biggest-threat-in-2025
- https://www.wiz.io/reports/cloud-data-security-report-2025
- https://www.kiteworks.com/cybersecurity-risk-management/ibm-2025-data-breach-report-ai-risks/
