Avoiding and/or detecting undesirable behaviour [ Sample Clauses

Avoiding and/or detecting undesirable behaviour [ we will prohibit systems interact- ing when this would lead to a resource violation. Moreover, our project directly addresses the following pervasive important issue mentioned in the Work Programme:
AutoNDA by SimpleDocs

Related to Avoiding and/or detecting undesirable behaviour [

  • Safeguarding and Protecting Children and Vulnerable Adults The Supplier will comply with all applicable legislation and codes of practice, including, where applicable, all legislation and statutory guidance relevant to the safeguarding and protection of children and vulnerable adults and with the British Council’s Child Protection Policy, as notified to the Supplier and amended from time to time, which the Supplier acknowledges may include submitting to a check by the UK Disclosure & Barring Service (DBS) or the equivalent local service; in addition, the Supplier will ensure that, where it engages any other party to supply any of the Services under this Agreement, that that party will also comply with the same requirements as if they were a party to this Agreement.

  • Commingling of Resold Services with Unbundled Network Elements and Combinations of Unbundled Network Elements 6.7.1 To the extent it is Technically Feasible and pursuant to the terms of Section 9.1, CLEC may Commingle Telecommunications Services purchased on a resale basis with an Unbundled Network Element or combination of Unbundled Network Elements.

  • Technical and Organizational Measures The following sections define SAP’s current technical and organizational measures. SAP may change these at any time without notice so long as it maintains a comparable or better level of security. Individual measures may be replaced by new measures that serve the same purpose without diminishing the security level protecting Personal Data.

  • Aggravating and Mitigating Factors The penalties in this matter were determined in consideration of all relevant circumstances, including statutory factors as described in CARB’s Enforcement Policy. CARB considered whether the violator came into compliance quickly and cooperated with the investigation; the extent of harm to public health, safety and welfare; nature and persistence of the violation, including the magnitude of the excess emissions; compliance history; preventative efforts taken; innovative nature and the magnitude of the effort required to comply, and the accuracy, reproducibility, and repeatability of the available test methods; efforts to attain, or provide for, compliance prior to violation; action taken to mitigate the violation; financial burden to the violator; and voluntary disclosure. The penalties are set at levels sufficient to deter violations, to remove any economic benefit or unfair advantage from noncompliance, to obtain swift compliance, and the potential costs, risks, and uncertainty associated with litigation. Penalties in future cases might be smaller or larger depending on the unique circumstances of the case.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Technical and Organisational Measures 8.1 The information security regime implemented by the Provider shall be compliant with all relevant legislation, and shall conform to recognised Good Industry Practice.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

Time is Money Join Law Insider Premium to draft better contracts faster.