Agencies SHOULD retain DNS, proxy and event logs for at least 18 months. 16.6.14. Event log auditing 16.6.14.R.01. Rationale Conducting audits of event logs is seen as an integral part of the maintenance of systems, as they will assist in the detection and attribution of any violations of agency security policy, including information security incidents, breaches and intrusions. 16.6.14.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2034] Agencies MUST develop and document event log audit requirements covering: the scope of audits; the audit schedule; action to be taken when violations are detected; reporting requirements; and roles and specific responsibilities. 16.7. Multi-Factor Authentication Objective 16.7.1. To ensure authentication systems incorporate Multi-Factor Authentication mechanisms to secure Privileged Accounts and in accordance with the Agency’s Privileged Access Management (PAM) policy. Context Scope 16.7.2. This section provides information and guidance on the establishment and operation of Multi-Factor Authentication (MFA). It is a critical component of robust Identity and Access Management (IAM), particularly where remote access workforces are required or exist. 16.7.3. Reference to other chapters and sections in this document is essential. In particular: Chapter 7 – Information Security Incidents; Section 9.1 – Information Security Awareness and Training ; Section 16.1 – Identification, Authentication and Passwords; Section 16.2 – System Access and Passwords; Section 16.3 – Privileged User Access; Section 16.4 – Privileged Access Management; and Chapter 17 - Cryptography. Background 16.7.4. Authentication is a key element of security that provides confirmation of the identity of all parties to a transaction. In this context a transaction may include browsing, financial operations and all types of data access, creation, copying and deletion. 16.7.5. Multi-Factor Authentication (MFA) is a security system that verifies a user’s identity by requiring multiple credentials, which may be of the same factor or type. Initial authentication often requires a username and password followed by a requirement for other (additional) credentials. It is important to recognise that MFA authentication is not necessarily the same as Two-Factor Authentication or Dual-Factor Authentication. MFA can enable, for example, valid users’ access to permit credential reset, even if they are using a username and password that may have been compromised. 16.7.6. Multi-Factor Authentication (MFA) is a strong defence and deterrent against many credential attacks, including brute-force, credential stuffing and password spraying attacks. It also defends against social engineering attacks seeking user credentials. 16.7.7. Multi-Factor Authentication (MFA) incorporates Two-Factor Authentication (2FA), which is also briefly discussed in Section 16.1 – Identification, Authentication and Passwords. 2FA requires two elements from any of the three factors of authentication and with the second factor from a different group to the first factor selected. These factors or groups are: 1. Something you have (preferably NOT the device itself but a SEPARATE authentication device such as a token, RFID card or smartcard). This is also known as the possession or ownership factor; 2. Something you know such as a PIN, One-Time Password (OTP), reusable password, pattern or other component of a standard authentication mechanism. This is also described as the knowledge factor; 3. Something you are (physical characteristics or biometrics of various types). This is also described as theinherence factor. 16.7.8. MFA is frequently used where the assurance provided by username and password is inadequate. Additional authenticators increase attack resistance and reduce risk of unauthorised access. Additional authentication also assists in managing Privileged Access (refer to Section 16.4 – Privileged Access Management). 16.7.9. MFA is most effective when knowledge, possession, and inherence authentication factors are used as compensating factors for other authentication weaknesses. This is discussed in more detail in 16.7.16 below. Using MFA increases attack resistance by increasing the difficulty of obtaining all necessary authenticators. 16.7.10. It is important to use a variety of factors to strengthen attack resistance in order to increase confidence levels in the chosen authentication system. For example, using a second factor from the knowledge group is less effective as passwords are inherently part of the knowledge group. Knowledge groups are most exposed to attack and compromise through social engineering. 16.7.11. To maximise the effectiveness and security of any Multi-Factor Authentication construct, the authentication service should be dedicated, hardened and isolated within the network’s security architecture. SMS 226 Version_3.5__January-2022

Select target paragraph3

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