-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Study options for DDoS attack prevention #1953
Comments
IMHO, this should be done on the server level rather than at the software level. |
+agreed. Search for existing solutions instead of building one from scratch. |
A little more information about possible strategies http://security.stackexchange.com/questions/73369/how-do-major-sites-prevent-ddos |
CDN is the most reliable approach. |
First of all, thanks for reading a good number of sources for your research. :) I know your research text has already been merged, but I still have a few comments to make. Sorry for not being able to read the text sooner. If there is text that is copy from someone else's text, please mark it as a quotation, if it is longer than 3 words. For instance, this snippet of text is copied from one of your sources: "It is a subtle dance and requires a bit more understanding of the application and its flow," If we copy text from others without marking it as a copy (and giving the source), we are plagiarizing. I'm wondering about this recommendation in a research document for APInf (API management tool): Based on this research, what levels do you think we should be focusing on and are these some concrete first steps? |
Study DDoS attack prevention and mitigation for APInf
Definition of done
There is a DDoS-prevention document created in our docs repository.
The text was updated successfully, but these errors were encountered: