Protection profile rules

How to view the filtering policies configured for your resource.

Strictera engineers create and configure your protected profile. You cannot edit it yourself. To change the filtering policy, contact support and we will adjust the rules to your requirements.

What it is

Profile rules shows how the system filters traffic to your subnets and IP addresses during DDoS attacks. You can see:

  • The conditions used to check traffic: protocol, port, packet length, and other parameters.

  • The action for a matching packet: pass, drop, or TCP or DNS authentication.

  • How much traffic was filtered by a particular rule.

Where to find profile rules in the UI

Open Network protection → Protected profiles. Select the ellipsis (…) next to the profile, then Profile rules.

Open profile rules

You will see the protected profile divided into three categories:

  • Rules—groups that filter most of your traffic.

  • Chains—additional rule sets for special cases.

  • Lists—IP addresses and subnets requiring special filtering, such as the black list and white list.

Each category is described in detail below.

Rules

This category shows the groups that filter most of your traffic.

Rule group types

Each group has a purpose: for example, allowing traffic from white-listed addresses or dropping traffic that exceeds a limit.

The list depends on your protected profile. Our engineers configure the profile individually for each customer, taking your traffic characteristics and the information in your connection questionnaire into account. Therefore, group names, contents, and the rules inside them can differ from the description below.

For example, the group list may look like this:

Rule groups

Select a group name to view:

  • the filtering rules it contains;

  • charts showing how much traffic was filtered by a particular rule in the group.

Below are examples of groups and the tasks they perform. They will help you understand the filtering logic, even if the groups in your profile have different names.

Group Purpose How it works Example

WHITELIST

Disable filtering for trusted addresses.

Checks whether the source is on the white list. If so, passes the packet to the resource without checks.

A packet from white-listed 192.0.2.15 is passed.

BLACKLIST

Block addresses that must not access your resource.

Checks whether the source is on the black list. If so, drops the packet.

A packet from black-listed 198.51.100.7 is dropped.

GOTO CHAIN

Send traffic to a chain.

Redirects matching packets to the specified chain. Without conditions, redirects all traffic that reaches the group.

A packet not handled by WHITELIST or BLACKLIST is redirected to monitoring.

UAD TRIGGER

Protect against botnets.

  1. We maintain a list of IP addresses used in botnet attacks.

  2. We monitor traffic from them to subnets and addresses linked to your protected profile.

  3. When traffic exceeds the rule threshold, packets are redirected to a dedicated chain of countermeasures for traffic typical of particular botnets.

The list and countermeasures are not disclosed and are not shown in the UI.

Traffic from listed botnet addresses exceeds 7,000 packets per second and is redirected to the mitigation chain.

ACL

Drop traffic that your services do not expect.

We create the ACL (Access Control List) from the information in your connection questionnaire. It describes:

  • Which services use which IP addresses.

  • Their protocols.

  • Source ports.

  • Destination ports.

Traffic outside this map is dropped because the resource does not expect it.

A UDP packet reaches port 53 of web server 203.0.113.10, which expects only TCP on ports 80 and 443. The packet is dropped.

BASE RULES

Stop common L3/L4 attacks and malformed traffic.

Checks for fragmentation, invalid packet parameters, and signs of flood and amplification attacks. See standard filtering rules.

A fragmented packet is dropped.

TCP AND DNS AUTH

Stop sources that cannot authenticate.

Sends traffic for TCP or DNS authentication. Successful sources are remembered for a time and are not checked again. Traffic from unsuccessful sources is dropped.

A UDP packet to port 53 is sent for DNS authentication.

RATELIMITS

Limit traffic that exceeds configured thresholds.

Limits can apply to each source IP, each destination IP, or the whole protected profile. Packets over the limit are dropped, and the source IP can be blocked temporarily.

With a limit of 2,000 UDP packets per second per source, 203.0.113.40 attempts 5,000 packets in a second. The address is blocked for 300 seconds.

