What is penetration testing?

Glossary

The short answer

Penetration testing is security testing in which authorized testers mimic real-world attacks to find ways around the security of an application, system or network. NIST SP 800-115 defines it in these terms. Unlike a vulnerability scan, a pentest tries to exploit weaknesses and chain them together, which proves real impact and shows which issues an attacker could actually use.

How does a penetration test work?

Every pentest starts with written permission and an agreed scope. Without authorization, the same activity is an attack. A typical test moves through these stages:

  1. Planning: define targets, rules of engagement, timing and contacts.

  2. Reconnaissance: gather information about the target, from public sources and active probing.

  3. Vulnerability analysis: identify weaknesses worth attempting.

  4. Exploitation: try to break in, escalate privileges and move toward sensitive data.

  5. Reporting: record each finding with evidence, severity and how to fix it.

  6. Retesting: verify that fixes worked.

Testers often use public methodologies such as the OWASP Web Security Testing Guide and PTES, and map techniques to MITRE ATT&CK.

What are the types of penetration testing?

Type

What the tester knows

Best for

Black box

Nothing beyond the target address

Simulating an outside attacker

Gray box

Some access, such as a user login

Testing what a customer or insider could do

White box

Full access, including source code

Finding the most issues in the time available

Tests are also grouped by target: web application, API, mobile app, cloud, internal network, and social engineering.

Why does penetration testing matter for startups?

Startups are often asked for a pentest report before closing an enterprise contract. Beyond that, a pentest is the most direct way to learn whether your access controls, authentication and APIs hold up against someone actively trying to break them. Finding a broken authorization check yourself costs far less than learning about it from a customer.

How NexusVoid handles it

Striker, NexusVoid’s vulnerability assessment and pentest product, runs pay per scan with more than 20 tools across web, API, cloud and mobile, and delivers a report in under 60 minutes. Results flow into the NexusVoid loop of Detect, Prove, Resolve, Test, Verify, so fixed issues are retested rather than assumed closed.

Related terms

  • VAPT (vulnerability assessment and penetration testing)

  • Vulnerability scanning

  • Attack surface management

  • MITRE ATT&CK

  • SOC 2 Type 1 vs Type 2

Frequently asked questions

How long does a penetration test take?

It depends on scope. A focused test of one web application or API can take from a few hours with automated tooling to one or two weeks with a manual team. Large engagements covering networks, cloud and several applications take longer. Ask for a written scope with dates, and budget time afterward to fix findings and run a retest.

What is the difference between a pentest and a vulnerability scan?

A vulnerability scan is automated and broad: it checks systems against known weaknesses and reports what might be wrong. A penetration test goes further by trying to exploit those weaknesses, chain them together and prove impact, such as reaching customer data. NIST describes scanning as identification and penetration testing as validation of vulnerabilities.

Do I need a pentest for SOC 2?

SOC 2 does not list a penetration test as a named, mandatory control. In practice, many auditors look for regular security testing as evidence for the monitoring and risk criteria, and enterprise customers frequently ask for a recent pentest report during security reviews. Most startups pursuing SOC 2 get one.

Is automated penetration testing as good as a manual one?

They answer different questions. Automated testing is fast, repeatable and cheap enough to run often, which suits code that changes every week. Skilled human testers are better at business logic flaws and creative chaining. Many teams run automated tests continuously and add manual testing for high-risk features or when a customer contract requires it.

Want to know what a pentest would find in your product this week? Book a call at /contact.

Something wrong in this post? Tell us at lakshay@nexusvoidai.com and we will fix it and say so.

Start with a real security program.

Tell us what you need to fix first and we will show that part live, on a stack like yours.