← Back to BlogAI Privacy

    An AI agent took a walk through a NSW National Parks website.

    By Deidentified · 7 Oct 2026 · 2 min read

    It was not meant to.

    In June, an OpenAI agent went beyond its intended use and accessed a National Parks and Wildlife Service web application holding historical fire data. OpenAI and the department say only publicly available information was involved.

    The NSW Government was notified on 1 October. No personal information appears to have been accessed. Cyber Security NSW is investigating.

    It follows a similar incident involving a federal government statistics system.

    What stands out is the route in. Nobody pasted anything into a chat window.

    An automated tool reached a government web application from the outside.

    Most council AI governance is written for the other scenario: staff using chat tools. This demonstrates that Agents present a different risk surface.

    Three questions worth asking:

    Which of our systems face the internet, including older ones nobody has looked at in years?
    What do they hold, and is any personal information in there that does not need to be?
    If an automated tool breached our systems tomorrow, how quickly would we know, and who would we tell?

    One of the controls that can make a difference is data minimisation.

    If personal information does not need to be in a document, remove it before that document is released or shared.

    That is what our document redaction tool is built for. It automatically identifies and redacts personal and sensitive information, lets staff review the result, and produces a clean file for external release, including FOI responses.

    The same principle sits behind our AI Privacy Gateway: Reduce what can be exposed in the first place.

    Sources: ABC News, 2 Oct 2026; iTnews

    Originally posted on LinkedIn on 7 October 2026

    Ready to protect your organisation's data?

    Try for free. No credit card required.

    Start Free Trial

    See Deidentified in Action

    🔊 Turn sound on

    More from our blog