This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Difference between revisions of "Denial of Service Cheat Sheet"

Jump to: navigation, search
m (Point to the official site)
(25 intermediate revisions by 2 users not shown)
Line 2: Line 2:
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:Cheatsheets-header.jpg|link=]]</div>
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:Cheatsheets-header.jpg|link=]]</div>
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
The Cheat Sheet Series project has been moved to [ GitHub]!
= Introduction  =
__TOC__{{TOC hidden}}
This article is focused on providing clear, simple, actionable defense guidance for preventing denial of service in your web applications. Denial of Service attacks are very common due to two factors :
Please visit [ Denial of Service Cheat Sheet] to see the latest version of the cheat sheet.
# The significant prevalence of cloud and web services 
# Easy to get testing tools to cause denial of service attacks.
Because it's very simple to launch the DOS attack, any web services don't have Anti-DOS defenses mitigation in place will be vulnerable to DOS attacks.
To avoid and mitigate DOS attack, both developers and operations engineering will need to have layered of defenses in place:
a) Service: When the service is built, it's developed with anti-DOS in mind such Input validation, Resource handling, Size or Length validation.
b) Web Host: Every Web server such Apache, NginX or Linux host provides the configuration of connection. Properly configure these network configuration may also help to mitigate the DOS attacks.
c) Infrastructure: Signature-based or behavior detection firewalls, load balance, fail-over, cloud anti-DDoS service
This objective of the article is to provide a list of common techniques for preventing DOS attack regardless of technology and platforms.
=Coding Defenses=
= Web Services Defenses =
General web services protection against DOS can be listed as 3 main category
* Max connection per IP address
* Max size of every HTTP request
* Timeout value of each HTTP request connection
==NginX secure configuration==
Define the connection timeout value.
client_body_timeout  10;
client_header_timeout 10;
keepalive_timeout    5 5;
send_timeout          10;
Limit the size of http request to mitigate the buffer overflow attack
client_body_buffer_size  100K;
client_header_buffer_size 1k;
client_max_body_size 100k;
large_client_header_buffers 2 1k;
= Network Infrastructure Defenses =
=Related Articles=
= Authors and Primary Editors  =
[[User:Tony_Hsu_HsiangChih|Tony Hsu]] - hsiang_chih[at]<br />
<br />
== Other Cheatsheets ==

Latest revision as of 14:36, 15 July 2019


The Cheat Sheet Series project has been moved to GitHub!

Please visit Denial of Service Cheat Sheet to see the latest version of the cheat sheet.