Agencies MUST conduct a risk assessment in order to determine the type and level of independent assurance required to satisfy certification
and accreditation requirements.
5.8.61.C.02.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1020]
In all cases where assurance on service provider operations cannot be obtained directly, agencies SHOULD obtain independent assurance
reports.
5.8.61.C.03.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1021]
In order to address identified risk areas, agencies SHOULD obtain relevant assurance reports and service provider certifications to inform a risk
assessment and Certification activities as well as other aspects of the certification processes such as evidence of controls effectiveness and
remediation plans.
5.8.62.
Independent Assurance
5.8.62.R.01.
Rationale
Independent assurance can be obtained directly from the service provider through Service Organisation Control (SOC) reports, as well as other
internationally recognised assurance frameworks. It will be important to corroborate individual reports by comparison with other reporting
mechanisms and independent certifications.
5.8.62.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1024]
Agencies MUST incorporate the results of any independent assurance reports into the agency Certification process, to understand the residual
risk position and controls required to manage risk appropriately.
5.9. Vulnerability Disclosure Policy (VDP)
Objective
5.9.1.
Agencies implement a Vulnerability Disclosure Policy (VDP) to enable members of the public to report vulnerabilities in the agency’s public-facing
systems and applications and receive feedback on such reports.
Context
Scope
5.9.2.
This section provides information on vulnerability disclosure for all externally-facing agency systems, including public-facing systems. Vulnerability
disclosure relating to internal systems is covered in Chapter 12 – Product Security.
5.9.3.
When selecting which systems, applications and data are within scope of a VDP, agencies may consider:
a. The sensitivity of information on the agency’s systems, including financial data, medical information, proprietary information, customer data or
other personally identifiable information (PII).
b. Security safeguards that are already in place on the system, such as encryption of data at rest.
c. The agency’s ability to segment its network or otherwise segregate sensitive information stored on its systems.
d. Regulatory, contractual, privacy or other restrictions placed on disclosure of protected classes of information (such as within the New Zealand
Classification System).
5.9.4.
Reference to other chapters and sections in this document is essential. In particular:
Chapter 4 - System Certification and Accreditation;
Chapter 5 – Information Security Documentation;
Section 6.2 - Vulnerability Analysis;
Section 6.3 - Change Management;
Chapter 7 – Information Security Incidents;
Section 12.4 – Product Patching and Updating;
Chapter 14 - Software Security.
Agencies must expect vulnerabilities
5.9.5.
Invariably all software, operating systems and applications have the potential to house exploitable vulnerabilities. Many vulnerabilities are identified
by users and other third parties. Some vulnerabilities may be undiscovered or inherent in the application or software. Others may be introduced during
upgrades, patches, configuration or other changes.
5.9.6.
It is essential that agencies establish a policy and processes to identify and remediate such vulnerabilities.
Agencies must establish a vulnerability reporting mechanism
5.9.7.
Published VDPs demonstrate that an agency has a mature and constructive approach when they receive a vulnerability report and also demonstrates
openness and transparency in the management of agency systems.
5.9.8.
Agencies should establish a process to allow any user (whether a member of the public, business partners, other agencies or agency staff), to report
potential vulnerabilities. Any such reporting is on a “no blame” basis, without fear of repercussion or penalty, provided the agency’s disclosure policy
is followed and no illegal activity is undertaken.
5.9.9.
The VDP must clearly state the conditions under which reports are received. In general terms this also includes a “no bug bounty” clause as well as
limits on web site, system or application probing.
5.9.10. An agency’s VDP will necessarily reflect that they may not control or own all of the software they use or the maintenance and development of
underlying software (such as compilers, programming or scripting languages and so on). The VDP should clearly state that while the agency can
receive reports about software, systems or services run on their behalf by third parties, providers or vendors, they may have to work with the reporting
party to report the vulnerability to the relevant vendor.
59
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents