16.3.5.
Use of privileged accounts
16.3.5.R.01.
Rationale
Inappropriate use of any feature or facility of a system that enables a privileged user to override system or application controls can be a major
contributory factor to failures, information security incidents, or system breaches.
16.3.5.R.02.
Rationale
Privileged access rights allow for system wide changes to be made and as such an appropriate and effective mechanism to log privileged users
and strong change management practices will provide greater accountability and auditing capability.
16.3.5.C.01.
ControlSystem Classification(s): Confidential, Secret, Top Secret; Compliance: MUST
[CID:1945]
Agencies MUST:
ensure strong change management practices are implemented;
ensure that the use of privileged accounts is controlled and accountable;
ensure that system administrators are assigned and consistently use, an individual account for the performance of their administration
tasks;
keep privileged accounts to a minimum; and
allow the use of privileged accounts for administrative work only.
16.3.5.C.02.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1946]
Agencies SHOULD:
ensure strong change management practices are implemented;
ensure that the use of privileged accounts is controlled and accountable;
ensure that system administrators are assigned an individual account for the performance of their administration tasks;
keep privileged accounts to a minimum; and
allow the use of privileged accounts for administrative work only.
16.3.6.
Privileged system access by foreign nationals
16.3.6.R.01.
Rationale
As privileged users may have the ability to bypass controls on a system it is strongly encouraged that foreign nationals are not given privileged
access to systems processing particularly sensitive information.
16.3.6.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST NOT
[CID:1949]
Agencies MUST NOT allow foreign nationals, including seconded foreign nationals, to have privileged access to systems that process, store or
communicate NZEO information.
16.3.6.C.02.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD NOT
[CID:1950]
Agencies SHOULD NOT allow foreign nationals, including seconded foreign nationals, to have privileged access to systems that process, store or
communicate classified information.
16.3.7.
Security clearances for privileged users
16.3.7.R.01.
Rationale
When frequent data transfers occur between systems of different classifications, having privileged users from the lesser system cleared to the
classification of the higher system will assist in any actions that need to be taken resulting from any data spill.
16.3.7.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1953]
Agencies involved in frequent transfers of data from another system to their system with a lesser classification SHOULD clear at least one
privileged user to the classification of the higher system.
16.4. Privileged Access Management
Objective
16.4.1. To ensure Privileged Access Management (PAM) is incorporated into IT Governance and that privileged accounts are managed in accordance with
agency’s PAM policy.
Context
Scope
16.4.2. This section provides information and guidance on the establishment and operation of an agency’s Privileged Access Management policy and control
mechanisms. This is sometimes also described as Privileged Account Management. In the context of this section the terms are synonymous.
16.4.3. Reference to other sections in this document is essential. In particular:
216
3.5
System Users;
5.1
Documentation Fundamentals;
6.3
Change Management;
9.1
Information Security Awareness and Training;
16.1
Identification, Authentication and Passwords;
16.2
System Access and Passwords;
16.3
Privileged User Access;
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents