5.9.11. Where specific legislation applies, for example a reported vulnerability may breach the Privacy Act, agencies must adhere to the legislation. This may
change how reports are managed and action communicated to the finder or reporter. This does not change the requirement to maintain
communication with the reporter/finder.
Agencies are expected to find and remediate vulnerabilities
5.9.12. The Protective Security Requirements places clear expectations on agencies to maintain awareness of vulnerabilities (seemandatory requirement
INFOSEC4).
5.9.13. Section 12.4 of the NZISM sets out expectations and controls to ensure security patches are applied in a timely manner.
5.9.14. The disclosure period commonly used by many vendors, manufacturers and government agencies is 90 days. Vulnerabilities will be either patched,
mitigated or managed within this period. In some cases earlier notification is provided to allow users to take mitigating actions until a patch or other
solution is available.
5.9.15. VDPs are expected to include a timeframe within which patches will be applied or remedial action taken when a vulnerability is reported to the agency.
Agencies to create a vulnerability reporting point
5.9.16. When security risks in agency services are discovered and reported to the agency, it is vital that a robust communication channel is available to
receive the report.
5.9.17. This is commonly described as a “security.txt”. A draft standard has been published (see References below) to help agencies (and other organisations)
outline a process for security researchers to securely report security vulnerabilities.
Vulnerability disclosure policies are a normal part of learning about and patching vulnerabilities
5.9.18. Vulnerability disclosure (sometimes also referred to as responsible disclosure or coordinated vulnerability disclosure) is now an internationally accepted
practice for technology organisations. The practice of vulnerability disclosure in modern computing dates to the late 1980s. There are related
examples (non-computing) which appeared in the mid-1800s when locksmiths exchanged vulnerability information.
Bug Bounties
5.9.19. “Bug bounties” are a monetary reward to security researchers for the discovery and reporting of software and other information system vulnerabilities
to the agency. Bug Bounties are separate to VDPs and should only be covered if the agency has a bug bounty programme in place.
Vulnerability disclosure policy (VDP) Content
5.9.20. A VDP will typically include:
A scoping statement setting out which systems the policy applies to (e.g. the agency’s website and other public-facing systems);
Details of how finders can contact the agency’s security team (including any public keys for encrypting reports);
Permitted activities;
Acknowledgement of reports and a response time (typically 60 or 90 days) for corrections, adjustments, or other “fixes”;
Reporters/finders agreeing to not share information about the vulnerability until the end of the disclosure period, to let the organisation fix the
issues before it becomes public;
Illegal activities are not permitted (specifying any relevant legislation, such as the Crimes Act, the Privacy Act etc.); and
Either a statement that bug bounties will not be paid for any discoveries, or information about the agency’s bug bounty programme.
References
5.9.21. Additional information relating to system auditing is contained in:
Reference
ISO 29147
Title
Information technology —
Security techniques —
Publisher
Source
ISO
https://www.iso.org/standard/72311.
html
ISO
https://www.iso.org/standard/69725.
html
ITEF
https://datatracker.ietf.org/doc/draft-
Vulnerability disclosure
ISO 30111
Information technology —
Security techniques —
Vulnerability handling processes
IEFT draft protocol for
A File Format to Aid in Security
Security.txt
Vulnerability Disclosure
A proposed standard which
foudil-securitytxt
security.txt
https://securitytxt.org/
allows websites to define
security policies
CERT NZ coordinated
CERT NZ
vulnerability disclosure policy
https://www.cert.govt.nz/itspecialists/guides/reporting-avulnerability/cert-nz-coordinatedvulnerability-disclosure-policy/
BOD 20-01
NZITF Coordinated Disclosure
guidelines
NZITF
https://nzitf.org.nz/coordinateddisclosure
Binding Operational Directive
20-01: Develop and Publish a
US Department of Homeland
Security
https://cyber.dhs.gov/bod/20-01/
Vulnerability Disclosure Policy
60
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents