# IRAP customer authorisation brief

Australia IRAP assessment | Worked example with fictional data

Step: Submit the authorisation package and monitor changes
Owner: Consuming organisation + authorising officer + service owner
When: Before operation under the proposed authorisation

## 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.

## Example

### 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.

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

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

Official reference: ASD cloud assessment and authorisation
https://www.cyber.gov.au/publication/cloud-assessment-and-authorisation

Use the current rules and any prescribed forms for your engagement.