Groups check each packet from top to bottom, in the order shown in the UI. If two groups conflict, the first matching group takes precedence. For example, if WHITELIST is above RATELIMITS, white-listed traffic passes even if it exceeds the limit.

Rule contents

The table shows the rules the system uses to filter traffic.

Base filtering rules

Each rule has two parts:

  • Rules—the conditions that traffic must match.

  • Actions—what happens when the conditions match.

For example, frag:, counter: IP_FRAG, Drop means: if an incoming IP packet is fragmented, label it IP_FRAG and drop it.

What is a label?

A label identifies which rule filtered a packet. For example, a fragmented packet is dropped and the statistics record one more packet with the IP_FRAG label.

The system uses these records to build charts showing how much traffic received a label and was therefore filtered by a particular rule.

A label does not always mean blocking. WHITELIST marks traffic passed from white-listed addresses. DNS_AUTH marks traffic sent for DNS authentication. Ordinary user traffic that is passed to your resource and is not white-listed has no separate label.

For label descriptions, see Protected profile traffic statistics.

Some rules work together:

Rules Actions

icmp: echo_reply

Allowed

icmp: echo_request

Allowed

protocol: icmp Except Allowed

counter: ACL_ICMP

Drop

Together, these rules allow ping requests (echo_request) and replies (echo_reply), then label all other ICMP traffic ACL_ICMP and drop it.

Allowed does not automatically pass a packet to your resource. It marks the packet as allowed and continues checking it against later rules.

A table row can contain several related rules. In this case, the number of rules is shown, for example 5 rules. You can expand this row.

An expandable rule group

Condition types

Conditions usually use parameter: value notation. For example, protocol: udp means UDP traffic. With several parameters, traffic must match all of them: protocol: udp dst: 53 means UDP traffic to destination port 53.

The table below lists the possible conditions.

Condition Meaning Examples or values

list

The list used by the rule.

whitelist, blacklist

src

Source IP address or port.

192.0.2.15/32, 0-1023

dst

Destination IP address or port.

198.51.100.21/32, 443

port

Source or destination port, regardless of direction.

53

protocol

Packet protocol.

One protocol, such as tcp, or a comma-separated list: udp,tcp,icmp.

len

Packet length in bytes.

76, 100-1500

Except <condition>

All traffic except traffic matching the condition.

Except len: 76.

frag

A fragmented IP packet.

frag:

tcpflags

TCP flags.

Possible values:

  • syn—synchronization flag;

  • ack—acknowledgment flag;

  • fin—connection termination flag;

  • rst—connection reset flag;

  • psh—push data flag;

  • urg—urgent data flag;

  • ece—ECN-Echo flag;

  • cwr—congestion window reduced flag.

The flags in a rule can be written as one flag (syn), several comma-separated flags (syn,ack), or a value/mask pair (syn/syn,ack).

More details

If one or more flags are specified, the rule checks that every listed flag is set in the packet.

For example:

  • syn—checks that syn is set;

  • syn,ack—checks that both syn and ack are set.

If a value/mask pair is specified, the right side of the slash lists the flags the rule checks, and the left side lists those that must be set.

For example, syn/syn,ack means the rule checks both syn and ack. The syn flag must be set, and ack must not be set.

The mask can be all. For example, syn/all means the rule checks all TCP flags, but only syn must be set.

icmp

ICMP message type.

  • echo_request—host availability request.

  • echo_reply—reply to an availability request.

  • unreach—destination host or service unreachable.

  • redirect—redirect traffic through another gateway.

Except Allowed

Traffic not allowed by earlier rules.

Except Allowed

bps

Traffic volume threshold in bits per second.

35000000, 800000000

pps

Packet count threshold in packets per second.

50, 2000

limitType

How the limit applies.

  • SOURCE_LIMIT—per source IP address.

  • HOST_LIMIT—per destination IP address.

  • PROFILE_LIMIT—all traffic of the protected profile.

  • BANDWIDTH_LIMIT—the protected profile’s total bandwidth.

