Generic DDoS protection plan
DDoS protection planddos-protection
Vendor-neutral DDoS protection plan. Use when the real product is not in the catalogue; every rule for this kind still applies.
- Provider
- default
- Category
- Security
- Official docs
- not recorded
- Generic?
- Vendor-neutral: the kind itself
| property | type | values | required | default |
|---|---|---|---|---|
| adaptiveThresholds | boolean | — | no | — |
| alwaysOn | boolean | — | no | — |
| managed | boolean | — | no | false |
| protectedResourceCount | integer | — | no | — |
| scope | enum | network | application | both | no | — |
| telemetry | boolean | — | no | — |
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.
nodes:
- { id: "ddos-protection", component: "ddos-protection" }Anti-DDoS Originalibaba-anti-ddos-originAnti-DDoS Proalibaba-anti-ddos-proGame Shieldalibaba-game-shieldAWS Shieldaws-shieldAzure DDoS Protectionazure-ddos-protectionCloudflare DDoS Protectioncloudflare-ddos-protectionCloudflare Magic Transitcloudflare-magic-transitNETSCOUT Arbor DDoSnetscout-arborRadware DefenseProradware-defenseproDigitalOcean DDoS Protectiondigitalocean-ddos-protection
# yaml-language-server: $schema=../../schema/component.schema.json # The vendor-neutral DDoS protection plan: the kind itself, with no product behind it. It sets no # defaults and adds no properties, so every required kind property stays required on the node. schemaVersion: "1" type: "component" id: "ddos-protection" kind: "ddos-protection" provider: "default"