Event and Incident Management Sample Clauses

Event and Incident Management. B.4.2.1 The Contractor must work with the Purchasing Entity to determine the actual scope of an Event and determine if the Event is an Incident. This may include, but is not limited to, gathering information from various sources such as log files, error messages, and other resources such as intrusion detection systems and firewalls that may produce evidence to determine if an Event is an Incident. B.4.2.2 The Contractor must collect evidence, follow Chain of Custody protocol, and document all actions taken during the Event or Incident Response. B.4.2.2.1 All Event and Incident documentation must be made available to the Purchasing Entity and law enforcement upon request. B.4.2.3 The Contractor must identify when the Purchasing Entity should contact law enforcement and the Contractor must work with law enforcement under the direction of the Purchasing Entity. B.4.2.4 Because of the sensitive and confidential nature of information and communication surrounding an Incident, the Contractor must ensure all communication is through secure channels and disclosure of Incident information is limited to identified Purchasing Entity personnel and limited to a need to know basis (as defined by the Purchasing Entity) for all others.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Event and Incident Management

  • Incident Event and Communications Management a. Incident Management/Notification of Breach - DST shall develop, implement and maintain an incident response plan that specifies actions to be taken when DST or one of its subcontractors suspects or detects that a party has gained material unauthorized access to Fund Data or systems or applications containing any Fund Data (the “Response Plan”). Such Response Plan shall include the following: i. Escalation Procedures - An escalation procedure that includes notification to senior managers and appropriate reporting to regulatory and law enforcement agencies. This procedure shall provide for reporting of incidents that compromise the confidentiality of Fund Data (including backed up data) to Fund via telephone or email (and provide a confirmatory notice in writing as soon as practicable); provided that the foregoing notice obligation is excused for such period of time as DST is prohibited by law, rule, regulation or other governmental authority from notifying Fund. ii. Incident Reporting - DST will use commercially reasonable efforts to promptly furnish to Fund information that DST has regarding the general circumstances and extent of such unauthorized access to the Fund Data.

  • Incident Management 3.1. We shall notify You without undue delay after We becomes aware of any accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data, including Personal Data, stored or otherwise processed by Us or Our sub-processors of which We become aware (“Security Incident”). 3.2. We shall use best efforts to identify the cause of such Security Incident and take the measures We deem necessary and within Our control for remediating and securing Customer Data; We shall coordinate such efforts with You without undue delay.

  • Change in Management Permit a change in the senior management of Borrower.

  • Management of Change a. The parties to this Collective Agreement accept that change in the health service is necessary in order to ensure the efficient and effective delivery of health services. They recognise a mutual interest in ensuring that health services are provided efficiently and effectively, and that each has a contribution to make in this regard.‌ b. Regular consultation between the employer, its midwives and the union is essential on matters of mutual concern and interest. Effective communication between the parties will allow for: • improved decision making; • greater co-operation between employer and midwives; and • a more harmonious, effective, efficient, safe and productive workplace.

  • Account Management 15.1 The Contractor is required to provide a dedicated Strategic Account Manager who will be the main point of contact for the Authority. The Strategic Account Manager will:  Attend quarterly, or as otherwise agreed, review meetings with the Authority, in person at the Authority’s premises or other locations as determined by the Authority  Attend regular catch-up meetings with the Authority, in person or by telephone/videoconference  Resolve any on-going operational issues which have not been resolved by the Contractor or Account Manager(s) and therefore require escalation  Ensure that the costs involved in delivering the Framework are as low as possible, whilst always meeting the required standards of service and quality. 15.2 The Contractor is also required to provide a dedicated Account Manager for every Framework Public Body using the Framework, if required by the Framework Public Body. The service to be provided will be agreed with each Framework Public Body and may include:  regular review meetings, which may be in person at the Framework Public Bodies’ premises, by video-conference, webinar or telephone  Regular catch-up meetings/telephone calls to discuss current and on-going issues  Work with the Framework Public Bodies Contract Manager to resolve any on-going operational issues  Work with the Framework Public Body ’s Contract Manager to pro-actively introduce initiatives to:  Create efficiencies in processes  Improve the environmental performance of the contract. 15.3 It is expected that end users will contact the Contractor in the first instance to resolve any operational issues. The Account Manager will act as a point of escalation to be contacted either by end users or by the Framework Public Body’s Contract Manager should there be issues that the Contractor needs to resolve. 15.4 Further details of the roles and responsibilities of the Contractor, Authority and Framework Public Bodies are provided in Schedule 4 – Management Arrangements

  • Change in Management or Control The Adviser shall provide at least sixty (60) days' prior written notice to the Trust of any change in the ownership or management of the Adviser, or any event or action that may constitute a change in “control,” as that term is defined in Section 2 of the Act .. The Adviser shall provide prompt notice of any change in the portfolio manager(s) responsible for the day-to-day management of the Funds.

  • Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.

  • Contact in Event of Unauthorized Transfer If you believe your Card and/or access code has been lost or stolen or that someone has transferred or may transfer money from your account without your permission, either call us immediately at:

  • Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.

  • Name Collision Occurrence Management 6.1. No-­‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-­‐Activation Period ends.

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