Security Monitoring and Incident Response Sample Clauses

Security Monitoring and Incident Response. Company and Seller shall collaborate on security monitoring and incident response, define points of contact on both sides, establish monitoring and response procedures, set escalation thresholds, and conduct training (i.e., aligned with the intent of NERC CIP-008-5). Seller shall, at the request of Company or, in the absence of any request from Company, at least quarterly, provide Company with a report of the incidents that it has identified and describe measures taken to resolve or mitigate. In the event that Seller discovers or is notified of a breach, potential breach of security, or security incident at Seller's Facility or of Seller's systems, Seller shall immediately (aa) notify Company of such potential, suspected or actual security breach, whether or not such breach has compromised any of Company's confidential information; (bb) investigate and promptly remediate the effects of the breach, whether or not the breach was caused by Seller; (cc) cooperate with Company with respect to any such breach or unauthorized access or use; (dd) comply with all applicable privacy and data protection laws governing Company's or any other individual's or entity's data; and (ee) to the extent such breach was caused by Seller, provide Company with reasonable assurances satisfactory to Company that such breach, potential breach, or security incident shall not recur. Seller shall provide documentation to Company evidencing the length and impact of the breach. Any remediation of any such breach will be at Seller's sole expense. If malicious software or unauthorized code is found to have been introduced into the Environment, Seller will promptly notify Company. Seller shall take immediate action to eliminate and remediate the effects of the Malware, at Seller's expense. Seller shall not modify or otherwise take corrective action with respect to the Company Systems except at Company's request. Seller shall promptly report to Company the nature and status of all efforts to isolate and eliminate malicious software or unauthorized code.
Sample 1
AutoNDA by SimpleDocs

Related to Security Monitoring and Incident Response

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

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

  • 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 school provided Chromebook for the student is an important learning tool to be used for educational purposes. In order to use the device each day, the student must be willing to accept the following responsibilities: ● I understand that district officials have the ability to monitor my use of the device AT ALL TIMES IN AND OUT OF SCHOOL and that communications, files, internet search activities, and any other actions using the device are not considered to be private. Note: RCCSD does not have the ability to and will not remotely operate the camera on the device. However, students can cover it when not in use to ensure others are not. ● I understand that the device assigned to me is on loan from Red Clay Consolidated School District. All accounts, programs, and files are subject to inspection at any time without notice. ● I will be responsible for ALL damage or loss of the device due to NEGLECT OR ABUSE including dropping it, getting it wet, and spills of food or drink. ● I will not try to repair my Chromebook. ● At ALL times when using my Chromebook, I will follow the Acceptable Use, Internet Safety Policy, and Student Code of Conduct, and related policies adopted by the Board of Education, and abide by all local, state, and federal laws. ● I will talk with my parent/guardian about their ground rules for going online when not at school. ● I will notify the school principal and my parents of any damage to the device as soon as possible. ● I will charge the Chromebook battery each night and will bring my Chromebook to school every day or be prepared for remote learning. ● I will keep my Chromebook clean. ● I will not lend my device to anyone. This includes family members and friends. Note: I could be held responsible for any inappropriate content on the District issued Chromebook. ● I will keep all passwords assigned to me secure. ● I will only use my account credentials to sign into my Chromebook. ● I am allowed to connect to non-district printers and wireless networks at home and in public places. ● I agree that e-mail or any other computer communication should be used only for appropriate, legitimate, and responsible communication. ● I agree not to share personal information about myself (full name, address, etc.) or about my family, friends or anyone else. ● I agree not to search for, download, display, post, or distribute vulgar, offensive material or images described in applicable district policies. (See the student handbook and/or the district's Acceptable Use Agreement.) ● I agree to abide by all school rules that address electronic device procedures. ● I will return the device when requested, at the end of the school year or upon my withdrawal. ● I agree to not deface or destroy this property in any way. Inappropriate use of the machine may result in the student losing their right to use the Chromebook. ● I understand that identification labels have been placed on the Chromebook. These labels are not to be removed or modified. Additional stickers, labels, tags, or markings of any kind are NOT to be added to the machine.

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

  • Emergency Response Partners must develop, maintain, and carry out a response plan for public water system emergencies, including disease outbreaks, spills, operational failures, and water system contamination. Partners must notify DWS in a timely manner of emergencies that may affect drinking water supplies.

  • Cost Responsibility for Interconnection Facilities and Distribution Upgrades 4.1 Interconnection Facilities 4.2 Distribution Upgrades

  • Primary Frequency Response Developer shall ensure the primary frequency response capability of its Large Generating Facility by installing, maintaining, and operating a functioning governor or equivalent controls. The term “functioning governor or equivalent controls” as used herein shall mean the required hardware and/or software that provides frequency responsive real power control with the ability to sense changes in system frequency and autonomously adjust the Large Generating Facility’s real power output in accordance with the droop and deadband parameters and in the direction needed to correct frequency deviations. Developer is required to install a governor or equivalent controls with the capability of operating: (1) with a maximum 5 percent droop ± 0.036 Hz deadband; or (2) in accordance with the relevant droop, deadband, and timely and sustained response settings from an approved Applicable Reliability Standard providing for equivalent or more stringent parameters. The droop characteristic shall be: (1) based on the nameplate capacity of the Large Generating Facility, and shall be linear in the range of frequencies between 59 and 61 Hz that are outside of the deadband parameter; or (2) based on an approved Applicable Reliability Standard providing for an equivalent or more stringent parameter. The deadband parameter shall be: the range of frequencies above and below nominal (60 Hz) in which the governor or equivalent controls is not expected to adjust the Large Generating Facility’s real power output in response to frequency deviations. The deadband shall be implemented: (1) without a step to the droop curve, that is, once the frequency deviation exceeds the deadband parameter, the expected change in the Large Generating Facility’s real power output in response to frequency deviations shall start from zero and then increase (for under-frequency deviations) or decrease (for over-frequency deviations) linearly in proportion to the magnitude of the frequency deviation; or (2) in accordance with an approved Applicable Reliability Standard providing for an equivalent or more stringent parameter. Developer shall notify NYISO that the primary frequency response capability of the Large Generating Facility has been tested and confirmed during commissioning. Once Developer has synchronized the Large Generating Facility with the New York State Transmission System, Developer shall operate the Large Generating Facility consistent with the provisions specified in Articles 9.5.5.1 and 9.5.5.2 of this Agreement. The primary frequency response requirements contained herein shall apply to both synchronous and non-synchronous Large Generating Facilities.

  • Company’s Response Upon receipt by the Company of a copy of a Conversion Notice, the Company shall as soon as practicable, but in no event later than one (1) Business Day after receipt of such Conversion Notice, send, via email, facsimile or overnight courier, a confirmation of receipt of such Conversion Notice to such Holder indicating that the Company will process such Conversion Notice in accordance with the terms herein. Within two (2) Business Days after the date of the Conversion Confirmation, the Company shall have issued and electronically transferred the shares to the Broker indicated in the Conversion Notice; should the Company be unable to transfer the shares electronically, it shall, within two (2) Business Days after the date of the Conversion Confirmation, have surrendered to FedEx for delivery the next day to the address as specified in the Conversion Notice, a certificate, registered in the name of the Holder, for the number of shares of Common Stock to which the Holder shall be entitled.

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