Reputation: 8657
Best practice for protecting against Denial of Service(DoS) attacks in ASP.NET Core
I'm looking for best practice advice/guidance (perhaps from Microsoft?) regarding denial of service (DoS) protection/mitigation for ASP.NET Core web applications.
The main two options I have found so far are:
- AspNetCoreRateLimit (ASP.NET Core middleware)
- Dynamic IP Restrictions (IIS module - assuming the site is hosted in IIS).
It seems like there are a number of pros and cons to consider when choosing one of these options over the other, so it would be good to understand what those are, and indeed if AspNetCoreRateLimit is intended to be used alongside Dynamic IP Restrictions or not.
Also note that AspNetCoreRateLimit is not part of ASP.NET Core releases from Microsoft, therefore I'm curious to know what Microsoft's official guidance is.
Upvotes: 8
Views: 5584
Answers (1)
Reputation: 4892
If you have a public facing website and want to prevent DDoS, doing it outside your ASP Core app would be the best method. You should investigate services like ClouldFlare.
Upvotes: 3
Related Questions
- How to detect DDOS attacks in ASP.Net Core
- C# MVC: What is a good way to prevent Denial Of Service (DOS) attacks on ASP.NET sites?
- How to prevent DoS attack in ASP.NET MVC applications?
- How to prevent Denial of Service (DoS) using IIS?
- ASP.Net module to block DOS attacks
- Which steps could you take to minimize the effect of a potential (D)DoS attack in IIS?
- ASP.NET Web application prevent denial of service attacks
- Prevent Malicious Requests - DOS Attacks
- How to protect a website from DoS attacks