System Classification(s): All Classifications; Compliance: SHOULD NOT 16.1.41.C.04. Control [CID:1871] Agencies SHOULD NOT: allow predictable reset passwords; reuse passwords when resetting multiple accounts; store passwords in the clear on the system; allow passwords to be reused within eight password changes; and allow system users to use sequential passwords. 16.1.42. Resetting passwords 16.1.42.R.01. Rationale To reduce the likelihood of social engineering attacks aimed at service desks, agencies will need to ensure that system users provide sufficient evidence to verify their identity when requesting a password reset for their system account. This evidence could be in the form of: the system user physically presenting themselves and their security pass to service desk personnel who then reset their password; physically presenting themselves to a known colleague who uses an approved online tool to reset their password; or establishing their identity by responding correctly to a number of questions before resetting their own password. 16.1.42.R.02. Rationale Issuing complex reset passwords maintains the security of the user account during the reset process. This can also present an opportunity to demonstrate the selection of strong passwords. 16.1.42.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:1875] Agencies MUST ensure system users provide sufficient evidence to verify their identity when requesting a password reset for their system account. 16.1.43. Password authentication 16.1.43.R.01. Rationale LAN Manager’s authentication mechanism uses a very weak hashing algorithm known as the LAN Manager hash algorithm. Passwords hashed using the LAN Manager hash algorithm can easily be compromised using rainbow tables or brute force attacks. 16.1.43.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1878] Agencies SHOULD disable LAN Manager for password authentication on workstations and servers. 16.1.44. Session termination 16.1.44.R.01. Rationale Developing a policy to automatically logout and shutdown workstations after an appropriate time of inactivity will assist in preventing the compromise of an unattended workstation that contains classified or sensitive information. Such a policy will also reduce the power consumption requirements of the agency during non-operational hours. 16.1.44.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1881] Agencies SHOULD develop and implement a policy to automatically logout and shutdown workstations after an appropriate time of inactivity. 16.1.45. Session and screen locking 16.1.45.R.01. Rationale Screen and session locking will prevent access to an unattended workstation. 16.1.45.R.02. Rationale Ensuring that the screen does not appear to be turned off while in the locked state will prevent system users from forgetting they are still logged in and will prevent other system users from mistakenly thinking there is a problem with a workstation and resetting it. 16.1.45.C.01. ControlSystem Classification(s): Confidential, Secret, Top Secret; Compliance: MUST [CID:1885] Agencies MUST: configure systems with a session or screen lock; configure the lock to activate: after a maximum of 10 minutes of system user inactivity; or if manually activated by the system user; configure the lock to completely conceal all information on the screen; ensure that the screen is not turned off or enters a power saving state before the screen or session lock is activated; have the system user reauthenticate to unlock the system; and deny system users the ability to disable the locking mechanism. 16.1.45.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1886] Agencies SHOULD: configure systems with a session or screen lock; 212 Version_3.5__January-2022

Select target paragraph3

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