Security Event Data Sample Clauses

Security Event Data. Secureworks will process Security Event Data as part of its provision of Services. Customer acknowledges that Secureworks may also process Security Event Data in order to develop, enhance and/or improve its security services and the products and services it offers and provides to customers. Secureworks shall be the controller in respect of any personal data in the Security Event Data and, for the duration of its processing of such Security Event Data, Secureworks shall (i) comply with applicable Privacy Laws and (ii) safeguard such Security Event Data with security measures that are no less protective than those set out in this DPA. Restrictions on the disclosure and transfer of Personal Data in this DPA shall not apply in connection with Secureworks’ processing of the Security Event Data for the purposes described in this clause, however, Secureworks shall not disclose any Security Event Data that is traceable to Customer to any third parties (other than Affiliates and Subprocessors) unless permitted under the MSA and/or this DPA, or the disclosure is required in order to comply with applicable law or legal process. Secureworks shall not be required to return or delete Security Event Data upon termination of the Services (for any reason). Customer shall ensure its personnel and any other data subjects whose personal data is processed by Secureworks in connection with the Services are appropriately notified of the fact their personal data may be processed in connection with the development, enhancement and/or provision of Secureworks’ products or services as described in this clause. If Customer is compelled by a legally binding order (e.g. of a court or regulatory authority of competent jurisdiction) to have the Security Event Data deleted, then Secureworks agrees, as appropriate, to anonymise, pseudonymise or delete the Security Event Data that is the subject of the binding order as soon as practicable.
AutoNDA by SimpleDocs
Security Event Data. MSSP will notify Customers (including as part of each Customer Agreement) about Secureworks’ use of Security Event Data as described in this clause 7. Secureworks will process Security Event Data as part of its provision of SaaS Solutions. Customer acknowledges that Security Event Data may also be processed in order to develop, enhance and/or improve security services and the products and services offered and provided to customers. Secureworks shall be the controller in respect of any personal data (as defined in the GDPR) in the Security Event Data and, as such, is responsible for processing the Security Event Data in accordance with applicable Privacy Laws. Restrictions on the disclosure and transfer of Personal Data in this DP Schedule shall not apply in connection withthe processing of Security Event Data for the purposes described in this clause, PROVIDED THAT Secureworks shall not disclose any Security Event Data that is traceable to a Customer to any third parties (other than Affiliates and Subprocessors) unless permitted under this DP Schedule and/or the MSSP Addendum, or the disclosure is required in order to comply with applicable law or legal process. Secureworks shall not be required by MSSP or any Customer to return or delete Security Event Data upon termination of the SaaS Solutions (for any reason).’ If Customer is compelled by a legally binding order (e.g. of a court or regulatory authority of competent jurisdiction) to have the Security Event Data deleted, then Secureworks agrees, as legally required, to anonymize or delete the Security Event Data that is the subject of the binding order as soon as practicable following receipt of a certified copy of such binding order.

Related to Security Event Data

  • Authority Event of Default Any of the following events shall constitute an event of default by the Authority ("Authority Event of Default”), when not caused by a Developer Event of Default:

  • Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include:

  • Default Events (a) Any material breach of the Funding Agreement by the Recipient, including those set out below, will be an event of default (“Default Event”):

  • Additional Event of Suspension Section 4.01. Pursuant to Section 6.02 (l) of the General Conditions, the following additional event is specified, namely, that a situation has arisen which shall make it improbable that the Program, or a significant part thereof, will be carried out.

  • Protection of Site from encroachments During the Concession Period, the Concessionaire shall protect the Site from any and all occupations, encroachments or Encumbrances, and shall not place or create nor permit any Contractor or other person claiming through or under the Concessionaire to place or create any Encumbrance or security interest over all or any part of the Site or the Project Assets, or on any rights of the Concessionaire therein or under this Agreement, save and except as otherwise expressly set forth in this Agreement.

  • U.S. Government Restricted Rights The Software is commercial computer software subject to RESTRICTED RIGHTS. In accordance with 48 CFR 12.212 (Computer software) or DFARS 227.7202 (Commercial computer software and commercial computer software documentation), as applicable, the use, duplication, and disclosure of the Software by the United States of America, its agencies or instrumentalities is subject to the restrictions set forth in this Agreement.

  • Audit Rights Periods 25.4.1 Audit Rights Period for Construction-Related Accounts and Records. Accounts and records related to the design, engineering, procurement, and construction of Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades shall be subject to audit for a period of twenty-four months following Connecting Transmission Owner’s issuance of a final invoice in accordance with Article 12.2 of this Agreement.

  • Student Data Property of LEA All Student Data transmitted to the Provider pursuant to the Service Agreement is and will continue to be the property of and under the control of the LEA. The Provider further acknowledges and agrees that all copies of such Student Data transmitted to the Provider, including any modifications or additions or any portion thereof from any source, are subject to the provisions of this DPA in the same manner as the original Student Data. The Parties agree that as between them, all rights, including all intellectual property rights in and to Student Data contemplated per the Service Agreement, shall remain the exclusive property of the LEA. For the purposes of FERPA, the Provider shall be considered a School Official, under the control and direction of the LEA as it pertains to the use of Student Data, notwithstanding the above.

  • Developer Event of Default Any of the following events shall constitute an event of default by the Developer ("Developer Event of Default") unless such event has occurred as a result of a Force Majeure Event or the Authority Event of Default or any governmental action for reasons other than any breach, default or lapse on the part of the Developer:

  • Security Violations and Accounts Updates Grantee will adhere to the Confidentiality Article requirements and HHS Data Usage Agreement of this contract and immediately contact System Agency if a security violation is detected, or if Grantee has any reason to suspect that the security or integrity of the CMBHS data has been or may be compromised in any way.

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