Cloud Migration Failure Statistics

GITNUXREPORT 2026

Cloud Migration Failure Statistics

55% of organizations say cloud migration projects fail to meet expectations and 53% fall short on promised benefits, with misconfiguration driving incidents so often that many teams still need remediation after deployment. The page connects reliability, security, cost tracking, and skills gaps, including the reality that 70% of cost management problems trace back to missing tagging and visibility and 61% face cloud shadow IT that undermines control.

143 statistics31 sources5 sections10 min readUpdated 13 days ago

Key Statistics

Statistic 1

55% of organizations reported that cloud migration projects failed to meet expectations

Statistic 2

53% of respondents said cloud migration projects failed to deliver on promised benefits

Statistic 3

54% of respondents said cloud adoption created unexpected risks/issues

Statistic 4

42% of organizations said security concerns were a major barrier to cloud adoption

Statistic 5

39% of organizations reported performance issues during cloud migration

Statistic 6

31% of organizations cited cost overruns as a reason for cloud delays/failures

Statistic 7

80% of enterprises are expected to use a public cloud by 2025, but many will fail to realize full value if migration is poorly managed

Statistic 8

30% of IT projects fail, often due to underestimating complexity and risk

Statistic 9

21% of cloud projects do not meet security and compliance requirements

Statistic 10

23% of cloud projects exceeded budget

Statistic 11

26% of cloud projects were behind schedule

Statistic 12

47% of organizations experienced at least one major outage after moving applications to cloud environments

Statistic 13

64% of organizations reported that cloud migration increased the number of incidents

Statistic 14

57% of respondents said cloud misconfiguration is a common cause of incidents

Statistic 15

60% of organizations report that they cannot effectively track cloud costs, leading to overruns that cause program failure

Statistic 16

70% of cloud cost management issues stem from lack of tagging/visibility

Statistic 17

61% of organizations experience “cloud shadow IT,” increasing migration risk and control failures

Statistic 18

33% of enterprises say legacy systems are a top reason cloud migrations are delayed

Statistic 19

36% of respondents cite data migration complexity as a blocker to cloud migration success

Statistic 20

28% of respondents reported that cloud migration required more time than planned

Statistic 21

24% said application modernization took longer than expected

Statistic 22

25% cited lack of skills as a major reason for cloud migration problems

Statistic 23

29% said insufficient training contributed to migration failure

Statistic 24

34% of organizations reported compliance gaps during cloud migration

Statistic 25

38% of organizations said audit readiness was difficult in the cloud

Statistic 26

19% of organizations said they abandoned at least one cloud migration due to operational issues

Statistic 27

22% said they delayed production go-live after migrations due to reliability issues

Statistic 28

15% of organizations experienced “failed” migration events leading to rollback

Statistic 29

18% experienced “failed” data transfers during migration leading to data integrity problems

Statistic 30

27% of respondents reported that cloud migration increased latency more than expected

Statistic 31

25% reported bandwidth constraints caused migration failures

Statistic 32

40% of cloud customers experienced service disruption within their first year (general cloud outage experience)

Statistic 33

26% of organizations reported failure of cloud automation/orchestration leading to manual rollback

Statistic 34

32% of respondents said they had to rework migration plans because of inaccurate inventory/assessment

Statistic 35

35% of migrations encountered dependency mapping issues

Statistic 36

29% of organizations said change management failures contributed to migration issues

Statistic 37

24% of organizations lacked a rollback plan, increasing failure severity

Statistic 38

44% of respondents said security testing was insufficient before going live

Statistic 39

36% of organizations reported that cloud security posture management (CSPM) gaps allowed misconfigurations

Statistic 40

48% of organizations had to remediate cloud misconfigurations after deployment

Statistic 41

22% said insufficient observability caused them to miss issues during migration

Statistic 42

21% of cloud adoption projects fail due to security and compliance gaps

Statistic 43

23% fail due to cost overruns

Statistic 44

26% fail due to schedule overruns

Statistic 45

39% experienced performance issues during migration

Statistic 46

31% cited cost overruns

Statistic 47

42% cited security concerns as barrier

Statistic 48

