Start hereAgree the operating boundary and assessor
~63 days leftOpen step
Guide library
Audit report Asia–Pacific

Australia IRAP assessment

Australian IRAP security assessment and cloud authorisation

Scope an independent assessment with an ASD-endorsed assessor, organise control evidence and give the consuming organisation what it needs to make a risk decision.

Issuing authority
Australian Signals Directorate (ASD)
Timing
Confirm the assessment timetable with the assessor. The ASD procurement guidelines call for in-scope outsourced cloud services to undergo IRAP assessment at least every 24 months. Significant changes can require revalidation earlier.
Reviewed
Inside this guide
4 steps · 4 templates

Who it applies to

Organisations commissioning, supporting or relying on an IRAP assessment of an ICT system, cloud service, gateway or GovLink at SECRET or below. Check the consuming organisation’s requirements and assurance needs before agreeing on the scope.

What you’ll produce

A scoped assessment report with control findings, limitations and remediation, plus a separate authorisation decision from the consuming organisation when required.

Read the report’s boundary, control findings and customer responsibilities. The consuming organisation decides whether the proposed use is acceptable. Keep the actual authorisation and any conditions in its own decision record.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What will reviewers test, and for which period?
Confirm scope, report purpose, testing period or as-of date and the evidence the reviewer expects. Reserve time for delayed records, walkthroughs and retesting.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Walk through one recent transaction or control with the owner and a reviewer. Pull the full source list and trace an item back to original evidence.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor missing populations, controls without a reviewer and overdue fixes. Bring potential issues with the reporting period to the sponsor.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

Australia IRAP assessment kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Agree the operating boundary and assessor · System owner + consuming organisation + endorsed assessor [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Walk through one recent transaction or control with the owner and a reviewer. Pull the full source list and trace an item back to original evidence.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Does the report cover the exact product, regions, features and support locations the customer plans to use?
  • Which controls does the customer operate, and who can accept the residual risk?

Worked scenario

A SaaS provider is asked to support a Commonwealth customer. The provider and assessor define the Australian hosting region, identity, backups and support operations in scope. The customer reviews its own configuration and the provider’s findings before seeking authorisation for its intended use.

What to read next

  • Essential Eight

    Plan and assess implementation of ASD’s Essential Eight mitigations.

  • APRA CPS 234

    Check separate information security obligations for an APRA-regulated entity.

FROM THE SOURCE

Cases and numbers

ISM procurement guidance · September 2026

24 monthsMaximum interval specified for covered outsourced cloud reassessments

Use a dated cloud assessment and track changes between reviews

ASD’s cloud FAQ says reaching 24 months does not automatically invalidate a report. Customers should check whether the scope and evidence remain accurate and whether the provider has issued addenda.

What to check Track the assessment date, latest addendum, covered service and each material change in your supplier register.

ASD cloud assessment and authorisation FAQ (opens in a new tab)
DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • Before assessment starts

    Agree which ISM release applies

    For in-scope outsourced cloud assessments, use the latest release available before the start or a subsequent release.

    Official reference (opens in a new tab)
  • At least every 24 months

    Reassess covered outsourced cloud services

    Check significant changes between assessments and maintain relevant addenda and current assurance evidence.

    Official reference (opens in a new tab)
  • Before relying on the service

    Record the consuming organisation’s authorisation

    Match findings and the customer’s control responsibilities to its intended environment and use.

    Official reference (opens in a new tab)
The whole journeyabout 63 days across 4 steps
  1. 01Agree the operating boundary and assessor, System owner + consuming organisation + endorsed assessor, about 14 days
  2. 02Build control evidence for the actual environment, Security lead + platform operations + control owners, about 21 days
  3. 03Review findings and agree remediation, Assessor + system owner + remediation owners, about 14 days
  4. 04Submit the authorisation package and monitor changes, Consuming organisation + authorising officer + service owner, about 14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 4 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Agree the operating boundary and assessorSystem owner + consuming organisation + endorsed assessorBefore commissioning the assessmentSet a start dateIRAP scope and responsibility matrixOpen
Build control evidence for the actual environmentSecurity lead + platform operations + control ownersBefore assessment fieldworkSet a start dateIRAP control evidence registerOpen
Review findings and agree remediationAssessor + system owner + remediation ownersDuring and after assessmentSet a start dateIRAP findings and remediation recordOpen
Submit the authorisation package and monitor changesConsuming organisation + authorising officer + service ownerBefore operation under the proposed authorisationSet a start dateIRAP customer authorisation briefOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Agree the operating boundary and assessor

    Who System owner + consuming organisation + endorsed assessor When Before commissioning the assessment

    Confirm the use case, information classification, exact service, regions, physical facilities, subprocessors, external services and customer-operated controls. Verify the named assessor’s endorsement. Agree the ISM release, assessment scope, deliverables, evidence access and schedule.

    What to produce

    IRAP scope and responsibility matrixSpreadsheet

    Gather first

    • Customer use case
    • Classification and handling rules
    • Service architecture
    • Supplier and region inventory
    • Current ISM and assessor engagement

    How to prepare it

    1. List in-scope products, features, sites, operational teams and types of data. Account for support, telemetry, backup, restoration and dependencies as well as production traffic.
    2. Assign an implementing and evidence owner for each responsibility across the provider, customers and third parties. Record exclusions and how a customer can keep excluded features out of its configuration.
    3. Have the assessor and system owner agree the boundary, ISM version, assessment output and protected evidence access.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional service scope
    Banksia Casework, Australian production region and the declared disaster-recovery region. The system owner records backup and support locations separately.
    Shared control
    The provider operates the identity integration. The consuming organisation manages group membership and reviews access to its tenant.
    Evidence gap
    A new analytics subprocessor is outside the agreed scope. Product records which feature uses it and how the customer can disable it.

    Check before handing it over

    The scope names the customer use, specific environments, responsibility owners and material exclusions.

    Give the signed boundary and responsibility matrix to the assessor and both organisations’ control owners.

  2. 02

    Build control evidence for the actual environment

    Who Security lead + platform operations + control owners When Before assessment fieldwork

    Map control applicability, implementation and responsibilities to source evidence. Index diagrams, dated configuration exports, policy, operational records and relevant third-party assurance. Match inherited evidence to the same services, locations and control periods.

    What to produce

    IRAP control evidence registerSpreadsheet

    Gather first

    • Agreed ISM release
    • Applicability matrix
    • Architecture
    • Configuration and operating records
    • Inherited assurance documentation

    How to prepare it

    1. For each relevant control, record its reference, intended implementation, responsibility, status, evidence date and source owner.
    2. Gather redacted records that show the control in the assessed environment. If reusing assurance, confirm service, configuration, location, period and responsibility before linking it.
    3. Put sensitive records in the agreed restricted workspace. Assign outstanding items a due date and document when the assessor reviews each record.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence row
    Banksia privileged access review. Security links a dated review record, the approved access list and evidence of owner sign-off for the production region.
    Inherited assurance
    Hosting provider report covers a named data centre. Compliance verifies the location against the system inventory and documents facility and customer responsibilities.

    Check before handing it over

    The assessor can trace each statement to dated evidence, record a finding and identify open gaps.

    Provide scoped access to the assessor and give each evidence owner a list of unresolved items.

  3. 03

    Review findings and agree remediation

    Who Assessor + system owner + remediation owners When During and after assessment

    Support the assessor with factual evidence and record limitations. Validate the reported boundary, evidence dates, control findings and customer responsibilities. Assign findings an owner, due date, proposed treatment and proof of retest or review.

    What to produce

    IRAP findings and remediation recordSpreadsheet

    Gather first

    • Assessment report
    • Report control identifiers
    • Scope and limitations
    • Risk evaluation
    • Remediation and verification records

    How to prepare it

    1. Capture each finding under the report reference and keep the assessor’s finding distinct from the organisation’s response. Check which environments and customer uses are affected.
    2. Assign an owner, action, due date and acceptance criteria. Record dependencies and interim measures, then attach dated evidence of the completed fix.
    3. Ask the assessor about verification or an addendum where needed. Show any remaining risk and whose decision is required.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional finding
    Periodic access review evidence is missing for a support group. The service owner retrieves the current membership, removes stale assignments and arranges an independent review of the updated record.
    Closure evidence
    Approved membership export, change record, review date and assessor verification where agreed.

    Check before handing it over

    Open findings and verified actions are both traceable to the assessment report and relevant environment.

    Give the system owner the updated findings and give the risk owner a summary of unresolved items.

  4. 04

    Submit the authorisation package and monitor changes

    Who Consuming organisation + authorising officer + service owner When Before operation under the proposed authorisation

    Review the report against the proposed use and local controls. Have the authorising officer record the residual risk, decision and conditions. Track changes to locations, service features or suppliers, and ask for a new assessment or addendum when appropriate.

    What to produce

    IRAP customer authorisation briefMemo

    Gather first

    • Assessment report and addenda
    • Customer architecture and control matrix
    • Findings and mitigation status
    • Local risk criteria
    • Decision authority

    How to prepare it

    1. Validate scope and report currency against the intended deployment. Obtain the relevant report and addenda and record material changes or gaps.
    2. Explain the consuming organisation’s responsibilities and evidence. Summarise open findings and proposed controls in terms of business impact and the specific data and services in use.
    3. Give the authorising officer a decision record with scope, constraints, evidence, residual risk, expiry or review triggers and signatures. Track approval conditions after the decision.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional decision scope
    Banksia Casework in the approved region, with customer-managed identity and no analytics feature. The customer’s authorising officer records the exact use and review date.
    Change trigger
    A new hosting region, support provider or identity change triggers a review of the report and approved configuration before the scope expands.

    Check before handing it over

    A reader can identify which use was authorised, by whom, on what evidence and with which conditions.

    Give operations and procurement the approved boundary and every condition they must track.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes