Integration options
We offer four options for integrating protection. They allow you to adapt our solution to any infrastructure: cloud, hybrid, or on-premises. An integration option describes how protection is connected to your resource: how data is transferred, where filtering takes place, and what you need to configure or connect.
The options can be customized. If you have specific requirements, we will take them into account. Just describe the task to your account manager.
Integration options overview
The table below briefly compares all options. The following sections describe each option in detail.
| Proxy | Module | Hybrid | IP transit with your server log analysis | |
|---|---|---|---|---|
How it works |
We receive traffic in our cloud, remove bots, and send it to your infrastructure. |
WAAP software installed in your infrastructure removes bots from traffic. |
1. We receive traffic in our cloud and filter it: we block all connections except valid TCP sessions. We send valid TCP sessions to your infrastructure. 2. WAAP software installed in your infrastructure removes bots from traffic. |
We announce your subnets from our protection platform, receive traffic, remove DDoS attacks, and send it to your infrastructure. |
Bot protection |
✅ |
✅ |
✅ |
❌ |
Protection from L7 DDoS attacks |
✅ |
✅ |
✅ |
✅ (Unlike the other options, filtering is based on IP addresses rather than requests, so the false positive rate is higher.) |
Protection from L3–L4 DDoS attacks |
✅ |
❌ |
✅ |
✅ (Unlike the other options, filtering is based on IP addresses rather than requests, so the false positive rate is higher.) |
Without disclosing the TLS/SSL certificate |
❌ |
✅ |
✅ |
✅ |
Without changing the DNS A record |
❌ |
✅ |
❌ |
✅ |
Without installing WAAP software |
✅ |
❌ |
❌ |
✅ |
Why block non-TCP traffic?
To protect against DDoS attacks. Other protocols, such as UDP and ICMP, are usually not used by web services but are often used in DDoS attacks. Botnets generate large volumes of UDP or ICMP traffic and overload the network channel. If your service uses TCP, it is best to filter all non-TCP connections to keep it secure.
What is WAAP software?
WAAP software is a module we developed for NGINX and Angie web servers. It is installed on your proxy server and blocks bots.
First, WAAP software extracts request metadata from decrypted traffic, without the request body or cookies, and sends it to our protection system. The system analyses this metadata to determine whether the request was sent by a bot or a person. It then checks the protection settings for your resource and decides whether to allow the request. For example, if you asked to block only scrapers, it will decide to block a request from a scraper but allow a request from a search engine crawler. The system sends these decisions to WAAP software. WAAP software applies them and filters the traffic. As a result, requests from all bots except those you allow are blocked.
WAAP software advantages:
-
Traffic is decrypted within your infrastructure, so you do not need to provide your SSL/TLS certificate;
-
Sensitive data remains private: WAAP software does not send the request body or cookies. It sends only metadata, such as SNI, the JA3 fingerprint, and other data;
-
The WAAP software protection scheme complies with PCI DSS requirements.
Proxy
How it works: We block requests from all bots except those you allow. Your resource is protected from DDoS attacks, scrapers, ad click fraud, brute-force attacks, and other malicious automation.
Recommended for: all users affected by bots who can use cloud-based protection and disclose their SSL certificate.
What you need to connect this option:
-
Complete the questionnaire our engineers send you so that we can configure protection based on your requirements.
-
Upload your SSL/TLS certificate in the management console.
-
Point your DNS A record to the IP address we provide.
How filtering works:
-
Clients send requests to your resource.
-
Requests reach our cloud protection system.
-
The system decrypts the traffic using the SSL certificate and analyses every request to determine whether it was sent by a bot or a person.
-
The system filters requests and blocks all bots except those you allow. We can flexibly configure filtering based on your requirements. You can also set a White list, Black list, Geo restrictions, and Custom rules yourself.
-
Only requests from people and allowed bots are sent to your resource.
Module
How it works: We block requests from all bots except those you allow. Traffic filtering takes place entirely within your infrastructure: WAAP software is installed on your web server and filters traffic without network intermediaries.
What is WAAP software?
WAAP software is a module we developed for NGINX and Angie web servers. It is installed on your proxy server and blocks bots.
First, WAAP software extracts request metadata from decrypted traffic, without the request body or cookies, and sends it to our protection system. The system analyses this metadata to determine whether the request was sent by a bot or a person. It then checks the protection settings for your resource and decides whether to allow the request. For example, if you asked to block only scrapers, it will decide to block a request from a scraper but allow a request from a search engine crawler. The system sends these decisions to WAAP software. WAAP software applies them and filters the traffic. As a result, requests from all bots except those you allow are blocked.
WAAP software advantages:
-
Traffic is decrypted within your infrastructure, so you do not need to provide your SSL/TLS certificate;
-
Sensitive data remains private: WAAP software does not send the request body or cookies. It sends only metadata, such as SNI, the JA3 fingerprint, and other data;
-
The WAAP software protection scheme complies with PCI DSS requirements.
Recommended for: users who need on-premises protection from bots without changing DNS records or sending SSL/TLS certificates to an external system. This option is suitable for organizations with high security requirements.
What you need to connect this option:
-
Complete the questionnaire our engineers send you so that we can configure protection based on your requirements.
-
Install WAAP software in your infrastructure on NGINX or Angie servers. We will help with the installation.
How filtering works:
-
Clients send requests to your resource.
-
Traffic reaches the proxy server in your infrastructure, where WAAP software is installed and your SSL/TLS certificate is configured.
-
The proxy server decrypts traffic using the SSL/TLS certificate.
-
WAAP software extracts request metadata, without the request body or cookies, and sends it to our cloud protection system.
-
The system analyses each request’s metadata to determine whether it was sent by a bot or a person.
-
The system checks your resource protection settings and decides whether to allow each request. For example, if you asked to block only scrapers, it will decide to block a request from a scraper but allow a request from a search engine crawler.
-
The system sends its decisions to WAAP software.
-
WAAP software in your infrastructure applies the decisions: it blocks some requests and allows others.
-
Clean traffic reaches your resource: only requests from people and bots you allow.
Hybrid
How it works: First, we filter traffic in the cloud and allow only valid TCP sessions into your infrastructure. These sessions reach a web server in your infrastructure where WAAP software is installed. WAAP software blocks illegitimate bots and allows only requests from people and authorized automation to reach the resource.
Your resource is protected from DDoS attacks and malicious automation, including scrapers, ad click fraud, brute-force attacks, and other threats, without disclosing your SSL/TLS certificate.
What is WAAP software?
WAAP software is a module we developed for NGINX and Angie web servers. It is installed on your proxy server and blocks bots.
First, WAAP software extracts request metadata from decrypted traffic, without the request body or cookies, and sends it to our protection system. The system analyses this metadata to determine whether the request was sent by a bot or a person. It then checks the protection settings for your resource and decides whether to allow the request. For example, if you asked to block only scrapers, it will decide to block a request from a scraper but allow a request from a search engine crawler. The system sends these decisions to WAAP software. WAAP software applies them and filters the traffic. As a result, requests from all bots except those you allow are blocked.
WAAP software advantages:
-
Traffic is decrypted within your infrastructure, so you do not need to provide your SSL/TLS certificate;
-
Sensitive data remains private: WAAP software does not send the request body or cookies. It sends only metadata, such as SNI, the JA3 fingerprint, and other data;
-
The WAAP software protection scheme complies with PCI DSS requirements.
What is an invalid TCP session and why should it be blocked?
An invalid TCP session is a connection that does not complete the TCP handshake according to protocol rules. For example, it may be interrupted during the handshake stage (SYN–SYN/ACK–ACK) or contain malformed packets with formatting errors. Such sessions are most often created by botnets during DDoS attacks: they overload the server with half-open or invalid connections and prevent real users from connecting. These sessions do not carry useful traffic and should be blocked.
Why block non-TCP traffic?
To protect against DDoS attacks. Other protocols, such as UDP and ICMP, are usually not used by web services but are often used in DDoS attacks. Botnets generate large volumes of UDP or ICMP traffic and overload the network channel. If your service uses TCP, it is best to filter all non-TCP connections to keep it secure.
Recommended for: users who need protection from DDoS attacks and bots without disclosing their SSL/TLS certificate.
What you need to connect this option:
-
Complete the questionnaire our engineers send you so that we can configure protection based on your requirements.
-
Install WAAP software in your infrastructure on NGINX or Angie servers. We will help with the installation.
-
Point your DNS A record to the IP address we provide.
How filtering works:
-
Clients send requests to your resource.
-
Requests reach our cloud protection system.
-
The system checks whether TCP connections are established correctly.
-
Invalid connections and all non-TCP traffic are blocked.
-
All valid TCP sessions are sent to your resource.
-
Traffic reaches the proxy server in your infrastructure, where WAAP software is installed and your SSL/TLS certificate is configured.
-
The proxy server decrypts traffic using the SSL/TLS certificate.
-
WAAP software extracts request metadata, without the request body or cookies, and sends it to our cloud protection system.
-
The system analyses each request’s metadata to determine whether it was sent by a bot or a person.
-
The system checks your resource protection settings and decides whether to allow each request. For example, if you asked to block only scrapers, it will decide to block a request from a scraper but allow a request from a search engine crawler.
-
The system sends its decisions to WAAP software.
-
WAAP software in your infrastructure applies the decisions: it blocks some requests and allows others.
-
Clean traffic reaches your resource: only requests from people and bots you allow.
IP transit with your server log analysis
How it works: During a DDoS attack, we block all bots except those you allow. At other times, we allow all requests. This option protects against DDoS attacks at L3, L4, and L7.
|
Important: filtering in this option is less precise than in the other options because it is based on IP addresses rather than requests. This increases the risk of a false positive, when a legitimate user can be blocked because they use the same IP address or subnet as an attacker. For example, mobile operators assign one public IP address to hundreds or thousands of users. If a bot sends a suspicious request from this address, the system may block the entire IP address, including other users who simply access your resource from their smartphones. |
Recommended for: users who need protection from DDoS attacks and do not want to disclose their SSL/TLS certificate or install WAAP software in their infrastructure.
What you need to connect this option:
-
Complete the questionnaire our engineers send you so that we can configure protection based on your requirements.
-
Provide the pool of protected IP addresses, establish a BGP session with our network, and accept clean traffic over L2.
-
Configure log forwarding from your platforms, such as web servers, to our cloud. We will agree on the log format with you.
How filtering works:
-
We announce your subnet.
-
Clients send requests to your resource.
-
All traffic is sent to our protection system.
-
While there is no DDoS attack, all requests are allowed to reach your resource. When a DDoS attack begins, the system filters traffic:
-
L3/L4—filtering is based on packet headers and connection behaviour;
-
L7—filtering is based on logs from your platforms. Although packet contents remain encrypted, logs allow our system to distinguish bots from people. The system blocks IP addresses that send illegitimate bot traffic—that is, all bots except those you allow.
-
-
Traffic from people and bots you allow reaches your resources.