Processing security Sample Clauses

Processing security. The processor is obliged to take all necessary measures to guarantee security of processing. The person responsible is entitled to the Processors to issue instructions in this regard at any time. These instructions are to be implemented immediately by the processor, and to other (sub) processors of the processor, that they are permitted to use.
Sample 1Sample 2
AutoNDA by SimpleDocs
Processing security. 4.1 Plecto shall implement all measures required by Article 32 of the Data Protection Regulation, which shall include, appropriate technical and organizational measures, to ensure a level of safety fitting these risks.
Sample 1Sample 2
Processing security. The Data Processor will initiate the level of security and all measures required in accordance with the Data Processing Agreement and the instructions of the Data Controller, cf. Appendix C.1, any data security requirements that are specified in the Main Agreement and its appendices, and oth- erwise in accordance with the General Data Protection Regulation, Article 32. Given this, and taking into account the current technical level, implementation costs and the na- ture, scope, context and purpose of the processing, as well as the risks of varying probability and severity to the rights and freedoms of natural persons, the Data Processor will conduct the appro- priate technical and organisational measures to ensure a level of security that is appropriate for these risks. What constitutes appropriate technical and organisational measures must also be assessed in rela- tion to the specific system, the purpose of the processing and the type of personal data. In the assessment of the appropriate level of security, consideration will also be given to the risks posed by the processing, namely in the event of accidental or illegal destruction, loss, alteration, unauthorised disclosure or access to personal data that has been transmitted, stored or otherwise processed. The above obligation implies that the Data Processor must conduct a risk assessment for the data subjects that are linked to the ongoing risk assessment of the Data Processor in accordance with ISO 27001 and then implement measures to address identified risks. Depending on what is relevant and thus established in the instructions and any data security requirements as specified in the Main Agreement and its appendices, this may include the following measures: The Data Processor shall develop guidelines for securing external communication lines and must take measures to ensure that those who are unauthorised cannot access data through these con- nections. The Data Controller is responsible for designing the test data, including anonymisation or pseu- donymisation of this data. The Data Processor implements the test data provided by the Data Controller in the relevant systems and solutions. The Data Processor must be able to restore the availability and access to personal data in a timely manner in the event of an accidental physical or technical incident. The Data Processor must ensure that event logging for recording user activity, exceptions, errors and information security events is stored and revie...
Sample 1
Processing security. In the processing, the Processor has taken suitable technical and organisational security measures, with due account of the state of the art, the costs of implementation and the nature, scope, context and purposes of the personal data, as well as risks of varying likelihood and severity to the rights and freedoms of natural persons. Such security measures shall protect the data provided against accidental or unlawful destruction, loss or alteration and against unauthorised disclosure, abuse or other processing in violation of the provisions of the Personal Data Protection Act or, after the General Data Protection Regulation enters into force, the General Data Protection Regulation. The Parties agree that the implemented measures are sufficient on the date of the signing of the Agreement. The Processor shall thereafter regularly assess the adequacy of the implemented measures. Changes to the security level attributable to changes in the Controller’s circumstances shall be agreed separately. When the Controller has informed the Processor in writing that the Controller is subject to the Security Order (Order no. 528 of 15/06/2000 with subsequent amendments), the Processor shall also comply with the Order with regard to the processing of personal data on behalf of the Controller, for as long as the Order is applicable.
Sample 1
Processing security. 4.1 The Contractor shall implement appropriate technical and organizational measures required to ensure a level of protection of the Customer Data commensurate to the risk, taking into account the state of the art, the cost of implementation and, to the extent known to the Contractor, the nature, scope, circumstances and purposes of the processing of the Customer Data and the varying likelihood and severity of the risk to the rights and freedoms of the data subjects. 4.2 The Contractor shall, in particular, take the technical and organizational measures ("XXX") specified at xxxxx://xxxxx.xxxxx.xxx/ukpremium#xxx to this DPA before the start of the processing of the Customer Data and maintain them during the term of the Main Agreement and ensure that the processing of Customer Data is carried out in accordance with these measures. 4.3 It shall be incumbent upon the Customer to review the technical and organizational measures taken by the Contractor, particularly to review whether these measures are also sufficient with regard to circumstances of the data processing that are not known to the Contractor. 4.4 Since the technical and organizational measures are subject to technical progress, the Contractor shall be entitled and obliged to implement alternative, adequate measures in order not to fall below the security level of the specified XXX. If the Contractor makes significant changes to the specified XXX, then it shall inform the Customer thereof in advance.
Sample 1
Processing security. The Data Processor has partnered with sub-processors to ensure secure and robust data processing. The data will be physically placed in external data centres or in the Data Processor’s own server rooms. The Data Processor continuously receives statements from sub-processors that ensure that the sub-processors meet the Data Processor’s policies in the mentioned areas. The Data Processor’s policies with regard to data security relate to: Personal access card and/or code is required to access the facilities where the data is located.
Sample 1
Processing security. 6.1 The Contractor will take all necessary and appropriate technical and organizational measures in accordance with Article 32 of the GDPR, to ensure a sufficient level of protection for Client Data. This takes into account the state of technology, the implementation costs and the nature, scope, circumstances and purposes of the processing of Client Data, as well as the varying likelihood and severity of the risk to the rights and freedoms of the data subjects. 6.2 The Contractor is permitted to change or adapt technical and organizational measures during the term of the contract as long as they continue to meet the legal requirements.
Sample 1
AutoNDA by SimpleDocs
Processing security. 4.1 Fenerum shall implement all measures required by Article 32 of the Data Protection Regulation, which shall include, appropriate technical and organizational measures, to ensure a level of safety fitting these risks.
Sample 1

