ASD ISM 2028 Test software artefacts for security weaknesses
What it says
All software artefacts are tested to detect known weaknesses using static application security testing (SAST), dynamic application security testing (DAST) or software composition analysis (SCA), depending on the software artefact type, before being imported into the authoritative source for software.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Before any software artefact enters the authoritative source for software, test it for known weaknesses with SAST, DAST or SCA, whichever suits that type of artefact.
All software artefacts must be tested for known weaknesses before they are imported into the authoritative source for software, using the method that suits each artefact type:
- SAST (static application security testing) examines source or compiled code without running it.
- DAST (dynamic application security testing) probes a running application from outside.
- SCA (software composition analysis) identifies third-party components and their published vulnerabilities.
The test is run on the artefact itself before import. A supplier's own test report does not replace it.
Free. Save your status, tasks and notes.
Why it matters
An artefact can bring in a known weakness, such as a library version with a published vulnerability. Testing before import can reveal it while the artefact can still be refused or replaced with a fixed version, before any software is built on it.
How to implement
Match each artefact type to SAST, DAST or SCA.
For example, use SAST for source code and scripts, SCA for third-party libraries, container images and binaries, and DAST for a component that runs as a service. Decide which method covers configuration files too, so no type held in the authoritative source goes untested.
Run the tests in the import route, before the artefact is stored.
Use the repository manager's policy checks, or an import pipeline that tests artefacts in a staging area and promotes only tested ones. For DAST, run the component in an isolated test environment first. Test the exact version being imported, not an earlier one or a supplier's report.
Set what a finding means for the import.
For example, refuse artefacts with known vulnerabilities above a severity you set, or import a fixed version, tracking accepted findings in the issue tracker (ISM-2025) for timely resolution (ISM-1754). Where a third-party component has a software bill of materials, ISM-2054 requires using it to ensure no known vulnerabilities, so accept none.
Block routes that skip testing.
Remove direct uploads that bypass the test stage, and make a failed or unfinished test refuse the import. Where a hosted repository cannot run tests on import, bring artefacts in through a staging repository you control.
Keep it running
Keep test tools and their vulnerability data current, since SCA only finds what has been published. Recheck the mapping when a new artefact type, language or import route is added; artefacts already imported are retested under ISM-2102.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
The mapping of artefact types to SAST, DAST or SCA, and a breakdown of the artefact types actually held in the authoritative source.
Look at
Whether every type held, including configuration files and binaries, has a test method suited to it.
Good evidence
Every artefact type found in the authoritative source is mapped to SAST, DAST or SCA as suits it, with no type left untested.
- Check 2 of 3What an auditor asks for
Ask for
Test records for a sample of artefacts picked from the authoritative source itself.
Look at
Whether each was tested with its mapped method, on that exact version, before its import date.
Good evidence
Each sampled artefact has a SAST, DAST or SCA result for that exact version dated before its import, not only a supplier report or a test run after import.
- Check 3 of 3What an auditor asks for
Ask for
A demonstration importing a library version with a published vulnerability, and an import attempted through each route with the test stage unavailable.
Look at
Whether the test detects the weakness, and whether any route lets an artefact in untested.
Good evidence
The test reports the published vulnerability before import and the agreed rule is applied, and no route imports an artefact without a completed test.
Mappings
Closest match in ISO/IEC 27001: A.8.25, Secure development life cycle, which this control partially meets.
ISO/IEC 27001: 2 mappings
This control partially meets A.8.25.
ISM-2028 requires organisations to test software artefacts for known weaknesses using SAST/DAST/SCA before they are imported into the authoritative source for software. Annex A 8.25 requires secure development lifecycle rules to be established and applied, which typically includes security testing activities and quality gates. ISM-2028 is a specific SDL rule focused on vulnerability detection prior to import, whereas Annex A 8.25 also covers many other secure engineering practices beyond testing.
This control partially meets A.8.29.
ISM-2028 requires all software artefacts to be tested for known weaknesses (e.g., via SAST/DAST/SCA) before being imported into an authoritative software source. Annex A 8.29 requires organisations to define and implement security testing as part of development and acceptance processes, which includes (but is not limited to) the types of vulnerability testing ISM-2028 calls out. Annex A 8.29 is broader because it covers the overall security testing process across the SDLC and acceptance, while ISM-2028 is a specific gate focused on pre-import testing for known weaknesses.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




