Cyber Security and Incident Reporting Sample Clauses

Cyber Security and Incident Reporting. 49.1. If DFARS 252.204 -7012 Safeguarding Covered Defense Information and Cyber Incident Reporting is applicable to the Subcontract issued by Buyer, Seller shall be responsible for the following in addition to those requirements specified in the above: 49.1.1. As defined therein, the Seller shall rapidly report cyber incidents to the DoD at https: //xxxxxx.xxx.xxx and the Buyer, providing the requisite information required under the DFARS clause.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Cyber Security and Incident Reporting. If DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting, is applicable to purchase orders issued by BUYER, SELLER shall be responsible for the following in addition to those requirements specified in the above DFARS clause: (a) As defined therein, the SELLER shall rapidly report Cyber incidents to the DoD at xxxx://xxxxxx.xxx.xxx and the BUYER, providing the requisite information required under the clause (b) Without exception, any Cyber incident the SELLER encounters shall be reported to BUYER as soon as practicable within 72 hours of discovery of incident. (c) In the event of a data breach, BUYER shall be afforded unfettered access to certain technical information (e.g., logs, packet flow information, etc.). This information will be required to satisfy BUYER’S customer information requests. (d) Failure to report or provide these notices will be considered a material breach of this Agreement In further support of this requirement, should BUYER elect to utilize supplier checklists, representations or certifications of compliance, outside supplier verification, and/or onsite security audits, SELLER shall support as required to meet the continuing needs of its customer.
Sample 1Sample 2See All (5)
Cyber Security and Incident Reporting. If DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting, is applicable to purchase orders issued by STS, Seller shall be responsible for the following in addition to those requirements specified in the above DFARS clause: (a) As defined therein, the Seller shall rapidly report Cyber incidents to the DoD at xxxx://xxxxxx.xxx.xxx and to STS, providing the requisite information required under the clause. (b) Without exception, any Cyber incident the Seller encounters shall be reported to STS within 24 hours. (c) In the event of a data breach, STS shall be afforded unfettered access to certain technical information (e.g., logs, packet flow information, etc.). This information will be required to satisfy STS’s customer information requests. (d) Failure to provide these notices will be considered a material breach of this Purchase Order. In further support of this requirement, should STS elect to utilize supplier checklists, representations or certifications of compliance, outside vendor verification, and/or onsite security audits, Seller shall support as required to meet the continuing needs of STS’s customer.
Sample 1Sample 2
Cyber Security and Incident Reporting. If DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting, is applicable to purchase orders issued by Buyer, Seller shall be responsible for the following in addition to those requirements specified in the above DFARS clause: (a) As defined therein, the Seller shall rapidly report Cyber incidents to the DoD at xxxx://xxxxxx.xxx.xxx and the Buyer, providing the requisite information required under the clause (b) Without exception, any Cyber incident the Seller encounters shall be reported to Buyer as soon as practicable within 72 hours of discovery of an incident (c) In the event of a data breach, Buyer shall be afforded unfettered access to certain technical information (e.g., logs, packet flow information, etc.). This information will be required to satisfy Buyer’s customer information requests.
Sample 1Sample 2

Related to Cyber Security and Incident Reporting

  • Security Incident Reporting A security incident occurs when CDA information assets are or reasonably believed to have been accessed, modified, destroyed, or disclosed without proper authorization, or are lost, or stolen. Subrecipient must comply with CDA’s security incident reporting procedures located at xxxxx://xxx.xxxxx.xx.xxx/ProgramsProviders/#Resources.

  • Foreign Assets/Account Reporting Information Italian residents who, during the fiscal year, hold investments abroad or foreign financial assets (e.g., cash, Shares and RSUs) which may generate income taxable in Italy are required to report such on their annual tax returns (UNICO Form, RW Schedule) or on a special form if no tax return is due. The same reporting obligations apply to Italian residents who, even if they do not directly hold investments abroad or foreign financial assets (e.g., cash, Shares and RSUs), are beneficial owners of the investment pursuant to Italian money laundering provisions.

  • Incident Reporting Transfer Agent will use commercially reasonable efforts to promptly furnish to Fund information that Transfer Agent has regarding the general circumstances and extent of such unauthorized access to the Fund Data.

  • Data Security and Unauthorized Data Release The Requester and Approved Users, including the Requester’s IT Director, acknowledge NIH’s expectation that they have reviewed and agree to manage the requested controlled-access dataset(s) and any Data Derivatives of controlled-access datasets according to NIH’s expectations set forth in the current NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy and the Requester’s IT security requirements and policies. The Requester, including the Requester’s IT Director, agree that the Requester’s IT security requirements and policies are sufficient to protect the confidentiality and integrity of the NIH controlled-access data entrusted to the Requester. If approved by NIH to use cloud computing for the proposed research project, as outlined in the Research and Cloud Computing Use Statements of the Data Access Request, the Requester acknowledges that the IT Director has reviewed and understands the cloud computing guidelines in the NIH Security Best Practices for Controlled-Access Data Subject to the NIH GDS Policy. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification, the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.

  • Implementation of and Reporting on the Project A. The Grantee shall implement and complete the Project in accordance with Exhibit A and with the plans and specifications contained in its Grant Application, which is on file with the State and is incorporated by reference. Modification of the Project shall require prior written approval of the State. B. The Grantee shall submit to the State written progress reports until the completion of the Project. These reports shall be submitted upon request by the State and shall contain such detail of progress or performance on the Project as is requested by the State.

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

  • Foreign Asset/Account Reporting; Exchange Controls Participant’s country may have certain foreign asset and/or account reporting requirements and/or exchange controls which may affect Participant’s ability to acquire or hold shares of Stock under the Plan or cash received from participating in the Plan (including from any dividends received or sale proceeds arising from the sale of shares of Stock) in a brokerage or bank account outside Participant’s country. Participant may be required to report such accounts, assets or transactions to the tax or other authorities in his or her country. Participant also may be required to repatriate sale proceeds or other funds received as a result of Participant’s participation in the Plan to his or her country through a designated bank or broker and/or within a certain time after receipt. Participant acknowledges that it is his or her responsibility to be compliant with such regulations, and Participant should consult his or her personal legal advisor for any details.

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

  • Reporting Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.

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