Cybernion
← Insights

IRAP

Australian Government Information Classifications: OFFICIAL to SECRET

21 June 2026 · Updated 7 Nov 2026

Australian Government information classifications run from OFFICIAL through OFFICIAL: Sensitive, PROTECTED and SECRET to TOP SECRET, set by the damage a compromise would cause. The owning agency sets the level, not the provider. For IRAP, the ISM control set is the same at OFFICIAL: Sensitive and PROTECTED, while physical, personnel and network obligations tighten at the higher levels.

What are the Australian Government information classifications?

A classification is not a label an organisation picks to look careful. It is the output of a harm test the government calls the business impact level: how much damage a compromise of the information would do to the national interest, to organisations, or to individuals. Once the harm is set, the marking follows.

There are two sensitivity markings and three security classifications. UNOFFICIAL covers information that is not part of official duties. OFFICIAL is the routine level for most government work, and OFFICIAL: Sensitive is a step above it. Above that line the information is security classified: PROTECTED, then SECRET, then TOP SECRET. Each step up means a higher impact level and stricter handling, storage, access and disposal under the Protective Security Policy Framework (PSPF).

What does each Australian Government classification mean?

The marking tells a reader two things at once: how sensitive the information is, and how much protection it must carry. The damage descriptors are deliberately blunt.

Marking What it covers Harm if compromised
OFFICIAL Routine government information, low business impact No or insignificant damage
OFFICIAL: Sensitive Sensitive information needing limited distribution Limited damage to the national interest, organisations or individuals
PROTECTED Valuable, sensitive information Damage to the national interest, organisations or individuals
SECRET Very valuable, sensitive information Serious damage to the national interest
TOP SECRET The most sensitive national security information Exceptionally grave damage to the national interest

Who sets the classification, and why does it decide the IRAP scope?

The agency that owns the information sets the classification, not the provider and not the assessor. This catches cloud and SaaS teams who assume they can self select a lower level to keep the assessment small, but that choice is not theirs to make. Where a system will hold an agency’s PROTECTED data, it is a PROTECTED system, whatever the provider would prefer. If there is any uncertainty about the level, that conversation happens with the agency before an assessment is scoped, not after.

It matters because the classification drives everything downstream: the ISM controls in scope, the clearances the people involved need, and the assessment boundary. The most expensive mistake we see in the first week is an assumed level. An assessment scoped at OFFICIAL: Sensitive for a system that should have been PROTECTED is redone, not adjusted, and the repeated work falls at the assessed entity’s cost. The level is best confirmed in writing with the agency, alongside a check of whether an IRAP assessment is needed at all.

Do the ISM controls change between OFFICIAL: Sensitive and PROTECTED for IRAP?

No, and this is the part most providers get wrong. A common assumption is that a PROTECTED system is assessed against a larger or harder set of Information Security Manual (ISM) controls than an OFFICIAL: Sensitive one. The control set is the same at both levels, and ASD’s Cloud Controls Matrix confirms that controls applicable at OFFICIAL: Sensitive are equally applicable at PROTECTED.

The difference is in the obligations around the controls, set by the PSPF, and every one of them falls inside the scope of an IRAP assessment, not beside it. So the real question is rarely which controls apply. It is what the classification demands of the facilities, the people and the network.

Obligation OFFICIAL: Sensitive PROTECTED
ISM control set The same control set applies The same control set applies (the Cloud Controls Matrix confirms it)
Physical security Zone One or Zone Two security area with a standard lockable commercial cabinet Zone Four or Zone Five security area with a SCEC endorsed Class C security container
Personnel Employment screening check Baseline security clearance from AGSVA for ongoing access
Network and transmission Encryption of data in transit per the ISM Transmitted over a PROTECTED or higher network, per the PSPF
Authorisation Standard scrutiny of residual risk Greater scrutiny of residual risk

How does SECRET change an IRAP assessment?

The real jump is into SECRET, which adds further physical, personnel and network controls on top, and the bar for clearances rises. So the gap in cost and time between PROTECTED and SECRET is wider than the gap from OFFICIAL: Sensitive to PROTECTED, even though both look like a single rung on the ladder. An IRAP assessment measures whichever set applies against the ISM, and the classification is what selects that set. The complete IRAP guide walks through the rest of the process.

Why confirm the classification before scoping an IRAP assessment?

