Skip to content
Knowledge base Updated: February 5, 2026

Why Does Your Pentest Report Gather Dust? The Remediation Gap Problem

Pentest completed, report delivered, 47 vulnerabilities identified. A year later - same holes. Why don't companies fix what pentesters find?

“We have a pentest report. 47 vulnerabilities, including 8 critical. The report went to IT and… nothing happened.” This is a story we hear regularly. Companies spend tens of thousands of dollars on penetration testing, receive detailed reports with specific vulnerabilities - and then those reports end up in a drawer. We call this the remediation gap - the gap between problem identification and its resolution.

Quick Navigation

Remediation gap in numbers

Industry data paints a concerning picture:

StatisticValueSource
Average time to fix critical vulnerability205 daysQualys Research

Many companies that commission a re-test after a year still have the same vulnerabilities as before. This means the first pentest was a wasted investment.

📚 Read the complete guide: Penetration Testing: Penetration testing - types, methodologies, process

Why don’t companies fix vulnerabilities?

1. The IT team is overloaded

This is the most common cause. The IT department has 3-5 people who:

  • Handle helpdesk (100 tickets daily)
  • Maintain infrastructure (servers, networks, backup)
  • Deploy new projects (business is pushing)
  • Put out fires (something broke, VIP can’t log in)

The pentest report goes to the end of the queue. “We’ll get to it when we have time.” Time never comes.

2. Lack of competence

Pentest indicates: “Weak Kerberos configuration - vulnerable to Kerberoasting.”

IT admin thinks: “What’s Kerberoasting? How do I fix it? Where do I look?”

Pentesters are great at finding holes. But their reports often assume a level of knowledge that a typical admin doesn’t have. Without specific “click here, type this” steps - the fix doesn’t happen.

3. Fear of change

“If I change the firewall configuration, email might stop working.”

“If I update the server, the old application might break.”

IT fears changes because changes generate problems. Better to live with a theoretical vulnerability than a certain outage after a failed patch. This is flawed thinking, but human.

4. Lack of ownership

The report identifies 47 vulnerabilities across 15 different systems. Who’s responsible for fixing each one?

  • Web application → developer team
  • Active Directory → system admin
  • Firewall → network admin
  • Database → DBA

Without clear ownership assignment, everyone waits for “someone else” to fix it.

5. Lack of prioritization

47 vulnerabilities. Where to start?

If the report doesn’t give a clear answer “fix these 3 this week, these 5 this month, the rest can wait” - IT throws up their hands. Everything is urgent = nothing is urgent.

6. Organizational silos

  • CISO ordered the pentest (compliance requires it)
  • IT got the report (because it’s “technical”)
  • IT reports to CTO (not to CISO)
  • CTO has other priorities (new features, not patching holes)
  • Nobody coordinates, nobody holds accountable

Consequences of an unclosed cycle

Consequence 1: Wasted investment

The pentest cost $10,000. If you don’t fix anything - that’s money thrown away. You might as well not have done the pentest at all.

Consequence 2: False sense of security

“We had a pentest, we’re secure.” No, you had a pentest that showed you are NOT secure. The pentest itself doesn’t fix anything.

Consequence 3: Auditor asks about follow-up

ISO 27001 / NIS2 Auditor: “I see a pentest report from March. What remediation actions have you taken?”

You: ”…”

This is an audit finding. Knowingly ignoring identified risks is worse than not knowing about them.

Consequence 4: The incident that could have been prevented

Breach through a vulnerability described in a report from 6 months ago. The board asks: “Did you know about this hole?” Yes, you knew. There was a report. Now what?

How to close the cycle: pentest → fix → verify

Step 1: Prioritization before the report

A good pentest is not just a list of vulnerabilities with CVSS scores. It’s prioritization by business risk:

VulnerabilityCVSSBusiness ImpactPriority
SQL Injection in customer portal9.8Data of 100k customersP1 - Week
Weak AD passwords7.5Access to everythingP1 - Week
XSS in admin panel6.1Only 3 adminsP2 - Month
TLS 1.0 on dev server5.3No prod dataP3 - Quarter

CVSS isn’t everything. SQL Injection on a test server (CVSS 9.8, but no data) is less urgent than weak passwords in production AD (CVSS 7.5, but access to everything).

Step 2: Remediation plan with ownership

For each vulnerability:

  • What to fix (detailed description)
  • Who is responsible (name, not department)
  • When is the deadline (specific date)
  • How to verify (success criteria)
IDVulnerabilityOwnerDeadlineVerification
V-001SQL InjectionJohn SmithFeb 15Retest by nFlo
V-002Weak AD passwordsJane DoeFeb 22GPO audit
V-003Missing patchesMike JohnsonMar 1WSUS report

Step 3: Regular follow-up

It’s not enough to create a plan and forget about it.

Weekly:

  • Status update from owners (done / in progress / blocked)
  • Blocker escalation

Monthly:

  • Progress report for management
  • Priority update (new vulnerabilities, business changes)

Step 4: Retest

After the fix - verification. Not “admin says he fixed it.” The pentester returns and checks:

  • Is the vulnerability actually fixed?
  • Did the fix introduce new problems?
  • Is coverage complete (all variants)?

Only after a positive retest is the vulnerability closed.

Remediation Support - partner, not policeman

The problem with the “pentest and goodbye” model

Traditional model:

  1. Pentest firm does the test
  2. Delivers the report
  3. Disappears

They leave the client with a list of 50 vulnerabilities and best wishes. It’s like a doctor who diagnoses a disease, prescribes 20 medications that can’t be found at the pharmacy, and says “good luck!”

The “Pentest + Fix” model

New approach:

  1. Penetration testing (as always)
  2. Prioritization session (2h with client)
  3. Package of remediation support hours
  4. Retest of fixed vulnerabilities

The pentester doesn’t just point out errors - they help fix them. They sit with the admin and together configure WAF, AD hardening, patches.

Benefits of remediation support

For IT:

  • Don’t have to learn everything themselves
  • Have an expert for difficult questions
  • Knowledge transfer - they learn in the process

For Security:

  • Vulnerabilities actually fixed
  • Closed cycle to show auditors
  • Measurable progress (not just “report delivered”)

For business:

  • One vendor from A to Z (less coordination)
  • Faster time-to-fix
  • Better ROI from pentests

Best practices for effective remediation

1. Establish SLA before the pentest

Before you order a pentest, agree internally:

  • Who will do the fixing (IT resources)?
  • In what timeframe (SLA per category)?
  • Who coordinates (CISO/Security/IT Manager)?

There’s no point doing a pentest if you don’t have people to fix things.

2. Attend the closing session

Pentesters usually do a “debriefing” after tests. Be there. Ask questions. Make sure you understand WHAT to fix and HOW.

3. Don’t be afraid to ask for help

If you don’t know how to fix a vulnerability - say so. It’s better to ask for support than leave a hole open. A good pentest vendor will help or point you in the right direction.

4. Automate where you can

Some vulnerabilities can be fixed automatically:

  • Missing patches → WSUS/SCCM
  • Weak passwords → GPO + password policy
  • Old TLS → group configuration

Automation = repeatability = less work at the next pentest.

5. Learn from each pentest

After closing the cycle:

  • What went well?
  • What was a blocker?
  • What processes to improve for the future?

Each subsequent pentest should be easier to remediate because you learn from mistakes.

6. Build remediation into the contract

Consider the “Pentest + Fix” model from the start:

  • Fixed price for pentest + package of remediation hours
  • Retest included in price
  • One vendor, one invoice

Summary

Remediation gap is one of the biggest gaps in organizational cybersecurity. Companies spend money on identifying problems but not on fixing them. It’s like buying a home alarm and never turning it on.

Closing the cycle requires:

  1. Prioritization - you know what to fix first
  2. Ownership - you know who’s responsible
  3. Support - you have someone to help
  4. Verification - you’re sure it’s fixed

A pentest without remediation is a wasted investment. A report in a drawer doesn’t protect against attack.


Have a pentest report and don’t know how to start fixing? We offer remediation support - we help fix found vulnerabilities. Contact us to discuss details.


Learn key terms related to this article in our cybersecurity glossary:


Learn More

Explore related articles in our knowledge base:


Explore Our Services

Need cybersecurity support? Check out:


See also:

Frequently asked questions

What is the remediation gap in penetration testing and how common is it?

The remediation gap is the persistent problem where organizations commission penetration tests, receive reports listing critical vulnerabilities, but fail to fix the identified issues within a reasonable timeframe. Research consistently shows that a significant percentage of critical vulnerabilities identified in pentests remain unresolved 90 days or more after report delivery. The gap exists because the pentest creates a deliverable but organizations frequently lack defined ownership, budget, prioritization processes, or technical capacity to translate findings into completed fixes.

What are the most common reasons organizations fail to remediate pentest findings?

Common reasons include unclear ownership where no specific team or individual is assigned accountability for each finding, insufficient budget allocated for remediation work that was not anticipated in annual planning cycles, competing IT priorities that push security fixes below other projects, technical complexity of certain remediations requiring significant architecture changes, and lack of follow-up verification creating no urgency to complete fixes. In some cases, findings are dismissed without adequate technical review using reasoning that underestimates actual exploitability.

How should organizations structure their remediation process to close the gap?

Effective remediation requires assigning named owners to every finding before the pentest report meeting concludes, establishing severity-based SLAs such as 30 days for critical findings and 90 days for high findings, integrating findings into existing ticket tracking systems rather than managing them in separate pentest documents, allocating dedicated remediation budget in advance of testing rather than scrambling for approval afterward, and scheduling verification testing with the pentest provider to confirm critical fixes are effective before closing them.

What role does verification testing play in closing the remediation gap?

Verification or re-testing is essential because organizations frequently consider a vulnerability resolved when a developer marks the ticket as fixed, without independent confirmation that the fix actually works. Developers commonly misunderstand the root cause and implement fixes that address symptoms rather than the underlying vulnerability. A formal re-test of critical and high findings by the original pentest team, or an independent tester, provides objective confirmation that the remediation is effective and documents the completed risk reduction for compliance and management reporting purposes.

Share:

Talk to an expert

Have questions about this topic? Get in touch with our specialist.

Sales Representative
Grzegorz Gnych

Grzegorz Gnych

Sales Representative

Response within 24 hours
Expert consultation
Individual approach

Providing your phone number will speed up contact.

Want to Reduce IT Risk and Costs?

Book a consultation - we respond within 24h

Response in 24h Custom quote No obligations