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.

Attacks/Breaches

1/24/2019
11:45 AM
50%
50%

Cloud Customers Faced 681M Cyberattacks in 2018

The most common attacks involved software vulnerabilities, stolen credentials, Web applications, and IoT devices.

Cloud customers were hit with 681 million cyberattacks last year, according to analysts at cloud security provider Armor, which recently analyzed cloud attacks detected in 2018.

The most common cloud-focused threats leveraged known software vulnerabilities, involved brute-force and/or stolen credentials, targeted the Internet of Things (IoT), or aimed for Web applications with SQL injection, cross-site scripting, cross-site request forgery attacks, or remote file inclusion. Researchers based the list on volume; these are not the most advanced or lethal cloud attacks.

Yet they continue to work, are easy to access, and are fairly simple to use, they explained in a blog post on their findings. Any cybercriminal can rent an exploit kit containing attack tools for a reasonable amount of cash. For example, they said, the older and established Disdain Exploit Kit was charging rental fees starting at $80 per day, $500 per week, and $1,400 per month. Kits are designed to be accessible to cybercriminals at all levels and are constantly updated with new exploits.

"Organizations that ignore patching leave themselves open to attacks that can take time and resources away from their business and can cause a lot of damage," said Corey Milligan, senior security researcher with Armor's Threat Resistance Unit (TRU).

TRU predicts IoT attacks, DDoS campaigns, targeted ransomware, advanced phishing campaigns, and attacks targeting containers and cloud services will be prevalent in 2019.

Read more details here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
1/30/2019 | 5:42:07 PM
Re: 691 M
Definitely agree, its always easier to qualify statistics if they are broken down into a regular trend, in this case by year.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
1/30/2019 | 5:40:35 PM
Re: Valuable Assessment
(Around known vulnerabilities) I agree that all known vulnerabilities need to be patched but prioritizing the criticals and severes over other moderate risk vulnerabilities may make mitigation more easily digestible, especially for organizations that are just starting to put together a program.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
1/30/2019 | 5:38:17 PM
Re: Valuable Assessment
About Equifax. If I recall correctly, they only had one individual responsible for patching which the executives tried to use as a scapegoat for the breach. I was baffled. But you'd be surprised how many organizations don't even have one person dedicated to patching. 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
1/27/2019 | 6:39:42 PM
Re: Valuable Assessment
Unfortunately, too many companies continue under the methodology that they are not going to make changes until they are burnt by the stove. Agree. Most companies do not care until they get hit and of course they go out of business just after that.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
1/27/2019 | 6:36:57 PM
Re: Valuable Assessment
definitely complements the logic of prioritizing patching Makes sense. Prioritization may not be enough, all the know vulnerabilities should be closed in a timely manner I would guess.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
1/27/2019 | 6:34:20 PM
Re: Valuable Assessment
Equifax - case closed. Learn from a true master. Makes sense. We should try to apply all patches needed as a timely manner.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
1/27/2019 | 6:31:39 PM
Re: Valuable Assessment
SANS has stated that 90% of risk can be mitigated through patching That makes sense and I would agree with it. Patching is critical.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
1/27/2019 | 6:30:40 PM
691 M
681 million cyberattacks last year, according to analysts at cloud security provider Armor, This does not give any how big the number is. It needs to be compared to previous years to make sense.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
1/24/2019 | 5:18:15 PM
Re: Valuable Assessment
Yup, definitely complements the logic of priorizing patching. I guess from "learning from a true master" it aligns with the premise of a smart man learns from their own mistakes but a brilliant man learns from others. Unfortunately, too many companies continue under the methodology that they are not going to make changes until they are burnt by the stove.
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
1/24/2019 | 3:08:20 PM
Re: Valuable Assessment
Equifax - case closed.  Learn from a true master.
Page 1 / 2   >   >>
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...