Identification and Authentication. Customer shall assure that any access to any database related to the Cloud Services, whether by Customer or SAP, is automatically disconnected after a period of no-activity and that it has in place a method of handling malfunctions connected with identification authentication, all in accordance with the requirements under Section 9 of the Regulations.
Identification and Authentication. 8. For access to In-Scope Information and for host devices that support it, assign unique credentials (eg. UserIDs, passwords) to authorized individual users, assign individual ownership to system service accounts, and ensure that system service accounts are not shared by administrators.
Identification and Authentication. The purpose of authentication is to provide reliable identification for access to data or information systems. Entity must maintain the identity of active users, linking actions to specific users, and all other identification and authentication requirements. Non-repudiation must be maintained for each user accessing DPS data.
Identification and Authentication. All access to any Customer Information or any West Processing Resources shall be Identified and Authenticated as defined in this Section. “Identification” refers to processes which establish the identity of the person or entity requesting access to Customer Information and/or West Processing Resources. “Authentication” refers to processes which validate the purported identity of the requestor. For access to Customer Information or West Processing Resources, West shall require Authentication by the use of an individual, unique user ID and an individual password and/or other appropriate Authentication technique (e.g. soft token, pin, etc.). West shall obtain written approval from Customer prior to using digital certificates as part of West’s Identification or Authorization processes. West shall maintain procedures to ensure the protection, integrity, and soundness of all passwords created by West and/or used by West in connection with the Agreement.
Identification and Authentication. 40. A banking corporation shall determine the means of personal identification and authentication for its E-Banking activity in accordance with the risk assessment and policy approved by the Board of Directors.
Identification and Authentication. All access to any Mercury Information or any Global Processing Resources shall be Identified and Authenticated as defined in this Section. “Identification” refers to processes which establish the identity of the person or entity requesting access to Mercury Information and/or Global Processing Resources. “Authentication” refers to processes which validate the purported identity of the requestor. For access to Mercury Information or Global Processing Resources, each party shall require *****. Each party shall maintain its own procedures to ensure the protection, integrity, and soundness of all passwords created and/or used in connection with the Agreement.
Identification and Authentication. The data importer shall take the measures that ensures the identification and authentication of the users. The data importer shall establish a mechanism that permits the identification of any user who tries to access the information system and the verification of his authorization. The data importer’s documentation shall establish the frequency, which under no circumstances shall be less than yearly, with which the passwords shall be changed. While in force, passwords shall be stored in an unintelligible way.
Identification and Authentication. User ID Requirements. The PSAP Manager shall require a unique logon ID to the Call Handling software system for every dispatcher (but not the PC Windows): This unique logon shall have a 4‐character prefix corresponding to the PSAP County Code and Agency (Appendix D). The leading 4‐character prefix may be followed by whatever remaining characters desired according to individual PSAP policy. The logon shall have maximum character length is 32 and use only alpha‐numeric characters (no special characters such as “!@^&” may be used). Password Requirements. PSAP shall include the following minimum standards for establishing passwords: Have a minimum length of eight (8) characters Not be a dictionary word or proper name (best practice) Not be the same as the User ID (best practice) Password shall not shared.
Identification and Authentication. Each user who shares data as part of the eHealth Exchange shall be uniquely identified and their identity verified prior to granting access to a Participant’s system.
Identification and Authentication. 11.1 In relation to access to Subscriber Data, either in electronic or hard copy, by the Supplier’s team, the Supplier shall:
