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.
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.
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: Physical security of data Access control Personal access card and/or code is required to access the facilities where the data is located.
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.
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.
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.
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: Encryption of personal data 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. Anonymisation/pseudonymisation of test data 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. Accessibility 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. Logging The Data Processor must ensure that event logging for r...
AutoNDA by SimpleDocs

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

  • 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 1. 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 Local Line’s data from BellSouth’s data, the following shall apply:

  • 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 Month, Assuming Institution shall provide Receiver:

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

  • Interconnection Service Interconnection Service allows the Interconnection Customer to connect the Large Generating Facility to the Participating TO’s Transmission System and be eligible to deliver the Large Generating Facility’s output using the available capacity of the CAISO Controlled Grid. To the extent the Interconnection Customer wants to receive Interconnection Service, the Participating TO shall construct facilities identified in Appendices A and C that the Participating TO is responsible to construct. Interconnection Service does not necessarily provide the Interconnection Customer with the capability to physically deliver the output of its Large Generating Facility to any particular load on the CAISO Controlled Grid without incurring congestion costs. In the event of transmission constraints on the CAISO Controlled Grid, the Interconnection Customer's Large Generating Facility shall be subject to the applicable congestion management procedures in the CAISO Tariff in the same manner as all other resources.

  • Points of Interconnection and Trunk Types 2.1 Point(s) of Interconnection.

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