Loss of User IDs and Passwords. The Physician/Provider is responsible for the loss of any user IDs and passwords and any subsequent suspected or actual unauthorized disclosure or misuse of these IDs or passwords.
Loss of User IDs and Passwords Sample Clauses
Related to Loss of User IDs and Passwords
Usernames and Passwords 1. Staff will not share usernames and passwords with anyone, including supervisors and technical support staff.
Protection of Customer Data The Supplier shall not delete or remove any proprietary notices contained within or relating to the Customer Data. The Supplier shall not store, copy, disclose, or use the Customer Data except as necessary for the performance by the Supplier of its obligations under this Call Off Contract or as otherwise Approved by the Customer. To the extent that the Customer Data is held and/or Processed by the Supplier, the Supplier shall supply that Customer Data to the Customer as requested by the Customer and in the format (if any) specified by the Customer in the Call Off Order Form and, in any event, as specified by the Customer from time to time in writing. The Supplier shall take responsibility for preserving the integrity of Customer Data and preventing the corruption or loss of Customer Data. The Supplier shall perform secure back-ups of all Customer Data and shall ensure that up-to-date back-ups are stored off-site at an Approved location in accordance with any BCDR Plan or otherwise. The Supplier shall ensure that such back-ups are available to the Customer (or to such other person as the Customer may direct) at all times upon request and are delivered to the Customer at no less than six (6) Monthly intervals (or such other intervals as may be agreed in writing between the Parties). The Supplier shall ensure that any system on which the Supplier holds any Customer Data, including back-up data, is a secure system that complies with the Security Policy and the Security Management Plan (if any). If at any time the Supplier suspects or has reason to believe that the Customer Data is corrupted, lost or sufficiently degraded in any way for any reason, then the Supplier shall notify the Customer immediately and inform the Customer of the remedial action the Supplier proposes to take. If the Customer Data is corrupted, lost or sufficiently degraded as a result of a Default so as to be unusable, the Supplier may: require the Supplier (at the Supplier's expense) to restore or procure the restoration of Customer Data to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer, and the Supplier shall do so as soon as practicable but not later than five (5) Working Days from the date of receipt of the Customer’s notice; and/or itself restore or procure the restoration of Customer Data, and shall be repaid by the Supplier any reasonable expenses incurred in doing so to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer. Confidentiality
Antivirus software All workstations, laptops and other systems that process and/or store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY must have installed and actively use comprehensive anti-virus software solution with automatic updates scheduled at least daily.
Customer Materials 11.1. The Supplier including any of its employees, agents, consultants, contractors and any third party shall:
Customer Data 4.1 The Customer shall own all right, title and interest in and to all of the Customer Data and shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data.
Links to Third Party Websites In your use of the Service and/or the Company’s website, you may encounter various types of links that enable you to visit websites operated or owned by third parties (“Third Party Site”). These links are provided to you as a convenience and are not under the control or ownership of the Company. The inclusion of any link to a Third Party Site is not (i) an endorsement by the Company of the Third Party Site, (ii) an acknowledgement of any affiliation with its operators or owners, or (iii) a warranty of any type regarding any information or offer on the Third Party Site. Your use of any Third Party Site is governed by the various legal agreements and policies posted at that website.
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.
Access to Personal Information by Subcontractors Supplier agrees to require any subcontractors or agents to which it discloses Personal Information under this Agreement or under any SOW to provide reasonable assurance, evidenced by written contract, that they will comply with the same or substantially similar confidentiality, privacy and security obligations with respect to such Personal Information as apply to Supplier under this Agreement or any SOW. Supplier shall confirm in writing to DXC that such contract is in place as a condition to DXC’s approval of use of a subcontractor in connection with any SOW. Upon request of DXC, Supplier will provide to DXC a copy of the subcontract or an extract of the relevant clauses. Supplier shall ensure that any failure on the part of any subcontractor or agent to comply with the Supplier obligations under this Agreement or any SOW shall be grounds to promptly terminate such subcontractor or agent. If during the term of this Agreement or any SOW, DXC determines, in its exclusive discretion, that any Supplier subcontractor or agent cannot comply with the Supplier obligations under this Agreement or with any SOW, then DXC may terminate this Agreement in whole or in part (with respect to any SOW for which such subcontractor or agent is providing services), if not cured by Supplier within the time prescribed in the notice of such deficiency.
User Data In addition to any disclosures authorized by Section 24, You and Your Authorised Users consent and agree that the RIM Group of Companies may access, preserve, and disclose Your or Your Authorised Users' data, including personal information, contents of your communication or information about the use of Your BlackBerry Solution functionality and the services or software and hardware utilized in conjunction with Your BlackBerry Solution where available to RIM ("User Data"), to third parties, including foreign or domestic government entities, without providing notice to You or Your Authorized Users under the laws of countries where the RIM Group of Companies and its service providers, other partners and affiliates are located in order to: (i) comply with legal process or enforceable governmental request, or as otherwise required by law; (ii) cooperate with third parties in investigating acts in violation of this Agreement; or (iii) cooperate with system administrators at Internet service providers, networks or computing facilities in order to enforce this Agreement. You warrant that You have obtained all consents necessary under applicable law from Your Authorised Users to disclose User Data to the RIM Group of Companies and for the RIM Group of Companies to collect, use, process, transmit, and/or disclose such User Data as described above.
Background Data The Disclosing Party's Background Data, if any, will be identified in a separate technical document.
