Skip to content
Software development
ASD ISMISM-2102

ASD ISM 2102 Periodically test software artefacts for weaknesses

What it says

Existing software artefacts in the authoritative source for software are periodically tested to detect known weaknesses using SAST, DAST or SCA, depending on the software artefact type, throughout the software development life cycle.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Retest the artefacts already held in the authoritative source for software for known weaknesses at an interval you set, using SAST, DAST or SCA to suit each type, across the whole life cycle.

Software artefacts already stored in the authoritative source for software must be retested periodically for known weaknesses, throughout the software development life cycle including maintenance after release, using the method that suits each type:

  • SAST, static application security testing, which examines code without running it
  • DAST, dynamic application security testing, which probes a running application
  • SCA, software composition analysis, which finds third-party components with published vulnerabilities.

The control sets no interval, so the organisation sets one. Testing at import is ISM-2028.

Why it matters

A library that tested clean at import can have a published vulnerability months later, and pinned versions (ISM-2154) never update themselves. Periodic retesting can find such weaknesses in artefacts already in use, so they can be fixed rather than carried into every new release.

How to implement

  1. List the artefacts held in the authoritative source by type.

    Include third-party libraries, container images, compiled code and configuration files, including older versions still used by supported releases. The repository manager's component report or a software bill of materials helps. Map each type to SAST, DAST or SCA.

  2. Set the retest interval and record it.

    The control sets none, so base it on how quickly new vulnerabilities in your components are published and how exposed the software is. SCA tools that recheck stored components whenever new vulnerability data arrives give near-continuous coverage; schedule SAST and DAST reruns, and rerun SAST when its rules are updated.

  3. Run tests against everything stored, not only active projects.

    Schedule them in the repository manager or pipeline, so artefacts in projects nobody is changing are still tested. Keep each result with the date, artefact version and method used.

  4. Track and resolve what the tests find.

    Raise each finding in the issue tracker (ISM-2025) and resolve it in a timely manner, as ISM-1754 requires, usually by moving the pin to an approved fixed version (ISM-2154).

Keep it running

Add new repositories and artefact types to the schedule as they appear, and keep tools' vulnerability data current. A newly published vulnerability under active exploitation should prompt an immediate retest instead of waiting for the next interval.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    The set retest interval and how it was chosen, with the test history for a sample of artefacts picked from the authoritative source itself.

    Look at

    Whether each sampled artefact, including ones in projects no longer changing, was retested with the method suited to its type, and the longest gap between tests.

    Good evidence

    Every sampled artefact was retested with SAST, DAST or SCA as suits its type, and no gap between tests exceeds the set interval.

  2. Check 2 of 3What an auditor asks for

    Ask for

    Periodic test results from before and after the publication of a vulnerability the auditor picks from recent public advisories, in a component the repository's own component listing shows is held.

    Look at

    Whether the first periodic test after publication flagged it in every artefact the listing shows uses the component.

    Good evidence

    The first periodic test after publication flagged the weakness in every artefact that uses the affected component.

  3. Check 3 of 3What an auditor asks for

    Ask for

    The artefact types held in the authoritative source, compared with the types each periodic test covers.

    Look at

    Whether any type, such as container images or configuration files, is never retested.

    Good evidence

    Every artefact type held is covered by periodic SAST, DAST or SCA suited to it, with none left out.

Mappings

Closest match in ISO/IEC 27001: A.8.29, Security testing in development and acceptance, which this control partially meets.

ISO 27001

ISO/IEC 27001: 1 mapping

ISO 42001

ISO/IEC 42001: 1 mapping

  • A.6.2.4AI system verification and validationPartially overlaps

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.