// requirements → implementation → evidence

ISM implementation guides

23 guides grounded in a pinned public mapping. Each pairs implementation suggestions with evidence to retain and the specific limits of the mapped checks.

Every mapping is partial. Kubernetes manifests, admission policies and scanner findings can support an assessment, but cannot prove that a whole ISM control is met. These guides confer no full-control compliance or IRAP certification.

Responsibility must be agreed across the platform, workload and organisation. Managed cloud services do not automatically establish inherited controls; review the provider’s applicable evidence and your system boundary.

Coverage gaps

The other 1120 controls have reference pages only. Cloud-provider configuration, human access, organisational processes and runtime effectiveness need evidence beyond these detectors. New September requirements for credential revocation, backup immutability, reproducible builds and AI agent behaviour are not inferred from generic manifest checks.

For example, ISM-1405 has an official reference page, but no guide in this bounded set. The absence of a mapped finding means no conclusion about the control.

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.

Need ISM evidence from your Kubernetes platform?

Tell us which controls your assessor is asking about. We'll work out what your cluster can show and what has to come from somewhere else.

Book a free discovery call →