The short answer
At least once a year, and again after any big change to your systems. That is what most auditors and frameworks expect, and some, like PCI DSS, require it.
Once a year is the baseline
Most compliance rules and auditors expect a pentest every year:
- PCI DSS requires internal and external tests at least every 12 months.
- SOC 2 and ISO 27001 auditors usually expect a yearly test.
- For HIPAA, a yearly test is common practice, and HHS has proposed making it a rule.
Your customers often ask too. A report more than a year old is one of the first things a big buyer's security team will question.
Test again after big changes
A change can open a new door. Plan an extra test, even a small one, after:
- A major new feature or release
- A new login or single sign-on system
- A move to a new cloud, or a big change to your cloud setup
- Buying or merging with another company
- Adding AI that can take actions
When to test more often
Some teams test twice a year, or test each big release. It makes sense when:
- You ship big changes every few weeks.
- You hold very sensitive data, like health or payment data.
- Your customers or contracts ask for it.
Time it with your audit
Plan the test so the report, the fixes and the retest are all done before your audit or renewal.
- 1Pick your dateCount back from your audit or customer deadline.
- 2Leave time to fixMost teams need a few weeks to fix what is found.
- 3RetestA retest shows the fixes worked. Auditors like to see it.
We can start within a week, and most tests take one to three weeks.