configure the lock to activate:
after a maximum of 15 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.46. Suspension of access
16.1.46.R.01. Rationale
Locking a system user account after a specified number of failed logon attempts will reduce the risk of brute force attacks.
16.1.46.R.02. Rationale
Removing a system user account when it is no longer required will prevent personnel from accessing their old account and reduce the number
of accounts that an attacker can target.
16.1.46.R.03. Rationale
Suspending inactive accounts after a specified number of days will reduce the number of accounts that an attacker can target.
16.1.46.R.04. Rationale
Investigating repeated account lockouts will reduce the security risk of any ongoing brute force logon attempts and allow security management
to act accordingly.
16.1.46.C.01. ControlSystem Classification(s): Confidential, Secret, Top Secret; Compliance: MUST
[CID:1892]
Agencies MUST:
Record all successful and failed logon attempts;
lock system user accounts after three failed logon attempts;
have a system administrator reset locked accounts;
remove or suspend system user accounts as soon as possible when personnel no longer need access due to changing roles or leaving the
agency; and
remove or suspend inactive accounts after a specified number of days.
16.1.46.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1893]
Agencies SHOULD:
lock system user accounts after three failed logon attempts;
have a system administrator reset locked accounts;
remove or suspend system user accounts as soon as possible when personnel no longer need access due to changing roles or leaving the
agency; and
remove or suspend inactive accounts after a specified number of days.
16.1.47. Investigating repeated account lockouts
16.1.47.R.01. Rationale
Repeated account lockouts may be an indication of malicious activity being directed towards compromising a particular account.
16.1.47.C.01. ControlSystem Classification(s): Confidential, Secret, Top Secret; Compliance: SHOULD
[CID:1896]
Agencies SHOULD ensure that repeated account lockouts are investigated before reauthorising access.
16.1.48. Logon banner
16.1.48.R.01. Rationale
A logon banner for a system serves to remind system users of their responsibilities when using the system. It may also be described as a
“Splash Screen” or “User Consent Screen”.
16.1.48.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1899]
Agencies SHOULD have a logon banner that requires a system user to acknowledge and accept their security responsibilities before access to
the system is granted.
16.1.48.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1900]
Agencies SHOULD seek legal advice on the exact wording of logon banners.
16.1.48.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1901]
Agency logon banners SHOULD cover issues such as:
the system’s classification;
access only being permitted to authorised system users;
the system user’s agreement to abide by relevant security policies;
the system user’s awareness of the possibility that system usage is being monitored;
the definition of acceptable use for the system; and
213
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents