Stopping Millions of Brute-force Account Takeover Attacks in Seconds

A Newcomer’s Take on Account Takeover (ATO)

As the newest member of PerimeterX, and the lead for PerimeterX Bot Defender product marketing, the first days with the company have been an amazing learning experience. The rabbit hole of research I have undertaken in the last week on the topic of botnet attacks and account takeover (ATO) schemes has truly opened my eyes to the challenges digital businesses face today. I have also been amazed, and sometimes puzzled, to see the different opinions and marketing claims from the various solution providers out there.

Many vendors in the bot detection and application security space are scrambling to highlight their unique solution for ATO attack detection and prevention, yet seem to miss some of the basic ATO attack characteristics. For example, a competitor has been touting their ATO blocking capabilities by highlighting 48 million ATO attempts blocked within a 60-hour time period. Additionally, this vendor claimed that only 0.5% of login attempts are “malicious” on a typical day. However, it is commonly known among industry leaders that over 70% of login requests, even on smaller retail sites, are malicious. Furthermore, using the competitors’ data, their advertised ATO block rate equates to only 52%! From my initial take, these metrics seemed to not be worth advertising, but I needed to confirm.

DevOps Connect:DevSecOps @ RSAC 2022

After reading these claims, I was curious about our own capabilities, so I checked in with my team to find out more about our own ATO attack blocking rates with PerimeterX Bot Defender. With some of our larger customers, Bot Defender regularly identifies nearly 2 billion ATO attacks in the same 60-hour time period as the aforementioned competitor – over 45 times the rate of our competitor!

Bot Defender blocking 2 Billion ATO attacks in 60 hours

The claims from the (Read more...)

*** This is a Security Bloggers Network syndicated blog from PerimeterX Blog authored by PerimeterX Blog. Read the original post at: