Penetration Testing Is a Point in Time. How Often Should You Test, and What Happens In Between?

6 Minute read
Seyton Hayes
Technical Director | Digital Forensics & Incident Response Specialist
Penetration Testing Is a Point in Time. How Often Should You Test, and What Happens In Between?: Cyber Resilience article cover
In this article

Share this article

At a technology strategy session in November 2026, the IT executive of a South African hospital group summed up a frustration we hear often. Once a year an external team runs a penetration test, the findings are fixed, the board is told the organisation looks sharp, and the box is ticked. “But a pen test is a point in time,” he said. The moment the testers leave, the environment changes again and nobody is checking.

He was right, and he was also clear that he did not want to give up independent testing. What he wanted was visibility in between: something that would tell his team, every week or month, when a server was unpatched or a new weakness had appeared.

That is the right way to think about penetration testing frequency. The question is not only how often to test, but how you stay informed between tests.

The short answer

Most organisations should commission an independent penetration test at least once a year and after any significant change to systems, applications or network design. Internet-facing and high-value systems may need testing more often. Between tests, continuous vulnerability scanning and monitoring keep you informed of new weaknesses so they can be fixed before the next test, or an attacker, finds them.

Why once a year is no longer enough on its own

Attackers are moving faster than annual cycles. Mandiant’s M-Trends 2026 estimates the mean time to exploit a vulnerability is now minus seven days, meaning many vulnerabilities are exploited before a patch is available. Verizon’s 2026 Data Breach Investigations Report found that exploiting vulnerabilities has overtaken stolen credentials as the most common way into an organisation, at 31% of breaches.

A penetration test remains the best way to find out what an attacker could actually achieve in your environment. It simply cannot tell you about the vulnerability published the week after the testers leave.

How often should you test?

A useful benchmark comes from the payment card industry. PCI DSS v4.0.1 (requirement 11.4) requires internal and external penetration tests at least once every 12 months and after any significant infrastructure or application change. Even if PCI DSS does not apply to you, that combination of a calendar floor plus change-based triggers is sound practice.

Changes that should trigger a test

  • A new internet-facing application, portal or API
  • Migration of critical systems to the cloud, or a new hosting provider
  • Major changes to network design, segmentation or remote access
  • A merger, acquisition or new subsidiary joining the network
  • After a significant security incident, once remediation is complete
  • New client, regulator or insurer requirements

When to test more often

Consider six-monthly or quarterly testing for systems that are internet-facing, hold sensitive personal or financial data, or change frequently. Application tests should follow major releases.

A twelve-month cycle showing an annual independent penetration test, change-triggered tests, and continuous vulnerability scanning and remediation in between
Independent testing sets the baseline. Continuous scanning and remediation keep it current.

Penetration test, vulnerability assessment or continuous vulnerability management?

These are often confused, and they answer different questions. Our article on vulnerability assessment services covers the assessment side in more detail.

Penetration testVulnerability assessmentContinuous vulnerability management
Question it answersWhat could an attacker actually achieve?Which known weaknesses exist right now?Are new weaknesses being found and fixed on time?
MethodSkilled testers chain weaknesses together, manually and with toolsMostly automated scanning, validated by an analystScheduled authenticated scanning, prioritisation, remediation tracking and retest
Typical frequencyAnnually and after major changePoint in time, often quarterlyWeekly to monthly, ongoing
OutputExploited attack paths, business impact, prioritised fixesList of vulnerabilities with severityTrend of open risk, overdue fixes, coverage
IndependenceShould be independent of the team being testedCan be internal or externalUsually internal or managed service

What should happen between tests

  • Know what you own. You cannot scan what you have not inventoried. Keep an up-to-date list of internet-facing and internal assets, including cloud services.
  • Scan inside, not only outside. Authenticated internal scans find the missing patches and weak configurations that attackers use to move once they are in.
  • Prioritise by exploitability, not score alone. Use the severity score as a starting point, then raise anything listed in CISA’s Known Exploited Vulnerabilities catalogue or with a high EPSS exploit-probability score, especially on internet-facing systems.
  • Give the fixers the findings. Remediation stalls when results sit with one team and the fix with another.
  • Track to closure and retest. Agree fix timeframes by severity and report what is overdue.
  • Watch for exploitation. Monitoring through a SOC catches attempts to use weaknesses you have not fixed yet.

“If the IT team doesn’t have direct access to the vulnerability scan results, the mitigation effort generally falls short. The people fixing things need to see what’s wrong and confirm they’ve actually fixed it.”

Qurash Ramlal, Customer Success Manager, Cyber Resilience

This is what frameworks expect as well. CIS Control 7 calls for continuous vulnerability management, and ISO/IEC 27001:2022 includes the management of technical vulnerabilities among its Annex A controls.

Five-step continuous vulnerability management loop: discover, scan, prioritise, fix, verify
The loop that runs between penetration tests.

Getting more value from each penetration test

  • Scope it properly. Agree rules of engagement covering in-scope ranges, applications, testing windows and exclusions before testing starts.
  • Test both perspectives. External tests show what the internet sees; internal tests show what happens after a phishing click or a compromised supplier account.
  • Fix, then retest. A finding is only closed when a retest confirms it.
  • Look for root causes. If the same misconfiguration appears every year, the problem is a process, not a server.
  • Keep the tester independent. Internal scanning complements an independent test; it does not replace it.

Where Cyber Resilience fits

Our testing team began as forensic investigators, so findings are validated, prioritised and written for both the technical team and the board. We run penetration testing and vulnerability assessments, and provide ongoing vulnerability management supported by our TOTALIS platform, which ranks vulnerabilities using CVSS, EPSS and VPR and tracks each fix to closure.

Next step: Ask us to review your testing programme. We will suggest a cycle of independent testing and continuous scanning that fits your risk and budget.

Key takeaways

  • Test at least annually and after significant change; test high-value, internet-facing systems more often.
  • A penetration test is a snapshot. Continuous vulnerability management keeps you informed in between.
  • Prioritise by real-world exploitability and give the people fixing issues direct access to findings.

Related Insights

Seyton Hayes

Technical Director | Digital Forensics & Incident Response Specialist

Seyton Hayes is a cybersecurity specialist with more than 25 years of experience across enterprise security, incident response, digital forensics, and operational resilience.

Having previously led breach response and digital forensics capabilities within complex banking environments, Seyton specialises in helping organisations investigate incidents, strengthen security operations, and respond effectively to evolving cyber threats.Seyton’s technical leadership and practical experience in defending large-scale enterprise environments make him a trusted advisor to organisations seeking to strengthen operational resilience and respond effectively to evolving cyber threats.

Expertise

Incident Response • Digital Forensics • Threat Intelligence • Security Operations • Ethical Hacking

Frequently asked questions

How often should a penetration test be done?

At least once a year and after any significant change to systems, applications or network design. Organisations with internet-facing services that hold sensitive data, or that change often, may need six-monthly or quarterly testing of those systems.

Is a vulnerability scan the same as a penetration test?

No. A vulnerability scan lists known weaknesses, mostly automatically. A penetration test uses skilled testers to exploit and chain weaknesses to show what an attacker could actually achieve and what the business impact would be.

Can internal vulnerability scanning replace an external penetration test?

No. Continuous internal scanning keeps you informed between tests, but an independent penetration test provides an objective view that boards, auditors, insurers and clients rely on. The two work best together.

What should happen after a penetration test?

Prioritise the findings by risk, assign owners and deadlines, fix them, then retest to confirm closure. Look for root causes behind repeat findings and report progress to management.

How long does a penetration test take?

It depends on scope. A focused external test can take days; a full-scope engagement covering internal, external, wireless and application testing takes longer. Scope, testing windows and rules of engagement are agreed before testing starts.

Related Insights

Cyber resilience insights grounded in operational reality.

Practical guidance, operational perspectives, regulatory insights, and forensic-led thinking across cybersecurity, governance, resilience, and digital risk.

Need Clarity on your CURRENT RESILIENCE POSTURE?

Whether you need a focused assessment, operational support, governance maturity, or incident response guid-ance, we will help you understand your current position and build a practical path forward.