Guide
Pentest remediation timelines by severity
How long should a client have to fix what a penetration test finds? These are the timelines most organizations use, what standards and regulators actually require, and how to make the deadlines stick.
Updated 11 November 2026 · By the Closeout team
Typical remediation timelines by severity
There is no single legal standard for pentest findings, but most organizations land on something close to this:
| Severity | Typical deadline | Notes |
|---|---|---|
| Critical | 7 to 15 days | Notify the client during testing, don't wait for the report |
| High | 30 days | Shorter if internet-facing or with a public exploit |
| Medium | 60 to 90 days | Often grouped into the next release cycle |
| Low | 90 to 180 days | Or the next planned maintenance window |
| Informational | No deadline | Hardening advice; review at the next test |
The clock usually starts when 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.
What the standards say
- CISA BOD 26-04 (US federal civilian agencies, issued 10 June 2026) replaced BOD 19-02 and BOD 22-01. Deadlines now depend on public exposure, presence in the Known Exploited Vulnerabilities catalog, whether exploitation can be automated and technical impact, not on severity alone: from 3 calendar days plus forensic triage for the worst combination to the next system upgrade for the lowest risk. Agencies apply them from 7 December 2026.
- FedRAMP: from 7 December 2026, certified cloud offerings follow the Vulnerability Detection and Response rules, with deadlines by offering class, potential agency impact, 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: exploitable weaknesses found in a penetration test corrected according to the entity's risk ranking and retested (requirement 11.4.4), with no day count; patches for critical vulnerabilities installed within one month of release (requirement 6.3.3).
- ISO 27001 and SOC 2 set no day counts. They require you to define remediation timelines, follow them and keep evidence (ISO/IEC 27001:2022 Annex A control 8.8, management of technical vulnerabilities).
In practice, the client's own policy is what an auditor will check against, so the timelines should be written down and agreed before testing starts. The remediation deadline calculator turns a policy into a due date for each finding.
What should move a deadline
- Exploitability: a public exploit, or presence in the KEV catalog, shortens the deadline whatever the score says.
- Exposure: internet-facing systems get less time than internal ones behind several controls.
- Data at risk: anything touching credentials, payment or personal data moves up.
- Compensating controls: a WAF rule or network restriction can justify more time, but not closing the finding.
- Size of the fix: an architectural change may need a plan with milestones rather than a single date.
How to make timelines stick
- Agree the deadlines in the statement of work, before testing, not after the report lands.
- Give every finding an owner on the client side and a due date, not just a severity.
- Track status where the client works, not in a PDF: a portal, their issue tracker, or both.
- Retest as soon as a fix is deployed, so “fixed” means verified. See our guide to pentest retesting.
- Report on it: the share of findings closed within their deadline is the number management understands.
When a deadline is missed
Missed deadlines are common; silent ones are the problem. The client should either agree a new date with a reason, put a compensating control in place, or formally accept the risk: in writing, by someone with the authority to accept it, and with an expiry date so it is reviewed again. An accepted risk is still reported, for example in the attestation letter, as accepted rather than fixed.
Frequently asked questions
Who sets the remediation deadlines?
The client owns them, usually in their vulnerability management policy. The testing firm recommends deadlines based on severity and context, and it helps to agree them in the statement of work.
When does the remediation clock start?
Usually when the report is delivered. For critical findings, when the client is notified, which should happen as soon as the tester confirms the issue during testing.
Should critical findings wait for the final report?
No. Critical findings should be reported to the client immediately, by an agreed secure channel, so they can act while testing continues.
Are remediation deadlines legally required?
Only in some regimes, such as US federal agencies under CISA directives or FedRAMP. Elsewhere, standards like PCI DSS, ISO 27001 and SOC 2 require deadlines to be defined and met, and auditors check against the client's own policy.
Is CVSS enough to set the deadline?
It's a starting point. Exposure, whether an exploit is public, the data at risk and compensating controls should all adjust the final deadline.