Insights

OVIC Protective Data Security Plan: from self-assessment to evidence

A Protective Data Security Plan reports an organisation’s maturity against the Victorian Protective Data Security Standards. The ratings carry more weight and are easier to defend when they rest on evidence rather than self-assessment alone.

What does OVIC require, and when?

Victorian public sector bodies covered by Part 4 of the Privacy and Data Protection Act 2014 must report to the Office of the Victorian Information Commissioner (OVIC) under the Victorian Protective Data Security Framework (VPDSF). OVIC’s reporting guidance sets out two obligations:

  • A Protective Data Security Plan (PDSP) every two years. Reporting falls in even-numbered years, with submissions due between 1 July and 31 August. The next cycle is 2028.
  • An annual attestation, signed by the public sector body Head, confirming that the organisation continues its programme of protective data security activities and that its PDSP is accurate. The Head cannot delegate it.

An organisation that undergoes significant change, such as a change to its operating environment or risk profile, may also need to submit a PDSP outside the regular cycle.

OVIC had planned to revise the Standards in time for 2026, but delayed the review, so the 2026 cycle used the current Standards. Watch for changes before 2028. OVIC’s 2026 how-to guide explains how to complete the plan.

Why is self-assessment not enough?

A PDSP asks the organisation to rate its own maturity against each standard. Internal teams usually know where the gaps are, but a rating based on what is documented, rather than what operates, can overstate the position.

The difference matters most at attestation. The Head is confirming that the plan is accurate. If a policy exists but nobody follows it, or a register was last updated three years ago, the rating it supports will not hold up to scrutiny.

What does an independent assessment add?

An independent assessment tests the self-assessment against evidence before the Head signs. It typically produces:

  • a gap register at element level, showing what is in place, partly in place or missing;
  • an evidence index linking each element to the records that support it;
  • a clear account of what could not be verified, and why; and
  • a rationale for the maturity rating at each standard.

The organisation still owns its ratings and its attestation. The assessment gives the Head a clearer basis for both.

How do findings become improvements?

Findings are most useful when they become defined pieces of work. Common examples include:

  • an internal control library that maps the organisation’s controls to the VPDSS elements;
  • an information value and business impact level assessment;
  • an information classification and handling framework;
  • a data governance policy;
  • a cryptographic key management standard; and
  • an evidence and control assurance framework, so that each control produces the records needed to show it works.

Each piece can be commissioned on its own and sequenced against the maturity targets in the organisation’s plan. Not every organisation needs all of them.

Why doesn’t a new document change the rating?

Writing a policy does not, on its own, raise maturity. The organisation has to approve the document, put it into practice and keep the records that show it operates. A practical way to close that gap is a first operating session: soon after approval, staff carry out the task for the first time, such as populating a key inventory or running a post-incident review, with support. The resulting record is the organisation’s own evidence that the control works.

Where should you start for 2028?

  1. Revisit the 2026 plan and the maturity targets it set for 2028.
  2. Test the ratings against evidence early, while there is time to act on the findings.
  3. Prioritise the work that moves the most important standards towards their targets.
  4. Build and operate the documents and controls, keeping the records as you go.
  5. Re-verify before attestation, so the Head signs with confidence.

Original ideas are Sypha’s. This article was drafted with AI assistance and verified against primary sources under our assurance process. Reviewed, edited and approved for publication by James Munro, Principal | Managing Director, Sypha Defence Advisory.

Related service: OVIC / VPDSS Assurance.

Sources

Checked 4 November 2026.

← All insights

A clear starting point

Discuss your assurance needs

Tell us what you need to assess, the obligations you work under and the decisions ahead. We will agree a clear scope and the evidence needed to answer your questions.