UserIDs, Passwords, and Tokens. Applicant shall ensure that Consumer Sentinel Network log in user IDs, passwords, and tokens are properly secured.
UserIDs, Passwords, and Tokens Sample Clauses
Related to UserIDs, Passwords, and Tokens
Passwords and Security You acknowledge that you will be the only authorized user of Firstrade Securities Inc.'s Electronic Services for your account(s). You will be fully responsible for the confidentiality and use of your user name(s) and password (s) and you agree that you will be fully and solely responsible for all activities, including brokerage transactions, which arise from the use of your user name (s) or password(s) (except as provided for in paragraph 5 below). You also agree that you will be fully and solely responsible for all activities, including brokerage transactions, which arise from your authorization to link your brokerage account(s) to any other Firstrade Securities Inc. account(s). You acknowledge that we may tape record conversations with you, whether in person or by telephone, for purposes of verification and you consent to such recording.
User IDs and Password Controls All users must be issued a unique user name for accessing DHCS PHI or PI. Username must be promptly disabled, deleted, or the password changed upon the transfer or termination of an employee with knowledge of the password, at maximum within 24 hours. Passwords are not to be shared. Passwords must be at least eight characters and must be a non-dictionary word. Passwords must not be stored in readable format on the computer. Passwords must be changed every 90 days, preferably every 60 days. Passwords must be changed if revealed or compromised. Passwords must be composed of characters from at least three of the following four groups from the standard keyboard: • Upper case letters (A-Z) • Lower case letters (a-z) • Arabic numerals (0-9) • Non-alphanumeric characters (punctuation symbols)
Passwords and Employee Access Provider shall secure usernames, passwords, and any other means of gaining access to the Services or to Student Data, at a level suggested by Article 4.3 of NIST 800-63-3. Provider shall only provide access to Student Data to employees or contractors that are performing the Services. Employees with access to Student Data shall have signed confidentiality agreements regarding said Student Data. All employees with access to Student Records shall pass criminal background checks.
Passwords Passwords are an important aspect of computer security. A poorly chosen password may result in unauthorized access and/or exploitation of Placer County’s resources. All users, including contractors and vendors with access to the County’s systems, are responsible for the creation and protection of passwords and additionally any updates to County Password policies must be followed. Users must not use the same password for Placer County accounts and personal accounts. The reliability of passwords for maintaining confidentiality cannot be guaranteed. Always assume that someone, in addition to the intended or designated recipient, may read any and all messages and files. Any user suspecting that his/her password may have been compromised must, without delay, report the incident to Placer County IT.
Use of information, data and software In the event that you receive any data, information or software via the Trading Platform other than that which you are entitled to receive pursuant to this Client Agreement, you will immediately notify us and will not use, in any way whatsoever, such data, information or software.
Usernames and Passwords 1. Staff will not share usernames and passwords with anyone, including supervisors and technical support staff.
Use of School Equipment The Association shall have the right to use school facilities and equipment, including duplicating equipment, calculating machines, computers and printers and all types of audiovisual equipment at reasonable times, when such equipment is not otherwise in use.
Access to Software Access Rights to Software which is Results shall comprise: Access to the Object Code; and, where normal use of such an Object Code requires an Application Programming Interface (hereafter API), Access to the Object Code and such an API; and, if a Party can show that the execution of its tasks under the Project or the Exploitation of its own Results is technically or legally impossible without Access to the Source Code, Access to the Source Code to the extent necessary. Background shall only be provided in Object Code unless otherwise agreed between the Parties concerned.
Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.
Records and Documentation The Sub-Recipient agrees to make available to AAAPP staff and/or any party designated by the AAAPP any and all contract related records and documentation. The Sub-Recipient shall ensure the collection and maintenance of all program related information and documentation on any such system designated by the AAAPP. Maintenance includes valid exports and backups of all data and systems according to AAAPP standards.
