Skip to content
SECQON

Asked for a pentest report by Friday: a realistic 48-hour plan

· 6 min read · Pentest reports

It is Wednesday. A prospect's security team has asked for your most recent penetration test report, the contract is waiting on it, and someone has said "by Friday". You have no security hire, and a manual testing firm has quoted a start date three weeks out.

This is a plan you can actually run in 48 hours, with the points where it slips marked.

Hour 0 to 1: confirm what they will accept

Before you buy anything, reply to the prospect's security contact with two questions:

  1. Is an automated external penetration test acceptable, or do you need a human-led test?
  2. Which asset do you need tested: the application they will use, its API, or both?

If they need a human-led test, no automated product will satisfy them, and you should tell your sales lead now that Friday is not realistic. If an automated test is acceptable, carry on. Most teams get an answer within a few hours.

Hour 1 to 2: pick the asset

Choose the one asset that matters to this buyer. That is usually the application they will log in to, for example app.yourcompany.com, rather than your marketing site.

Write down the exact host name. A test of yourcompany.com does not cover app.yourcompany.com, and a reviewer will notice if the report names a different host from the one they use.

Hour 2 to 3: prove you own it

Any legitimate tester will make you prove you control the asset before sending it a single request. With SecQon that is one of three methods:

  • a DNS TXT record on the domain;
  • a file hosted at a path on the site;
  • a meta tag in the page's HTML.

This is the step most likely to slip. A DNS change may need someone with access to your DNS provider, and propagation is usually the slowest part. If DNS access is slow to arrange, the hosted file or meta tag is often quicker, because it can go out with a normal deploy.

Hour 3: tell your team, then start the test

Tell whoever is on call that an external security test is about to run against production. The test is built not to break things. Destructive and data-extraction actions are blocked, payloads are bounded, and traffic is rate-limited per asset. Your team should still know, so that a WAF alert or an unusual log line does not start an incident.

Then start the test. The full Deep and penetration-test scan runs in the background. On a real site it takes hours, not minutes: the template sweep alone of one of our own sites took about 4.2 hours. Start it on Wednesday afternoon, not Thursday evening.

Hour 4 to 20: let it run

You do not need to watch it. You are emailed when the report is ready, and the report and questionnaire pack appear in the app.

Use the time to draft the covering note you will send with the report (see below).

Hour 20 to 40: read it and fix what you can

When the report arrives, read the one-page summary first. It lists the findings to fix first, with the proof for each. Then:

  1. Fix the demonstrated and confirmed high-severity findings first. These are reproduced, not guesses. Our guide to reading the labels explains the order in more detail.
  2. Pick off the quick configuration fixes. Missing security headers, cookie flags and weak TLS settings are often a one-line change each, and the report includes configuration for common servers and frameworks.
  3. Write a status for everything else. "Scheduled for next sprint" or "accepted risk, because…" is a legitimate answer. Silence is not.

You do not need a clean report to send one. Security reviewers expect findings. What they look for is that you know about them and have a plan.

Hour 40 to 48: send it

Send the report with a short covering note that says:

  • the asset tested and the date of the test;
  • that the test was automated and external;
  • which findings you have already fixed, and the plan for the rest.

If the questionnaire has its own vulnerability-management questions, the questionnaire pack answers them from the same scan, and marks the questions only you can answer, such as those about encryption at rest or MFA policy.

What can make you miss Friday

  • The buyer needs a human-led test. Find out in hour 0, not hour 40.
  • DNS access. If only one person can change DNS and they are away, use the hosted-file method instead.
  • Starting late. The test takes hours. Starting on Thursday night leaves no time to fix anything.
  • A large site. The more of the site the crawl finds, the longer the test runs.

What it costs, and what if it fails

The one-off pentest report is one full penetration test of one verified asset, bought once, with no subscription and no card kept on file. If the scan fails on our side, you can run it again free, or we refund you if we cannot run it within 30 days.

Find out how an attacker would break into your website — and get the report your customer asked for.

We test your site from outside, like an attacker would, in hours, not weeks. The dated PDF labels each finding by its proof (demonstrated, confirmed, likely) and shows the fix.

Buy one report — $99Compare plans

More articles