New Member
1 POST & 0 LIKES
|
Post by account_disabled on Mar 13, 2024 23:28:30 GMT -8
Is assessed a small margin is taken and countermeasures are selected so as to protect an individual client without falling down. It is important to understand that any typical hosting is under DDoS attack almost at least one client is under attack at any given time. Therefore DDoS for us is even somewhat banal. Over years we have seen a lot of things and in principle we know the key and not only patterns . Good evening On September closer to we were hit by another DDoS which we know what to do with. They recaptured and went to rest. Before I had time to finish my tea the attack was repeated then again and then again. Each time Buy Email List the interval decreased and the volume increased. Screenshot from StormWall at that moment Next for those who like a brief summary I will list the causeandeffect relationship that arose in the infrastructure. More is poured into the site than it can handle routers are overloaded until signaling is lost we block the attack via OOB via RTBHFS or switch the network to a thirdparty traffic cleaning center the target of the attack changes within five minutes. ![](https://static.wixstatic.com/media/e47be9_2a7b64eef8674fe1a6a849c60eeb2326~mv2.jpg/v1/fill/w_560,h_328,al_c,lg_1,q_80,enc_auto/e47be9_2a7b64eef8674fe1a6a849c60eeb2326~mv2.jpg) Among the additional problems in St. Petersburg uplinks are connected through switches with oversubscription QOS either does not work or there is not enough buffer the alarm system falls apart. Additionally there are huge stretched VLANs which means that an attack on one subnet will affect a huge number of clients. Monitoring and countermeasures are too slow. Sometimes we had to prioritize in other locations we dont have our own network and the data centers are blocking us protecting their infrastructure.
|
|