Foreign nationals may be granted a national security clearance if risks can be mitigated. Refer to PSR Personnel Security for more information.
PSR References
9.2.4.
Additional policy and information on granting and maintaining security clearances can be found in:
Reference
Title
Source
PSR Mandatory
GOV4, INFOSEC1, PERSEC1, PERSEC2, PERSEC3,
http://www.protectivesecurity.govt.nz
Requirements
PERSEC4, PHYSEC1 and PHYSEC2
https://www.protectivesecurity.govt.nz/governance/mandatoryrequirements-2/
https://www.protectivesecurity.govt.nz/information-security/mandatoryrequirements-2/
https://www.protectivesecurity.govt.nz/personnel-security/mandatoryrequirements/
https://www.protectivesecurity.govt.nz/physical-security/physicalsecurity-mandatory-requirements-2/
PSR content
protocols
Management protocol for information security
Management protocol for personnel security
https://www.protectivesecurity.govt.nz/informationsecurity/management-protocol/
Management Protocol for physical security
https://protectivesecurity.govt.nz/personnelsecurity/clearances/recruiting-and-managing-clearance-holders/
https://protectivesecurity.govt.nz/personnelsecurity/clearances/recruiting-and-managing-clearance-holders/
PSR requirements
Creating a security culture
https://www.protectivesecurity.govt.nz/personnel-security/creating-a-
sections
Build security awareness
security-culture/
Security zones
https://www.protectivesecurity.govt.nz/governance/build-security-
Recruiting and managing national security clearance
awareness/
holders
https://www.protectivesecurity.govt.nz/security-zones/
https://protectivesecurity.govt.nz/personnelsecurity/clearances/recruiting-and-managing-clearance-holders/
Rationale & Controls
9.2.5.
Documenting authorisations, security clearance and briefing requirements
9.2.5.R.01.
Rationale
Ensuring that the requirements for access to a system are documented and agreed upon will assist in determining if system users have
appropriate authorisations, security clearances and need-to-know to access the system.
9.2.5.R.02.
Rationale
Types of system users for which access requirements will need to be documented include general users, privileged users, system
administrators, contractors and visitors.
9.2.5.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1480]
Agencies MUST specify in the System Security Plan (SSP) any authorisations, security clearances and briefings necessary for system access.
9.2.6.
Authorisation and system access
9.2.6.R.01.
Rationale
Personnel seeking access to a system will need to have a genuine business requirement to access the system as verified by their supervisor or
manager. Once a requirement to access a system is established, the system user should be given only the privileges that they need to
undertake their duties. Providing all system users with privileged access when there is no such requirement can cause significant security
vulnerabilities in a system.
9.2.6.C.01.
ControlSystem Classification(s): Top Secret; Compliance: MUST
[CID:1483]
Agencies MUST:
limit system access on a need-to-know/need-to-access basis;
provide system users with the least amount of privileges needed to undertake their duties; and
have any requests for access to a system authorised by the supervisor or manager of the system user.
9.2.6.C.02.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1484]
Agencies SHOULD:
limit system access on a need-to-know/need-to-access basis;
provide system users with the least amount of privileges needed to undertake their duties; and
have any requests for access to a system authorised by the supervisor or manager of the system user.
9.2.7.
Recording authorisation for personnel to access systems
9.2.7.R.01.
Rationale
In many cases, the requirement to maintain a secure record of all personnel authorised to access a system, their user identification, who
provided the authorisation and when the authorisation was granted, can be met by retaining a completed system account request form signed
by the supervisor or manager of the system user.
9.2.7.C.01.
86
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1487]
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents