|
| 1 | +--- |
| 2 | +title: Managed DDoS Protection |
| 3 | +sidebar_label: DDoS Protection |
| 4 | +--- |
| 5 | + |
| 6 | +Zuplo provides automatic DDoS (Distributed Denial of Service) protection for all |
| 7 | +APIs deployed on the platform. This service detects and mitigates attacks in |
| 8 | +real-time, ensuring your APIs remain available even under attack. |
| 9 | + |
| 10 | +:::note |
| 11 | + |
| 12 | +Zuplo Managed DDoS is only available for customers using Zuplo's managed edge |
| 13 | +deployment model. Customers using managed dedicated deployments should refer to |
| 14 | +the |
| 15 | +[Managed Dedicated WAF Options](./zuplo-waf.mdx#managed-dedicated-waf-options) |
| 16 | +document. |
| 17 | + |
| 18 | +::: |
| 19 | + |
| 20 | +## What is DDoS? |
| 21 | + |
| 22 | +DDoS attacks attempt to overwhelm your API by flooding it with malicious traffic |
| 23 | +from multiple sources. Zuplo's protection covers both: |
| 24 | + |
| 25 | +- **Network Layer Attacks (Layer 3/4)**: UDP floods, SYN floods, and other |
| 26 | + network-level attacks |
| 27 | +- **Application Layer Attacks (Layer 7)**: HTTP floods, slowloris, and other |
| 28 | + application-level attacks |
| 29 | + |
| 30 | +## Key Benefits |
| 31 | + |
| 32 | +- **Always-On**: Protection is automatic from deployment—no configuration needed |
| 33 | +- **Multi-Layer Defense**: Covers both network and application layer attacks |
| 34 | +- **Unmetered Protection**: No bandwidth limits during attacks |
| 35 | +- **Adaptive**: Continuously updated to handle new attack patterns |
| 36 | +- **Minimal False Positives**: Smart detection reduces blocking of legitimate |
| 37 | + traffic |
| 38 | +- **Avoid Unexpected Costs**: Zuplo never charges for requests that are blocked |
| 39 | + by DDoS protection protecting you from unexpected overage fees. |
| 40 | + |
| 41 | +## Protection Levels |
| 42 | + |
| 43 | +Zuplo offers different sensitivity levels for DDoS protection, allowing you to |
| 44 | +balance security with accessibility based on your specific needs. |
| 45 | + |
| 46 | +### Working Copy Environments |
| 47 | + |
| 48 | +All Working Copy environments (`.zuplo.dev` domains) are automatically protected |
| 49 | +with **Medium** sensitivity. This provides robust protection while minimizing |
| 50 | +the risk of blocking legitimate traffic during development and testing. |
| 51 | + |
| 52 | +### Preview and Production Environments |
| 53 | + |
| 54 | +Preview and production deployments benefit from advanced DDoS protection |
| 55 | +capabilities: |
| 56 | + |
| 57 | +- **Default Setting**: Medium sensitivity (balanced protection) |
| 58 | +- **Enterprise Customization**: Optional enterprise add-on allowing |
| 59 | + configuration of protection levels |
| 60 | + |
| 61 | +### Sensitivity Levels Explained |
| 62 | + |
| 63 | +Enterprise customers with the DDoS customization add-on can choose from four |
| 64 | +sensitivity levels: |
| 65 | + |
| 66 | +#### High Sensitivity |
| 67 | + |
| 68 | +- Most aggressive protection with the lowest threshold for triggering mitigation |
| 69 | +- Ideal for APIs that face frequent attacks or handle highly sensitive data |
| 70 | +- May occasionally block legitimate traffic during unusual usage patterns |
| 71 | + |
| 72 | +#### Medium Sensitivity (Default) |
| 73 | + |
| 74 | +- Balanced approach providing strong protection with moderate thresholds |
| 75 | +- Recommended for most production APIs |
| 76 | +- Optimizes for both security and accessibility |
| 77 | + |
| 78 | +#### Low Sensitivity |
| 79 | + |
| 80 | +- Higher threshold for triggering mitigation |
| 81 | +- Suitable for APIs with highly variable traffic patterns |
| 82 | +- Reduces false positives for legitimate traffic spikes |
| 83 | + |
| 84 | +#### Essentially Off |
| 85 | + |
| 86 | +- Minimal protection with the highest threshold |
| 87 | +- Protection still activates for extremely large attacks to maintain network |
| 88 | + stability |
| 89 | +- Recommended only when you have alternative DDoS protection mechanisms. |
| 90 | + |
| 91 | +## How Protection Works |
| 92 | + |
| 93 | +### Detection |
| 94 | + |
| 95 | +Zuplo's DDoS protection uses sophisticated algorithms to analyze traffic |
| 96 | +patterns in real-time. The system examines multiple factors including: |
| 97 | + |
| 98 | +- Request rates and patterns |
| 99 | +- Source IP reputation |
| 100 | +- Geographic distribution |
| 101 | +- Protocol compliance |
| 102 | +- Behavioral anomalies |
| 103 | + |
| 104 | +### Mitigation |
| 105 | + |
| 106 | +When an attack is detected, the system automatically applies appropriate |
| 107 | +mitigation techniques: |
| 108 | + |
| 109 | +1. **Traffic Filtering**: Malicious traffic is filtered at the edge before |
| 110 | + reaching your API |
| 111 | +2. **Rate Limiting**: Excessive requests from suspicious sources are throttled |
| 112 | +3. **Connection Management**: Advanced TCP protection handles sophisticated |
| 113 | + connection-based attacks |
| 114 | + |
| 115 | +### Continuous Improvement |
| 116 | + |
| 117 | +The protection system continuously evolves: |
| 118 | + |
| 119 | +- Managed rulesets are regularly updated |
| 120 | +- New attack patterns are incorporated into detection algorithms |
| 121 | +- Protection mechanisms adapt based on the global threat landscape |
| 122 | + |
| 123 | +## Enterprise Customization |
| 124 | + |
| 125 | +Enterprise customers can enhance their DDoS protection with: |
| 126 | + |
| 127 | +- **Custom Sensitivity Levels**: Adjust protection thresholds per environment |
| 128 | +- **Advanced Analytics**: Detailed attack reports and traffic analysis |
| 129 | +- **Custom Rule Configuration**: Tailor protection to specific traffic patterns |
| 130 | + |
| 131 | +:::tip |
| 132 | + |
| 133 | +Contact your Zuplo account team to learn more about Enterprise DDoS |
| 134 | +customization options. |
| 135 | + |
| 136 | +::: |
0 commit comments