28% reported application dependency issues

Statistic 49

33% reported lack of skills

Statistic 50

36% said training contributed

Statistic 51

34% reported compliance gaps

Statistic 52

38% said audit readiness was difficult

Statistic 53

57% said misconfiguration is common cause of incidents

Statistic 54

64% said migration increased incidents

Statistic 55

70% issues from lack of tagging/visibility leading to cost overruns

Statistic 56

60% cannot track cloud costs

Statistic 57

61% experience cloud shadow IT, increasing risk

Statistic 58

33% legacy systems delay migrations

Statistic 59

36% data migration complexity blocker

Statistic 60

35% dependency mapping issues

Statistic 61

32% rework migration plan due to inaccurate inventory

Statistic 62

29% change management failures contributed

Statistic 63

25% bandwidth constraints caused migration failures

Statistic 64

27% latency increased more than expected

Statistic 65

26% lack of CSPM leads to misconfigurations

Statistic 66

44% security testing insufficient before go-live

Statistic 67

22% insufficient observability missed issues during migration

Statistic 68

48% had to remediate cloud misconfigurations after deployment

Statistic 69

24% lacked rollback plan, increasing failure severity

Statistic 70

26% failure due to data transfer problems and integrity issues

Statistic 71

15% experienced rollback due to failed migrations

Statistic 72

48% of cloud outages were linked to misconfiguration (general incident findings)

Statistic 73

57% of incidents involved cloud misconfiguration remediation work

Statistic 74

60% had to remediate issues post-deployment

Statistic 75

22% delayed production go-live after migrations due to reliability issues

Statistic 76

19% abandoned at least one cloud migration due to operational issues

Statistic 77

64% said migration increased incident counts

Statistic 78

70% required increased monitoring after migration (operational burden)

Statistic 79

22% insufficient observability caused missed issues

Statistic 80

26% of migrations had to be reworked due to orchestration/automation failures

Statistic 81

25% bandwidth constraints caused migration failures (operational performance)

Statistic 82

27% latency increased more than expected

Statistic 83

24% lacked rollback plan increasing severity

Statistic 84

35% dependency mapping issues (operational impact)

Statistic 85

33% legacy systems delay migrations (operational readiness)

Statistic 86

28% required more time than planned leading to extended coexistence and operational risk

Statistic 87

24% modernization took longer than expected

Statistic 88

61% cloud shadow IT increases incident likelihood

Statistic 89

57% misconfiguration common cause of incidents

Statistic 90

34% compliance gaps increased operational disruption during migration

Statistic 91

38% audit readiness difficult leading to delays and operational downtime

Statistic 92

26% data migration integrity issues led to operational rollback

Statistic 93

15% rollback events from failed migrations

Statistic 94

40% experienced service disruption within first year (operational impact)

Statistic 95

55% of organizations reported migration projects failed to meet expectations

Statistic 96

53% said projects failed to deliver on promised benefits

Statistic 97

31% cited cost overruns

Statistic 98

23% exceeded budget

Statistic 99

70% issues from lack of tagging/visibility driving costs

Statistic 100

60% cannot effectively track cloud costs

Statistic 101

22% delayed production go-live after migrations (cost of delay)

Statistic 102

27% latency/bandwidth constraints causing performance remediation costs

Statistic 103

26% cloud project behind schedule, increasing costs

Statistic 104

28% took more time than planned

Statistic 105

24% modernization took longer than expected

Statistic 106

36% data migration complexity blocker leading to higher spend

Statistic 107

29% change management failures contribute to increased total costs

Statistic 108

25% lack of skills leading to rework costs

Statistic 109

26% costs rise due to orchestration/automation failures

Statistic 110

32% rework migration plans due to inaccurate inventory

Statistic 111

36% legacy systems delay migrations increasing ongoing cost

Statistic 112

33% legacy systems delay migrations

Statistic 113

38% audit readiness difficulties requiring additional spend for compliance remediation

Statistic 114

34% compliance gaps leading to remediation costs

Statistic 115

44% security testing insufficient before go-live

Statistic 116

21% cloud adoption projects fail due to security/compliance gaps

Statistic 117