Because the classification sets the timeline, the cost and the physical work, not just the paperwork. For a SaaS provider preparing for an agency contract, confirmation that the information is OFFICIAL: Sensitive keeps the preparation focused on ISM controls work. Had the same data been PROTECTED, preparation would have started with a facilities and staffing assessment before any controls work began. Meeting PROTECTED physical security is a significant undertaking for a commercial provider without established government facility arrangements, so it should be scoped and costed before the assessment, not discovered midway through.

Clearances change the timeline too. A Baseline clearance through AGSVA (the Australian Government Security Vetting Agency) can take weeks to months depending on personal circumstances and the backlog at the time, so the process starts early or it becomes the critical path. The IRAP readiness checklist puts both decisions at the front of preparation for this reason.

A SaaS assessment also has to cover the SaaS layer itself, referencing the cloud provider’s existing assessment for the infrastructure beneath it. The provider’s report does not remove that obligation. It informs how the assessment is scoped, which we cover for SaaS and cloud providers.

Is IRAP authorisation harder at PROTECTED?

Yes, in practice, even though the framework and the process are identical. The ISM controls and the assessment stages do not change, while the weight an authorising officer puts on residual risk does. On a PROTECTED system an unresolved finding carries more consequence, so officers apply greater scrutiny before they accept the risk and authorise the system to operate. The decision is harder to obtain at PROTECTED, which is another reason to confirm the level early and prepare to the obligations it brings.

What about TOP SECRET and caveats in IRAP?

Two things fall outside the usual cloud path. TOP SECRET systems are handled inside accredited government environments, not assessed through the commercial cloud route that covers OFFICIAL: Sensitive to SECRET. Where a roadmap mentions TOP SECRET, that is a different conversation and a different environment.

Caveats are the second. A caveat is an extra warning of special handling stacked on top of a classification, and it is mandatory where it applies. Caveats attach to PROTECTED or higher and cannot be applied to OFFICIAL or OFFICIAL: Sensitive. One older marking, the NATIONAL CABINET caveat, is being phased out as National Cabinet is no longer a committee of Cabinet. For cloud and SaaS providers, the classification and any caveat together decide what an IRAP assessment of the service must cover. Cybernion runs IRAP assessments at OFFICIAL: Sensitive, PROTECTED and SECRET, and the classification is the first thing we confirm.

Frequently asked questions

Can a provider choose its own classification level for an IRAP assessment?

No. The agency that owns the information sets the level under the PSPF business impact levels. A provider does not classify data on an agency’s behalf, so confirm the level in writing before scoping the system.

Is the IRAP control set different at OFFICIAL: Sensitive and PROTECTED?

No. The ISM control set is the same at both, and ASD’s Cloud Controls Matrix confirms it. What differs is physical security, personnel clearances and network obligations, all of which fall within the scope of an IRAP assessment.

What physical security does a PROTECTED system require for IRAP?

A Zone Four or Zone Five security area with a SCEC endorsed Class C security container. OFFICIAL: Sensitive systems require a Zone One or Zone Two security area with a standard lockable commercial cabinet. The gap is significant for commercial providers without established government facility arrangements.

Do our staff need security clearances for an IRAP assessed system?

Access to OFFICIAL: Sensitive information requires an employment screening check. Ongoing access to a PROTECTED system requires a Baseline security clearance issued by AGSVA. Clearances can take weeks to months, so start the process before the assessment begins.

Is IRAP authorisation harder to obtain at PROTECTED?

Yes, in practice. The ISM framework and the assessment process are the same, but authorising officers apply greater scrutiny to residual risks on PROTECTED systems, and an unresolved finding carries more weight.

Can you run an IRAP assessment for a TOP SECRET system in commercial cloud?

No. TOP SECRET is handled inside accredited government environments, not the commercial cloud IRAP route that covers OFFICIAL: Sensitive to SECRET.

How often must a cloud service be reassessed under IRAP?

Within 24 months under PSPF requirement 0109, against the latest ISM at the time of assessment.


Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.

Talk to us. We aren’t always chasing a transaction.

Sources:

  1. Protective Security Policy Framework, sensitive and classified information and requirement 0109, PSPF Annual Release 2024
  2. Security classifications and protective markings, Australian Government Style Manual, 2026
  3. Information Security Manual (ISM), ASD, June 2026
  4. Cloud assessment and authorisation, including the Cloud Controls Matrix, ASD, 2024
  5. ASD IRAP Consumer Guide, July 2025

Last updated: 7 November, 2026

Related serviceIRAP AssessmentSee the service →

Talk to us about your engagement

A scoped proposal within one business day.