Because section.io is the only CDN that allows you to choose the reverse proxies that run in your stack, you can choose to bring the Web Application Firewall created by the security experts at Threat X into your web site’s delivery infrastructure.
Threat-X is a reverse proxy that inspects and adapts to web site attacks that can infiltrate 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.
You can add Threat X to your section.io setup Content Delivery Grid very quickly. There are a few phases to this process.
When creating your application you will want to select the Threat-X on the second page of the setup process.
You will then want to follow the steps below:
Naturally, you can see Threat X is on your site by looking at the Overview page in Aperture, section.io’s management console.
The section.io platform writes a log for each HTTP request that passes through Threat X. These will be available in our powerful Kibana interface alongside logs from all of the other proxies in your stack.