Recommended Control 09: Recommended Control 10: Recommended Control 11: Recommended Control 12: 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 remove or suspend inactive accounts after a specified number of days 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 Agency logon banners should cover issues such as: the system’s description access only being permitted to authorized 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 legal ramifications of violating the relevant policies Agencies should configure systems to display the date and time of the system user’s previous login during the login process Developing policies and procedures will ensure consistency in identification, authentication and authorization, across agency systems and with relevant standards. Sharing passwords and UserIDs (credentials) may be convenient but invariably hampers efforts to identify a specific user and attribute actions to a specific person or system. While agencies and users find convenience in sharing credentials, doing so is highly risky. Shared credentials can defeat accountability and the attribution and non‐repudiation principles of access control. This is particularly important where administrative access to networks and servers is provided through shared credentials. However, agencies may have a compelling business reason for the use of shared accounts. These may include Anonymous, Guest and Temporary Employee (such relieving a receptionist) credentials. It may not be possible to attribute the use of such accounts to a specific person. As shared accounts are non‐user‐specific, agencies will need to determine an appropriate method of attributing actions undertaken by such accounts to specific personnel. For example, a logbook may be used to document the date and time that a person takes responsibility for using a shared account and the actions logged against the account by the system. 86

Select target paragraph3

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