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
F2FoundationsAbout 20 minutes

What VAPT Is, and Doing It Legally

How vulnerability assessment and penetration testing differ, how professional assessments are structured, and why authorisation is the first rule.

Read First: F1

You Will Be Able To

  • Explain the difference between vulnerability assessment and penetration testing.
  • Describe the phases of NIST SP 800-115 and where OpenVAPT stops.
  • Explain why written authorisation and scope come before any testing.

VA Versus PT

A vulnerability assessment (VA) looks for known weaknesses and rates them, without exploiting anything. A penetration test (PT) is performed by skilled, authorised testers. They try to exploit weaknesses to prove real impact and to find chains a scanner cannot see.

VAPT combines both. OpenVAPT teaches and performs only the VA part, automatically, on one machine. That is a deliberate design choice, not a missing feature.

Methodologies

NIST SP 800-115 describes four phases: planning, discovery, attack and reporting. Other widely used frameworks include the Penetration Testing Execution Standard (PTES), the OWASP Web Security Testing Guide (WSTG) for web applications, and OSSTMM.

OpenVAPT implements planning (scope fixed in code), discovery (read-only collection), analysis (checks) and reporting. The attack phase is absent by design.

Authorisation, Scope and the Law

Testing a system without permission is a crime in most countries. Examples include the Computer Fraud and Abuse Act in the United States and the Computer Misuse Act 1990 in the United Kingdom. Others are Directive 2013/40/EU in the European Union and the Computer Crimes Act 1997 in Malaysia. The Council of Europe Convention on Cybercrime has been joined by many countries. Some countries also license people who sell security testing as a service. Always follow the law where you and the machine are.

Professional testers work only with written authorisation that defines scope, timing and rules of engagement. OpenVAPT enforces the strictest possible scope in code: the machine it runs on and nothing else. Even so, you need the right to run it on that machine.

In Summary

A vulnerability assessment finds and rates weaknesses. A penetration test also exploits them. Both need written authorisation and a clear scope. OpenVAPT assesses only the machine it runs on.

Apply It

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

CheckTitleSeverity
NET-LSN-001Inventory of Listening Network ServicesInfo

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 scan --dry-run and read every operation it would perform.
  2. Find the loopback guard in internal/scope/scope.go and its test. Explain why host names are refused.
  3. Write a one-paragraph scope statement for assessing your own test server.

Check Yourself

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

Question 1

1. What does a penetration test do that a vulnerability assessment does not?

Question 2

2. Which NIST SP 800-115 phase does OpenVAPT deliberately leave out?

Question 3

3. What must exist before testing a system you do not own?

Question 4

4. Which scope does OpenVAPT enforce in its code?

Question 5

5. Which of these is a methodology for testing web applications?

Question 6

6. You run OpenVAPT on a server you rent but do not control. Does its loopback-only scope make the test lawful?

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). F2: What VAPT Is, and Doing It Legally (Version 0.1.0-alpha.6). OpenVAPT Academy. Retrieved October 16, 2026, from https://openvapt.com/academy/f2.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_f2,
  author       = {{OpenVAPT}},
  title        = {{F2: What VAPT Is, and Doing It Legally}},
  year         = {2026},
  howpublished = {\url{https://openvapt.com/academy/f2.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.