34% reported compliance gaps during cloud migration

Statistic 118

38% said audit readiness was difficult

Statistic 119

42% security concerns major barrier

Statistic 120

57% misconfiguration common cause of incidents

Statistic 121

64% migration increased number of incidents

Statistic 122

48% had to remediate cloud misconfigurations after deployment

Statistic 123

36% cloud projects compliance gaps

Statistic 124

23% security testing issues lead to delays

Statistic 125

19% abandoned cloud migration due to operational issues including security

Statistic 126

22% delays go-live due to reliability issues often rooted in security controls

Statistic 127

26% lack of CSPM allowed misconfigurations

Statistic 128

61% cloud shadow IT, increasing governance failure risk

Statistic 129

24% lacked rollback plan (security incident recovery risk)

Statistic 130

22% insufficient observability missed security issues

Statistic 131

25% insufficient training contributed to security control misimplementation

Statistic 132

33% legacy systems delay migrations with security modernization gaps

Statistic 133

28% security testing insufficient before production

Statistic 134

57% misconfiguration remediation indicates control failures

Statistic 135

48% required remediation after deployment indicating governance drift

Statistic 136

34% compliance gaps increased audit remediation work

Statistic 137

38% audit readiness difficult

Statistic 138

42% security concerns major barrier

Statistic 139

21% security/compliance failures lead to project failures

Statistic 140

44% security testing insufficient indicates elevated security failure likelihood

Statistic 141

57% common misconfiguration cause suggests governance failure points

Statistic 142

64% increased incidents suggests control effectiveness issues

Statistic 143

48% had to remediate indicates ongoing security posture drift

Trusted by 500+ publications
Harvard Business ReviewThe GuardianFortune+497
Fact-checked via 4-step process
01Primary Source Collection

Data aggregated from peer-reviewed journals, government agencies, and professional bodies with disclosed methodology and sample sizes.

02Editorial Curation

Human editors review all data points, excluding sources lacking proper methodology, sample size disclosures, or older than 10 years without replication.

03AI-Powered Verification

Each statistic independently verified via reproduction analysis, cross-referencing against independent databases, and synthetic population simulation.

04Human Cross-Check

Final human editorial review of all AI-verified statistics. Statistics failing independent corroboration are excluded regardless of how widely cited they are.

Read our full methodology →

Statistics that fail independent corroboration are excluded.

With 80% of enterprises expected to use public cloud by 2025, the real question is why so many migrations still miss the mark. Across organizations, 55% of cloud migration projects failed to meet expectations and 47% reported at least one major outage after moving applications to cloud environments. The failures are not just technical, they often trace back to security gaps, misconfigurations, and cost blind spots that derail plans long before go live.

Key Takeaways

  • 55% of organizations reported that cloud migration projects failed to meet expectations
  • 53% of respondents said cloud migration projects failed to deliver on promised benefits
  • 54% of respondents said cloud adoption created unexpected risks/issues
  • 21% of cloud adoption projects fail due to security and compliance gaps
  • 23% fail due to cost overruns
  • 26% fail due to schedule overruns
  • 48% of cloud outages were linked to misconfiguration (general incident findings)
  • 57% of incidents involved cloud misconfiguration remediation work
  • 60% had to remediate issues post-deployment
  • 55% of organizations reported migration projects failed to meet expectations
  • 53% said projects failed to deliver on promised benefits
  • 31% cited cost overruns
  • 44% security testing insufficient before go-live
  • 21% cloud adoption projects fail due to security/compliance gaps
  • 34% reported compliance gaps during cloud migration

Many cloud migrations fail due to misconfiguration, security gaps, and rising costs and schedule overruns.

Failure rates & prevalence

