How often should a business run a penetration test?
We recommend at least once a year, and again after any significant change. Neither ASD's Essential Eight nor CPS 234 sets a fixed interval. For APRA-regulated entities, CPS 234 ties testing frequency to how fast threats and assets change, how critical they are and the consequences of an incident.
In detail
Neither CPS 234 nor ASD's Essential Eight sets a penetration testing interval for a private business. The Essential Eight sets fixed intervals for vulnerability scanning, and CPS 234 requires APRA-regulated entities to review their testing program at least annually. We recommend a yearly test plus another after any significant change.
Under CPS 234 paragraph 27, an APRA-regulated entity must test its controls through a systematic testing program whose nature and frequency are commensurate with the rate at which vulnerabilities and threats change, the criticality and sensitivity of the asset, the consequences of an incident, exposure to environments where it cannot enforce its policies, and how often the assets change.
The same standard has the sufficiency of the program reviewed at least annually or on a material change to information assets or the business environment (paragraph 31), testing done by appropriately skilled and functionally independent specialists (paragraph 30), and deficiencies that cannot be remediated in a timely manner escalated to the Board or senior management (paragraph 29).
NIST SP 800-115 says resource availability is often a limiting factor in the type and frequency of assessments, and recommends a repeatable and documented methodology, which it says provides consistency and structure to assessments. Its footnote records the US federal rule under FISMA: testing and evaluation at a frequency depending on risk, but no less than annually.
| Change | What the test covers |
|---|---|
| A new application, API or online service goes live | The new code and its authentication, authorisation and input handling |
| An authentication change: single sign-on, a new identity provider or a new MFA method | The sign-in paths and every way around them |
| A cloud migration or a new hosting arrangement | The exposed services, the identities and the configuration in the new environment |
| A merger, an acquisition or a new integration with a partner's systems | The connection points and the trust each side extends to the other |
| An incident, once remediation is finished | The path the attacker used, and whether the fix holds |
ASD's Essential Eight sets vulnerability scanning intervals (at least daily for online services at Maturity Level One), and these are separate from penetration testing.

For an Australian organisation
CPS 234 applies to ADIs, general insurers, life companies, private health insurers and RSE licensees (paragraph 2). ASD does not require an Essential Eight implementation to be checked by an independent party, though an independent assessment may be required by a government directive or policy, a regulatory authority or a contract.
Outside APRA regulation and any contract or government directive that requires independent assessment, neither CPS 234 nor the Essential Eight sets a testing interval, and neither places a frequency obligation on a private firm.
The interval is the business's own decision: write it into the security policy and the security schedule of client contracts, with the changes listed in the table as the reasons to bring a test forward.
