Advanced TCP Protection setup
Follow the steps described in the following sections to get started with Advanced TCP Protection.
Step 1 – Request initial configuration
When you get access to Advanced TCP Protection, there are no configured thresholds in your account.
Thresholds are based on your network’s individual behavior, derived from your traffic profile as monitored by Cloudflare. Defining the thresholds will effectively determine what the High, Medium, and Low sensitivities will be for your specific case.
Ask your Implementation Manager to configure initial threshold values.
Once thresholds are configured, the Implementation Manager will let you know that Advanced TCP Protection has been initialized and can be configured and enabled.
Step 2 – Add prefixes
Add the prefixes you would like to use with Advanced TCP Protection. You will be able to register prefixes that you previously onboarded to Magic Transit or a subset of these prefixes.
You cannot add unapproved prefixes to Advanced TCP Protection. Contact your account team to get help with prefix approvals.
Step 3 – (optional) Add IP addresses or prefixes to the allowlist
Add prefixes to the allowlist if their traffic should bypass Advanced TCP Protection rules.
The allowlist only applies to source IPs — it does not apply to your own IPs or prefixes. To exclude a subset of an onboarded prefix from Advanced TCP Protection, refer to Exclude a prefix or a prefix subset.
Step 4 – Create a global configuration
Create a rule for SYN Flood Protection and another rule for Out-of-state TCP Protection, both with global scope and in monitoring mode. These rules will apply to all received packets.
Step 5 – Enable Advanced TCP Protection
- In the Cloudflare dashboard, go to Account Home > L3/4 DDoS > Advanced TCP Protection.
- Under General settings, toggle the feature status to Enabled.