Cloudflare DDoS Protection

cloudflare DDoS protection plancloudflare-ddos-protection

Always-on HTTP and network-layer DDoS managed rulesets applied automatically to every zone and prefix.

Provider: cloudflare
Kind: DDoS protection plan
Category: Security
Official docs: https://developers.cloudflare.com/ddos-protection/managed-rulesets/http/

Properties · 4 set by this component

property	type	values	required	kind default	this component
adaptiveThresholds	boolean	—	no	—	inherited
advancedDdosProtection · component property	boolean	—	no	false	inherited
alwaysOn	boolean	—	no	—	▸ true
managed	boolean	—	no	false	▸ true
mitigationAction · component property	enum	block \| managed-challenge \| force-connection-close \| log	no	—	inherited
originErrorRateThreshold · component property	integer	—	no	1000	inherited
protectedResourceCount	integer	—	no	—	inherited
scope	enum	network \| application \| both	no	—	▸ both
sensitivity · component property	enum	high \| medium \| low \| essentially-off	no	high	inherited
telemetry	boolean	—	no	—	▸ true

Rules that apply · 0

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

No rule reads this kind yet. That is a gap, not a guarantee.

Use it in a design

nodes:
  - { id: "ddos-protection", component: "cloudflare-ddos-protection" }

Other DDoS protection plan products · 10

Anti-DDoS Originalibaba-anti-ddos-originalibabacloudddos-protection Anti-DDoS Proalibaba-anti-ddos-proalibabacloudddos-protection Game Shieldalibaba-game-shieldalibabacloudddos-protection AWS Shieldaws-shieldawsddos-protection Azure DDoS Protectionazure-ddos-protectionazureddos-protection Cloudflare Magic Transitcloudflare-magic-transitcloudflareddos-protection Generic DDoS protection planddos-protectionddos-protection NETSCOUT Arbor DDoSnetscout-arborddos-protection Radware DefenseProradware-defenseproddos-protection DigitalOcean DDoS Protectiondigitalocean-ddos-protectiondigitaloceanddos-protection

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Cloudflare DDoS Protection: the HTTP and network-layer managed rulesets are always enabled for
3# every zone and prefix ("HTTP DDoS Attack Protection managed ruleset"); rule sensitivity defaults
4# to high and the origin-error rule trips at 1,000 errors per second.
5schemaVersion: "1"
6type: "component"
7id: "cloudflare-ddos-protection"
8kind: "ddos-protection"
9provider: "cloudflare"
10docs: "https://developers.cloudflare.com/ddos-protection/managed-rulesets/http/"
11defaults:
12  managed: true
13  scope: "both"
14  alwaysOn: true
15  telemetry: true
16properties:
17  sensitivity:
18    type: "enum"
19    values: ["high", "medium", "low", "essentially-off"]
20    default: "high"
21  mitigationAction:
22    type: "enum"
23    values: ["block", "managed-challenge", "force-connection-close", "log"]
24  originErrorRateThreshold:
25    type: "integer"
26    default: 1000
27  advancedDdosProtection:
28    type: "boolean"
29    default: false

The same page as markdown, for an agent: /catalogue/components/cloudflare-ddos-protection.md