Security Incident and Resolution Reporting Sample Clauses

Security Incident and Resolution Reporting. Upon discovering that the confidentiality, integrity or availability of the Web server or the website’s information resources is threatened or compromised, the Contractor must report the security incident to the Authority/Corporation. For purposes of this section the following events are considered security incidents: 1. Unauthorized access that is either successful or unusually persistent. 2. Instances of any malicious code that either has a widespread impact throughout the Contractor’s organizational Web environment or has specifically affected the Authority/Corporation’s Web server or website. 3. Denial of service attack that is either successful and adversely affects website access or is unusually persistent. 4. Scans and probes that precede or are related to a security incident listed above. 5. The Contractor shall contact the Authority/Corporation via telephone and supply the following information when initially reporting the discovery of a security incident: a. Name, phone/pager/cell number and e-mail address of the individual making the report. b. Type of security incident(s) – unauthorized access, malicious code, denial of service, probes, scans and/or other suspected activity that could result in a significant adverse impact. c. Location of affected system – street address, floor/room number and city/state. d. Detailed description of the security incident. e. Date and time the security incident occurred. f. Date and time the security incident was detected. g. How the security incident was detected. h. Business impact/criticality of the security incident.
Sample 1
AutoNDA by SimpleDocs

Related to Security Incident and Resolution 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.

  • Security Incident Notification The Transfer Agent shall promptly notify the Trust but in no event later than 72 hours following discovery of any Security Incident(s). Such notification shall include the extent and nature of such intrusion, disclosure, or unauthorized access, the identity of the compromised Customer Confidential Information (to the extent it can be ascertained), how the Transfer Agent was affected by the Security Incident, and its response to such Security Incident. The Transfer Agent shall use continuous and diligent efforts to remedy the cause and the effects of such Security Incident in an expeditious manner and deliver to the Trust a root cause analysis and future incident Mitigation plan with regard to any such incident. The Transfer Agent shall reasonably cooperate with the Trust’s investigation and response to each Security Incident. If the Trust determines in its sole discretion that it may need or be required to notify any individual(s) as a result of a Security Incident, the Trust shall have the right to control all such notifications and the Transfer Agent shall bear all direct costs associated with the notification, to the extent the notification and corresponding actions are required by U.S. law, and subject to the limitation of liability set forth in the Agreement. Without limiting the foregoing, unless otherwise required by U.S. law, no such notifications shall be made by the Transfer Agent without the Trust’s prior written consent and the Trust shall, together with the Transfer Agent, determine the content and delivery of all such notifications. For the avoidance of doubt, the Transfer Agent shall be solely responsible for all costs and expenses, subject to the limitations of liability under the Agreement that the Trust and/or the Transfer Agent may incur to the extent that they are attributable to or arise from the Transfer Agent’s breach of its confidentiality obligations under the Agreement.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Security Incidents 11.1 Includes identification, managing and agreed reporting procedures for actual or suspected security breaches.

  • Security Incident “Security Incident” means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system.

  • Litigation Reporting If Contractor is served with a pleading or other document in connection with an action before a court or other administrative decision making body, and such pleading or document relates to this Participating Addendum or may affect Contractor’s ability to perform its obligations under this Participating Addendum, Contractor shall, within 10 days after being served, notify the State of such action and deliver copies of such pleading or document to the State’s primary contact identified in §5 of the Participating Addendum .

  • Collateral Reporting it will provide the Agent, in each case in respect of each Trading Company, and on a consolidated and consolidating basis, with the following documents at the following times in form satisfactory to the Agent: (a) on a weekly basis on each Wednesday based on figures as of the previous Friday, a Borrowing Base Certificate incorporating, inter alia, a schedule of credit notes, a summary of collections of accounts receivable, a schedule of Accounts created since the last such schedule, with effect from any Inventory Eligibility Date, a report of the Inventory balance (by location) based on the perpetual inventory reports and such further details as the Agent may request; (b) upon request, copies of invoices, credit notes, shipping and delivery documents; (c) monthly ageings of accounts receivable to be delivered no later than the 10th day of each month in respect of the immediately preceding month; (d) monthly perpetual inventory reports by category to be delivered no later than the 10th day of each month in respect of the immediately preceding month; (e) on a monthly basis, a report listing the top ten (10) customers of Ideal during that month, providing (i) details of the level of sales made to each such customer; (ii) details of any credit notes issued to each such customer or any other account adjustments made in respect of such customer; and (iii) the amount of cash actually received from each such customer during the relevant month; (f) with effect from any Inventory Eligibility Date, upon request, monthly perpetual inventory reports with effect from any Inventory Eligibility Date, a quarterly report of all Inventory based on a physical stock count; (g) monthly ageings of accounts payable no later than the 10th day of the following month, together with a specific breakdown (in reasonable detail) of the monthly ageings of accounts payable to the largest ten supplier creditors of Ideal and details of the Inventory held by Ideal in respect of such accounts payable and each such supplier; (h) with effect from any Inventory Eligibility Date, upon request, copies of purchase orders, invoices, and delivery documents for Inventory and Equipment acquired by that Trading Company; (i) such other reports as to the Collateral and the Accounts (and each Borrower hereby authorises the Agent to make enquiries of its customers in this respect) as the Agent shall request from time to time; and (j) certificates of an officer of Ideal certifying as to the foregoing;

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • Financial Reporting and Rent Rolls Each Mortgage Loan requires the Mortgagor to provide the owner or holder of the Mortgage Loan with (a) quarterly (other than for single-tenant properties) and annual operating statements, (b) quarterly (other than for single-tenant properties) rent rolls (or maintenance schedules in the case of Mortgage Loans secured by residential cooperative properties) for properties that have any individual lease which accounts for more than 5% of the in-place base rent, and (c) annual financial statements.

  • Monthly Reporting Within twenty (20) calendar days following the end of each calendar month, Registry Operator shall deliver to ICANN reports in the format set forth in Specification 3 attached hereto (“Specification 3”).

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