Cybernion
← Insights

State Government

What Is the Victorian Protective Data Security Framework (VPDSF)?

30 Aug 2026 · Updated 30 Aug 2026

The Victorian Protective Data Security Framework (VPDSF) is Victoria’s mandatory scheme for protecting public sector information, administered by the Office of the Victorian Information Commissioner under the Privacy and Data Protection Act 2014. It carries twelve mandatory Standards, the VPDSS, and is reported through a biennial security plan and attestation. It is risk based and does not set an Essential Eight maturity floor.

Victoria took a different road from New South Wales and Western Australia. It did not build its regime on the Essential Eight. It built it on protecting information, under privacy legislation, with a data security regulator holding the pen.

What is the Victorian Protective Data Security Framework (VPDSF)?

The Victorian Protective Data Security Framework (VPDSF) is the whole of government framework for protecting Victorian public sector information. It is administered by the Office of the Victorian Information Commissioner (OVIC), and it derives its authority from Part 4 of the Privacy and Data Protection Act 2014.

That legislative base matters. The Information Commissioner has a statutory power to develop the framework and to issue the standards under it, so this is not policy that lives on a departmental circular. The framework is the overarching document. Under it are the Victorian Protective Data Security Standards (VPDSS), the twelve mandatory standards that carry the actual requirements, and a set of supporting practitioner guides. The framework also brings a protective marking scheme and a way to assess how sensitive information is, so an agency knows which information needs the most protection. In short, the VPDSF sets the system, and the VPDSS sets what an organisation must have in place.

What are the Victorian Protective Data Security Standards (VPDSS)?

The Victorian Protective Data Security Standards (VPDSS) are twelve high level mandatory requirements that every in scope organisation must meet. The current version cut the earlier set of eighteen standards down to twelve, each stated as an outcome rather than a prescriptive control.

# Standard
1 Information Security Management Framework
2 Information Security Value
3 Information Security Risk Management
4 Information Access
5 Information Security Obligations
6 Information Security Incident Management
7 Business Continuity and Disaster Recovery
8 Third Party Arrangements
9 Information Security Reporting to OVIC
10 Personnel Security
11 ICT Security
12 Physical Security

The twelve span five security domains, governance, information, personnel, ICT and physical. Standard 1, for example, requires an organisation to establish and maintain an information security management framework relevant to its size, resources and risk posture. The detail behind each standard is in the elements and in OVIC’s implementation guidance, which draws on ISO 27001. The standards are deliberately broad, so they apply across a health regulator, a courts body and a transport agency alike.

Who must comply with the VPDSF and VPDSS?

The VPDSF and VPDSS are mandatory for Victorian public sector organisations within the scope of the Privacy and Data Protection Act 2014. That includes departments, public entities, Victoria Police and the Crime Statistics Agency.

The exclusions are as important as the inclusions. The Act carves out councils, universities, public hospitals and health services, multi purpose services, and ambulance services, so those bodies are not bound by the VPDSS. There is a caveat worth knowing: an otherwise exempt entity that performs a public function on behalf of a regulated organisation may still pick up obligations. Contracted service providers are captured indirectly rather than named. The Act requires a public sector body head to ensure a provider does not do anything that contravenes a protective data security standard for the public sector data it handles, and organisations must assess their providers as part of their security risk profile assessment. So the reach to a supplier runs through the agency, not straight from OVIC.

Does the Victorian Protective Data Security Framework require the Essential Eight?

No. The VPDSF does not mandate the ASD Essential Eight at a set maturity level. This is the clearest structural difference between Victoria and the more prescriptive states.

Victoria’s model is outcome and risk based. An organisation has to meet the twelve standards, including the ICT security standard, and it decides how, guided by its own assessment of the security value of its information. The standards’ underlying elements cite AS ISO/IEC 27001:2023 and the related risk standard as their primary source, so the technical baseline is ISO aligned rather than Essential Eight aligned. Many Victorian organisations do use the Essential Eight to satisfy the ICT security standard, because it is a sensible way to implement technical controls. But there is no Essential Eight maturity level that acts as a compliance floor in Victoria. Do not assume parity with New South Wales here. The obligation is to meet the standard, not to hit a named maturity number.

What is a Protective Data Security Plan (PDSP) and when is it due?

A Protective Data Security Plan (PDSP) is the report an organisation submits to OVIC to show how it is meeting the VPDSS. It carries an attestation signed by the public sector body head, and it is submitted on a biennial cycle, in the window from 1 July to 31 August of the reporting year.

