Last verified: 2026-08-15

• AI application controls (first of their kind): ISM-2112 — AI applications that process classified data have their ability to directly access external public data sources disabled; ISM-2113 — AI applications flag organisationally-defined risky actions for human approval before execution; ISM-2114 — behavioural/performance baselines are established for AI applications and monitored for deviations. Further AI-related controls cover secure deletion of AI chat prompts/outputs, AI-augmented vulnerability assessments and software security testing, and AI-augmented event detection — confirm current control numbers against the ISM June 2026 changes document on cyber.gov.au before citing them.
• Cryptography: the ASD Approved Cryptographic Protocols control now covers all scenarios where data is encrypted in transit (not only traffic crossing network infrastructure), and a new control recommends mobile apps encrypt sensitive/classified data over public networks with ASD-approved cryptography.
• Essential Eight: none of the June 2026 controls carry an Essential Eight mapping — E8 maturity work and June-2026 ISM compliance are separate workstreams.

1. Leverage existing IRAP reports: agencies consume the CSP's current IRAP assessment report for the inherited control layer rather than commissioning a fresh assessment of the provider — the agency assesses only its own configuration/workload layer
2. Shared responsibility matrix (use that name): a documented split of which ISM controls the provider vs the agency owns, reviewed annually
3. Core control set: tenant isolation; ASD-approved cryptography for data in transit AND at rest; MFA for privileged and remote access; event logging with agency access; personnel security (clearances/screening for support staff)
4. Data sovereignty and residency: where data is stored, processed, and supported from — including subcontractors and offshore support locations — with contractual residency commitments
5. Contractual assurance: incident notification to the agency, evidence provision, right to audit

1. Define the system (boundary, assets, classification, security objectives)
2. Select controls (using applicability markings for the system's classification)
3. Implement controls
4. Assess controls (via IRAP or internal assessment)
5. Authorise the system (Authorising Official signs System Security Plan)
6. Monitor the system (continuous monitoring, event logging, periodic re-assessment)

1. Confirm: system classification level, operating environment (cloud/on-prem/hybrid), current security posture
2. Produce a control table covering all applicable chapters for the stated classification
3. For each control: Status (Implemented / Partial / Not Implemented / N/A), Evidence Needed, Gap Notes
4. Summarise critical gaps; recommend remediation priority
5. Offer to produce a System Security Plan (SSP) outline or remediation roadmap

• ✅ Implemented — control in place with documented evidence
• 🟡 Partial — partially implemented, evidence incomplete
• ❌ Not Implemented — no implementation
• N/A — formally excluded with documented justification

1. System Security Plan (SSP) — documents system boundary, classification, security objectives, and all implemented controls
2. Security Risk Assessment — identify threats, vulnerabilities, and residual risks
3. IRAP Assessment (mandatory for systems handling PROTECTED+, recommended for OS) — independent review by ASD-certified IRAP assessor
4. Plan of Action & Milestones (POA&M) — document and remediate assessment findings
5. Authorisation to Operate (ATO) — Authorising Official reviews residual risk and signs off
6. Ongoing monitoring — continuous control monitoring, annual or biennial re-assessment

• Confirm IRAP assessor is listed on the ASD IRAP register
• Artefacts required: SSP, network diagrams, asset register, risk register, policy suite, evidence of implemented controls, previous assessment findings (if any)
• Assessment scope: all controls relevant to the system's classification level
• Re-assessment: every 24 months minimum, or after significant change
• Outcome: IRAP Assessment Report → feeds the ATO decision

• Always include: Purpose, Scope, Classification marking, ISM control references, Review cycle, Document owner
• Key documents: System Security Plan (SSP), Security Risk Assessment, Incident Response Plan, Change Management Plan, Continuous Monitoring Plan
• Map each document section to the relevant ISM chapter and control ID(s)

• The Essential Eight is a prioritised subset of ISM controls — the eight highest-value mitigation strategies
• Essential Eight compliance ≠ full ISM compliance; it addresses a subset of the broader control set
• Essential Eight Maturity Levels (ML0–ML3) measure implementation depth for each of the eight strategies
• For full government compliance, both ISM controls AND Essential Eight targets apply
• Reference: ASD publishes an Essential Eight to ISM control mapping document

• references/guidelines-overview.md

  — All 22 ISM guideline chapters with domain summaries and key control areas

• references/control-applicability.md

  — Full control applicability framework, classification scoping rules, and Essential Eight mapping

• User asks about a specific chapter or domain → load

  guidelines-overview.md

• User asks about control applicability, scoping, or classification → load

  control-applicability.md

• Gap analysis for any classification level → load both
• IRAP or authorisation preparation → load both

This skill provides general compliance information, not legal advice. Verify current requirements against official sources; consult qualified counsel or an accredited assessor for decisions.