User Authentication. 6.2.6.1 Users will usually be authenticated by use of a password. Strong authentication methods (e.g. one-time passwords, digital signatures, etc.) may be required in the future.
6.2.6.2 Passwords must not be stored in script files.
6.2.6.3 Passwords must be entered by the user in real time.
6.2.6.4 Passwords must be at least six to eight (6-8) characters in length, not blank or a repeat of the userid; contain at least one letter, and at least one number or special character must be in a position other than the first or last one. This format will ensure that the password is hard to guess. Most systems are capable of being configured to automatically enforce these requirements. Where a system does not mechanically require this format, the users must manually follow the format.
6.2.6.5 Systems will require users to change their passwords regularly (usually every thirty-one (31) days).
6.2.6.6 Systems are to be configured to prevent users from reusing the same password for six (6) changes/months.
6.2.6.7 Personal passwords must not be shared. A user who has shared his password is responsible for any use made of the password.
User Authentication. Computershare shall implement processes designed to authenticate the identity of all network users through the following means:
User Authentication. 9.7.1 Users will usually be authenticated by use of a password. Strong authentication methods (e.g. one- time passwords, digital signatures, etc.) may be required in the future.
9.7.2 Passwords must not be stored in script files.
9.7.3 Passwords must be entered by the user.
9.7.4 Passwords must be at least 6-8 characters in length, not blank or a repeat of the user id; contain at least one letter, and at least one number or special character must be in a position other than the first or last one. This format will ensure that the password is hard to guess. Most systems are capable of being configured to automatically enforce these requirements. Where a system does not mechanically require this format, the users must manually follow the format.
9.7.5 Systems will require users to change their passwords regularly (usually every 31 days).
9.7.6 Systems are to be configured to prevent users from reusing the same password for 6 changes/months.
9.7.7 Personal passwords must not be shared. A user who has shared his password is responsible for any use made of the password.
User Authentication. 37.5.1 Users will usually be authenticated by use of a password. Strong authentication methods (e.g. one-time passwords, digital signatures, etc.) may be required in the future.
37.5.2 Passwords must not be stored in script files.
37.5.3 Passwords must be entered by the user in real time.
37.5.4 Personal passwords must not be shared. A user who has shared his password is responsible for any use made of the password.
User Authentication. Each Participant Member shall require that any Individual User that requests EHI or requests to send EHI be authenticated at a minimum of AAL2.
User Authentication. The first time you access Online Banking, you will be asked to enter a security code. To obtain this code, select an accessible phone number from the list displayed on your screen and select whether you would prefer a text or a phone call. If you have chosen a text, enter the code that you receive via text into the appropriate field on your computer. If you have chosen a phone call, read or enter the code on your computer screen when prompted. If you fail to see your telephone numbers on the list, please make sure you have entered your User ID correctly. If re-entering your User ID doesn't solve the problem, please call your Surrey Bank & Trust branch for assistance. Your current phone number(s) may not be in our system. You will be required to re-enter the security code periodically. Once you have logged into Online Banking successfully, you may log into the Surrey Bank Mobile app using your Online Banking User ID and password. You must also enter a security code the first time you log into Mobile Banking on your phone and/or tablet. We must have your correct mobile number in our files. You will receive a text after entering your User ID and password into the app. Once you have logged in successfully on your mobile phone, you will be prompted to set up Touch ID, facial recognition, or a six-digit passcode. Mobile Banking users who fail to login successfully three times are locked out of the Mobile Banking app for 24 hours. Any transfer, loan payment or loan advance initiated in Online Banking prior to 5 p.m. (Eastern Time) on a business day (Monday through Friday, excluding legal holidays) is posted to your account the same day. All transactions completed after 5 p.m. (Eastern Time), or on a non-business day, will be posted the following banking day. Our Bill Pay service will process variable payments on the business day (Monday through Friday, except holidays) you designate, provided that the payment instructions are received prior to the Bill Pay Service cut-off time, which is currently 5 p.m. (Eastern Time). Variable bill payment requests received after the cut-off time or at any time on a non-business day will be processed on the next business day. Any Mobile Deposit submitted prior to 4 p.m. (Eastern Time) on a business day (Monday through Friday, excluding legal holidays) is posted to your account the same day. All deposits submitted after 4 p.m. (Eastern Time), or on a non-business day, will be posted the following banking day. Incoming or outgoing...
User Authentication. Each user must logon (using credentials chosen at registration) before the download manager is permitted to download content. SpiralFrog maintains a unique account for each user –registering with the service is a prerequisite for getting access to downloadable content. SpiralFrog will implement a mechanism intended to prevent multiple users from sharing a single user id by monitoring simultaneous usage patterns by the same user ID. Should we see multiple concurrent hits for a user ID on multiple IP addresses the account will be locked out from the service and the user notified.
User Authentication. NetWitness shall implement Processes designed to authenticate the identity of its system users through the following means:
i. User IDs. Each user of a system containing Customer’s Content shall be assigned a unique identification code (“User ID”).
User Authentication. The first time you access Online Banking, you will be asked to enter a security code. To obtain this code, select an accessible phone number from the list displayed on your screen and select whether you would prefer a text or a phone call. If you have chosen a text, enter the code that you receive via text into the appropriate field on your computer. If you have chosen a phone call, read or enter the code on your computer screen when prompted. If you fail to see your telephone numbers on the list, please make sure you have entered your User ID correctly. If re-entering your User ID doesn’t solve the problem, please call your Surrey Bank & Trust branch for assistance. Your phone number(s) may not be in our system. Periodically, you will be asked to re-enter the security code, usually after you have deleted the cookies on your computer.
User Authentication. AGENCY will permit access to HMIS only with use of a User authentication system consisting of a username and a password which the User may not share with others. Written information pertaining to User access (e.g., username and password) shall not be stored or displayed in any publicly accessible location. Passwords shall be between eight and twelve characters long and include both letters and numbers. Passwords shall not be, or include the username, the HMIS vendor’s name, the HMIS LEAD name, the AGENCY's name, or consist entirely of any word found in the common dictionary or any of the forenamed words spelled backwards. The use of default passwords on initial entry into the HMIS is allowed so long as the User changes the default password on first use. Individual Users must not be able to log on to more than one workstation at a time, or be able to log on to the network at more than one location at a time. Passwords and usernames shall be consistent with guidelines issued from time to time by HUD and HMIS LEAD. Passwords and usernames shall not be exchanged electronically without HMIS LEAD's approval.
