Tag Info

New answers tagged

2

In most cases, it is very hard to mitigate DDoS attacks on your own. Most banks and large companies will engage the service of professional DDoS mitigation service providers. The latter will detect anomaly traffic patterns and reroute all traffic to their scrubbing centers for filtering out the bad traffic. The following filtering-based mechanisms are ...


1

Use of a scrubbing provider can potentially help, depending on the type of "normal" traffic and how much control you have over it. In the best case, that traffic would be human-initiated http or https traffic, and scrubbing could consist of using JavaScript based tests and CAPTCHA spash screens to whitelist the legitimate traffic. If the legitimate traffic ...


0

I found this article, which seems to explain what's going on: https://wiki.apache.org/httpd/ProxyAbuse I have modified the default host config to return http 444 now. Hopefully the culprits will realise that this is not an open proxy and just go away at some point. E.g.: server { listen 80 default_server; listen [::]:80 default_server ...


0

It would depend on a number of factors, such as what protocol was used. Let's assume for the sake of the answer that the protocol in question is unencrypted HTTP. 1) Buffer Overflow. This would be the trickiest of the 3 to identify, as it could just look like a large request. It's possible that you could identify it from some common patterns that people ...


0

If you don't have any specific protection against DDOS you are probably vulnerable, those measures are usually quite expensive and many customer prefer to use services like cloudflare and others. Here some tips which may apply or not depending on technology/language: fingerprint your webserver version and openssl version and look for public known common ...


0

The likelihood is you are vulnerable. If you use a scale-able cloud application platform and have enough resource budget or you use a massive CDN (content delivery network - http://en.wikipedia.org/wiki/Content_delivery_network) you might not be. Likewise if your ISP is especially pro-active in mitigating such threats you may be ok. So in terms of how you ...


5

Do you have a site? If so, you're vulnerable. A distributed denial of service attack (DDOS) consists of a number of computers throwing data at your site faster than it can handle it. Unless you're operating on the scale of Google, you're vulnerable. Your main defense is to not be a target worth the effort of attacking. A conventional denial of service ...


3

A DDoS works by making a system running out of a scarce resource. What happens then depends on the resource that is exhausted. For instance, the resource may be CPU. The attackers send many requests, and the server must spend some CPU resources to respond to these requests. When the load augments, the server begins to respond slower, then becomes sluggish, ...


3

Answer (like a lot of answers in info sec): It depends. If the DDoS attack is swamping the network infrastructure, it may be difficult for an outbound packet to make it through (even with higher priority) because the network switches and appliances might be too busy to process it. On top of this, if it is a TCP connection then it'll need the reply packets ...


0

What would happen if the attacker sends the data at the same bandwitch, but keeping up to your size limit? What's the difference between sending 100 100MB files, and sending 10000 1MB files? If you want to be immune to DDOS attack, than you can forget - you can't. Event the biggest giants are affected by such attacks from time to time. Even the biggest ...


0

Your code is good for monitoring users activity on the server but to be honest, It can't help preventing DDOS attacks since the aim of DDOS attacks is to send tons of requests to the server to make it too busy to respond to its intended users. your code seems to be doing lots of checking to determine if the number of requests has reached beyond your ...



Top 50 recent answers are included