ISM lookup / Cyber security incidents

ISM-0917 · September 2026

Handling and containing malicious code infections

Guidelines for cyber security incidents / Responding to cyber security incidents / Handling and containing malicious code infections

Official control wording

When malicious code is detected, the following steps are taken to handle the infection: - the infected systems are isolated - all previously connected media used in the period leading up to the infection are scanned for signs of infection and isolated if necessary - antivirus applications are used to remove the infection from infected systems and media - if the infection cannot be reliably removed, systems are restored from a known good backup or rebuilt.

Applicability

  • Non-classified (NC)
  • OFFICIAL: Sensitive (OS)
  • PROTECTED (P)
  • SECRET (S)
  • TOP SECRET (TS)

These are ASD’s applicability markings. Select and tailor controls for your system’s risk, classification and operating context with the system owner and authorising officer.

Implementation guidance

This control is included as official reference material. We have not published a reviewed Kubernetes implementation mapping for it. Browse the 23 guides with bounded public mappings.

Official source

ASD’s ISM OSCAL v2026.09.4 · Original catalogue JSON · Pinned checksums and edition details

Control source identifier: ism-0917. Check the official release before relying on this snapshot for an assessment.

Official control wording and applicability: Australian Signals Directorate, © Commonwealth of Australia 2026. September 2026 ISM, OSCAL v2026.09.4, reproduced under CC BY 4.0. Formatting is adapted for this website.

Latticework Systems’ implementation guidance is our interpretation. Provenance and scope.