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   >   >>
Government Shutdown Brings Certificate Lapse Woes
Curtis Franklin Jr., Senior Editor at Dark Reading,  1/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security 2018
This Dark Reading Tech Digest explores the biggest news stories of 2018 that shaped the cybersecurity landscape.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-6443
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. Because of a bug in ctl_getitem, there is a stack-based buffer over-read in read_sysvars in ntp_control.c in ntpd.
CVE-2019-6444
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. process_control() in ntp_control.c has a stack-based buffer over-read because attacker-controlled data is dereferenced by ntohl() in ntpd.
CVE-2019-6445
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. An authenticated attacker can cause a NULL pointer dereference and ntpd crash in ntp_control.c, related to ctl_getitem.
CVE-2019-6446
PUBLISHED: 2019-01-16
An issue was discovered in NumPy 1.16.0 and earlier. It uses the pickle Python module unsafely, which allows remote attackers to execute arbitrary code via a crafted serialized object, as demonstrated by a numpy.load call.
CVE-2019-6442
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. An authenticated attacker can write one byte out of bounds in ntpd via a malformed config request, related to config_remotely in ntp_config.c, yyparse in ntp_parser.tab.c, and yyerror in ntp_parser.y.