17.9.24. Developing Key Management Plans (KMPs)
17.9.24.R.01. Rationale
Most modern cryptographic systems are designed to be highly resistant to cryptographic analysis but it MUST be assumed that a determined
attacker could obtain details of the cryptographic logic either by stealing or copying relevant material directly or by suborning an New Zealand
national or allied national. Cryptographic system material is safeguarded by implementing strong personnel, physical, documentation and
procedural security measures.
17.9.24.R.02. Rationale
Cryptographic system material is safeguarded by implementing strong key management plan (KMP) encompassing personnel, physical,
documentation and procedural security measures.
17.9.24.C.01. ControlSystem Classification(s): Confidential, Secret, Top Secret; Compliance: MUST
[CID:3016]
Agencies MUST develop a KMP when they have implemented a cryptographic system using HGCP.
17.9.24.C.02. ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:3017]
The level of detail included in a KMP MUST be consistent with the criticality and classification of the information to be protected.
17.9.24.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:3018]
Agencies SHOULD develop a KMP when they have implemented a cryptographic system using commercial grade cryptographic equipment.
17.9.25. Contents of KMPs
17.9.25.R.01. Rationale
When agencies implement the recommended contents for KMPs they will have a good starting point for the protection of cryptographic systems
and their material within their agencies.
17.9.25.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:3021]
The table below describes the minimum contents which SHOULD be documented in the KMP.
Topic
Objectives
Content
Objectives of the cryptographic system and KMP, including
organisational aims.
Refer to relevant NZCSIs.
System description
The environment.
Maximum classification of information protected.
Topology Diagram(s) and description of the cryptographic
system topology including data flows.
The use of keys.
Key algorithm.
Key length.
Key lifetime.
Roles and administrative responsibilities
Documents roles and responsibilities, including the:
COMSEC Custodian;
Cryptographic systems administrator;
Record keeper; and
Auditor.
Accounting
How accounting will be undertaken for the cryptographic
system.
What records will be maintained.
How records will be audited.
Classification
Classification of the cryptographic system hardware.
Classification of cryptographic system software.
Classification of the cryptographic system documentation.
Information security incidents
A description of the conditions under which compromise of key
material should be declared.
References to procedures to be followed when reporting and
dealing with information security incidents.
254
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents