Additional measures for Data Centers Sample Clauses

Additional measures for Data Centers. All Data Centers adhere to strict security procedures enforced by guards, surveillance cameras, motion detectors, access control mechanisms and other measures to prevent equipment and Data Center facilities from being compromised. Only authorized representatives have access to systems and infrastructure within the Data Center facilities. To protect proper functionality, physical security equipment (e.g., motion sensors, cameras, etc.) undergo maintenance on a regular basis. • SAP and all third-party Data Center providers log the names and times of authorized personnel entering SAP’s private areas within the Data Centers.
Sample 1Sample 2Sample 3See All (73)
Additional measures for Data Centers. All Data Centers adhere to strict security procedures enforced by guards, surveillance cameras, motion detectors, access control mechanisms and other measures to prevent equipment and Data Center facilities from being compromised. Only authorized representatives have access to systems and infrastructure within the Data Center facilities. To protect proper functionality, physical security equipment (e.g., motion sensors, cameras, etc.) undergo maintenance on a regular basis.
Sample 1Sample 2Sample 3See All (7)
Additional measures for Data Centers. All Data Centers adhere to strict security procedures enforced by guards, surveillance cameras, motion detectors, access control mechanisms and other measures to prevent equipment and Data Center facilities from being compromised. Only authorized representatives have access to systems and infrastructure within the Data Center facilities. To protect proper functionality, physical security equipment (e.g., motion sensors, cameras, etc.) undergo maintenance on a regular basis. RELISH and all third-party Data Center providers log the names and times of authorized personnel entering RELISH’s private areas within the Data Centers. System Access Control. Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the RELISH Security Policy. All personnel access RELISH’s systems with a unique identifier (user ID). RELISH has policies designed to provide that no rights are granted without authorization and in case personnel leaves the company their access rights are revoked. RELISH has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. The company network is protected from the public network by firewalls. RELISH uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. Security patch management processes to deploy relevant security updates on a regular and periodic basis. Full remote access to RELISH’s corporate network and critical infrastructure is protected by authentication. Data Access Control. As part of the RELISH Security Policy, Personal Data requires at least the same protection level as “confidential” information according to the RELISH Information Classification standard. Access to Personal Data is granted on a need-to-know basis. Personnel have access to the information that they require in order to fulfill their duty. RELISH uses authori...
Sample 1
Additional measures for Data Centers. All Data Centers adhere to strict security procedures enforced by guards, surveillance cameras, motion detectors, access control mechanisms and other measures to prevent equipment and Data Center facilities from being compromised. Only authorized representatives have access to systems and infrastructure within the Data Center facilities. To protect proper functionality, physical security equipment (e.g., motion sensors, cameras, etc.) undergo maintenance on a regular basis. RELISH and all third-party Data Center providers log the names and times of authorized personnel entering RELISH’s private areas within the Data Centers. System Access Control. Data processing systems used to provide the Cloud Service must be prevented from being used without authorization.
Sample 1

Related to Additional measures for Data Centers

  • Provisional Measures 1. The judicial authorities shall have the authority to order prompt and effective provisional measures: (a) to prevent an infringement of any intellectual property right from occurring, and in particular to prevent the entry into the channels of commerce in their jurisdiction of goods, including imported goods immediately after customs clearance; (b) to preserve relevant evidence in regard to the alleged infringement. 2. The judicial authorities shall have the authority to adopt provisional measures inaudita altera parte where appropriate, in particular where any delay is likely to cause irreparable harm to the right holder, or where there is a demonstrable risk of evidence being destroyed. 3. The judicial authorities shall have the authority to require the applicant to provide any reasonably available evidence in order to satisfy themselves with a sufficient degree of certainty that the applicant is the right holder and that the applicant’s right is being infringed or that such infringement is imminent, and to order the applicant to provide a security or equivalent assurance sufficient to protect the defendant and to prevent abuse. 4. Where provisional measures have been adopted inaudita altera parte, the parties affected shall be given notice, without delay after the execution of the measures at the latest. A review, including a right to be heard, shall take place upon request of the defendant with a view to deciding, within a reasonable period after the notification of the measures, whether these measures shall be modified, revoked or confirmed. 5. The applicant may be required to supply other information necessary for the identification of the goods concerned by the authority that will execute the provisional measures. 6. Without prejudice to paragraph 4, provisional measures taken on the basis of paragraphs 1 and 2 shall, upon request by the defendant, be revoked or otherwise cease to have effect, if proceedings leading to a decision on the merits of the case are not initiated within a reasonable period, to be determined by the judicial authority ordering the measures where a Member's law so permits or, in the absence of such a determination, not to exceed 20 working days or 31 calendar days, whichever is the longer. 7. Where the provisional measures are revoked or where they lapse due to any act or omission by the applicant, or where it is subsequently found that there has been no infringement or threat of infringement of an intellectual property right, the judicial authorities shall have the authority to order the applicant, upon request of the defendant, to provide the defendant appropriate compensation for any injury caused by these measures. 8. To the extent that any provisional measure can be ordered as a result of administrative procedures, such procedures shall conform to principles equivalent in substance to those set forth in this Section. SECTION 4: SPECIAL REQUIREMENTS RELATED TO BORDER MEASURES12

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant- assisted project in accordance with Section 287.057, Florida Statutes.

  • Non-tariff Measures 1. A Party shall not adopt or maintain any non-tariff measures on the importation of any good of the other Party or on the exportation of any good destined for the territory of the other Party except in accordance with its WTO rights and obligations or in accordance with other provisions of this Agreement. 2. Each Party shall ensure its non-tariff measures permitted in paragraph 1 are not prepared, adopted or applied with a view to, or with the effect of, creating unnecessary obstacles to trade between the Parties.

  • 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.

  • Technical and Organisational Measures The Supplier shall, taking into account the state of technical development and the nature of Processing, implement and maintain appropriate technical and organisational measures to protect the Personal Data against unauthorised or unlawful Processing, destruction or accidental loss, alteration, or unauthorised disclosure of the Personal Data.

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Connecting Transmission Owner’s Scope of Work and Responsibilities The Connecting Transmission Owner will design, construct, own, operate and maintain all Connecting Transmission Owner’s Interconnection Facilities, except as otherwise stated above and in the Project Specific Specifications. The Connecting Transmission Owner will complete all engineering reviews, field verifications and witness testing, etc. in accordance with the ESBs and the Project Specific Specifications. Connecting Transmission Owner shall provide the revenue metering CT/PT units and meter socket enclosure. The Connecting Transmission Owner shall: • provide, run, and wire both ends of the color-coded cable for the revenue metering instrument transformer secondary wiring; • perform all terminations; and • supply and install the meter. The revenue meter may require a communications link to the RTU. The Connecting Transmission Owner will specify and run those communications cables. The Connecting Transmission Owner shall complete all wiring, testing and commissioning of the RTU.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Approved Services; Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at xxxx://xxx.xxxxx.xxx/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.