Using Threat-X with section.io

Because section.io is the only CDN that offers your choice of reverse proxy, you can choose to bring the Web Application Firewall created by the security experts at Threat X into your web site’s delivery infrastructure.

About Threat X

Threat X is a reverse proxy that inspects and adapts to web site attacks that can inflitrate your web site and cause problems for your business.

Because Threat X doesn’t simply rely upon statically defined rule sets like old WAFs (and CDNs based on those old WAFs) you can expect a higher degree of security.

This also means that there’s a lower cost to maintain that level of security, because the adaptive nature of the platform means that you don’t need to spend time and money on in-house security experts to keep your rules up to date.

Of course, you can still rely on Threat X for virtual patching, which is one of the most sought after features in a WAF.

Setting up Threat X in section.io

You can add Threat X to your section.io setup CDN very quickly. There are a few phases to this process.

  1. Contact section.io support. Our engineers will organize an account with Threat X, and manage introducing the new proxy to your existing setup. If you don’t have an existing setup, create an account and add your site. Then, reach out to us. The section.io team will provide you with credentials to access the Threat X management console.
  2. Threat X will then be running on your site, inspecting your traffic. This period allows the system to form a baseline of “good traffic”.
  3. After a while, look at the threats that are hitting your site. You’ll want to look for any false positives - this is where Threat X has detected an attack that could be a result of bugs in your site.
  4. Change Threat X from inspection mode into blocking mode.

Other things to note

Naturally, you can see when Threat X is on your site by looking at the Overview page in Aperture, section.io’s management console.

Also, our powerful Kibana interface will show you all the HTTP requests made in the CDN, and this also includes the HTTP traffic passing throught the Threat X console.