Home  /  Insights  /  VPDSS and ISO 27001: a guide for Victorian agencies and suppliers
Insights

VPDSS and ISO 27001: a guide for Victorian agencies and suppliers

If you work for a Victorian agency, or sell to one, you will meet the Victorian Protective Data Security Standards. ISO 27001 covers most of the same ground. Here’s how the two fit, where the gaps are and what suppliers should have ready.

Cyber Veda

Quick answer: The Victorian Protective Data Security Standards (VPDSS V2.0) are 12 mandatory standards for Victorian public sector bodies covered by Part 4 of the Privacy and Data Protection Act 2014 (Vic), overseen by OVIC. Suppliers are not bound directly, but agencies must make sure their contracted service providers don’t contravene the standards, so obligations reach you through the contract. ISO 27001 maps well to most of the 12 standards, but not to the Victorian-specific parts: business impact level assessments, protective markings and reporting to OVIC.

What the VPDSF and VPDSS are

The Victorian Protective Data Security Framework (VPDSF) is set up under Part 4 of the Privacy and Data Protection Act 2014 (Vic) and administered by the Office of the Victorian Information Commissioner (OVIC). The framework explains how Victorian public sector organisations should manage information security risk. The Victorian Protective Data Security Standards (VPDSS) are the mandatory part: 12 high-level standards covering governance, information, personnel, ICT and physical security.

The current version is VPDSS V2.0, issued by the Information Commissioner on 28 October 2019 after the Special Minister of State approved it. It replaced the 2016 standards. There is no V3.0. What changes more often is the Implementation Guidance, which breaks each standard into numbered elements and names the primary source each element comes from. Version 2.4 of that guidance, published in January 2026, is current. Its release does not change the standards.

Who it applies to

Part 4 applies to Victorian public sector agencies and bodies: departments, Victorian Public Service bodies and public entities under the Public Administration Act 2004 (Vic), among others. Section 84 sets out who is in and out. Councils and universities are generally excluded, with exceptions: a council acting as a Committee of Management of Crown land or as a cemetery trust is covered for that work, for example.

Agencies covered by Part 4 must:

  • not contravene the standards in handling public sector information and systems
  • make sure their contracted service providers don’t contravene them either, for the information the provider handles for the agency
  • carry out a security risk profile assessment, including an assessment of those providers
  • develop a Protective Data Security Plan (PDSP) that addresses the standards, including how contracted providers comply, and give a copy to the Information Commissioner

The 12 standards

#StandardClosest ISO 27001:2022 coverage
1Information Security Management FrameworkClauses 4 to 10 (the ISMS itself)
2Information Security Value5.9 asset inventory, 5.12 classification, 5.13 labelling (partial)
3Information Security Risk ManagementClauses 6.1.2, 6.1.3, 8.2 and 8.3
4Information Access5.15 to 5.18, 8.2 to 8.5, 7.2
5Information Security ObligationsClause 7.3, 5.4, 6.3
6Information Security Incident Management5.24 to 5.28
7Information Security Aspects of Business Continuity and Disaster Recovery5.29, 5.30, 8.13, 8.14
8Third Party Arrangements5.19 to 5.23
9Information Security Reporting to OVICNone
10Personnel Security6.1 to 6.6
11ICT Security8.1 to 8.34 (technological controls)
12Physical Security7.1 to 7.14

The mapping is close because OVIC built it that way. The Implementation Guidance cites AS/NZS ISO/IEC 27001 as the primary source for the Standard 1 elements and ISO/IEC 27002 for many others, alongside the Commonwealth Protective Security Policy Framework (PSPF), the Information Security Manual (ISM) and the Essential Eight. For a refresher on the controls in the right-hand column, see our guide to ISO 27001 Annex A controls.

The reporting cycle

Standard 9 sets the rhythm for agencies, and it has no ISO 27001 equivalent:

  • Protective Data Security Plan, every two years. The PDSP is a self-assessment against the standards and their elements, with an implementation plan and an attestation signed by the head of the public sector body. The 2026 PDSP had to be submitted between 1 July and 31 August 2026, and OVIC does not grant extensions.
  • Attestation, every year. In the years between plans, the agency head attests that the activities in the previous PDSP are continuing.
  • Out-of-cycle PDSP. Section 89(4) requires an updated plan when the agency undergoes, or expects, a significant change to its operating environment or security risks.
  • Incident notification. Agencies are encouraged to notify OVIC of incidents affecting information with a business impact level (BIL) of 2, “limited”, or higher. That includes OFFICIAL: Sensitive, PROTECTED and Cabinet-in-Confidence information.

For an agency that already runs an ISMS, the PDSP becomes much easier. Your risk register, Statement of Applicability, internal audit results and management review minutes are most of the evidence a self-assessment needs.

How obligations reach suppliers

OVIC is clear that contracted service providers and funded agencies are not public sector agencies, so they have no direct obligations under Part 4. You don’t report to OVIC, and there is no VPDSS certification for suppliers. But the agency is responsible for making sure you don’t contravene the standards, and it must cover you in its own risk assessment and PDSP. So the obligations arrive through the contract.

Standard 8 tells agencies how to do that. Its elements expect the agency to cover the whole lifecycle of the arrangement, write requirements from all security areas into the contract in line with the security value of the information, assess the risk of your service before signing and apply security controls when the arrangement ends. In practice you will see some mix of:

  • a contract clause requiring you to adhere to the VPDSS, or to specific elements
  • a security questionnaire or assessment before award
  • requests for independent evidence, such as an ISO 27001 certificate or a SOC 2 report
  • incident notification timeframes, audit rights, and rules on data location, subcontracting and return or destruction of information

