Rationale & Controls 16.5.10. Authentication 16.5.10.R.01. Rationale Authenticating remote system users and devices ensures that only authorised system users and devices are allowed to connect to agency systems. 16.5.10.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:1973] Agencies MUST authenticate each remote connection and user prior to permitting access to an agency system. 16.5.10.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1974] Agencies SHOULD authenticate both the remote system user and device during the authentication process. 16.5.11. Remote privileged access 16.5.11.R.01. Rationale A compromise of remote access to a system can be limited by preventing the use of remote privileged access from an untrusted domain. 16.5.11.C.01. ControlSystem Classification(s): Confidential, Secret, Top Secret; Compliance: MUST NOT [CID:1977] Agencies MUST NOT allow the use of remote privileged access from an untrusted domain, including logging in as an unprivileged system user and then escalating privileges. 16.5.11.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD NOT [CID:1978] Agencies SHOULD NOT allow the use of remote privileged access from an untrusted domain, including logging in as an unprivileged system user and then escalating privileges. 16.5.12. VPNs 16.5.12.R.01. Rationale Virtual Private Networks (VPN’s) use a tunnelling protocol to create a secure connection over an intermediate (public) network such as the internet. A VPN uses techniques such as encryption, authentication, authorisation and access control to achieve a secure connection. See Chapter 17 for details on cryptographic selection and implementation. 16.5.12.R.02. Rationale A VPN can connect remote or mobile workers or remote locations to a private (agency) network. 16.5.12.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1982] Agencies SHOULD establish VPN connections for all remote access connections. 16.6. Event Logging and Auditing Objective 16.6.1. Information security related events are logged and audited for accountability, incident management, forensic and system monitoring purposes. Context Scope 16.6.2. This section covers information on the automatic logging of information relating to network activities. Information regarding manual logging of system management activities can be found in Section 16.3 - Privileged Access. See also Chapter7 - Information Security Incidents. 16.6.3. A security event is a change to normal or expected behaviour of a network, network component, system, device or user. Event logging helps improve the security posture of a system by increasing the accountability of all user actions, thereby improving the chances that malicious behaviour will be detected. 16.6.4. It is important that sufficient details are recorded in order for the logs to be useful when reviewed or when an investigation is in progress. Retention periods are also important to ensure sufficient log history is available. Conducting audits of event logs is an integral part of the security and maintenance of systems, since they will help detect and attribute any violations of information security policy, including cyber security incidents, breaches and intrusions. References 16.6.5. Additional information relating to event logging is contained in: Reference ISO/IEC 27001:2013 Title Information technology — Security techniques — Publisher Source ISO https://www.iso.org/standard/54534. html Information security management systems — Requirements - Monitoring 222 Version_3.5__January-2022

Select target paragraph3

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