legal ramifications of violating the relevant policies. 16.1.49. Displaying when a system user last logged in 16.1.49.R.01. Rationale Displaying when a system user has last logged onto a system will assist system users in identifying any unauthorised use of their account. Accordingly, when any case of unauthorised use of an account is identified, it should be reported to an ITSM immediately for investigation. 16.1.49.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1904] Agencies SHOULD configure systems to display the date and time of the system user’s previous login during the login process. 16.1.50. Display of Last User Logged on 16.1.50.R.01. Rationale Agency systems that process or store sensitive information, have monitors displayed in unsecured locations, or are remotely accessed, revealing logged on user’s full names or domain account names presents a number of risks. These include user spoofing (user name is now known), presentation of a target of opportunity for unsecured workstations and a potential privacy breach. These risks are higher on shared workstations, such as Internet access workstations. 16.1.50.R.02. Rationale In Windows and some other systems it is possible that individuals with administrator access can identify last logged information through access to Local Group Policy. This level of access must be carefully controlled and monitored. 16.1.50.R.03. Rationale Some systems may cache credentials on any workstation or other parts of the system. Caching is frequently found where workstations, laptops or mobile devices require domain credentials when disconnected from the domain. This practice can pose some risk and recommended practice is to disable credential caching except where specifically required for operational purposes. 16.1.50.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD NOT [CID:1909] Agencies SHOULD NOT permit the display of last logged on username, credentials or other identifying details. 16.1.50.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD NOT [CID:1910] Agencies SHOULD NOT permit the caching of credentials unless specifically required. 16.2. System Access and Passwords Objective 16.2.1. Access to information on systems is controlled in accordance with agency policy and this manual. Context Scope 16.2.2. This section covers information on accessing systems for all system users. Additional information on privileged users can be found inSection 16.3 Privileged Access and additional information on security clearance, briefing and authorisation requirements can be found inSection 9.2 Authorisations, Security Clearances and Briefings. Rationale & Controls 16.2.3. Access from foreign controlled systems and facilities 16.2.3.R.01. Rationale If a New Zealand system is to be accessed overseas it will need to be from at least a facility owned by a country that New Zealand has a multilateral or bilateral agreement with. NZEO systems can be accessed only from facilities under the sole control of the government of New Zealand and by New Zealand citizens. 16.2.3.C.01. System Classification(s): All Classifications; Compliance: MUST NOT Control [CID:1920] Agencies MUST NOT allow access to NZEO information from systems and facilities not under the sole control of the government of New Zealand and New Zealand citizens. 16.2.3.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD NOT [CID:1921] Unless a multilateral or bilateral security agreement is in place, agencies SHOULD NOT allow access to classified information from systems and facilities not under the sole control of the government of New Zealand and New Zealand citizens. 16.2.4. Enforcing authorisations on systems 16.2.4.R.01. Rationale Enforcing authorisations of system users through the use of access controls on a system will assist in enforcing the need-to-know principle. 16.2.4.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:1924] Agencies MUST have authorisation of system users enforced by access controls. 16.2.5. Protecting compartmented information on systems 16.2.5.R.01. Rationale Compartmented information is particularly sensitive and as such extra measures need to be put in place on systems to restrict access to those with sufficient authorisation, briefings and a demonstrated need-to-know or need- to access. 214 Version_3.5__January-2022

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents