Understand the traffic that belongs.
A game server, an API and a public website have different traffic patterns. Start with your protocols, normal peaks and previous incidents so we can discuss protection in the context of the service.
04 / DDoS protection
Keep the noise
out of the way.
Plan protection around the traffic your service should receive—and the disruption it needs to withstand.
Discuss protectionPermitted pathStopped at the filter
- AssessInspect incoming traffic
- FilterApply agreed controls
- RoutePass permitted traffic
Illustrative filtering. Coverage, controls and thresholds follow your service.
Your configuration
Make it your configuration.
- Scope
- Protected resources and attack layers
- Capacity
- Applicable thresholds confirmed in the proposal
- Response
- Filtering, escalation and protective measures
- Boundaries
- Exclusions and application responsibilities
Scope confirmed per serviceScope, price and timing confirmed in your proposal.
Set the protection boundary.
Identify the resources, attack layers and locations to be covered. The proposal sets out applicable thresholds, supported protocols and exclusions. Protection has technical limits; it cannot promise uninterrupted service under every attack.
Agree the response before the incident.
Filtering, rate limiting and escalation need a defined operating path. In severe cases, protective action may include temporary null-routing. Your service terms explain the available mitigation and notification arrangements.
Secure the application behind the network.
Network protection is one layer. Patching, access control and application security remain part of running a resilient service. Build those responsibilities into the same operating plan.
Before you begin
Before you
make your move.
Is DDoS protection available in every location?+
Coverage is confirmed for the specific service and location. Ask us to identify the included protection and any additional options in your proposal.
What happens during a large attack?+
The response depends on the service, attack and infrastructure risk. Review the agreed filtering, escalation and protective measures, together with any contracted SLA and remedies.
The next step
Define the traffic
you need to protect.
Share the protocols, normal load and any previous attack patterns. We will assess the available coverage and agree the protection boundary for your service.
Discuss protection requirements