The cadence is a two year loop with an annual check inside it. In the reporting year, the organisation lodges a full PDSP with its attestation. In the intervening year, it still submits an annual attestation confirming the security program is continuing and that it has done its security risk profile assessment. If something significant changes, the organisation has to submit out of cycle rather than wait for the next window. This is a lighter touch reporting rhythm than the annual attestation New South Wales, Queensland and Western Australia run, but the biennial plan itself is a heavier document. The trade is depth every two years against a lighter yearly confirmation.

How does the VPDSF relate to the Commonwealth PSPF and ISO 27001?

The VPDSF is Victoria’s own framework, but it does not displace the Commonwealth regime where Commonwealth information is involved. Where a Victorian organisation holds national interest information, or information generated by or for a Commonwealth agency, the Commonwealth Protective Security Policy Framework requirements remain mandatory for that information.

For everything else, the point of reference is ISO 27001. The VPDSS standards are described as consistent with national and international standards, and their elements map back to ISO 27001 clauses and the ISO risk standard. An organisation that already runs an ISO 27001 information security management system will find much of the VPDSS is evidenced by controls it already operates, though the Victorian reporting, the security value assessment and the OVIC specific standards still have to be handled directly. This runs alongside the other jurisdictions in the state cyber security frameworks overview. For an organisation working out how to evidence the VPDSS, Cybernion helps through ISO 27001 and Essential Eight advisory and assessment.

Frequently asked questions

What is the Victorian Protective Data Security Framework (VPDSF)?

The Victorian Protective Data Security Framework (VPDSF) is Victoria’s whole of government scheme for protecting public sector information. It is administered by the Office of the Victorian Information Commissioner (OVIC) under Part 4 of the Privacy and Data Protection Act 2014. The framework carries the Victorian Protective Data Security Standards (VPDSS), a set of twelve mandatory standards spanning governance, information, personnel, ICT and physical security, and it is reported through a biennial Protective Data Security Plan.

What are the Victorian Protective Data Security Standards (VPDSS)?

The Victorian Protective Data Security Standards (VPDSS) are twelve high level mandatory requirements that Victorian public sector organisations must meet. They cover an information security management framework, information security value, risk management, information access, security obligations, incident management, business continuity, third party arrangements, reporting to OVIC, personnel security, ICT security and physical security. Together they span five security domains, governance, information, personnel, ICT and physical.

Who must comply with the VPDSF and VPDSS?

The VPDSF and VPDSS are mandatory for Victorian public sector organisations within the scope of the Privacy and Data Protection Act 2014, including departments, public entities, Victoria Police and the Crime Statistics Agency. Councils, universities, public hospitals and health services, and ambulance services are excluded by the Act. Contracted service providers are captured indirectly, because a public sector body must ensure its providers do not breach the standards for the data they handle.

Does the Victorian Protective Data Security Framework require the Essential Eight?

No. The VPDSF does not mandate the ASD Essential Eight at a set maturity level. Victoria’s model is outcome and risk based, built on the twelve VPDSS standards, whose underlying elements draw on ISO/IEC 27001. Agencies still implement technical controls under the ICT security standard, and many use the Essential Eight to do so, but the framework does not set an Essential Eight maturity level as a compliance floor the way New South Wales and Western Australia do.

What is a Protective Data Security Plan (PDSP)?

A Protective Data Security Plan (PDSP) is the report a Victorian public sector organisation submits to OVIC to show how it is meeting the VPDSS. It is submitted with an attestation signed by the public sector body head on a biennial cycle, between 1 July and 31 August of the reporting year. In the intervening years the organisation still submits an annual attestation confirming its security program is continuing, and an out of cycle submission is required on significant change.


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.

Sources:

  1. Victorian Protective Data Security Standards, Office of the Victorian Information Commissioner, October 2019
  2. Victorian Protective Data Security Framework V2.1, Office of the Victorian Information Commissioner, 27 September 2023
  3. VPDSS Implementation Guidance, Office of the Victorian Information Commissioner, January 2026
  4. Agency reporting obligations, Office of the Victorian Information Commissioner, 2026
  5. Privacy and Data Protection Act 2014 (Vic), Victorian Government, 2014

Last updated: 30 August, 2026

Talk to us about your engagement

A scoped proposal within one business day.