The ISM includes a control requiring vulnerability assessments and penetration tests prior to deployment, before significant changes, and at least annually, so testing is an expected part of securing systems assessed against it. An IRAP assessment evaluates whether such controls are in place and documents residual risk; penetration testing provides the technical evidence that supports that picture. Test before deployment, on significant change, and at least annually, and remediate findings before the assessment.
IRAP assesses controls against the ISM, and one of those controls asks, in effect, whether the system has been tested. So penetration testing and IRAP are naturally linked.
Does the ISM require penetration testing?
Yes, in substance. The Information Security Manual includes a control calling for vulnerability assessments and penetration tests to be conducted on systems, prior to deployment, before or after significant changes, and at least annually. So testing is an expected part of securing a system that will be assessed against the ISM, not an optional extra. The related June 2026 additions also introduced a control on using AI to augment vulnerability assessments and penetration tests, reflecting how the discipline is evolving. (Control numbers shift between ISM releases, so always check the current ISM for the exact reference; the durable point is the testing-on-deployment, on-change, and at-least-annually expectation.)
An IRAP assessment evaluates whether a system meets the applicable ISM controls and documents the residual risk for an authorising officer to accept. Because testing is one of the things the ISM expects, an IRAP assessment will look for evidence that vulnerability assessment and penetration testing are being done and that findings are managed. So while the assessment itself is a controls assessment rather than a penetration test, testing is closely tied to it.
How testing fits IRAP, and when to do it
Penetration testing supports an IRAP-assessed system by providing evidence that technical controls actually work and that vulnerabilities are being identified and remediated, which is exactly what the relevant ISM control expects. Test results feed the risk picture that the IRAP report and its risk management describe, giving the authorising officer real technical assurance rather than documentation alone.
On timing, align with the ISM expectation: test prior to deployment, before or after significant changes, and at least annually thereafter. There are two practical reasons to test ahead of an IRAP assessment specifically. First, testing before the assessment allows findings to be remediated so they do not surface as issues in the report or as residual risks the authorising officer must weigh. Second, ongoing testing supports maintaining the authorisation between assessments, since a system’s security degrades as it changes. So testing is part of both preparing for an IRAP assessment and sustaining an authorised system over its life. For an organisation preparing for IRAP that wants testing to fit the ISM expectations, Cybernion can help through IRAP advisory and penetration testing.
Frequently asked questions
Does the ISM require penetration testing?
The Information Security Manual includes a control calling for vulnerability assessments and penetration tests to be conducted on systems, prior to deployment, after significant changes, and at least annually. So testing is an expected part of securing systems assessed against the ISM. An IRAP assessment evaluates whether such controls are in place, so penetration testing is closely tied to IRAP even though the assessment itself is a controls assessment rather than a pen test.
How does penetration testing relate to an IRAP assessment?
An IRAP assessment evaluates a system against the ISM controls and documents the residual risk for an authorising officer. Penetration testing supports this by providing evidence that technical controls work and that vulnerabilities are being identified and managed, which is one of the things the ISM expects. Testing is generally done as part of preparing for and maintaining an authorised system, and its results feed the risk picture the assessment describes.
What ISM control covers penetration testing?
The ISM includes a control requiring that vulnerability assessments and penetration tests are conducted for systems prior to deployment, before significant changes, and at least annually, with a related control covering the use of AI to augment these activities. The exact control numbers change between ISM releases, so refer to the current ISM, but the requirement to test on deployment, on significant change, and at least annually is the key point.
When should we pen test for an IRAP-assessed system?
Aligned with the ISM expectation, test prior to deployment, before or after significant changes to the system, and at least annually thereafter. Testing before an IRAP assessment helps ensure findings are remediated so they do not become issues in the report, and ongoing testing supports maintaining the authorisation between assessments. So testing is part of both preparing for and sustaining an authorised system.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- Information Security Manual, Australian Signals Directorate, 2026
- Infosec Registered Assessors Program, Australian Signals Directorate, 2026
Last updated: 30 August, 2026