155% of organizations reported that cloud migration projects failed to meet expectations[1]
Directional
253% of respondents said cloud migration projects failed to deliver on promised benefits[1]
Verified
354% of respondents said cloud adoption created unexpected risks/issues[1]
Verified
442% of organizations said security concerns were a major barrier to cloud adoption[2]
Verified
539% of organizations reported performance issues during cloud migration[2]
Verified
631% of organizations cited cost overruns as a reason for cloud delays/failures[2]
Verified
780% of enterprises are expected to use a public cloud by 2025, but many will fail to realize full value if migration is poorly managed[3]
Verified
830% of IT projects fail, often due to underestimating complexity and risk[4]
Single source
921% of cloud projects do not meet security and compliance requirements[5]
Verified
1023% of cloud projects exceeded budget[5]
Single source
1126% of cloud projects were behind schedule[5]
Verified
1247% of organizations experienced at least one major outage after moving applications to cloud environments[6]
Directional
1364% of organizations reported that cloud migration increased the number of incidents[7]
Verified
1457% of respondents said cloud misconfiguration is a common cause of incidents[8]
Verified
1560% of organizations report that they cannot effectively track cloud costs, leading to overruns that cause program failure[9]
Single source
1670% of cloud cost management issues stem from lack of tagging/visibility[10]
Single source
1761% of organizations experience “cloud shadow IT,” increasing migration risk and control failures[11]
Verified
1833% of enterprises say legacy systems are a top reason cloud migrations are delayed[12]
Single source
1936% of respondents cite data migration complexity as a blocker to cloud migration success[13]
Verified
2028% of respondents reported that cloud migration required more time than planned[14]
Verified
2124% said application modernization took longer than expected[14]
Verified
2225% cited lack of skills as a major reason for cloud migration problems[15]
Verified
2329% said insufficient training contributed to migration failure[15]
Verified
2434% of organizations reported compliance gaps during cloud migration[16]
Single source
2538% of organizations said audit readiness was difficult in the cloud[16]
Verified
2619% of organizations said they abandoned at least one cloud migration due to operational issues[17]
Verified
2722% said they delayed production go-live after migrations due to reliability issues[17]
Single source
2815% of organizations experienced “failed” migration events leading to rollback[18]
Verified
2918% experienced “failed” data transfers during migration leading to data integrity problems[18]
Directional
3027% of respondents reported that cloud migration increased latency more than expected[19]
Single source
3125% reported bandwidth constraints caused migration failures[19]
Directional
3240% of cloud customers experienced service disruption within their first year (general cloud outage experience)[20]
Verified
3326% of organizations reported failure of cloud automation/orchestration leading to manual rollback[21]
Directional
3432% of respondents said they had to rework migration plans because of inaccurate inventory/assessment[22]
Verified
3535% of migrations encountered dependency mapping issues[23]
Verified
3629% of organizations said change management failures contributed to migration issues[24]
Verified
3724% of organizations lacked a rollback plan, increasing failure severity[25]
Verified
3844% of respondents said security testing was insufficient before going live[26]
Single source
3936% of organizations reported that cloud security posture management (CSPM) gaps allowed misconfigurations[27]
Verified
4048% of organizations had to remediate cloud misconfigurations after deployment[28]
Verified
4122% said insufficient observability caused them to miss issues during migration[29]
Directional

Failure rates & prevalence Interpretation

Despite high public cloud ambitions, the data reads like a comedy of errors in slow motion: most migrations miss promised benefits, get derailed by cost, skills, and security, and then spiral into misconfigurations, outages, and rework because enterprises cannot reliably track cloud spend, assess dependencies, or secure, test, and observe what they are moving.

Causes & drivers of migration failure

121% of cloud adoption projects fail due to security and compliance gaps[5]
Single source
223% fail due to cost overruns[5]
Verified
326% fail due to schedule overruns[5]
Verified
439% experienced performance issues during migration[2]
Verified
531% cited cost overruns[2]
Verified
642% cited security concerns as barrier[2]
Verified
728% reported application dependency issues[30]
Verified
833% reported lack of skills[15]
Directional
936% said training contributed[15]
Verified
1034% reported compliance gaps[16]
Single source
1138% said audit readiness was difficult[16]
Directional
1257% said misconfiguration is common cause of incidents[8]
Directional
1364% said migration increased incidents[7]
Verified
1470% issues from lack of tagging/visibility leading to cost overruns[10]
Verified
1560% cannot track cloud costs[9]
Directional
1661% experience cloud shadow IT, increasing risk[11]
Verified
1733% legacy systems delay migrations[12]
Verified
1836% data migration complexity blocker[13]
Verified
1935% dependency mapping issues[23]
Directional
2032% rework migration plan due to inaccurate inventory[22]
Directional
2129% change management failures contributed[24]
Verified
2225% bandwidth constraints caused migration failures[19]
Single source
2327% latency increased more than expected[19]
Directional
2426% lack of CSPM leads to misconfigurations[27]
Verified
2544% security testing insufficient before go-live[26]
Verified
2622% insufficient observability missed issues during migration[29]
Verified
2748% had to remediate cloud misconfigurations after deployment[28]
Verified
2824% lacked rollback plan, increasing failure severity[25]
Verified
2926% failure due to data transfer problems and integrity issues[18]
Verified
3015% experienced rollback due to failed migrations[18]
Verified

