Rationale & Controls
16.1.31. Policies and procedures
16.1.31.R.01. Rationale
Developing policies and procedures will ensure consistency in identification, authentication and authorisation, across agency systems and with
relevant standards. Refer also to Section 16.4 – Privileged Access Management.
16.1.31.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1827]
Agencies MUST:
develop, implement and maintain a set of policies and procedures covering all system users’:
identification;
authentication;
authorisation;
privileged access identification and management; and
make their system users aware of the agency’s policies and procedures.
16.1.32. System user identification
16.1.32.R.01. Rationale
Having uniquely identifiable system users ensures accountability.
16.1.32.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1829]
Agencies MUST ensure that all system users are:
uniquely identifiable; and
authenticated on each occasion that access is granted to a system.
16.1.33. Shared accounts
16.1.33.R.01. Rationale
Sharing passwords and UserIDs (credentials) may be convenient but invariably hampers efforts to identify a specific user and attribute actions
to a specific person or system. While agencies and users find convenience in sharing credentials, doing so is highly risky. Shared credentials
can defeat accountability and the attribution and non-repudiation principles of access control. This is particularly important where
administrative access to networks and servers or access to classified information is provided through shared credentials.
16.1.33.C.01. ControlSystem Classification(s): Top Secret; Compliance: MUST NOT
[CID:1832]
Agencies MUST NOT use shared credentials to access accounts.
16.1.33.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD NOT
[CID:1833]
Agencies SHOULD NOT use shared credentials to access accounts.
16.1.34. System user identification for shared accounts
16.1.34.R.01. Rationale
Agencies may have a compelling business reason for the use of shared accounts. These may include Anonymous, Guest and Temporary
Employee (such relieving a receptionist) credentials. It may not be possible to attribute the use of such accounts to a specific person.
16.1.34.R.02. Rationale
As shared accounts are non user-specific, agencies will need to determine an appropriate method of attributing actions undertaken by such
accounts to specific personnel. For example, a logbook may be used to document the date and time that a person takes responsibility for using
a shared account and the actions logged against the account by the system.
16.1.34.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1837]
If agencies choose to allow shared, non user-specific accounts they MUST ensure that an independent means of determining the identification
of the system user is implemented.
16.1.35. Methods for system user identification and authentication
16.1.35.R.01. Rationale
A personal identification number is typically short in length and employs a small character set, making it susceptible to brute force attacks.
16.1.35.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST NOT
[CID:1840]
Agencies MUST NOT use a numerical password (or personal identification number) as the sole method of authenticating a system user to access
a system.
16.1.35.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1841]
Agencies SHOULD ensure that they combine the use of multiple methods when identifying and authenticating system users.
16.1.36. Protecting stored authentication information
16.1.36.R.01. Rationale
Limiting the storage of unprotected authentication information reduces the possibility of an attacker finding and using the information to access
a system under the guise of a valid system user.
209
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents