Free tool

Pentest remediation deadline calculator

Set a remediation deadline for every pentest finding by severity, from the day the report is delivered. Paste your findings to get a due date for each one, then copy the table into your report or download it as CSV for Jira or Excel. Free, no sign-up, and it runs in your browser.

Everything runs in your browser. Nothing you paste is sent to us or stored on a server.

Deadline policy
Your findings (optional)

Deadlines

SeverityDaysDue date
Critical15 calendar days6 December 2026in 15 days
High30 calendar days21 December 2026in 30 days
Medium90 calendar days19 February 2027in 90 days
Low180 calendar days20 May 2027in 180 days
Informationalno deadline, review at the next test

Typical pentest remediation deadlines

There is no single legal deadline for pentest findings. These are the two policies the calculator starts from:

SeverityCommon practiceStrict
Critical15 days7 days
High30 days30 days
Medium90 days60 days
Low180 days90 days
InformationalNo deadlineNo deadline

Use the strict column for internet-facing systems or anything handling credentials, payment or health data. Whatever you choose, write it in the engagement letter before testing starts: deadlines agreed after the report lands are much harder to hold. Our guide to pentest remediation timelines covers what should move a deadline and what to do when one is missed.

What standards and regulators require

  • CISA BOD 26-04 (US federal civilian agencies, issued 10 June 2026) replaced BOD 19-02 and BOD 22-01. Deadlines no longer follow severity alone: they depend on whether the asset is publicly exposed, whether the flaw is in the Known Exploited Vulnerabilities catalog, whether exploitation can be automated and its technical impact. The worst combination must be fixed within 3 calendar days plus forensic triage; the lowest-risk ones can wait for the next system upgrade. Agencies apply the timelines from 7 December 2026.
  • FedRAMP moves all certified cloud offerings to its Vulnerability Detection and Response rules on 7 December 2026, with deadlines set by the offering's class, the potential impact on agencies, internet reachability and exploitability. They replace the old fixed windows of 30 days for high, 90 for moderate and 180 for low.
  • PCI DSS v4.0.1 sets no day count for pentest findings: requirement 11.4.4 asks for exploitable findings to be corrected according to the entity's risk ranking and retested. Requirement 6.3.3 requires patches for critical vulnerabilities within one month of release.
  • ISO/IEC 27001:2022 and SOC 2 set no day counts either. They require a defined process (Annex A control 8.8, management of technical vulnerabilities), deadlines that are followed, and evidence of both.
Outside US federal systems, the client's own policy is the standard an auditor checks against. The calculator's “Copy policy text” gives you a paragraph to paste into the policy, the SOW or the report.

How to use the dates

  • Put the due date on each finding in the report, not only the severity: owners plan against dates.
  • Import the CSV into the client's tracker, so the deadline lives where the work happens.
  • Schedule the retest before the earliest deadline, so “fixed” means verified. See how to retest pentest fixes.
  • Report the outcome in the attestation letter: what was fixed in time, what was accepted, what is still open.

Frequently asked questions

What is a typical remediation deadline for a critical pentest finding?

Most organizations give 7 to 15 days for critical findings, 30 days for high, 60 to 90 days for medium and 90 to 180 days for low. Informational findings usually have no deadline. These are common practice, not a legal standard: the client's own vulnerability management policy is what an auditor checks.

When does the remediation clock start?

Usually on the day the report is delivered. For critical findings it should start when the client is told, which should be as soon as the tester confirms the issue during testing, not when the report arrives.

Calendar days or business days?

Most policies and regulations, including CISA's directives, count calendar days. Business days are sometimes used for short internal deadlines; if you use them, say so in the policy, because 30 business days is about six weeks.

Should actively exploited vulnerabilities get a shorter deadline?

Yes. A vulnerability in CISA's Known Exploited Vulnerabilities catalog, or with a public exploit, should be treated as more urgent than its CVSS score suggests. The calculator can give those findings the deadline of the next severity up.

Does PCI DSS set a deadline for pentest findings?

Not in days. PCI DSS v4.0.1 requirement 11.4.4 requires exploitable vulnerabilities found in a penetration test to be corrected according to the entity's risk ranking and then retested. Separately, requirement 6.3.3 requires patches for critical vulnerabilities to be installed within one month of release.

Is my data sent anywhere?

No. The calculator runs entirely in your browser. Your settings and pasted findings are kept only in your browser's local storage so a reload doesn't lose them.