Skip to Content
OpenVAPTAlpha
Pre-release. Academic, non-commercial, source-available code built by AI Cybersecurity Engineers. Free for your own use, 100% at your own risk. This website collects no data. Read MoreRead Less
Pre-release. OpenVAPT has no Stable release yet. Every build is an Alpha, Beta or Release Candidate: it may be incomplete or wrong, so use it only on test machines, 100% at your own risk. See Release Channels
Academic, non-commercial, source-available code built by AI Cybersecurity Engineers. These are AI systems, not people or registered engineers. Free for your own personal or business use, on your own machines, 100% at your own risk. Not for sale. Not for providing services. This website collects no data. Read the Acknowledgements
Pre-release. OpenVAPT has no Stable release yet. Every build is an Alpha, Beta or Release Candidate: it may be incomplete or wrong, so use it only on test machines, 100% at your own risk. See Release Channels
Academic, non-commercial, source-available code built by AI Cybersecurity Engineers. These are AI systems, not people or registered engineers. Free for your own personal or business use, on your own machines, 100% at your own risk. Not for sale. Not for providing services. This website collects no data. Read the Acknowledgements
P25PractitionerAbout 20 minutes

Availability Without Load Testing

Why a self-assessment never floods a server to test it, and which settings show whether a site can resist floods and slow requests.

Read First: F3

You Will Be Able To

  • Explain the difference between performance testing and a configuration review.
  • Name the settings that limit request rate, size and duration.
  • Know when real load testing is appropriate and who must approve it.

Two Different Activities

Performance testing sends heavy traffic on purpose to measure speed and find breaking points. Done without permission, the same traffic is a denial of service attack.

A self-assessment instead reads the configuration that decides how the server behaves under pressure. No heavy traffic is sent, so the review is designed not to strain the service.

What to Look For

Rate limits stop one client sending too many requests. Size limits stop huge uploads. Time limits stop clients that send a request very slowly to hold a worker open.

On nginx these are limit_req_zone, limit_conn_zone and client_max_body_size. On Apache they are mod_reqtimeout and optional modules such as mod_evasive.

Login Protection

Repeated failed logins are a flood aimed at one door. SSH MaxAuthTries and a log-based blocker such as fail2ban, sshguard or CrowdSec slow attackers down.

When Real Load Testing Is Right

Before a launch or a big event, a team may load test its own system. Do it on a copy where possible, in an agreed window, with written approval from the owner and the hosting provider.

In Summary

Never flood a server to assess it. Read its rate, size and time limits instead, and keep real load tests for your own systems, with written approval.

Apply It

These OpenVAPT checks put this module into practice. Open one to see its detection logic and source code.

Printable Worksheet · Teacher Answer Key · For Teachers · Print this page with your browser's Print command for a handout.

Also available as plain Markdown for notes, scripts and AI tools. Same facts, same source, no styling.

Lab

  1. Run: openvapt demo vulnerable --only WEB-APA-011,WEB-NGX-006 --out p25 and list the missing limits.
  2. Write the nginx lines that add a login rate limit of 10 requests per minute per address.

Check Yourself

Answers are checked in your browser and never stored or sent.

Question 1

1. Why does OpenVAPT not send heavy traffic to test availability?

Question 2

2. What does a slow request attack (Slowloris) exploit?

Question 3

3. Which nginx directive limits request rate?

Question 4

4. Which Apache module protects against slow requests?

Question 5

5. Who must approve a real load test?

References

Cite This Page

If this page helped your work, please cite it. The version and web address are filled in; the access date is today's date in your browser. Every other style, and when credit is required, is on How to Cite OpenVAPT.

APA 7
OpenVAPT. (2026). P25: Availability Without Load Testing (Version 0.1.0-alpha.6). OpenVAPT Academy. Retrieved October 16, 2026, from https://openvapt.com/academy/p25.html

In text: (OpenVAPT, 2026). Accessed: the date shown is today's date from your own browser (the site's build date without JavaScript); change it to the day you read the page.

BibTeX
@misc{openvapt_p25,
  author       = {{OpenVAPT}},
  title        = {{P25: Availability Without Load Testing}},
  year         = {2026},
  howpublished = {\url{https://openvapt.com/academy/p25.html}},
  note         = {OpenVAPT Academy, version 0.1.0-alpha.6. Accessed 16 October 2026}
}

Accessed: the date shown is today's date from your own browser (the site's build date without JavaScript); change it to the day you read the page.

Citing OpenVAPT does not mean OpenVAPT endorses, approves or has reviewed your work.