Incident Response Policy Sample Clauses

Incident Response Policy. Sema4 will implement an incident response policy that specifies how Sema4 will respond in the event of a Security Incident, as defined in the BAA, as amended by the Amendment.
Sample 1
AutoNDA by SimpleDocs
Incident Response Policy. Rubrik’s Incident Response Policy includes directions to be followed in the event of any action deemed a security incident. This policy includes the roles and responsibilities of personnel assigned to the security incident, the leadership responsibilities, command and control methods, and guidance on developing and implementing corrective action plans. STANDARD CONTRACTUAL CLAUSES (PROCESSORS) Name of the data exporting organisation: Address: Tel.: ; e-mail: Other information needed to identify the organisation …………………………………………………………… (the data exporter) And Name of the data importing organisation: Rubrik, Inc. Address: 0000 Xxxx Xxxxx Xxxx, Xxxx Xxxx, XX 00000, Xxxxxx Xxxxxx Tel.: +0 000 000 0000; e-mail: xxx@xxxxxx.xxx Other information needed to identify the organisation: ………………………………………………………………… (the data importer) each a “party”; together “the parties”, HAVE AGREED on the following Contractual Clauses (the Clauses) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1.
Sample 1
Incident Response Policy. Rubrik’s Incident Response Policy includes directions to be followed in the event of any action deemed a security incident. This policy includes the roles and responsibilities of personnel assigned to the security incident, the leadership responsibilities, command and control methods, and guidance on developing and implementing corrective action plans. APPENDIX 3 TO THE STANDARD CONTRACTUAL CLAUSES ADDITIONAL SAFEGUARDS ADDENDUM This Additional Safeguards Addendum (“Safeguards Addendum”) is in response to the Schrems II case and provides information regarding Rubrik’s data access and additional safeguards for Customer’s benefit. This Safeguards Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (“SCC”). Rubrik remains committed to securing a strong privacy posture and is actively reviewing global privacy trends and guidelines. Current guidance on the use of SCC as a transfer tool post-Schrems II, including the guidance outlined in the EDPB recommendation 01/2020, makes it clear that each data transfer must be reviewed on a case-by-case basis in order to evaluate the effectiveness of the transfer tool. Rubrik’s assessment of the use of SCC post-Schrems II takes into account the additional safeguards set forth in this Safegaurds Addendum. While Rubrik is a U.S. company and is subject to U.S. laws, to date Rubrik has not received a U.S. law enforcement request regarding any Customer Personal Data. In the event Rubrik receives such a request going forward, Rubrik will abide by the terms of this Safeguards Addendum and the DPA.
Sample 1
Incident Response Policy. Kronologic maintains an incident response policy with steps to follow in the case of a suspected breach which Kronologic regularly reviews and updates.
Sample 1

Related to Incident Response Policy

  • Incident Response Operator shall have a written incident response plan that reflects best practices and is consistent with industry standards and federal and state law for responding to a data breach, breach of security, privacy incident or unauthorized acquisition or use of any portion of Data, including PII, and agrees to provide LEA, upon request, an executive summary of the written incident response plan.

  • Client Responsibility For clarity, the parties agree that in reviewing the documents referred to in clause (b) above, Patheon’s role will be limited to verifying the accuracy of the description of the work undertaken or to be undertaken by Patheon. Subject to the foregoing, Patheon will not assume any responsibility for the accuracy of any application for receipt of an approval by a Regulatory Authority. The Client is solely responsible for the preparation and filing of the application for approval by the Regulatory Authority and any relevant costs will be borne by the Client.

  • Security Incident Response Upon becoming aware of a Security Incident, MailChimp shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.

  • Client Responsibilities You are responsible for (a) assessing each participants’ suitability for the Training, (b) enrollment in the appropriate course(s) and (c) your participants’ attendance at scheduled courses.

  • Student Responsibilities The Student Agrees to:

  • Payment Responsibility The payment obligations of each Participating Manufacturer pursuant to this Agreement shall be the several responsibility only of that Participating Manufacturer. The payment obligations of a Participating Manufacturer shall not be the obligation or responsibility of any Affiliate of such Participating Manufacturer. The payment obligations of a Participating Manufacturer shall not be the obligation or responsibility of any other Participating Manufacturer. Provided, however, that no provision of this Agreement shall waive or excuse liability under any state or federal fraudulent conveyance or fraudulent transfer law. Any Participating Manufacturer whose Market Share (or Relative Market Share) in any given year equals zero shall have no payment obligations under this Agreement in the succeeding year.

  • Management Responsibility No Limited Partner, as such, shall take part in the management of the business or transact any business for the Partnership.

  • Cost Responsibility Interconnection Customer shall be responsible for and shall pay upon demand all Costs associated with the interconnection of the Customer Facility as specified in the Tariff. These Costs may include, but are not limited to, an Attachment Facilities charge, a Local Upgrades charge, a Network Upgrades charge and other charges. A description of the facilities required and an estimate of the Costs of these facilities are included in Sections 3.0 and 4.0 of the Specifications to this ISA.

  • Joint Responsibility If the Seller determines that the Interface Problem is attributable partially to the design of a Warranted Part and partially to the design of any Supplier Part, the Seller will, if so requested by the Buyer, seek a solution to the Interface Problem through cooperative efforts of the Seller and any Supplier involved. The Seller will promptly advise the Buyer of such corrective action as may be proposed by the Seller and any such Supplier. Such proposal will be consistent with any then existing obligations of the Seller hereunder and of any such Supplier towards the Buyer. Such corrective action, unless reasonably rejected by the Buyer, will constitute full satisfaction of any claim the Buyer may have against either the Seller or any such Supplier with respect to such Interface Problem.

  • Customer’s Responsibility The policies in this document apply to the use of Data by Customers, Redistributors and their End Customers. Customers are responsible for compliance with this policy by all members of the Customer’s Group and by all persons to whom they distribute Data where authorised to do so. Turquoise recommends that Customers make this Schedule available to all Subscribers to their services having access to Data which is subject to Charges, reporting requirements or usage restrictions.

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