Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Cloud

1/24/2018
12:15 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Financial Impact of Cloud Failure Could Hit $2.8B in Insured Loss

A new report highlights the potential financial damage of downtime at top cloud services providers.

The public cloud industry is projected to continue growing revenue at a rate of 36% each year through 2026, according to a new report from AIR and Lloyd's of London. As demand for cloud services grows, so too do the potential consequences of cloud failure. Downtime at a major cloud provider could hit $19 billion in ground-up losses, researchers report.

New data from AIR and Lloyd's of London demonstrates the financial impact of downtime incidents at several top cloud service providers. Their report shows how 12.4 million businesses in the US, which it states is the most established cyber insurance market, would be affected if cloud systems were to fail for a span of several hours to eleven days.

This is intended to help insurers struggling to understand their exposure to systemic risk. Its goal is to help them prepare for an extreme event with potential to generate millions of claims.

Today's insurance industry would be little help if a cloud service provider failed. In the event a cyber incident took a US-based top-three cloud provider offline for three to six days, researchers predict it would cost $6.9 billion to $14.7 billion USD in ground-up losses and $1.5 billion to $2.8 billion USD in insured loss.

The gap is due to cyber insurers' low penetration rates, especially among small- and medium-sized businesses, in addition to limited coverage. Most policies have low limits and long waiting periods, with about eight to 24 hours of downtime before coverage starts to kick in. Researchers say this is an opportunity for insurers to provide coverage for extreme scenarios.

The cloud industry is highly concentrated, researchers say, with the top 15 cloud providers making up 70% of industry market share. More businesses are using these services: 37% of companies are expected to use infrastructure-as-a-service as their primary environment in 2018, and the number primarily relying on traditional on-prem infrastructure will drop to 43%.

As dependence on cloud continues to grow, cyber insurers should be wary of threats with the power to bring it down. The report classifies four types of "silent" threats: environmental (natural disasters, critical infrastructure failure), adversarial (actors with malicious intent), accidental (employee mistakes), and structural (equipment and software failure).

David Bradford, chief strategy officer and director of strategic partner development at Advisen, calls cloud computing "a huge risk that [insurers] haven't really come to grips with" and "one of the few things putting the breaks on the cyber marketplace."

"If a large cloud provider goes down, the insurer would be responsible for thousands of different companies using that service," he says.

Researchers report the most likely causes of interrupted cloud services include malicious attacks by external actors, employee errors, and hardware and software failures. Data indicates 50% of businesses targeted in a DDoS attack were also the victims of theft, and 36% of companies hit in these incidents were infected with malware.

Related Content:

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.