Skip to main content
All articles

Data Sovereignty

IRAP and Stakeholder Management Software: What Buyers Should Ask

An engagement record is only as defensible as the system that holds it. What procurement teams need to know about IRAP, and the questions that separate evidence from marketing.
  • January 2026 · Updated October 2026
  • 9 min read

Short answer

IRAP is ASD's program of endorsed assessors who independently assess systems against the Information Security Manual (ISM). An assessment produces a report, not a certificate, and the buying agency decides whether to authorise the system. When buying stakeholder management software, ask whether the vendor's own application was assessed or only its cloud provider, which controls and classification level were in scope, how recent it is, and where all data, including AI processing, is held. Vendors without an assessment should say so plainly and show what they can evidence instead.

What is IRAP?

The Infosec Registered Assessors Program (IRAP) is run by the Australian Signals Directorate (ASD). ASD endorses qualified security professionals to carry out independent security assessments of ICT systems, cloud services and gateways, up to SECRET, against the controls in the ISM.

IRAP is not a certification. There is no "IRAP certified" stamp issued by the government. ASD does not accredit, certify, endorse or register any system under IRAP, and says statements claiming otherwise misrepresent the program. An assessor produces a security assessment report that documents which controls were implemented and effective, which were not, and the residual risks. The consuming agency then makes a risk-based decision about whether to authorise the service.

That distinction matters. Vendors claiming to be "IRAP certified" are misrepresenting the framework. Look instead for evidence of a completed IRAP assessment of the specific system, at the appropriate classification level, by an ASD-endorsed assessor.

How do the ISM, the Essential Eight and the PSPF relate to IRAP?

The Information Security Manual (ISM), maintained by ASD, is the cyber security framework that IRAP assessments test against. It contains a large set of controls covering areas such as system hardening, access management, cryptography, network security and personnel security. An assessment looks at the controls relevant to the system and its classification, and will generally not cover every ISM control.

The Essential Eight are the eight mitigation strategies ASD ranks as most effective: patch applications, patch operating systems, multi-factor authentication, restrict administrative privileges, application control, restrict Microsoft Office macros, user application hardening and regular backups. ASD's maturity model sets out levels of implementation. Expectations vary by agency and by the information involved. In cloud-hosted software, many of these controls are shared between the vendor and its infrastructure provider, so ask where the boundary sits.

The Protective Security Policy Framework (PSPF) sets the overarching protective security requirements for Australian Government entities. According to ASD's IRAP policy, under the PSPF outsourced information technology systems, cloud services and gateways (up to SECRET) must be assessed by an IRAP assessor, and entities providing outsourced services must provide their IRAP assessment reports to the government entities consuming them.

The Hosting Certification Framework, run by the Digital Transformation Agency, applies to hosting of systems at PROTECTED, whole-of-government systems and sensitive government data, and certifies data centre and cloud providers.

Why does stakeholder data need careful security?

Procurement teams sometimes underestimate how sensitive stakeholder records are. A list of who attended a community meeting looks harmless, but over time these systems accumulate information that is personal, politically sensitive and relied on as evidence. How each item is marked is for the originating agency to decide under the PSPF.

Types of stakeholder data and why they are sensitive
Data typeWhy it is sensitive
Contact details (names, emails, phone numbers, addresses)Personal information under the Privacy Act 1988 or state privacy law
Views and positions on contentious projects or policyPersonally identifiable and potentially politically sensitive
Consultation with Traditional Owners and cultural heritage informationCulturally sensitive, may include restricted knowledge, and subject to protocols agreed with the community
Internal engagement strategies and risk assessmentsMay reveal deliberations and may be requested under FOI or RTI
Complaints and records of commitmentsEvidence in audits, compliance reporting and disputes

Engagement records are frequently requested under FOI or RTI and relied on in audits and disputes, so the security of the platform holding them has to be defensible. For residency questions, see Australian data sovereignty: what government buyers need to know.

Which security areas matter most for a stakeholder platform?

The ISM is broad, but for a SaaS stakeholder platform these areas usually get the most attention from assessors and agency security teams. Check the current ISM and your agency's requirements for the specific controls.

  • Data residency: where data at rest, in transit and in processing sits, including backups, logs, search indexes and temporary caches.
  • Encryption: how data is encrypted at rest and in transit, and who controls the keys.
  • Access control: role-based access, least privilege, and multi-factor authentication for users and administrators.
  • Audit logging: tamper-evident logs of access, changes, administrative actions and sign-ins, retained to meet your records obligations.
  • Incident response: a documented plan and a contractual notification commitment that meets your agency's expectations.
  • Supply chain: every subprocessor, third-party library and cloud service documented and assessed for risk.

Where do the gaps usually appear?

