When using Microsoft Windows systems, cached credentials are stored in the Security Accounts Manager database and
can allow a user to logon to a workstation they have previously logged onto even if the domain is not available. Whilst
this functionality may be desirable from an availability perspective, this functionality can be abused by an adversary
who can retrieve these cached credentials. To reduce this security risk, cached credentials should be limited to only one
previous logon.
Security Control: ISM-1685; Revision: 0; Updated: Sep-21; Applicability: All; Essential Eight: ML2, ML3
Credentials for local administrator accounts and service accounts are unique, unpredictable and managed.
Security Control: ISM-0418; Revision: 5; Updated: Mar-22; Applicability: All; Essential Eight: N/A
Physical credentials are stored separately from systems to which they grant access.
Security Control: ISM-1597; Revision: 0; Updated: Aug-20; Applicability: All; Essential Eight: N/A
Credentials are obscured as they are entered into systems.
Security Control: ISM-1402; Revision: 6; Updated: Mar-22; Applicability: All; Essential Eight: N/A
Credentials stored on systems are protected by a password manager; a hardware security module; or by hashing, salting
and stretching them before storage within a database.
Security Control: ISM-1686; Revision: 0; Updated: Sep-21; Applicability: All; Essential Eight: ML3
Windows Defender Credential Guard and Windows Defender Remote Credential Guard are enabled.
Security Control: ISM-1749; Revision: 0; Updated: Mar-22; Applicability: All; Essential Eight: N/A
Cached credentials are limited to one previous logon.
Security Control: ISM-1590; Revision: 1; Updated: Mar-22; Applicability: All; Essential Eight: N/A
Credentials are changed if:
they are directly compromised
they are suspected of being compromised
they appear in an online data breach database
they are discovered stored on networks in the clear
they are discovered being transferred across networks in the clear
membership of a shared account changes
they have not been changed in the past 12 months.
Session termination
Implementing measures to automatically terminate user sessions and reboot workstations outside of business hours,
after an appropriate period of inactivity, can assist in both system maintenance activities as well as removing an
adversary that may have compromised a system but failed to gain persistence.
Security Control: ISM-0853; Revision: 2; Updated: Mar-22; Applicability: All; Essential Eight: N/A
Outside of business hours, after an appropriate period of inactivity, user sessions are automatically terminated and
workstations are rebooted.
Session and screen locking
Session and screen locking prevents unauthorised access to a system which a user has already authenticated to.
Security Control: ISM-0428; Revision: 8; Updated: Mar-22; Applicability: All; Essential Eight: N/A
Systems are configured with a session or screen lock that:
activates after a maximum of 15 minutes of user inactivity, or if manually activated by users
88
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents