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
Line 24: Line 24:
=Primary Defenses=
=Coding Defenses=
==Defense Option 1: xxxx ==
== Defense Option 2: xxxx ==
= Web Services Defenses =
= Host Defenses =
= Network Infrastructure Defenses =
=Related Articles=
=Related Articles=

Revision as of 08:40, 20 March 2017


Last revision (mm/dd/yy): 03/20/2017


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 :

  1. The significant prevalence of cloud and web services
  2. 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

Host Defenses

Network Infrastructure Defenses

Related Articles

Authors and Primary Editors

Tony Hsu - hsiang_chih[at]

Other Cheatsheets