Why a report goes out of date
A penetration test describes the system on the days it was tested. Every release that changes how users sign in, what data is stored or what the API returns can create weaknesses that the report never covered.
Changes that usually justify a new test
Consider testing again after:
- A new or changed login, single sign-on or role model.
- A new public API, webhook or partner integration.
- A payment, billing or document-handling flow.
- A move to new cloud infrastructure or a new tenant model.
- A large new module that adds many pages or endpoints.
What the rules say
PCI DSS asks for penetration testing after significant infrastructure or application changes, in addition to regular testing. SOC 2 and ISO/IEC 27001 do not name a test frequency, but auditors and customers commonly expect evidence from the last 12 months. Check the exact wording that applies to you.
Planning around releases
Agree the test window before the release freezes, not after launch. Test the build that will ship, fix the high findings, then retest so the final report shows them closed. Smaller changes can often be covered by a focused test on only the changed areas.
Sources
General guidance, not legal, audit or compliance advice. Confirm requirements with your auditor or assessor.