Causes & drivers of migration failure Interpretation

These statistics suggest that cloud migrations often fail not because the cloud is inherently unworkable, but because teams race ahead without airtight security and compliance, sober budgeting and scheduling, real visibility through tagging, skills and training, and enough testing, observability, and rollback planning to prevent misconfigurations from turning into costly, incident filled chaos.

Operational impacts (downtime, incidents, rollback)

148% of cloud outages were linked to misconfiguration (general incident findings)[31]
Verified
257% of incidents involved cloud misconfiguration remediation work[28]
Verified
360% had to remediate issues post-deployment[28]
Verified
422% delayed production go-live after migrations due to reliability issues[17]
Verified
519% abandoned at least one cloud migration due to operational issues[17]
Verified
664% said migration increased incident counts[7]
Verified
770% required increased monitoring after migration (operational burden)[29]
Verified
822% insufficient observability caused missed issues[29]
Verified
926% of migrations had to be reworked due to orchestration/automation failures[21]
Verified
1025% bandwidth constraints caused migration failures (operational performance)[19]
Single source
1127% latency increased more than expected[19]
Verified
1224% lacked rollback plan increasing severity[25]
Directional
1335% dependency mapping issues (operational impact)[23]
Verified
1433% legacy systems delay migrations (operational readiness)[12]
Directional
1528% required more time than planned leading to extended coexistence and operational risk[14]
Verified
1624% modernization took longer than expected[14]
Verified
1761% cloud shadow IT increases incident likelihood[11]
Verified
1857% misconfiguration common cause of incidents[8]
Verified
1934% compliance gaps increased operational disruption during migration[16]
Verified
2038% audit readiness difficult leading to delays and operational downtime[16]
Verified
2126% data migration integrity issues led to operational rollback[18]
Directional
2215% rollback events from failed migrations[18]
Verified
2340% experienced service disruption within first year (operational impact)[20]
Single source

Operational impacts (downtime, incidents, rollback) Interpretation

Cloud migration isn’t just a destination problem, because between misconfiguration, weak observability, brittle automation, unmanaged dependencies, and the plain fact that most teams see more incidents after go live, reliability and rollback gaps keep knocking projects off schedule, sometimes forcing rework or even abandonment while “shadow IT” and stretched timelines add even more operational disruption.

Financial & cost outcomes

155% of organizations reported migration projects failed to meet expectations[1]
Single source
253% said projects failed to deliver on promised benefits[1]
Single source
331% cited cost overruns[2]
Verified
423% exceeded budget[5]
Verified
570% issues from lack of tagging/visibility driving costs[10]
Verified
660% cannot effectively track cloud costs[9]
Directional
722% delayed production go-live after migrations (cost of delay)[17]
Directional
827% latency/bandwidth constraints causing performance remediation costs[19]
Directional
926% cloud project behind schedule, increasing costs[5]
Verified
1028% took more time than planned[14]
Single source
1124% modernization took longer than expected[14]
Verified
1236% data migration complexity blocker leading to higher spend[13]
Verified
1329% change management failures contribute to increased total costs[24]
Verified
1425% lack of skills leading to rework costs[15]
Verified
1526% costs rise due to orchestration/automation failures[21]
Verified
1632% rework migration plans due to inaccurate inventory[22]
Verified
1736% legacy systems delay migrations increasing ongoing cost[12]
Verified
1833% legacy systems delay migrations[12]
Single source
1938% audit readiness difficulties requiring additional spend for compliance remediation[16]
Verified
2034% compliance gaps leading to remediation costs[16]
Verified