syn

Source authentication for a TCP SYN packet.

  • hs—the system initiates a full three-way handshake with the source. If the source responds correctly and the connection is established, the system resets it with RST and considers authentication successful.

  • greylist—the system drops all SYN and SYN-ACK packets from the source for 10 seconds, then waits 30 seconds for another packet. A retry during this interval passes authentication.

  • synack—the system replies to SYN with SYN-ACK and waits for RST from the source. Receiving RST completes authentication.

  • none—no authentication.

synAck

Source authentication for a TCP SYN-ACK packet.

  • hs—the system initiates a full three-way TCP handshake with the source. If the source responds correctly and the connection is established, the system resets it with RST and considers authentication successful.

  • greylist—the system drops all SYN and SYN-ACK packets from the source for 10 seconds, then waits 30 seconds for another packet. A retry during this interval passes authentication.

  • none—no authentication.

except recorded

Do not recheck a source that recently passed TCP or DNS authentication. authtime is how long the system remembers it, in seconds.

except recorded: authtime 3600

asn

The autonomous system number of the source IP address.

64496

geoip

Source country or continent.

DE, FR, GB

seq

Byte sequence in the packet contents.

\x35, \x00

Action types

This shows what the system does with traffic when a rule matches. For example, it can allow or drop a packet, send it for authentication, or redirect it to another chain.

Action Effect

Accepted

Pass the packet to your resource.

Drop

Drop the packet.

Allowed

Mark the packet as allowed and continue checking later rules. Rules with Except Allowed apply only to traffic that earlier rules did not allow. For example, first mark TCP traffic as allowed, then drop all other packets.

Redirect to <chain name>

Send the packet to the named chain for further checks.

TCP authentication

Send TCP traffic for additional authentication.

DNS authentication

Send DNS traffic for additional authentication.

Temporary block for N sec.

Block the source address for the specified time.

Record source

Remember the source address. This action does not itself change traffic processing. Other rules use the record, for example to avoid authenticating a source again while the record is valid. A retention period can appear next to the action: "Record source for N seconds".

Record source and drop

Remember the source address and drop the current packet.

Bandwidth limit

Drop traffic over the limit set by bps, pps, and limitType.

Statistics charts

Charts show the traffic filtered by particular rules in bits per second (bps) or packets per second (pps).

Charts include only rules with labels. Rules without labels do not contribute data here.
Authentication rule statistics

By default, charts cover the last seven days. Select Last 7 days and choose the required period. Select the refresh icon next to the period to configure auto-refresh: off, 10 or 30 seconds, 5, 10, 15, or 30 minutes, or one hour.

The legend on the right lists labels. Select a label to show or hide its chart.

What does “No available statistics” mean instead of a chart?

There is no data for the selected rule group and period. Two causes are possible:

  1. The rules have no labels. If the Actions column has no counters with statistic labels, there is nothing to show on a chart.

  2. The rules did not run during the period. Profile rules filter traffic during an attack. If filtering was not used, no chart data is available. Try a longer period.

If the problem continues, contact support.

Chains

Chains are additional rule sets for special cases:

  1. A packet passes through the main rules.

  2. A main rule redirects it to a named chain.

  3. The packet is checked by the chain’s additional rules.

  4. The chain passes, drops, or authenticates the packet.

For example, monitoring is a service chain. During connection setup, we pass all your traffic through it to determine the detection thresholds. After protection is configured, this chain is no longer used.

For a selected chain, the chart shows how much traffic passed through it and the table shows its rules. Read these in the same way as the main rules.

Other chains are configured for your resource’s needs. Contact support to learn what a particular chain does.

Lists

Lists contain IP addresses and subnets that need special filtering. Your profile can contain:

A list does not act on traffic itself. A rule refers to it as a condition and applies an action. For example, a rule checks whether the source is white-listed and passes matching traffic to the resource.

Select a list name to view its entries.

An IP address list