PSR Mandatory Requirements
GOV3, INFOSEC1, INFOSEC2, INFOSEC3 and INFOSEC4
https://www.protectivesecurity.govt.nz
PSR content protocols
Management protocol for information security
https://www.protectivesecurity.govt.nz
PSR requirements sections
Review your security measures
https://www.protectivesecurity.govt.nz
Rationale & Controls
5.9.23.
Vulnerability disclosure policy (VDP) Risk Assessment
5.9.23.R.01.
Rationale
Selection of public-facing systems and services included in any VDP will be based on a risk assessment undertaken by the agency.
Considerations for such selection are discussed in the Context section above.
5.9.23.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:7130]
An agency MUST undertake a risk assessment to determine which systems and services to include in the agency’s VDP.
5.9.24.
Vulnerability disclosure policy (VDP) Essential Content
5.9.24.R.01.
Rationale
In order to demonstrate a mature and constructive approach to vulnerability discovery, management and remediation, an agency requires a
VDP to inform the public about:
the scope of public-facing systems covered by its VDP; and
the nature of vulnerabilities which can be reported under its VDP.
5.9.24.R.02.
Rationale
To aid consistency, it is important that government agencies have a core set of content in their VDP.
5.9.24.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:7133]
An agency MUST develop and publish a VDP.
5.9.24.C.02.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:7134]
An agency’s VDP MUST contain at least the following core content:
A scoping statement listing the systems the policy applies to;
Contact details;
Secure communication options (including any public keys);
Information the finder should include in the report;
Acknowledgement of reports and a response time;
Guidance on what forms of vulnerability testing are out of scope for reporters/finders (permitted activities);
Reporters/finders agreeing to not share information about the vulnerability until the end of the disclosure period, in order to allow the
agency to address any issues before they become public;
Illegal activities are not permitted (specifying the relevant legislation, such as the Crimes Act); and
Either that “Bug bounties” will not be paid for any discoveries, or it should provide information about the agency’s bug bounty programme.
5.9.25.
Vulnerability disclosure policy (VDP) Additional Content
5.9.25.R.01.
Rationale
As well as mandatory content listed above, additional information that agencies may consider providing includes guidance for reporters/finders
to locate the agency’s policy and how to confidentially communicate technical details to the agency’s security experts.
5.9.25.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:7136]
An agency SHOULD publish a security.txt to permit secure communications and direct any reports to a specific agency resource, in accordance
with the agency’s VDP.
5.9.26.
Vulnerability disclosure policy (VDP) Setting Expectations
5.9.26.R.01.
Rationale
Agencies must set clear expectations for reporters/finders on the timeframe within which agencies intend to address and remediate
vulnerabilities that have been reported to them. The industry standard for a vulnerability disclosure policy is 90 days.
5.9.26.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:7138]
An agency MUST commit to addressing disclosed vulnerabilities within the timeframe it sets in its policy.
5.9.26.C.02.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:7139]
An agency’s vulnerability disclosure timeframe SHOULD be set to no more than 90 days.
5.9.27.
Vulnerability disclosure policy (VDP) Integration
5.9.27.R.01.
Rationale
It is essential that a VDP is integrated and consistent with an agency’s information security documentation and its policies, processes and
procedures for Incident Management, Product Security and Software Security (Chapters 5, 7, 12, 14).
5.9.27.C.01.
62
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:7141]
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents