Integration options and clean traffic delivery methods

Learn about the available protection integration options and clean traffic delivery methods, and how to choose the right ones for your infrastructure.

Integration options

Two options are available: On-Demand and Cloud Signaling. Both use IP transit to protect you from DDoS attacks. The main difference is whether traffic passes through Strictera infrastructure all the time or only during an attack.

On-Demand Cloud Signaling

Choose this option if

You want Strictera to handle DDoS protection completely.

You have a traffic analyzer that can send BGP announcements. Strictera can be your main protection or a backup for local protection.

Main idea

Your traffic always passes through Strictera infrastructure. Our system analyzes it and:

  • When there is no attack, passes all incoming traffic to your network.

  • During an attack, blocks malicious traffic and passes only legitimate traffic.

By default, traffic goes directly to your infrastructure. Your analyzer monitors attacks and their volume.

The incoming route temporarily changes to users → Strictera → your infrastructure when:

  • The analyzer detects an attack and traffic needs to be diverted to Strictera for filtering.

  • Your local protection cannot handle the attack, or the attack overloads the incoming link.

Our system acts as a filter: it receives all traffic, blocks the attack, and passes only legitimate packets.

Who detects the attack

Strictera.

Your local traffic analyzer.

Who mitigates the attack

Strictera.

Your local protection can mitigate smaller attacks. When the analyzer signals Strictera, our system mitigates the attack.

How it works

  1. Configure routing so that traffic to the protected subnets enters Strictera infrastructure.

  2. Our analysis system monitors traffic volume against the thresholds in your monitoring objects.

  3. While no threshold is exceeded, all incoming packets are passed to your network using your chosen delivery method: an L2 connection or a GRE tunnel.

  4. When an anomaly is detected, protection drops malicious packets and passes only legitimate traffic.

  5. After the anomaly ends, filtering stops and all traffic is passed to your subnets again.

  1. Traffic goes directly to your infrastructure.

  2. Your local analyzer monitors attacks and their volume.

  3. When traffic needs to be diverted to Strictera for filtering, the analyzer sends a BGP announcement.

  4. The attacked prefixes are temporarily announced through Strictera infrastructure over BGP.

  5. Incoming traffic reaches Strictera. Our system drops malicious packets and passes legitimate ones.

  6. Clean traffic is delivered to your infrastructure using your chosen method: an L2 connection or a GRE tunnel.

  7. After the attack ends, monitoring continues for some time. If the attack does not return, the temporary announcements are withdrawn and traffic goes directly to your infrastructure again.

Connection requirements

On-Demand is available if you have your own autonomous system and IP addresses, or rent a protected IP pool from a Strictera partner.

Addresses rented from unrelated third-party operators cannot be connected.

With your own autonomous system and addresses:

  • Provide your AS number and the networks to protect. The minimum protected network size is /24.

  • (Optional) Complete the questionnaire our engineers send you if you need protection tailored to your resource. Without this questionnaire, protection uses the standard filtering rules.

  • Establish a BGP session with our autonomous system and announce the protected subnets through it.

With rented addresses:

  • Provide the IP addresses or subnets to protect. Networks smaller than /24, such as /28 or /30, can be connected.

  • (Optional) Complete the questionnaire our engineers send you if you need protection tailored to your resource. Without this questionnaire, protection uses the standard filtering rules.

  • Configure a BGP session with the Strictera partner from whom you rent the addresses.

Small networks can be connected without BGP, using a static or directly connected route.

Cloud Signaling requires your own autonomous system and subnets.

  • Tell us which traffic analysis solution your infrastructure uses. The solution must support BGP signaling.

  • Provide your AS number and the networks to protect. The minimum protected network size is /24.

  • (Optional) Complete the questionnaire our engineers send you so that we can configure protection more precisely.

  • Establish a BGP session with our autonomous system and configure BGP signaling.

Answers to common questions:

Why is it called On-Demand if traffic always passes through Strictera?

On-Demand describes when filtering takes place, rather than when traffic is routed to us.

Traffic passes through Strictera 24/7. Filtering starts only when an anomaly occurs:

  • If none of the traffic thresholds for your subnets is exceeded, all incoming traffic is passed to your infrastructure.

  • When at least one threshold is exceeded, protection drops malicious packets and passes only legitimate traffic, mitigating the attack.

How does BGP signaling differ from a permanent BGP announcement?

BGP signaling temporarily routes traffic to Strictera when local protection cannot handle an anomaly.

With a permanent announcement, all protected prefixes are always announced through our autonomous system. With BGP signaling, only attacked prefixes are announced through our autonomous system, and only during the anomaly.

For example, you have two subnets. With permanent announcements, traffic to both always passes through Strictera. With BGP signaling:

  • While there is no attack, or local protection handles it, traffic goes directly to your infrastructure.

  • If local protection cannot handle an attack against one subnet, it signals Strictera. We announce that subnet, receive and filter its traffic, and deliver clean packets. Traffic to the other subnet continues directly to you.

  • After the anomaly ends, the temporary announcement is withdrawn. Traffic to both subnets goes directly to your infrastructure again.

Clean traffic delivery methods

You can choose between two methods for delivering clean traffic to your infrastructure: an L2 connection or a GRE tunnel. The sections below explain how each method works and what you need to set it up.

We recommend an L2 connection for more stable delivery. The choice is yours.

L2 connection

What it is: a dedicated connection between your infrastructure and our mitigation infrastructure.

How it works: an L2 connection links our mitigation infrastructure to your network equipment. After filtering, clean traffic is sent through an agreed port or VLAN.

What you need: provide equipment location information and agree on connection parameters with our engineers.

If both sides are in the same data center, a cross-connect can link them. If they are at different locations, a last-mile provider is needed to connect the sites.

The required parameters depend on whether you use your own autonomous system and IP addresses or rent addresses from a Strictera partner. The questionnaires below list the information our engineers will ask for when connecting the service:

GRE tunnel

What it is: a way to deliver clean traffic over a public internet connection.

How it works: a GRE tunnel links our mitigation infrastructure to your network equipment. GRE encapsulates the original packets, adds a GRE header, and sends them to your public address. Your equipment removes the header and forwards the packets into your network.

What you need: provide a public /32 IP address for the tunnel and agree on connection parameters with our engineers.

The public /32 address is the tunnel endpoint. It must be reachable from the internet and must be outside the protected range.

The required parameters depend on whether you use your own autonomous system and IP addresses or rent addresses from a Strictera partner. The questionnaires below list the required information:

Choosing a delivery method

The table below compares L2 connections and GRE tunnels to help you choose a suitable option.

L2 connection GRE tunnel

How traffic is delivered

A dedicated connection between your infrastructure and our mitigation infrastructure.

A GRE tunnel over a public internet connection.

Physical connection

Required: directly in a data center or through a last-mile provider.

Not required.

Stability

More predictable: connection parameters are agreed in advance.

Less predictable; stability may depend on internet routes. Delays, packet loss, and session flaps are possible.

Bandwidth

Depends on the physical connection and agreed configuration.

Up to 10 Gbit/s.

Setup time

Usually 3–7 days.*

Up to 30 minutes for an emergency connection.*

*These times cover only our work after we receive all required data. Agreeing on settings or involving external contractors can take longer.

For ongoing use, we recommend an L2 connection. It uses a dedicated link and does not depend on public internet routes.

A GRE tunnel is useful when:

  • you need to connect protection while an attack is already underway;

  • a physical connection is not yet available;

  • you need a backup option, for example in case of a failure.