coltplatinum.Home

DDoS Mitigation

Reduce the impact of attacks aimed at overwhelming your service.

Distributed Denial of Service (DDoS) mitigation filters attack traffic according to the variant. For critical public services, review exposure and legitimate traffic.

It does not replace a firewall, WAF, vulnerability management or application redundancy.

Let’s talk
Conceptual scene with business buildings and differentiated traffic flows; it does not depict an actual route or facility.

How it works

Keep public services reachable when traffic becomes a threat.

Different types of traffic arrive at a mitigation point; the blue flow continues to services in this conceptual example.
InternetDDoS mitigationYour services

Define what we protect

Identify public addresses, services and normal traffic. The variant determines volumetric, protocol and application coverage and integration with Internet access.

Not every peak is an attack. Agree thresholds, exceptions and contacts so a legitimate sales campaign is not confused with hostile traffic.

Different types of traffic arrive at a mitigation point; the blue flow continues to services in this conceptual example.
InternetDDoS mitigationYour services

Separate the attack from useful traffic

Detection starts automatic mitigation. Colt access can use in-network protection; off-net designs need eligible prefixes and a GRE path returning cleaned traffic.

Check that legitimate users can complete transactions, not only that attack volume falls. SOC assistance depends on the variant.

Different types of traffic arrive at a mitigation point; the blue flow continues to services in this conceptual example.
InternetDDoS mitigationYour services

The application must recover too

After mitigation, review availability, errors and server saturation. Cleaning traffic does not restart a failed application or database, or restore its data.

Define network and application owners, escalation and incident review: what was blocked, what passed and which policy needs adjustment.

Illustrative case: from situation to decision

Situation
Traffic rises during a campaign and users cannot complete transactions.
Option
Distinguish legitimate demand from attack traffic; apply mitigation for the protected exposure.
Check
Check that legitimate users can work and that the application, firewall and access handle remaining traffic.

Mitigation does not replace a firewall, WAF, vulnerability remediation or application high availability.

Decisions for your project

Public scope
IPs, prefixes, DNS and exposed services; on-net or off-net variant.
Detection and exceptions
Normal profile, legitimate peaks, attack vectors and filtering policy.
Coordinated response
SOC variant, contacts, user tests and application recovery.

From design to operation

Inventory exposure, agree protection and rehearse response without generating production attacks.

Complements, alternatives and variants

Colt IP AccessComplementIntegrates connectivity and public-access protection.Managed FirewallComplementControls permissions and sessions after mitigation.

Product sources

Back to top