Skip to content

DDoS attacks on our website.

Moved Security
  • We often receive DDoS attacks on our website. Could you please provide a tutorial on how to deploy it on Vercel?

  • @周林锋 DDoS attacks are typically mitigated at the ISP or Firewall level, and should not be actioned at the server level ideally - however, most of this depends on the type of DDoS attack.

    For example, Layer 2 and 3 type attacks (Data and Network from the OSI Model) should always be handled by any traversing path other than the server itself - see below

    42853c8c-8a0b-4ce2-b2b3-97c9b96bed4d-image.png

    In this case, the ISP itself, or the firewall sitting in front of the server should have mitigation processes in place to prevent this type of attack hitting your server directly. Layer 7 attacks are different in their approach, and typically target the application directly. To avoid this, you should deploy a Web Application Firewall (WAF) that can filter out these types of attacks.

    Essentially, the “easy” choice here is Cloudflare, although I note that your server is potentially located in China, so this may not be an option - although AWS (operated by Sinnet) is available - more information here

    https://www.amazonaws.cn/en/new/2021/amazon-waf-available-china/

    If you can provide more information around the infrastructure you have (not here, but via PM for security reasons), I can guide you further.

  • phenomlabundefined phenomlab moved this topic from Chitchat on
  • No response from OP so marking as closed


Related Topics
  • 0 Votes
    3 Posts
    64 Views

    @Madchatthew feel free! You never know 😀

  • 1 Votes
    7 Posts
    128 Views

    That is like saying to a robber and murderer, hey come on in here and take all my things and by the way before you leave go ahead and stab me in the chest.

  • Protecting API Access on Apache/Cloudways

    Solved Security
    3
    1 Votes
    3 Posts
    152 Views

    @phenomlab issue was with high traffic spikes and the website used to get crashed. API is managed by others, its built in such a way they built it in such un protected way. we would be moving to nodejs own APIs soon to address all these issues. thought of solving it with help of you and a friend of mine is helping me build a new site with APIs. thanks

  • Adjusting HSTS settings for public wifi's

    Solved Security
    4
    2 Votes
    4 Posts
    416 Views

    @Hari Ok, no issues. Keep me posted…

  • Russian hackers hit with sanctions

    Security
    5
    2 Votes
    5 Posts
    278 Views

    @mathourthy Good question. They have zero effect from what I can see. It’s not going to stop them from targeting anyone else.

  • 1 Votes
    1 Posts
    138 Views
    No one has replied
  • Bad information security advice

    Security
    1
    1 Votes
    1 Posts
    147 Views
    No one has replied
  • 0 Votes
    4 Posts
    691 Views

    @DownPW 🙂 most of this really depends on your desired security model. In all cases with firewalls, less is always more, although it’s never as clear cut as that, and there are always bespoke ports you’ll need to open periodically.

    Heztner’s DDoS protection is superior, and I know they have invested a lot of time, effort, and money into making it extremely effective. However, if you consider that the largest ever DDoS attack hit Cloudflare at 71m rps (and they were able to deflect it), and each attack can last anywhere between 8-24 hours which really depends on how determined the attacker(s) is/are, you can never be fully prepared - nor can you trace it’s true origin.

    DDoS attacks by their nature (Distributed Denial of Service) are conducted by large numbers of devices whom have become part of a “bot army” - and in most cases, the owners of these devices are blissfully unaware that they have been attacked and are under command and control from a nefarious resource. Given that the attacks originate from multiple sources, this allows the real attacker to observe from a distance whilst concealing their own identity and origin in the process.

    If you consider the desired effect of DDoS, it is not an attempt to access ports that are typically closed, but to flood (and eventually overwhelm) the target (such as a website) with millions of requests per second in an attempt to force it offline. Victims of DDoS attacks are often financial services for example, with either extortion or financial gain being the primary objective - in other words, pay for the originator to stop the attack.

    It’s even possible to get DDoS as a service these days - with a credit card, a few clicks of a mouse and a target IP, you can have your own proxy campaign running in minutes which typically involves “booters” or “stressers” - see below for more

    https://heimdalsecurity.com/blog/ddos-as-a-service-attacks-what-are-they-and-how-do-they-work

    @DownPW said in Setting for high load and prevent DDoS (sysctl, iptables, crowdsec or other):

    in short if you have any advice to give to secure the best.

    It’s not just about DDos or firewalls. There are a number of vulnerabilities on all systems that if not patched, will expose that same system to exploit. One of my favourite online testers which does a lot more than most basic ones is below

    https://www.immuniweb.com/websec/

    I’d start with the findings reported here and use that to branch outwards.