Managed Service Accounts do not require manual credential management by system administrators, as the operating system automatically manages the credentials. This ensures that service account credentials are not misplaced or forgotten, and that they are automatically changed on a regular basis. Security Control: ISM-1619; Revision: 0; Updated: Oct-20; Applicability: All; Essential Eight: N/A Service accounts are created as group Managed Service Accounts. Account lockouts Locking an account after a specified number of failed logon attempts reduces the likelihood of successful credential spraying attacks by an adversary. However, care should be taken as implementing account lockout functionality can increase the likelihood of a denial of service. Alternatively, some systems can be configured to automatically slowdown repeated failed logon attempts (known as rate limiting) rather than locking accounts. Implementing multi-factor authentication is also an effective way of reducing the likelihood of successful credential spraying attacks. Security Control: ISM-1403; Revision: 2; Updated: Oct-19; Applicability: All; Essential Eight: N/A Accounts are locked out after a maximum of five failed logon attempts. Insecure authentication methods Authentication methods need to resist theft, interception, duplication, forgery, unauthorised access and unauthorised modification. For example, Local Area Network (LAN) Manager and NT LAN Manager authentication methods use weak hashing algorithms. As such, credentials used as part of LAN Manager authentication and NT LAN Manager authentication (i.e. NTLMv1, NTLMv2 and NTLM2) can easily be compromised. Instead, an organisation should use Kerberos for authentication within Microsoft Windows environments and ensure all privileged accounts are members of the Protected Users security group. Security Control: ISM-1603; Revision: 0; Updated: Aug-20; Applicability: All; Essential Eight: N/A Authentication methods susceptible to replay attacks are disabled. Security Control: ISM-1055; Revision: 4; Updated: Oct-20; Applicability: All; Essential Eight: N/A LAN Manager and NT LAN Manager authentication methods are disabled. Security Control: ISM-1620; Revision: 0; Updated: Oct-20; Applicability: All; Essential Eight: N/A Privileged accounts are members of the Protected Users security group. Protecting credentials When local administrator accounts use common usernames and credentials, it can allow an adversary that compromises credentials on one workstation or server to easily compromise other workstations and servers. As such, it is critical that credentials for local administrator accounts and service accounts are unique, unpredictable and managed. Storing physical credentials with a system, such as security keys, smart cards, one-time password tokens and written down memorised secrets, increases the likelihood of an adversary gaining access to the system. For example, when passphrases are written down and stuck to a computer monitor, smart cards are left on desks or security keys are left in laptop bags. Furthermore, obscuring credentials as they are entered into systems can assist in protecting them against screen scrapers and shoulder surfers. If storing credentials on a system, sufficient protection should be implemented to prevent them from being compromised. For example, credentials can be stored in a password manager or hardware security module, while credentials stored in a database should be hashed, salted and stretched. In addition, Windows Defender Credential Guard and Windows Defender Remote Credential Guard can be enabled to provide additional protection for credentials. 87

Select target paragraph3

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