Application Security

11/17/2017
01:00 PM
0%
100%

Businesses Can't Tell Good Bots from Bad Bots: Report

Bots make up more than 75% of total traffic for some businesses, but one in three can't distinguish legitimate bots from malicious ones.

One in three organizations can't differentiate good or legitimate bots from bad bots - a shortcoming that can affect application security.

Bots make up more than 75% of total traffic for some businesses, according to a Radware study on Web application security. The study found nearly half (45%) of businesses had been hit with a data breach in the past year, and 68% are not confident they can keep corporate information safe.

Malicious bots are a serious risk, as Web-scraping attacks can affect retailers by stealing intellectual property, undercutting prices, and holding mass inventory in limbo, the report states. In retail, 40% of businesses can't tell good bots from bad ones. The healthcare industry is also struggling: 42% of traffic comes from bots, but 20% of IT security execs can tell if they're nefarious.

Researchers found gaps in DevOps security, which likely stem from the pressure to consistently deliver application services. Half (49%) of respondents use the continuous delivery of application services and 21% plan to adopt it in the next 1-2 years. More than half (62%) believe this increases the attack surface and about half report they don't integrate security into continuous application delivery.

Read more details here.

Join Dark Reading LIVE for two days of practical cyber defense discussions. Learn from the industry’s most knowledgeable IT security experts. Check out the INsecurity agenda 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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
11/28/2017 | 9:42:38 PM
Re: Good or bad bots?
@Dr. T: Not really. There are security software solutions and analytics that detect what kind of bot a bot is -- and whether it is a bad bot or a so-called "good" bot.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
11/28/2017 | 9:41:43 PM
Re: White Bot, Black Bot, Good Bot, Bad Bot
@Dr. T: Maybe you and I have different ideas of what kinds of bots we want to allow. I have no intention of letting marketers' bots in.

Whitelisting, in any case, goes to specific bots/APIs/etc. -- as opposed to general types.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
11/27/2017 | 12:52:56 PM
DevOPs Security?
 

"they don't integrate security into continuous application delivery?"

I do not know what they do then, are they delivering and deploying over the top?

 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
11/27/2017 | 12:50:16 PM
Re: White Bot, Black Bot, Good Bot, Bad Bot
I agree, the question is how we applied that analogy to bots technologies.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
11/27/2017 | 12:47:59 PM
Re: White Bot, Black Bot, Good Bot, Bad Bot
Are you a good bot or a bad bot?

This is a good idea, all the bots have to prove that they are good bots first.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
11/27/2017 | 12:46:16 PM
Re: White Bot, Black Bot, Good Bot, Bad Bot
"Whitelist"

Whitelist  would be a god option to keep. It may be a useful new bot such as delivering you the best cyber Monday deal. You want to allow that.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
11/27/2017 | 12:43:55 PM
Good or bad bots?
 

Good or bad bots? You would not know that until but executed so it is a little bit of a luck.
DonHarper
50%
50%
DonHarper,
User Rank: Apprentice
11/23/2017 | 4:41:54 PM
Re: White Bot, Black Bot, Good Bot, Bad Bot
Brilliant one ! 
agenpokeronline
50%
50%
agenpokeronline,
User Rank: Apprentice
11/22/2017 | 4:53:18 PM
Re: White Bot, Black Bot, Good Bot, Bad Bot
Nice one !
AutoEcole18
50%
50%
AutoEcole18,
User Rank: Apprentice
11/21/2017 | 5:48:58 PM
Re: White Bot, Black Bot, Good Bot, Bad Bot
Nice one !
Page 1 / 2   >   >>
WebAuthn, FIDO2 Infuse Browsers, Platforms with Strong Authentication
John Fontana, Standards & Identity Analyst, Yubico,  9/19/2018
New Cold Boot Attack Gives Hackers the Keys to PCs, Macs
Kelly Sheridan, Staff Editor, Dark Reading,  9/13/2018
Mirai Hackers' Sentence Includes No Jail Time
Dark Reading Staff 9/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-17243
PUBLISHED: 2018-09-20
Global Search in Zoho ManageEngine OpManager before 12.3 123205 allows SQL Injection.
CVE-2018-17232
PUBLISHED: 2018-09-20
SQL injection vulnerability in archivebot.py in docmarionum1 Slack ArchiveBot (aka slack-archive-bot) before 2018-09-19 allows remote attackers to execute arbitrary SQL commands via the text parameter to cursor.execute().
CVE-2018-17233
PUBLISHED: 2018-09-20
A SIGFPE signal is raised in the function H5D__create_chunk_file_map_hyper() of H5Dchunk.c in the HDF HDF5 through 1.10.3 library during an attempted parse of a crafted HDF file, because of incorrect protection against division by zero. It could allow a remote denial of service attack.
CVE-2018-17234
PUBLISHED: 2018-09-20
Memory leak in the H5O__chunk_deserialize() function in H5Ocache.c in the HDF HDF5 through 1.10.3 library allows attackers to cause a denial of service (memory consumption) via a crafted HDF5 file.
CVE-2018-17235
PUBLISHED: 2018-09-20
The function mp4v2::impl::MP4Track::FinishSdtp() in mp4track.cpp in libmp4v2 2.1.0 mishandles compatibleBrand while processing a crafted mp4 file, which leads to a heap-based buffer over-read, causing denial of service.