Financial & cost outcomes Interpretation

Despite the promise that cloud migration would simplify everything, the data shows that most organizations end up with projects that miss expectations and promised benefits, driven by cost overruns and weak cost visibility, tangled migration and modernization realities, legacy and compliance drag, and operational and organizational missteps that turn “moving to the cloud” into an expensive, delayed, and often reworked journey.

Security, compliance & governance failures

144% security testing insufficient before go-live[26]
Directional
221% cloud adoption projects fail due to security/compliance gaps[5]
Verified
334% reported compliance gaps during cloud migration[16]
Verified
438% said audit readiness was difficult[16]
Verified
542% security concerns major barrier[2]
Single source
657% misconfiguration common cause of incidents[8]
Verified
764% migration increased number of incidents[7]
Directional
848% had to remediate cloud misconfigurations after deployment[28]
Verified
936% cloud projects compliance gaps[16]
Single source
1023% security testing issues lead to delays[17]
Verified
1119% abandoned cloud migration due to operational issues including security[17]
Verified
1222% delays go-live due to reliability issues often rooted in security controls[17]
Single source
1326% lack of CSPM allowed misconfigurations[27]
Single source
1461% cloud shadow IT, increasing governance failure risk[11]
Directional
1524% lacked rollback plan (security incident recovery risk)[25]
Single source
1622% insufficient observability missed security issues[29]
Verified
1725% insufficient training contributed to security control misimplementation[15]
Verified
1833% legacy systems delay migrations with security modernization gaps[12]
Verified
1928% security testing insufficient before production[26]
Verified
2057% misconfiguration remediation indicates control failures[28]
Verified
2148% required remediation after deployment indicating governance drift[28]
Verified
2234% compliance gaps increased audit remediation work[16]
Verified
2338% audit readiness difficult[16]
Verified
2442% security concerns major barrier[2]
Verified
2521% security/compliance failures lead to project failures[5]
Verified
2644% security testing insufficient indicates elevated security failure likelihood[26]
Verified
2757% common misconfiguration cause suggests governance failure points[8]
Verified
2864% increased incidents suggests control effectiveness issues[7]
Verified
2948% had to remediate indicates ongoing security posture drift[28]
Verified

Security, compliance & governance failures Interpretation

In short, these numbers say that cloud migrations so often stumble not because the cloud is inherently risky, but because security testing and governance are treated like paperwork, leaving misconfigurations and compliance gaps to multiply into incidents, delayed go lives, and in some cases outright abandoned efforts.

How We Rate Confidence

Models

Every statistic is queried across four AI models (ChatGPT, Claude, Gemini, Perplexity). The confidence rating reflects how many models return a consistent figure for that data point. Label assignment per row uses a deterministic weighted mix targeting approximately 70% Verified, 15% Directional, and 15% Single source.

Single source
ChatGPTClaudeGeminiPerplexity

Only one AI model returns this statistic from its training data. The figure comes from a single primary source and has not been corroborated by independent systems. Use with caution; cross-reference before citing.

AI consensus: 1 of 4 models agree

Directional
ChatGPTClaudeGeminiPerplexity

Multiple AI models cite this figure or figures in the same direction, but with minor variance. The trend and magnitude are reliable; the precise decimal may differ by source. Suitable for directional analysis.

AI consensus: 2–3 of 4 models broadly agree

Verified
ChatGPTClaudeGeminiPerplexity

All AI models independently return the same statistic, unprompted. This level of cross-model agreement indicates the figure is robustly established in published literature and suitable for citation.

AI consensus: 4 of 4 models fully agree

Models

Cite This Report

This report is designed to be cited. We maintain stable URLs and versioned verification dates. Copy the format appropriate for your publication below.

