1. Buffer overflow attack
2. Ping of Death or ICMP flood attack
3. Teardrop attack
These are the typical consequences that DDoS and DoS cause:
SYN Flood:
SYN Flood exploits a weakness in the TCP connection chain, known as the three-way handshake. The server will receive a synchronization message (SYN) to initiate the "handshake". The server receives the message by sending an acknowledgment (ACK) flag to the originating host, then closes the connection. However, in a SYN Flood, spoofed messages are sent and the connection is not closed => the service crashes.
UDP Flood:
User Datagram Protocol (UDP) is a sessionless network protocol. A UDP Flood targets random ports on a computer or network with UDP packets. The server checks for applications at those ports but finds none.
HTTP Flood:
HTTP Floods are almost like legitimate GET or POST requests exploited by a hacker. It uses less bandwidth than other types of attacks but it can force the server to use maximum resources.
Ping of Death:
Ping of Death manipulates IP protocols by sending malicious code to a system. This type of DDoS was popular two decades ago but is no longer effective today.
Smurf Attack:
Smurf Attack exploits Internet Protocol (IP) and ICMP (Internet Control Message Protocol) using a malware program called smurf. It spoofs an IP address and uses ICMP, then pings IP addresses on a given network.
Fraggle Attack:
Fraggle Attack uses a large amount of UDP traffic to the router's broadcast network. It's like a Smurf attack, using UDP more than ICMP.
Slowloris:
Slowloris allows attackers to use minimal resources in an attack and target web servers. Once connected to the desired target, Slowloris keeps that link open as long as possible with HTTP flooding. This type of attack has been used in several high-profile hacktivist DDoSings, including the 2009 Iranian presidential election. Mitigating the impact of this type of attack is critical. hard.
Application Level Attacks:
Application Level Attacks exploit vulnerabilities in applications. The target of this type of attack is not the entire server, but applications with known weaknesses.
NTP Amplification:
NTPAmplification exploits NTP (Network Time Protocol) servers, a protocol used to synchronize network time, to flood UDP traffic. This is an amplified reflection attack. In any reflection attack, there will be a response from the server to the fake IP. When amplified, the response from the server will no longer match the original request. Because it uses large bandwidth when suffering from DDoS, this type of attack is highly destructive and volumne.
Advanced Persistent DoS (APDoS):
Advanced Persistent DoS (APDoS) is a type of attack used by hackers hoping to cause serious damage. It uses many of the attacks mentioned previously (HTTP Flood, SYN Flood, etc.) and is typically aimed at sending millions of requests/second. APDoS attacks can last for weeks, depending on the hacker's ability to switch tactics at any time and create variety to avoid security protections.
Zero-day DDoS Attacks:
Zero-day DDoS Attacks is the name given to new DDoS attack methods that exploit unpatched vulnerabilities.
HTTP GET
HTTP GET is an application layer attack, smaller in scale and more targeted. Application Level Attacks exploit vulnerabilities in applications. The target of this type of attack is not the entire server, but applications with known weaknesses.
This type of attack will target Layer 7 of the OSI model. This is the layer with the highest network traffic, instead of targeting the third layer that is often chosen as the target in Bulk Volumetric attacks. HTTP GET exploits the submission process of some web browser or HTTP application and requests an application or server for each HTTP request, which is either a GET or POST.
HTTP Floods are almost like legitimate GET or POST requests exploited by a hacker. It uses less bandwidth than other types of attacks but it can force the server to use maximum resources. This type of attack is difficult to defend against because they use standard URL requests, rather than corrupted or high-volume scripts.
There really is no specific way to avoid becoming a victim of DoS or DDoS. However, we will introduce you to a few steps with the aim of somewhat reducing the type of attack that will use your computer to attack other computers.
Install and maintain anti-virus software.
Install a firewall and configure it to limit traffic to and from your computer.
Follow safe practice guidelines for distributing your email addresses.
Use email filters to help you manage unwanted traffic.
Specifically, for a data center, for example, the following preventive measures should be implemented:
ISPs often have DDoS protection at layers 3 and 4 (network traffic), but ignore Layer 7, which is more targeted, and overall the uniformity of protection layers is not good. ensure.
Companies handle DDoS: they use their existing infrastructure to fight any threat that comes their way. Typically, this is done through a load balancer, a content delivery network (CDN), or a combination of both. Smaller websites and services can outsource to third parties if they do not have the capital to maintain a bunch of servers.
Anti-DDoS service providers are always available. Typically, they will reroute your incoming traffic through their own system and "scrubbing" it against known attack methods. They can scan for suspicious traffic from sources or from uncommon geolocations. Or they can also reroute your legitimate traffic away from botnet sources.
Most modern firewalls and Intrusion Protection Systems (IPS) provide defense against DDoS attacks. These devices can take the form of a single device that scans all traffic to the system or software distributed at the server level. Dedicated anti-DDoS applications are also available on the market and can provide better protection against attacks targeting Layer 7.
Regularly scanning your network and monitoring traffic with alerts can also help you catch the risks of a DDoS attack early, as well as take action to minimize the damage.
Not every complete failure of service is the result of a denial of service attack. There are many technical problems with a network or with the administrators performing maintenance and management. However, with the following symptoms you can recognize a DoS or DDoS attack:
Unusually slow network performance (opening files or accessing websites)
If you can't access the website, you still look at it
Cannot access any website
The number of letters has increased dramatically in your account.
Even if you correctly identify a DoS or DDoS attack, you cannot identify the source or destination of the attack. Therefore, you should contact technical experts for support.
If you find that you cannot access your own files or any external websites from your computer, you should contact the network administrator of that network. This could indicate whether your computer or your organization's network is under attack.
If you notice problems with your computer, contact your service provider (ISP). If there are problems, your ISP can advise you on appropriate actions.
When you have a DDoS protection system in place, the first step to take is to identify attack vectors and critical applications. Which port is open? What bandwidth is available for you to use? Where is there likely to be network congestion? Which critical systems require additional protection?
Pay extra attention to areas of vulnerability based on dependencies on other systems in your infrastructure, for example central databases that may remove functionality for some applications in case it gets overloaded.
There are many open source software tools you can use to test mitigation from DDoS, as well as hardware options that can reach multi-gigabit throughput levels. However, hardware options will be a costly solution. Instead, a professional white hat security company can provide you with testing as an optional service.
DDoS attacks will certainly cause a lot of trouble, but with careful preparation, you can be ready to prevent or come up with solutions quickly, thereby avoiding disruptions. services for users while significantly minimizing the damage caused by DDoS.