The agency decides what assurance it needs. OVIC encourages agencies and suppliers to agree expectations before the engagement starts, which is your chance to ask exactly what evidence will satisfy them. Our guide to ISO 27001 for government suppliers covers the wider picture across federal and state buyers.

Where ISO 27001 covers you, and where it doesn’t

Strong coverage

Standards 1, 3, 4, 5, 6, 7, 8, 10 and 12 map well. An ISO 27001 ISMS gives you a governance framework, a documented risk process, access management, awareness training, incident and continuity plans, supplier controls, screening and physical security, all audited by an independent certification body. For most agencies, a current certificate with the right scope answers a large share of their questions.

Gaps to close

  • Security value and the BIL table. Standard 2 expects information to be assessed against a contextualised VPDSF business impact level table, with confidentiality, integrity and availability ratings recorded in an information asset register. ISO 27001 requires classification, but it lets you design your own scheme. If you handle agency information, show how your scheme maps to the agency’s BILs and protective markings such as OFFICIAL: Sensitive.
  • Reporting to OVIC. Standard 9 has no ISO equivalent. Suppliers don’t report to OVIC, but agencies do, and you may be asked for input to their PDSP.
  • ICT depth. ISO 27001 lets you set technical controls by risk. Several Standard 11 elements cite the ISM and the Essential Eight as primary sources, and some agencies ask for a stated Essential Eight maturity level. See Essential Eight vs ISO 27001.
  • Scope. A certificate only helps if its scope covers the people, systems and locations that handle the agency’s information. A certificate for one product line won’t satisfy a buyer whose data sits elsewhere.
  • Victorian context. Your ISO 27001 context and interested parties (clause 4) should name the agency, the PDP Act obligations it passes down and its contract requirements. Auditors look for that link, and agencies do too.

What suppliers should have ready

  1. A current ISO 27001 certificate with the right scope, issued by an accredited certification body, and your Statement of Applicability to share under NDA. See what a good SoA contains.
  2. A mapping of your controls to the 12 standards, showing where each is met and how the gaps above are closed. Agencies ask for this in questionnaire form; having it ready shortens every review.
  3. How you handle classified information: how you receive, label, store, share and destroy information at the BIL and markings the agency uses.
  4. Incident notification arrangements that meet the contract’s timeframes and give the agency what it needs to assess the incident.
  5. Personnel screening evidence proportionate to the information your staff access.
  6. Subcontractor flow-down: how the same requirements reach your own suppliers, including cloud providers.
  7. Exit arrangements for returning or destroying agency information at the end of the contract.

If you are not certified yet, an ISO 27001 project that builds the VPDSS mapping in from the start costs far less effort than retrofitting one later. Scope is what drives most of that effort; our guide to ISO 27001 cost in Australia explains why. Building one control set that answers both ISO 27001 and an agency’s VPDSS questionnaire is work we take on for clients.

For agencies: using ISO 27001 to run the VPDSS

Agencies can’t substitute a certificate for the PDSP, but an ISMS is a practical engine for it. The VPDSF expects a risk-based framework that is monitored and improved; ISO 27001 clauses 9 and 10 do exactly that through internal audit, management review and corrective action. Agencies that run the two together prepare their PDSP from records they already keep. Our guide to ISO 27001 clauses 4 to 10 explains what each clause requires.

Next step

We’re based in Melbourne, so for Victorian agencies and suppliers we can meet in person as well as remotely; see compliance for Melbourne businesses. If you are building your ISMS yourself, remember ISO 27001 requires internal audits to be objective and impartial. Staff can do it if they aren’t auditing their own work, which is why many small teams bring in an outside auditor for an independent internal audit. To talk through a VPDSS requirement in a contract or tender, book a free 30-minute consultation, or see how our ISO 27001 service works.

FAQ

Common questions

Is the VPDSS mandatory?

Yes, for Victorian public sector agencies and bodies covered by Part 4 of the Privacy and Data Protection Act 2014 (Vic). Councils and universities are generally excluded under section 84, with some exceptions. Private suppliers are not bound directly, but an agency can require them to adhere to the standards through the contract.

What is the current version of the VPDSS?

VPDSS V2.0, issued by the Victorian Information Commissioner on 28 October 2019. It contains 12 standards. OVIC updates the supporting Implementation Guidance more often; version 2.4, published in January 2026, is current and does not change the standards themselves.

Does ISO 27001 certification mean we comply with the VPDSS?

Not automatically. A well-scoped ISO 27001 ISMS covers most of what the 12 standards ask for, and OVIC’s own guidance cites ISO/IEC 27001 and 27002 as primary sources. But the VPDSS adds Victorian specifics, such as assessing information against the VPDSF business impact level table and handling protective markings, that you need to show separately.

Do contracted service providers report to OVIC?

No. OVIC says contracted service providers do not report their compliance to it, and there is no VPDSS certification for suppliers. The engaging agency decides what assurance it wants from you, and it covers its suppliers in its own Protective Data Security Plan.

How often do agencies report to OVIC?

Agencies submit a Protective Data Security Plan every two years, and an attestation by the agency head every year. The 2026 PDSP was due between 1 July and 31 August 2026. Agencies also submit an updated plan after a significant change to their operating environment or security risks.

Talk to someone who has taken companies like yours to audit.

Book a free 30-minute consultation. Tell us what is driving the need, and leave with a realistic timeline and the first three things to do.