Related to Processing security

  • Interconnection Customer Payments Not Taxable The Parties intend that all payments or property transfers made by the Interconnection Customer to the Participating TO for the installation of the Participating TO's Interconnection Facilities and the Network Upgrades shall be non-taxable, either as contributions to capital, or as a refundable advance, in accordance with the Internal Revenue Code and any applicable state income tax laws and shall not be taxable as contributions in aid of construction or otherwise under the Internal Revenue Code and any applicable state income tax laws.

  • Interconnection Customer (1) Interconnection Customer shall construct and, unless otherwise indicated, shall own, the following Interconnection Facilities: None (2) In the event that, in accordance with the Interconnection Construction Service Agreement, Interconnection Customer has exercised the Option to Build, it is hereby permitted to build in accordance with and subject to the conditions and limitations set forth in that Section, the following portions of the Transmission Owner Interconnection Facilities which constitute or are part of the Customer Facility: None Ownership of the facilities built by Interconnection Customer pursuant to the Option to Build shall be as provided in the Interconnection Construction Service Agreement.

  • Interconnection Customer Obligations The Interconnection Customer shall maintain the Large Generating Facility and the Interconnection Customer’s Interconnection Facilities in a safe and reliable manner and in accordance with this LGIA.

  • Subprocessing The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement.

  • Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Lightyear’s data from BellSouth’s data, the following shall apply: (1) Lightyear will accept responsibility for telecommunications services billed by BellSouth for its B&C Customers for Lightyear’s End User accounts which are resident in LIDB pursuant to this Agreement. Lightyear authorizes BellSouth to place such charges on Lightyear’s xxxx from BellSouth and shall pay all such charges, including, but are not limited to, collect and third number calls. (2) Charges for such services shall appear on a separate BellSouth xxxx xxxx identified with the name of the B&C Customers for which BellSouth is billing the charge. (3) Lightyear shall have the responsibility to render a billing statement to its End Users for these charges, but Lightyear shall pay BellSouth for the charges billed regardless of whether Lightyear collects from Lightyear’s End Users. (4) BellSouth shall have no obligation to become involved in any disputes between Lightyear and B&C Customers. BellSouth will not issue adjustments for charges billed on behalf of any B&C Customer to Lightyear. It shall be the responsibility of Lightyear and the B&C Customers to negotiate and arrange for any appropriate adjustments.

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:

  • Processing of Customer Personal Data 3.1 UKG will: 3.1.1 comply with all applicable Data Protection Laws in the Processing of Customer Personal Data; and 3.1.2 not Process Customer Personal Data other than for the purpose, and in accordance with, the relevant Customer’s instructions as documented in the Agreement and this DPA, unless Processing is required by the Data Protection Laws to which the relevant UKG Processor is subject, in which case UKG to the extent permitted by the Data Protection Laws, will inform Customer of that legal requirement before the Processing of that Customer Personal Data. 3.2 Customer hereby: 3.2.1 instructs UKG (and authorizes UKG to instruct each Subprocessor) to: (a) Process Customer Personal Data; and (b) in particular, transfer Customer Personal Data to any country or territory subject to the provisions of this DPA, in each case as reasonably necessary for the provision of the Services and consistent with the Agreement. 3.2.2 warrants and represents that it is and will at all relevant times remain duly and effectively authorized to give the instructions set out in Section 3.2.1 on behalf of each relevant Customer Affiliate; and 3.2.3 warrants and represents that it has all necessary rights in relation to the Customer Personal Data and/or has collected all necessary consents from Data Subjects to Process Customer Personal Data to the extent required by Applicable Law. 3.3 Schedule 1 to this DPA sets out certain information regarding UKG’s Processing of Customer Personal Data as required by Article 28(3) of the GDPR (and equivalent requirements of other Data Protection Laws).

  • Network Security The AWS Network will be electronically accessible to employees, contractors and any other person as necessary to provide the Services. AWS will maintain access controls and policies to manage what access is allowed to the AWS Network from each network connection and user, including the use of firewalls or functionally equivalent technology and authentication controls. AWS will maintain corrective action and incident response plans to respond to potential security threats.

  • Interconnection Customer Compensation If the CAISO requests or directs the Interconnection Customer to provide a service pursuant to Articles 9.6.3 (Payment for Reactive Power) or 13.5.1 of this LGIA, the CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff.

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5. 1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

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