Password change) Sample Clauses

The Password Change clause establishes the requirements and procedures for updating user passwords within a system or service. Typically, it outlines when and how users must change their passwords, such as after a security incident or at regular intervals, and may specify password complexity standards. This clause helps maintain account security by reducing the risk of unauthorized access due to compromised or outdated credentials.
POPULAR SAMPLE Copied 2 times
Password change). The Principal should use the automated service equipment to make password changes. There are no restrictions to the maximum number of changes.
Password change). Any System Administrator(s) will be required to change the initial passwords the first time they use their IDs to login into the System. It is the System Administrator’s responsibility to understand the security capabilities built into the Service and to assign and, as appropriate to your business and security needs, to restrict access to the various applications only to those employees who have a need to know, keeping in mind the importance of separation of duties as an important way of protecting You. The System Administrator also maintains the responsibility of setting certain limits related to dollar or volume thresholds for authorized users.
Password change). 4.4.1 Passwords should only be changed when there is reason to believe a password has been compromised. 4.4.2 Password cracking or guessing may be performed on a periodic or random basis by EdClub. If a password is guessed or cracked during one of these scans, the User will be required to change it to be in compliance with the Password Construction Guidelines.
Password change). 一、立約人如欲變更密碼者,得利用自動化服務設備自行更改密碼,其次數不受限制。 The Principal should use the automated service equipment to make password changes. There are no restrictions to the maximum number of changes. 二、立約人除妥善保管金融卡外,應自行牢記密碼並絕對保密,貴行亦不得以任何方式洩露立約人自行設定之密碼,否則應由有疏失之一方各負其責。立約人領卡後未予變更密碼,貴行認為安全有慮時,得逕為終止金融卡之啟用,但立約人得再為啟用之申請。 In addition to keeping proper custody of the ATM card, the Principal is also responsible for memorizing and maintaining secrecy of the password. The Bank can not reveal the Principal's passwords in any way. The two parties shall be responsible for the consequences of their own faults. If the Principal does not make a password change after collecting the ATM card, the Bank may de-activate the card on the grounds of security concerns. However, the Principal is still allowed to re-activate the card on a later date.
Password change). A Participant shall require that Registrants’ passwords be reconfirmed or changed every 180 days.
Password change). When a user attempts to update his password into a new one, he needs to execute the following steps: Step 1: The user initially inserts the smart card into the card reader and inputs his identity IDi and old password PWi. Next, the card reader computes h(h(IDi), h(PWi, r)) and checks whether it is equal to Ai. If it holds, the user is considered as a legal one. And thus, the card reader asks the user to key a new password. Step 2: After keying the new password, the card reader computes Ai∗ = h(h(IDi), h(PWi, r)), Bi∗ = Bi ⊕ h(PWi, r) ⊕ h(PWi∗, r) and Ci∗ = Ci ⊕ h(h(IDi) ⊕ h(PWi, r)) ⊕ h(h(IDi) ⊕ h(PWi∗, r)). The card reader replaces {Ai, Bi, Ci} with {Ai∗, Bi∗, Ci∗ }.
Password change). Whenever the Ui wants to change password, she/he executes password change process shown in Figure 6. The sequence of steps followed by ▇▇ is described as: Step 1: initially, Ui forwards IDi and pwi onto OBUi Step 2: OBUi , calculates ai=h(pwi) ⨁ bi and check di equals to h(IDi||ai||pwi), if so, Ui is requested to provide the new password(pw∗). Afterwards OBUi recalculates bi as h( pwi ) ⨁ bi ⨁ h(pw∗) and di ==h( IDi||ai||pw∗ ).otherwise, the request will be rejected. (1) IDi, pwi (2). 𝑎𝑖=h(𝑝𝑤𝑖) ⨁ 𝑏𝑖 if di==h(IDi||ai||pwi) Get pw∗ from Ui i Update bi=h(pwi) ⨁ bi ⨁ h(pw∗) else reject Ui OBUi
Password change). Receiving Party shall require Registrants to change the password that allows Registrant to access the VOW Data every 90 days.
Password change). All system-level passwords (for example, root, enable, admin, application administration accounts, and so on) must be changed on at least a quarterly basis.