Responsible disclosure guidelines

We take the security and privacy of our information seriously. If you identify a security issue with our systems, please tell us so that we can get it fixed.

On this page

    Disclosure of system security issues

    We value input from anyone in our community. Disclosure of security issues within our systems helps us to ensure the security and privacy of our information.

    If you have identified a security issue within our systems, our IT Security team will work with you to validate and fix it.

    We reserve all of its legal rights if you do not follow the Responsible Disclosure guidelines.

    Responsible Disclosure guidelines

    These guidelines are designed to help both you and us when you find a security issue with our systems. If you are doing security testing, please make every effort to avoid:

    • a breach of the privacy of individuals
    • anything that will slow the system down for users
    • disruption to production systems
    • destruction of data.

    As well as:

    • perform research only within the scope set out below
    • delete, and do not share, any ACC confidential information or personal information you might have obtained
    • keep information about any security issues with our systems that you’ve discovered confidential between yourself and us until we have had an opportunity to fix it
    • email us to report security issues with our systems as soon as possible after you find it.


    Our commitment to you

    If you follow these Responsible Disclosure guidelines when reporting an issue to us, we commit to:

    • being as straightforward and communicative as we can with you
    • treating the information you share with us as confidential between us and our suppliers, unless we have to disclose it because a third party discovers the security issue within our system before we’ve had the opportunity to resolve it, or the information on the security issue within our system is used to cause a privacy breach and we are required to handle the breach in accordance with the Privacy Act 2020
    • not taking any legal action against you related to your research provided you follow the Responsible Disclosure guidelines, keep our information confidential, and cause no damage or disruption to our services
    • working with you to understand and resolve the issue quickly, including an initial confirmation of your report within seven days of submission
    • considering recognition of your contribution with a letter of acknowledgement if you are the first to report the issue and we make a code or configuration change based on the issue.

    In scope

    The following websites are in scope

    Out of scope

    Services hosted by third-party providers or vendors are excluded from scope. Any other government departments or agency providers and services are excluded from scope.

    For issues that affect other government departments or agency providers, we suggest you contact CERT NZ who offer an anonymous reporting service for system security issues.


    In the interest of the safety of our users, employees, the internet at large, and you, the following test types are excluded from scope:

    • findings from physical testing such as office access, for example, open doors, tailgating
    • findings derived primarily from social engineering, for example, phishing, whaling
    • findings from applications or systems not listed in the ‘In scope’ section
    • UI and UX bugs and spelling mistakes
    • network level Denial of Service (DoS/DDoS) weaknesses
    • destruction or corruption of, or attempts to destroy or corrupt, data or information that belongs to us. This includes any information that may be relevant to you.

    How to report a security issue

    If you believe you’ve found a security issue in one of our products or platforms, email it to us.


    Write the report clearly and in English, and include the following details:

    • type of security issue
    • how you found the security issue
    • whether the security issue has been published or shared with others
    • affected configurations
    • exposure or possible exposure of any personal information
    • description of the location and potential impact of the security issue
    • a detailed description of the steps required to reproduce the issue or risk, for example, proof of concept scripts, screenshots, and compressed screen captures are all helpful to us
    • your name and contact details.

    How to remain anonymous

    CERT NZ operate a coordinated vulnerability disclosure process where the finder can use CERT NZ as a conduit with impacted vendors. 

    CERT NZ coordinated vulnerability disclosure policy.

    Last published: 15 March 2023