Basic protection
Basic protection is applied automatically to all Gcore-hosted resources. No additional enrollment or network submission is required.Access control list (ACL) rules
Basic protection uses a predefined access control list (ACL) to filter incoming traffic. The rules target two common attack methods: reflection attacks and IP spoofing.- Reflection attacks. Attackers use third-party servers to send large volumes of responses to the target. The ACL filters traffic associated with known reflection attacks using DNS, NTP, SSDP, MSSQL, LDAP, SNMP, CharGen, Memcache, Echo, RIP, and ARMS.
- IP spoofing. Attackers forge source IP addresses to hide where traffic originates. The ACL blocks packets with source addresses from the following ranges, which should not appear as sources of traffic from the public internet:
0.0.0.0/32,127.0.0.0/8,192.0.2.0/24,224.0.0.0/3,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16.
Null-routing
When an attack exceeds the allowable incoming-traffic threshold, Basic protection null-routes the targeted IP address for 12 hours. During that time the address is unreachable from the internet, including for legitimate traffic.Advanced protection
Unlike the 12-hour block, Advanced protection leaves the address reachable. Traffic passes through the Threat Mitigation System (TMS) at all times, and TMS drops malicious traffic while forwarding legitimate traffic. Advanced protection requires a routable IPv4 prefix of /24 or larger that the customer controls and originates from an ASN. The prefix does not have to be owned outright, and Gcore announces it only with authorization to do so. Incoming traffic first reaches Gcore’s TMS. Gcore directs it there by announcing the protected network prefixes through Border Gateway Protocol (BGP). After filtering, TMS forwards legitimate traffic through a GRE tunnel to an address on the customer’s router. This GRE endpoint is not a Gcore-assigned protected IP. Outgoing traffic follows a separate path and continues to use the network’s existing default gateway.Protection profiles
BGP and GRE determine how traffic reaches and leaves TMS. A protection profile determines how TMS handles that traffic. Each profile contains rules that define which traffic to filter and what action to take. Rules can match TCP, UDP, or ICMP traffic. When traffic matches a rule, TMS applies the specified action: drop the traffic or forward it to the protected network.Allowlists
To prevent legitimate traffic from partner systems, monitoring services, and other trusted sources from being mistakenly blocked, their IP addresses can be added to an allowlist.- Enterprise plans: Traffic from allowlisted IP addresses bypasses DDoS analysis and is not inspected by TMS.
- Public plans: Traffic from allowlisted IP addresses remains subject to DDoS filtering.
Other paths
An individual TCP or UDP service without a routable prefix uses Edge Proxy. Edge Proxy assigns a Gcore Anycast address, forwards traffic to an origin IP and port, and does not use an ASN, a BGP session, or a GRE tunnel.Bare Metal servers and dedicated servers use separate procedures. Advanced protection on those servers detects an attack within 5 seconds.