Security Rules (“Security Rules”) Sample Clauses

Security Rules (“Security Rules”). (a) Users are prohibited from violating or attempting to violate the security of the System, including, without limitation: (i) accessing data not intended for such User or logging into a server or account which the User is not authorized to access; (ii) attempting to probe, scan or test the vulnerability of a system or network or to breach security or authentication measures without proper authorization; (iii) sending unsolicited e-mail, including promotions and/or advertising of products or services; (iv) forging any TCP/IP packet header or any part of the header information; and (v) using any “page scrape,” “robot,” “spider,” or other automatic device, program, script, algorithm or methodology, or any similar or equivalent manual process, to access, acquire, copy, or monitor any portion of the System or any information contained therein.
AutoNDA by SimpleDocs

Related to Security Rules (“Security Rules”)

  • Security Rule “Security Rule” shall mean the Standards for the Protection of Electronic Protected Health Information at 45 CFR Part 160 and Part 164, Subparts A and C.

  • Electronic PHI Security Rule Obligations 5.1 With respect to Electronic PHI, Business Associate shall:

  • Data Security Requirements A. Data Transport. When transporting Confidential Information electronically, including via email, the data will be protected by:

  • Security Rule Obligations The following provisions of this section apply to the extent that Business Associate creates, receives, maintains or transmits Electronic PHI on behalf of Covered Entity.

  • Security Requirements 11.1 The Supplier shall comply, and shall procure the compliance of the Suppliers Personnel, with the Security Policy and the Security Plan and the Supplier shall ensure that the Security Plan produced by the Supplier fully complies with the Security Policy.

  • E1 Data Protection Act E1.1 For the purposes of this Clause E1, the terms “Data Controller”, “Data Processor”, “Data Subject”, “Personal Data”, “Process” and “Processing shall have the meaning prescribed under the DPA.

  • General Data Protection Regulation 10.1 Protecting your personal information is incredibly important to Excalibur. Our privacy policy which sets out how we do this is available here: xxxxx://xxx.xxxxxxxxxxxxxx.xx.xx/gdpr-policy/. This policy explains the information that we hold, how we use it, and how long we keep it for. Please take a few minutes to read it.

  • Security of Access Code You may use one (1) or more access codes with your electronic fund transfers. The access codes issued to you are for your security purposes. Any access codes issued to you are confidential and should not be disclosed to third parties or recorded on or with the card. You are responsible for safekeeping your access codes. You agree not to disclose or otherwise make your access codes available to anyone not authorized to sign on your accounts. If you authorize anyone to use your access codes, that authority shall continue until you specifically revoke such authority by notifying the Credit Union. You understand that any joint owner you authorize to use an access code may withdraw or transfer funds from any of your accounts. If you fail to maintain the security of these access codes and the Credit Union suffers a loss, we may terminate your EFT services immediately.

  • Data Protection Legislation the UK Data Protection Legislation and any other European Union legislation relating to personal data and all other legislation and regulatory requirements in force from time to time which apply to a party relating to the use of Personal Data (including, without limitation, the privacy of electronic communications) and the guidance and codes of practice issued by the Information Commissioner or relevant government department in relation to such legislation.

  • Information Security Requirements In cases where the State is not permitted to manage/modify the automation equipment (server/computer/other) that controls testing or monitoring devices, the Contractor agrees to update and provide patches for the automation equipment and any installed operating systems or applications on a quarterly basis (at minimum). The Contractor will submit a report to the State of updates installed within 30 days of the installation as well as a Plan of Actions and Milestones (POA&M) to remediate any vulnerabilities ranging from Critical to Low. The contractor will provide an upgrade path or compensatory security controls for any operating systems and applications listed as beyond “end-of-life” or EOL, within 90 days of the EOL and complete the EOL system’s upgrade within 90 days of the approved plan.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!