5.3.7.
Contents of SRMPs
5.3.7.R.01.
Rationale
Risks within an agency can be managed if they are not known, and if they are known, failing to treat or accept them is also a failure of risk
management. For this reason SRMPs consist of two components, a security risk assessment and a corresponding treatment strategy.
5.3.7.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:805]
The Security Risk Management Plan SHOULD contain a security risk assessment and a corresponding treatment strategy.
5.3.8.
Agency risk management
5.3.8.R.01.
Rationale
If an agency fails to incorporate SRMPs for systems into their wider agency risk management plan then the agency will be unable to manage
risks in a coordinated and consistent manner across the agency.
5.3.8.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:808]
Agencies SHOULD incorporate their SRMP into their wider agency risk management plan.
5.3.9.
Risk Management standards
5.3.9.R.01.
Rationale
For security risk management to be of true value to an agency there must be direct relevance to the specific circumstances of an agency and
its systems, as well as being based on an industry recognised approach or risk management guidelines. For example, guidelines and standards
produced by Standards New Zealand and the International Organization for Standardization.
The Protective Security Requirements requires that agencies adopt risk management approaches in accordance with ISO 31000:2018. Refer to
PSR governance requirement GOV2.
5.3.9.R.02.
Rationale
The International Organization for Standardization has developed an international risk management standard, including principles and
guidelines on implementation, outlined in ISO 31000:2018, Risk Management – Guidlines. The terms and definitions for this standard can be
found in ISO/IEC Guide 73, Risk Management – Vocabulary – Guidelines. The ISO/IEC 2700x series of standards also provides guidance.
5.3.9.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:812]
Agencies SHOULD develop their SRMP in accordance with international standards for risk management.
5.4. System Security Plans
Objective
5.4.1.
System Security Plans (SSPs) specify the information security measures for systems.
Context
Scope
5.4.2.
This section relates to the development of SSPs. Information relating to other mandatory documentation can be found inSection 5.1 - Documentation
Fundamentals.
5.4.3.
Further information to be included in SSPs relating to specific functionality or technologies that could be implemented for a system can be found in the
applicable areas of this manual.
Stakeholders
5.4.4.
There can be many stakeholders involved in defining a SSP including representatives from the:
project, who MUST deliver the capability (including contractors);
owners of the information to be handled;
system users for whom the capability is being developed;
management audit authority;
CISO, ITSM and system owners;
system certifiers and accreditors;
information management planning areas; and
infrastructure management.
Rationale & Controls
5.4.5.
Contents of System Security Plans (SSPs)
5.4.5.R.01.
Rationale
The NZISM provides a list of controls that are potentially applicable to a system based on its classification, its functionality and the technology
it is implementing. Agencies will need to determine which controls are in scope of the system and translate those controls to the SSP. These
controls will then be assessed on their implementation and effectiveness during an information security assessment as part of the accreditation
process.
5.4.5.R.02.
Rationale
In performing accreditations against the latest baseline of this manual, agencies are ensuring that they are taking the most recent threat
environment into consideration. GCSB continually monitors the threat environment and conducts research into the security impact of emerging
trends. With each release of this manual, controls can be added, rescinded or modified depending on changes in the threat environment.
47
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents