AS216394 · WireShield

Technical Guide

Symmetric vs. Asymmetric DDoS Protection

With symmetric protection reply traffic also passes through the filtering layer; with asymmetric protection only inbound traffic is filtered. Learn the differences, the trade-offs and how to choose.

Symmetric vs. asymmetric DDoS protection: how inbound and outbound traffic is routed

When choosing DDoS protection, one question is often skipped: is filtering inbound traffic enough, or does the protection need to see outbound traffic too? Yet this question decides which attacks the protection stops, and how precisely. The answer depends on the paths traffic takes into and out of your network: symmetric or asymmetric?

What do symmetric and asymmetric traffic mean?

A connection has two directions: requests coming to you and replies leaving you. In DDoS protection, the question is which of these directions the filtering layer sees.

  • Asymmetric: Inbound traffic passes through the filtering layer; your replies leave your network directly to the Internet.
  • Symmetric: Both inbound traffic and your replies pass through the filtering layer.

This difference decides whether the protection layer can tell if a packet is "part of a conversation your network started" or "traffic nobody asked for".

How does asymmetric DDoS protection work?

With asymmetric protection the layer sees only inbound traffic. Each packet is inspected on its own and decided by rules, thresholds and filters. This approach works with tools such as:

  • Rate limiters and thresholds
  • Spoofed-source filtering and invalid TCP flag checks
  • An amplification filter for known reflector source ports
  • SYN validation
  • Country/ASN policies, threat-intelligence feeds and signature rules

Advantage: It is simple to set up and needs no change to your routing; your reply traffic leaves by its usual path. For many hosting providers, ISPs and enterprise networks this is the starting point.

Limit: Because the layer does not see the reply direction, it cannot know whether a packet answers a connection your network started. Reflection and spoofed floods that a single packet does not reveal need dedicated filters, which means rules must be tuned more carefully. We explained why these attacks are hard to tell apart in our UDP flood guide.

How does symmetric DDoS protection work?

With symmetric protection your replies pass through the filtering layer too, so the layer knows which connections your network started. Inbound traffic is allowed through only when:

  • It answers a connection your network started,
  • It goes to a service you listed (for TCP, only the SYN of a new connection),
  • It is ping, if you allow it, or a required ICMP message (unreachable, time exceeded, PMTUD).

Everything else is dropped as "nobody asked for this". The result: reflection and spoofed floods that no single packet reveals stop on their own, because nobody requested that traffic.

Tip: To avoid cutting legitimate traffic because a service was missing from the list, run symmetric protection in Monitor mode first and review the "would drop" counters. For details see the prefix modes on the Technology page.

Comparison

Asymmetric protectionSymmetric protection
Traffic through the filterInbound onlyInbound and outbound
Reply trafficLeaves your network directlyPasses through the protection layer
SetupSimple, little routing changeThe reply path must be arranged
Reflection and spoofed floodsStopped with rules and filtersDropped naturally using conversation state
Service listNot neededServices open to the Internet are defined
Fits whenMany or changing services, complex routingPrefixes serving a few well-known services

Which should you choose?

  • Few, well-known services open to the Internet (web, DNS, a few game or VPN ports)? Symmetric protection is very precise.
  • Many services, or services that change often? Asymmetric protection keeps management easy.
  • Hard to route reply traffic through the protection? Start with asymmetric.
  • Want visibility of both requests and replies? Symmetric is preferred.

The choice for a prefix can change over time; many networks start asymmetric and move to symmetric as the need appears.

Symmetric and asymmetric protection in WireShield

WireShield supports both approaches. With remote DDoS protection and on-site (inline) protection with WireShield Edge, you choose the one that fits your network. Symmetric protection is set per prefix; in Always On mode filters always apply, in Automatic mode only during an attack, and in Monitor mode they only count. If no reply traffic has been seen yet, traffic is not cut: protection waits until it sees reply traffic. How each option is set up in your network is decided together in the technical assessment.

For more, see the traffic path section on the Technology page and the protection options guide in the documentation. For a general comparison of the two protection models, read our inline vs. remote post.

Common mistakes

  • Enabling symmetric protection before reply traffic passes through the protection.
  • Forgetting to list a service open to the Internet and cutting legitimate traffic.
  • Moving straight to enforce mode without trying Monitor mode first.
  • Looking only at bps with asymmetric protection and not tuning rules and thresholds.

Frequently asked questions

Is symmetric protection better than asymmetric?

Not better, different. Symmetric drops reflection and spoofed attacks naturally thanks to conversation state, but needs a service list and a reply path. Asymmetric is simpler to set up but needs rules to be tuned more carefully.

Does asymmetric protection stop reflection attacks?

Yes, with an amplification filter and source-port rules. But not every reflection type can be told apart by a single packet, so correctly tuned thresholds and rules matter.

Can I use both for one prefix?

The choice is per prefix. Different prefixes can use different approaches.

How do I find out which fits my network?

Knowing your topology, the services you offer and the path of your reply traffic is enough; we decide together in the technical assessment.

Next step

Share your topology and the services you offer and we will choose the right approach together. Talk to the technical team or request an Edge assessment.

All posts

Let’s review the right protection model for your network together.

Contact our team to talk through your technical needs.