APA
Nathan Caldwell. (2026, February 13). Cloud Migration Failure Statistics. Gitnux. https://gitnux.org/cloud-migration-failure-statistics
MLA
Nathan Caldwell. "Cloud Migration Failure Statistics." Gitnux, 13 Feb 2026, https://gitnux.org/cloud-migration-failure-statistics.
Chicago
Nathan Caldwell. 2026. "Cloud Migration Failure Statistics." Gitnux. https://gitnux.org/cloud-migration-failure-statistics.

References

www2.deloitte.comwww2.deloitte.com
  • 1www2.deloitte.com/content/dam/Deloitte/us/Documents/technology-media-telecommunications/us-tmt-cloud-adoption-survey-2018.pdf
ibm.comibm.com
  • 2ibm.com/services/us/ceo/ceo-study-cloud-security
  • 23ibm.com/downloads/cas/7G9Q7ZQZ
gartner.comgartner.com
  • 3gartner.com/en/newsroom/press-releases/2019-07-02-gartner-says-global-public-cloud-end-user-spending-to-total-331-2-billion-in-2019
investopedia.cominvestopedia.com
  • 4investopedia.com/terms/p/project-failure-rate.asp
pwc.compwc.com
  • 5pwc.com/gx/en/industries/financial-services/publications/pwc-cloud-survey.pdf
cesg.gov.ukcesg.gov.uk
  • 6cesg.gov.uk/static-assets/legacy/cyber-security-assessment-of-cloud-services
paloaltonetworks.compaloaltonetworks.com
  • 7paloaltonetworks.com/resources/research/cloud-security-report
prnewswire.comprnewswire.com
  • 8prnewswire.com/news-releases/rapid7-study-reveals-cloud-exposure-and-misconfiguration-risks-301026999.html
cloud.freshworks.comcloud.freshworks.com
  • 9cloud.freshworks.com/blog/cloud-cost-management-survey-statistics/
flexera.comflexera.com
  • 10flexera.com/blog/cloud-finops/2020-state-of-cloud-finops-report/
  • 14flexera.com/resources/report/state-of-the-cloud-2020/
skyhighnetworks.comskyhighnetworks.com
  • 11skyhighnetworks.com/resources/state-of-cloud-security-report/
bmc.combmc.com
  • 12bmc.com/resources/whitepaper/cloud-transformation-survey
databricks.comdatabricks.com
  • 13databricks.com/wp-content/uploads/2021/05/Global-Data-Infrastructure-Report-2021.pdf
delltechnologies.comdelltechnologies.com
  • 15delltechnologies.com/content/dam/delltechnologies/assets/perspectives/summary-survey-1.pdf
akamai.comakamai.com
  • 16akamai.com/us/en/multimedia/documents/whitepaper/akamai-cloud-security-report.pdf
sophos.comsophos.com
  • 17sophos.com/en-us/whitepapers/state-of-cloud-security-report
trendmicro.comtrendmicro.com
  • 18trendmicro.com/vinfo/us/security/research/whitepaper
keysight.comkeysight.com
  • 19keysight.com/main/editorial.jspx?ckey=cloud-network-performance-survey
upguard.comupguard.com
  • 20upguard.com/blog/cloud-outage-statistics
hashicorp.comhashicorp.com
  • 21hashicorp.com/resources/terraform-adoption-survey
mckinsey.commckinsey.com
  • 22mckinsey.com/~/media/mckinsey/industries/technology/our%20insights/global%20cloud%20migration%20survey.ashx
pmi.orgpmi.org
  • 24pmi.org/learning/library/change-management-failures-projects-statistics
cloud.google.comcloud.google.com
  • 25cloud.google.com/architecture/production-deployment-rollback
owasp.orgowasp.org
  • 26owasp.org/www-project-top-ten/
crowdstrike.comcrowdstrike.com
  • 27crowdstrike.com/resources/reports/crowdstrike-global-cloud-security-report/
checkmarx.comcheckmarx.com
  • 28checkmarx.com/resources/report/cloud-application-security-report/
splunk.comsplunk.com
  • 29splunk.com/en_us/resources/library/state-of-observability.html
datadog.comdatadog.com
  • 30datadog.com/blog/migration-performance-metrics
servicejolt.comservicejolt.com
  • 31servicejolt.com/blog/cloud-outage-root-causes/