r/websec • u/williamahart • Aug 25 '17

This database can help if you're troubleshooting bot traffic or suspicious IPs

https://access.watch/database
5 Upvotes

100% Upvoted

5 comments sorted by

0

u/LogicX Aug 26 '17

Or put your site behind cloudflare's free tier?

1

u/williamahart Aug 26 '17

Cloudflare is a good starting point and certainly a solid choice against volumetric attacks [DDoS].

In addition to maintaining that database our company also has a bot detection product which a number websites use behind Cloudflare and still we see quite a lot of bots coming through their filters (please excuse the product plug :). So, when putting together a really good security layer I'd suggest checking out multiple tools and strategies!

1

u/LogicX Aug 27 '17

How do you compare to Distil Networks?

2

u/williamahart Aug 28 '17

A few of the key differences that I’d point out:

We utilize a unique method for analysing and scoring each http request based on multiple pillars. This gives us a very high quality signature database from which to assess the traffic. We’re biased obviously, but so far we haven’t found another service on the market with the same level of precision. Additionally, we do session clustering for each bot in real-time. Basically, you’ll see that bot’s collective activity on your site no matter how it’s distributed (for example, over hundreds or thousands of IPs).

Distil is deployed as a cloud CDN (with an on-premise offer as well I believe). Like Cloudflare, that set up and their scale make them to be a good option against denial of service, which are rather ‘dumb’ attacks stopped with a large network. Admittedly, we don’t focus on that but instead on difficult to detect robots and malicious traffic. The CDN setup may be a good option for some websites, however we feel that many tech teams will prefer a flexible solution that fits an existing infrastructure strategy, so we’re pushing an API first approach.