Security Incident Reporting Requirements. Contractor shall promptly report a Security Incident to the Eligible User.
Security Incident Reporting Requirements. The Contractor shall report a Security Incident to the appropriate City identified contact immediately and without delay, as defined in the SLA.
Security Incident Reporting Requirements. The Contractor shall report a security incident to the Purchasing Entity identified contact immediately as soon as possible or promptly without out reasonable delay, or as defined in the SLA.
Security Incident Reporting Requirements. Contractor shall report a Security Incident to DTS immediately if Contractor reasonably believes there has been a Security Incident.
Security Incident Reporting Requirements. Unless otherwise stipulated, the Contractor shall immediately report a security incident related to its service under the Master Agreement, Participating Addendum, or SLA to the appropriate Purchasing Entity.
Security Incident Reporting Requirements. The contractor shall report a Security Incident to the State-identified contact(s) as soon as possible by telephone and email, but in no case later than two (2) days after the Security Incident occurs. Notice requirements may be clarified in the Service Level Agreement and shall be construed in accordance with IC 4-1-11 and IC 24-4.9 as they may apply.
Security Incident Reporting Requirements. If a system used for remote computing is lost, stolen, compromised, or suspected of being compromised, the user must immediately report the incident to their supervisor and the Information Security Office (x4040).
Security Incident Reporting Requirements. The Company shall report a security incident to the appropriate Customer identified contact once a full investigation into the nature of the breach has been conducted and concluded and sufficient steps to remediate or correct the breach have occurred to ensure that all customer data is secure and would not be further jeopardized by such notification and resolve the breach and recover any data disclosed as a result thereof, but under no circumstance is the Company to take longer than 72 hours to notify the Customer of a security breach.
Security Incident Reporting Requirements. Unless otherwise stipulated, CLI shall immediately report a Security Incident related to its service under the Agreement to the CUSTOMER.
Security Incident Reporting Requirements. All Information Security Incidents involving USAID data or systems must be reported in accordance with the requirements below, even if it is believed that the information security incident may be limited, small, or insignificant. USAID will determine the magnitude and resulting actions.
i. Contractor employees must report via e-mail all Information Security Incidents to the USAID Service Desk immediately, but not later than 30 minutes, after becoming aware of the Incident, at: XXX-XXXXXXXX@xxxxx.xxx, regardless of day or time, as well as the Contracting Officer and Contracting Officer’s representative and the Contractor Facilities Security Officer. Contractor employees are strictly prohibited from including any Sensitive Information in the subject or body of any email concerning information security incident reports. To transmit Sensitive Information, Contractor employees must use FIPS 140-2 compliant encryption methods to protect Sensitive Information in attachments to email. Passwords must not be communicated in the same email as the attachment.
ii. The Contractor must provide any supplementary information or reports related to a previously reported information security incident directly to CIO- XXXXXXXX@xxxxx.xxx, upon request. Correspondence must include related ticket number(s) as provided by the USAID Service Desk with the subject line “Action Required: Potential Security Incident”.
