residual risk is managed prudently and pragmatically.
4.5.18.R.03.
Rationale
It is especially important that All-of-Government systems and effects on systems of other agencies are also considered in the examination of
risk and determination of residual risk.
4.5.18.R.04.
Rationale
To assist in making an accreditation decision the Accreditation Authority may choose to review:
Information Security Documentation as described in Chapter 5;
any interaction with systems of other agencies or All-of-Government systems;
compliance audit reports;
the accreditation recommendation from the certification authority;
supporting documentation for any decisions to be non-compliant with any controls specified in this manual;
any additional security risk reduction strategies that have been implemented; and
any third party reviews or assurance reports available.
4.5.18.R.05.
Rationale
The Accreditation Authority may also choose to seek the assistance of one or more technical experts in understanding the technical
components of information presented to them during the accreditation process to assist in making an informed accreditation decision.
4.5.18.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:673]
The Accreditation Authority MUST accept the residual security risk relating to the operation of a system in order to award accreditation.
4.5.18.C.02.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:674]
The Accreditation Authority MUST advise other agencies where the accreditation decision may affect those agencies.
4.5.18.C.03.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:675]
The Accreditation Authority MUST advise the GCDO where the accreditation decision may affect any All-of-Government systems.
5. Information security documentation
5.1. Documentation Fundamentals
Objective
5.1.1.
Information security documentation is produced for systems, to support and demonstrate good governance.
Context
Scope
5.1.2.
This section is an overview of the information security documentation that each agency will need to develop. More specific information on each
document can be found in subsequent sections of this chapter.
5.1.3.
While this section describes a number of different but essential documents, it may be more advantageous and efficient to provide agency wide
documentation for some elements (for example Physical Security) which can then be re-used for all agency systems.
5.1.4.
Similarly some consolidation may be appropriate, for example, SOPs IRPs and EPs can easily be combined into a single document.
Note: For smaller agencies and smaller systems it is acceptable that all documentation elements are combined into a single document provided each
documentation element is clearly identifiable.
Note: Agencies may choose to name the documentation in different terms. This is acceptable provided the required level of detail is captured. Naming
conventions presented in the NZISM are not mandatory.
Information Security Documentation
5.1.5.
Information Security Documentation requirements are summarised in the table below.
Title
41
Abbreviation
Reference
Information Security Policy (incorporates
SecPol
5.1.7
the vulnerability disclosure policy)
VDP
5.9
Systems Architecture
-
5.1.8
Security Risk Management Plan
SRMP
5.1.9
System Security Plan
SSP
5.1.10
Site Security Plan
SitePlan
8.2.7
Standard Operating Procedures
SOPs
5.1.11
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents