Subscribe to receive notifications of new posts:

Cloudflare Threat Control: Making your website safer

2011-01-14

3 min read

One of the benefits of CloudFlare is that it provides broad, effective security for any website. CloudFlare is a first line of defense against all sorts of threats from comment spammers to automated crawlers that don't follow robots.txt. When you sign up for CloudFlare, you get a Threat Control panel. The Threat Control gives you insight into malicious visitors coming to your site.

As an important side note, threat traffic typically doesn't appear in Google Analytics. So, many web admins don't realize the number ofmalicious visitors coming to their websites.

We wanted to share some tips on how to interact with the Threat Controlpanel.

Threat Control Basics

You can get to your ‘Threat Control' by going to: Websites-> Dashboards-> Threat Control

Threat Control Overview

The Threat Control panel shows the malicious traffic to your website.

The alerts are broken down like this:

CloudFlare shows high priority alerts for things that should be reviewed. These have a "!" symbol. Generally, high priority alerts fall into one of two buckets:

  1. Visitors who CloudFlare challenged but passed the CAPTCHA and left a message requesting to be permanently allowlisted

  2. Visitors who were listed as threats in CloudFlare's global system but your security settings allowed to get through

Sometimes people are not sure what to do with the Threat Control. Other than review the alerts with a "!" (which always surface to the top), you don't have to do anything. You can just let CloudFlare do its thing.

But, if you want to dig into the data more, here is an overview of whatit means.

Taking action against a threat alert

[

](http://www.flickr.com/photos/damonbillian/5355748424/ "Threat Control Exploit Attacker by dbillian, on Flickr")

Using an example from my personal blog, I had a couple of exploit attacker attempts on January 5 and January 6. Given that exploit attackers are looking to do something malicious on my blog, like looking for weaknesses to inject malicious code, I can choose to block these visitors. If I use the ‘block option' on the right, any future visits from this IP will be blocked from entering my website.

Note: The difference between appearing in your Threat Control andBlocked list is that visitors in the Threat Control are presented with achallenge page, where entering a CAPTCHA gains them access to yourwebsite. Blocked visitors are not given the CAPTCHA so there is no wayfor them to access your website.

Adding your own entries to block

**[

](http://www.flickr.com/photos/damonbillian/5355748444/ "Screen shot 2011-01-10 at 4.52.12 PM by dbillian, on Flickr")**

You can easily add IP addresses to your Threat control. We've created a ‘Create A Custom Rule' option that allows you to block or trust by individual IP address, IP range, or by Country. Here is the quick rundown of the options:

Block individual IP address= The specific IP is banned from accessingyour site

Block IP range= IP range is banned from accessing your site

To block by IP range:To block 123.45.. you would enter 123.45.0.0/16To block 123.45.67.* you would enter 123.45.67.0/24

Block by country= All visitors from that country are presented with achallenge page. This is different than being banned. If a visitor passesthe CAPTCHA, they gain access to your website. This allows legitimatevisitors in a ‘bad neighborhood' the opportunity to access your website.

To block by country:Enter the country name in the field (a drop down list will appear) andchoose the block option.

Trust List:Any IP address, range or country you've trusted will be added here. If you would like to remove an entry from your ‘Trust List', simply click on the ‘trust' button to remove it as an entry.

Block List:Any IP addresses, ranges or countries you've blocked will be added here.

To remove an entry from your block list, click on the ‘block' option.

A couple of quick notes

We would recommend reviewing entries in your ‘Threat Control' panel on a regular basis for the following reasons:

  1. Challenged visitors may leave you a message requesting being allowlisted. Review these carefully, since some sophisticated bots can write notes.

  2. Our data sources are reliable about who to challenge, but there will be times when false positives appear. The most common source is a visitor from a shared network like a coffee shop or university, where someone on the network has an infected computer doing malicious things online, but that visitor's computer is clean. You can help correct these false positives by allowlisting that visitor in your Threat Control panel.

  3. Individual IP addresses are dynamic, which means they change. So a malicious IP may no longer be malicious after a few months. To help guide your decision about whether or not to remove a block, you can research the IP address on an individual basis on Project Honey Pot.

Modify your CloudFlare challenge page to align with your brand. CloudFlare allows you to add custom text and colors to your challenge page, and we are adding support for multiple languages in the coming weeks so visitors get a localized experience.

You have control over the security setting of each domain and can choose Low, Medium or High.

Related: Why bloggers and webadmins should care about botnets.

Have suggestions or comments? We love hearing from our users so contact us.

Cloudflare's connectivity cloud protects entire corporate networks, helps customers build Internet-scale applications efficiently, accelerates any website or Internet application, wards off DDoS attacks, keeps hackers at bay, and can help you on your journey to Zero Trust.

Visit 1.1.1.1 from any device to get started with our free app that makes your Internet faster and safer.

To learn more about our mission to help build a better Internet, start here. If you're looking for a new career direction, check out our open positions.
Best Practices

Follow on X

Cloudflare|@cloudflare

Related posts

December 17, 2018 6:44 PM

Real World Serverless: Serverless Use Cases and Best Practices

Cloudflare Workers has had a very busy 2018. Throughout the year, Workers moved from beta to general availability, continued to expand its footprint as Cloudflare grew to 155 locations, and added new features and services to help developers create increasingly advanced applications....