Application protection: operating principles, configuration, and tools

Application protection is a system that protects your resource from DDoS attacks and bots.

How protection works

Our system checks every request to your website or application. It blocks bots and DDoS attacks, while allowing requests from people and your legitimate automation.

How Application protection works

Here is what happens step by step:

  1. A user sends a request to your resource.

  2. The request reaches the protection system—the Strictera cloud platform or WAAP software installed in your infrastructure.

    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.

  3. The system analyses request telemetry across L3/L4–L7 layers. In other words, it evaluates how the request travels through the network, how the connection is established, and what is transmitted in the HTTP request.

    For example, the system checks:

    • Signs of statistical anomalies;

    • Request source reputation;

    • HTTP request parameters;

    • TLS connection parameters;

    • Other signs that help determine the nature of the traffic.

    The system evaluates all this data together. As a result, it understands where the request came from, what its technical characteristics are, and whether it was sent by a person or a bot.

  4. Filtering begins. The system checks different settings one by one:

    • Black list—if the request comes from an IP address on the list, it is blocked;

    • White list—if the request comes from an IP address on the list, it is allowed immediately, without further checks;

    • Custom rules—if the request matches a rule you created, the specified action is applied: allow, block, or present a challenge to the user (a CAPTCHA, JavaScript, or cookie challenge);

    • Individual protection profile—the request is processed according to settings we created for your resource. These settings ensure that protection works exactly as you need: it blocks what you want to block and allows only the required traffic.

    As a result, only requests from people and legitimate automation pass through filtering. Everything else is blocked.

  5. Requests that pass filtering are sent to your resource.

Setting up protection

What we configure for you

When you connect protection, we create an individual protection profile—a set of filtering settings based on your requirements. Here is how we create the profile:

  1. We discuss your requirements to understand whom to allow, whom to block, and which areas need special attention.

  2. We collect statistics on your traffic and identify patterns. This helps us build a profile of a legitimate client and detect bots more accurately.

  3. We configure protection based on your requirements and the collected statistics: create signatures, set rate limits, allowlist traffic, and more.

After that, the profile is ready, and protection works exactly as you need it to. Here is an example of a protection configuration:

Your requirements What we do

Block all bots except the corporate SEO bot you developed

Block DDoS attacks

We enable Anti-bot, a protection mode that blocks bots and allows only requests from people. It also blocks DDoS attacks.

We allowlist your SEO bot: we identify the characteristics that distinguish requests from the bot and configure Anti-bot to allow them.

Allow access to a private API only from your company subnet

We block all requests to the private API except requests from your subnet.

Protect specific endpoints in a public API that could be abused

We set rate limits for the required endpoints. Only a limited number of requests can be sent to them from one IP address.

If your requirements change, we will update the profile. Contact support, and our engineers will change the settings.

What you can configure yourself

You can manage protection yourself in the management console. The following tools are available:

These settings take priority. The protection system first follows your settings and then the settings in the individual profile.

Integration options

We offer four protection integration options. They make it possible to adapt our solution to any infrastructure: cloud, hybrid, or on-premises.

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

✅

❌

❌

✅

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.

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 cloud 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.

For details about each option, see Integration options.

Tools

The management console provides tools to help you analyse traffic and monitor protection:

How to connect and set up protection

If you are not yet a customer and are considering our solution, visit Strictera Application protection and book a demo. We will tell you about the product, help you choose a protection configuration, and assist with connection and setup.

If you already use Application protection and want to change settings or ask a question, contact support. Our engineers will be happy to advise you and, if needed, configure everything for you.