Many platforms were built for the private sector or overseas markets and adapted for Australian government use. Three gaps come up repeatedly:

  • Offshore processing: the main database is in Australia, but analytics, email delivery, search or AI processing happens offshore.
  • Offshore AI services: summaries, sentiment and drafting sent to AI services hosted overseas, so stakeholder comments and submissions leave the country. Ask whether data is retained or used for training.
  • Shared responsibility gaps: a cloud provider's IRAP assessment does not extend to the application on top of it. The vendor must separately show that its own controls meet the requirements.

For how onshore AI processing can work, see our AI platform overview.

How should procurement teams evaluate a vendor's IRAP position?

Go beyond marketing claims. These questions separate a completed, relevant assessment from aspiration:

  1. Has an ASD-endorsed IRAP assessor assessed your application, or only your cloud provider?

    Ask for the assessor, the date and the scope. A cloud provider's IRAP assessment covers its infrastructure; the vendor's application needs its own evidence.

  2. Against which classification level were controls assessed, and which controls were in scope?

    An assessment generally does not cover every ISM control. Read the report to see what was tested, and compare the level with the information your system will hold.

  3. How recent is the assessment, and what has changed since?

    Systems change. Ask when the assessment was done and what significant changes have been made to the system since.

  4. Where is all data hosted, processed and backed up?

    Ask for every location, including disaster recovery, logs, search indexes and support access.

  5. Where do AI models run, and what happens to the data they process?

    If the platform uses AI for summaries, sentiment or drafting, ask where inference runs, whether any data is sent to offshore AI services, and whether prompts or outputs are retained or used for training.

  6. Can you provide a complete subprocessor list?

    Every third party that touches stakeholder data: email, analytics, search, monitoring and support tools.

  7. What is your incident notification commitment?

    Compare the vendor's contractual commitment with your agency's requirements and with your own obligations under the Notifiable Data Breaches scheme.

  8. What Essential Eight maturity level can you evidence?

    Ask for evidence rather than a statement, and compare it with what your agency expects for the information involved.

A vendor that answers with specifics, including "no, we have not been assessed", is easier to evaluate than one that answers with generalities. "Our cloud provider is IRAP-assessed" is not an answer about the application. For a broader checklist, see choosing stakeholder engagement software in Australia.

Where VivoAI fits

Applying the standard above to ourselves: Not IRAP-assessed. The AWS Sydney infrastructure we run on is IRAP-assessed; that covers our infrastructure. No assessor is currently engaged, and we would rather you read that here than discover it midway through a procurement.

VivoAI is built against the Australian Government Information Security Manual (ISM), ISO/IEC 27001 controls and the ASD Essential Eight. What that means in practice:

  • Data stored and processed in AWS Sydney (ap-southeast-2), with the region enforced in code and offshore processing paths disabled by default.
  • AI inference onshore, against a model allowlist enforced in code; no data is sent to offshore AI services, and we do not train models on your data.
  • Australian-controlled encryption key management, AES-256 encryption at rest and TLS 1.2 or higher in transit.
  • Role-based access with mandatory multi-factor authentication.
  • Tamper-evident audit logging with seven-year retention.
  • A complete subprocessor list and a 24-hour incident notification commitment.

AWS is US-headquartered, so data held with it may still be subject to foreign laws such as the US CLOUD Act. See where the record lives, and what we can and can't claim.

Frequently asked questions

Can software be certified under IRAP?

No. ASD does not accredit, certify, endorse or register any system under IRAP. An ASD-endorsed assessor produces an assessment report, and the agency decides whether to authorise the system. A product cannot be "IRAP certified", so treat any claim that it is as a red flag.

Does a cloud provider's IRAP assessment cover the software running on it?

No. It covers the provider's infrastructure and services within its scope. The application layer, including how the vendor configures, secures and operates its own software, needs its own evidence.

Must outsourced services to Commonwealth agencies be IRAP-assessed?

ASD's IRAP policy says that under the Protective Security Policy Framework, outsourced information technology systems, cloud services and gateways (up to SECRET) must be assessed by an IRAP assessor, and that entities providing outsourced services must provide IRAP assessment reports to the government entities consuming them. Check the current PSPF and your agency's requirements for how this applies to your procurement.

Is VivoAI IRAP-assessed?

Not IRAP-assessed. The AWS Sydney infrastructure we run on is IRAP-assessed; that covers our infrastructure. VivoAI is built against the Australian Government Information Security Manual (ISM), ISO/IEC 27001 controls and the ASD Essential Eight.

Sources

This article is general information, not legal or security advice. Check the requirements that apply to your agency and obtain advice for your circumstances.

Next step

Ask us the hard security questions

Australian data residency and onshore AI, built against ISM controls, with straight answers about what we can and can't evidence.