How Long Does a Penetration Test Take? Timelines by Test Type
Harsh
Cybersecurity Experts
Table of Contents
- 01How long does penetration testing take? The short answer
- 02Typical duration by test type
- 03The phases of penetration testing
- 041. Discovery
- 052. Assessment
- 063. Validation
- 074. Reporting
- 085. Re-testing
- 09How does penetration testing work day to day?
- 10A week-by-week penetration testing timeline
- 11What makes a test take longer
- 12How to keep your test on schedule
- 13Planning around an audit or a release
- 14How Digisecuritas schedules engagements
- 15Check when we can start
- 16Frequently Asked Questions
How long does penetration testing take? The short answer
Most penetration tests take one to three weeks of active testing. Add about a week before for scoping and setup, and one to two weeks after for the report, your fixes and the re-test. From first call to final re-test report, four to six weeks is a realistic plan for a single application.
The exact length depends on what is being tested and how large it is. A small API can be covered in a few days. A large enterprise network with several applications can take more than a month.
Typical duration by test type
The ranges below describe active testing time for a typical mid-sized scope. Your own scope may sit outside them.
Test type | Typical testing time | What drives the length
|
|---|---|---|
Web application | 1 to 2 weeks | Number of user roles, dynamic pages and features |
API | 3 to 10 days | Number of endpoints, authentication schemes, quality of documentation |
Mobile app (one platform) | 1 to 2 weeks | App complexity, binary protections, whether the backend API is included |
External network | 3 to 5 days | Number of internet-facing IP addresses and services |
Internal network | 1 to 2 weeks | Number of hosts, network segments and Active Directory size |
Cloud environment | 1 to 2 weeks | Number of accounts, services in use and identity complexity |
Combined scope | 3 to 5 weeks | Total of the above, with some overlap |
The phases of penetration testing
The phases of penetration testing are the same whatever the target. Knowing them explains where the time goes.
1. Discovery
Scope is agreed, assets are listed and rules of engagement are signed. The tester receives accounts, documentation and access. This phase takes a few days of calendar time, most of it waiting for approvals and credentials on the client side.
2. Assessment
The tester maps the target and identifies vulnerabilities using manual techniques and automated tools. For an application, this means walking through every function with each user role. This is where most of the testing hours go.
3. Validation
Confirmed vulnerabilities are exploited to show what an attacker could reach. The tester chains findings where possible and collects proof.
4. Reporting
Findings are written up with severity scores, steps to reproduce and remediation guidance. Some firms take two to three weeks for this. Digisecuritas delivers reports within 72 hours of testing completion on average.
5. Re-testing
After your team fixes the findings, the tester verifies each fix and issues an updated report. The re-test itself takes one to three days. When it happens depends on how fast fixes are deployed.
How does penetration testing work day to day?
If you have not been through one, here is how penetration testing works from the client side.
Before the start date, you provide test accounts, allowlist the tester's IP addresses if needed and name a contact who can answer questions. On day one, the tester confirms access to everything in scope. During testing, you should hear from the tester when access breaks, when a question about intended behavior comes up and immediately if a critical issue is found. Normal business continues. Testing against production is paced to avoid disruption, and anything risky is agreed in advance.
At the end, you receive the report and a walkthrough call. Your developers fix, the tester re-tests and you receive the final version.
A week-by-week penetration testing timeline
A typical penetration testing timeline for one web application and its API:
Week | Activity | Who is busy
|
|---|---|---|
1 | Scoping call, statement of work, accounts and access set up | Both sides |
2 | Testing begins: mapping, authentication, access control | Tester |
3 | Testing continues: business logic, input handling, API | Tester |
3 to 4 | Report delivered, walkthrough call | Tester, then your team |
4 to 5 | Remediation | Your developers |
6 | Re-test and final report | Tester |
What makes a test take longer
Scope growth. Features, roles or environments added after the quote.
Access delays. Accounts not ready on day one are the most common cause of lost time.
Unstable test environments. A staging server that goes down mid-test stops the work.
Security controls that block the tester. A WAF or rate limiter that bans the tester's IP slows coverage. Decide beforehand whether you want those controls tested or bypassed for the engagement.
Missing documentation. An undocumented API has to be mapped by hand before it can be tested.
Slow remediation. The re-test waits for your fixes.
How to keep your test on schedule
Agree on the scope in writing, by asset.
Create test accounts for every role a week before the start.
Share API documentation or a request collection.
Give the tester a named contact with authority to answer questions the same day.
Freeze major releases to the test environment during the testing window.
Reserve developer time for fixes right after the report date.
Book the re-test date when you book the test.
Planning around an audit or a release
Work backward from your deadline. If a SOC 2 review period closes on June 30, the test, your fixes and the re-test should all be done before that date, which means starting by early May. If a product launches on a set day, testing has to end with enough time left to fix what it finds. Booking two months ahead is sensible, since testing firms fill their calendars toward year-end when audit deadlines cluster.
How Digisecuritas schedules engagements
Our engagements follow the five phases above: discovery, assessment, validation, reporting and re-testing. One re-test cycle is included in every project. Scope options and test types are listed on the VAPT services page.
Check when we can start
Tell us what you need tested and the date you need the report by. We will confirm the earliest start date and a schedule that meets your deadline.
Check availability for a test start date
