The attributes behind your decision
- Decision input
- Measured workload
- Primary variables
- Capacity, control, operations
- Validation
- Representative testing
- Next step
- Swiss hosting privacy
Identify the protected layer
Network filtering, transport protection and application-layer mitigation address different traffic. Ask which attacks, protocols, addresses and services are covered.
Understand detection and mitigation behavior
Confirm whether mitigation is always active or triggered, how traffic is routed, what thresholds apply and whether legitimate traffic can be affected.
Plan beyond upstream filtering
Rate limiting, caching, resilient application design, protected administrative access and incident communication remain important. DDoS protection does not fix application bottlenecks.
Request documented limits and response steps
Review capacity, exclusions, cost conditions, escalation contacts and reporting. Test the incident process where possible and avoid absolute “unlimited protection” claims.
Separate traffic filtering from application capacity
A traffic flood and an expensive application request can exhaust different resources. Network filtering may address some traffic patterns while the application still needs request limits, caching and an efficient database. Describe the workload and suspected failure mode before assuming one protection feature covers all incidents.
Ask what traffic the selected service handles, what happens during an incident, how support is contacted and which limits apply. Monitor application response time and resource saturation as well as network volume. Maintain a response plan that includes safe access, traffic changes and recovery verification.