Incident Response Plan. Policies and procedures are implemented, designed to detect, respond to, and otherwise address incidents, including specific points of contact in the event of an incident, and procedures to: (i) monitor and detect actual and attempted attacks on, or intrusions into, the processing systems, (ii) identify and respond to suspected or known incidents, (iii) immediately mitigate the harmful effects of any incidents without detriment to measures or actions necessary to determine the seriousness of the breach.
Incident Response Plan. Procedures for responding to, documenting, and mitigating where practicable suspected or known incidents involving a possible breach of security and their outcomes.
Incident Response Plan. Supplier shall be able to implement and maintain an existing incident response plan containing milestones and service level-agreements for its incident response capability, describing the structure and organization of the incident response capability, providing a high-level approach for how the incident response capability aligns with its overall organizational policies and procedures, and meets the unique requirements of the Supplier, which relate to mission, size, structure, and functions. The incident response plan will also define reportable incidents and resources needed to effectively maintain and mature an incident response capability, as well as provide metrics for measuring the incident response capability. The plan shall then be approved by designated Supplier officials.
13.3.1. Copies of the incident response plan shall be distributed to incident response personnel and Supplier organization elements.
13.3.2. Reviews of the incident response plan shall occur annually and include a table-top exercise, documentation, test plan, and results.
13.3.3. Revisions to the incident response plan shall be made to address system/organizational changes or problems encountered during plan implementation, execution, or testing.
13.3.4. Supplier shall communicate incident response plan changes to incident response personnel and organizational elements.
Incident Response Plan. Talos will maintain an incident response plan to detect, respond to, contain, investigate, and remediate cybersecurity incidents, including all incidents that compromise the confidentiality, integrity, and availability of data, systems, networks, and services. The plan shall identify and assign roles and responsibilities to key stakeholders and decision-makers across the organization. Talos shall regularly test the incident response plan.
Incident Response Plan. This policy addresses what to do when the company has experienced a security breach. I, , having account # , hereby grant unlimited authority to Monolith Solar Associates LLC to act as my Agent with regards to actions and correspondence related to the Utility. I further authorize you to release to Monolith Solar Associates LLC any account information requested as well as act as an agent for my satellite accounts. Monolith Solar Associates LLC is granted full power to act on my behalf in the same manner as if I were personally present. In order for Monolith Solar to sell the Solar Credits to you, you and/or the Utility must provide us your electrical consumption history and other information, including, but not limited to, the following:
1. Your service address;
2. Your electric Utility account number;
3. Sales tax district used by the distribution Utility and whether the Utility identifies you as tax exempt;
4. Rate service class and subclass or rider by account and by meter, where applicable;
5. Electric load profile reference category or code, if not based on service class, whether your account is settled with the NYISO utilizing an actual 'hourly' or a 'class shape' methodology, or Installed Capacity (ICAP) tag, which indicates your peak electricity demand;
6. Your number of meters and meter numbers;
7. Whether you receive any special delivery or commodity “first through the meter” incentives, or incentives from the New York Power Authority;
8. Your Standard Industrial Classification (SIC) code (if applicable);
Incident Response Plan. Alteryx maintains an incident response program to address any suspected unauthorized access to or use of Licensee Content or to Alteryx systems that process or have access to Licensee Content, including, but not limited to: (i) promptly notifying Licensee of a confirmed breach, together with sufficient detail to inform Licensee of any potential risks to Licensee systems or data; (ii) taking all reasonable steps required to address the source of the suspected breach and to mitigate any identified risks; and (iii) providing Licensee with updates and information to demonstrate adequate resolution of the vulnerabilities giving rise to the suspected breach.
Incident Response Plan. External Party shall document and implement a Security Incident response plan which all External Party Employees are required to follow in the event that a Security Incident is suspected or confirmed; this Security Incident response plan shall include notifications, points of contact, backup procedures and all relevant actions that are required to recover from a Security Incident.
Incident Response Plan. Supplier shall deploy and follow policies and procedures to detect, respond to, and otherwise address Security Incidents including procedures to (i) identify and respond to reasonably suspected or known Security Incidents, mitigate harmful effects of Security Incidents, document Security Incidents and their outcomes, and (ii) restore the availability or access to Buyer Personal Data in a timely manner. Upon request, Supplier shall provide Buyer with a copy of its incident response plan.
Incident Response Plan. The SI's Information Security Program shall include an incident response plan to address and handle Security Incidents relating to NFPS Data and MTA Group Confidential Information and, at a minimum, shall also apply to NFPS Security-Sensitive SI Resources (the "Incident Response Plan"). This Incident Response Plan shall comply with Good Industry Practices and the requirements set out in the Technical Specifications. The SI shall periodically test its incident Response Plan, all in accordance with Good Industry Practices. The SI shall submit a draft of the Incident Response Plan to the MTA for review and approval, and the SI shall otherwise ensure that the Incident Response Plan has been approved and is implemented prior to the earlier of (i) the commencement of the first Pilot Test, and (ii) the SI's collection of NFPS Data from any MTA Group customer.
Incident Response Plan. Vendor shall have a written incident response plan, to include prompt notification to HCSD in the event of a security or privacy incident, as well as best practices for responding to a breach of HCSD Protected Information and Data. Provider agrees to share its incident response plan upon request. Upon the occurrence of any actual or suspected unauthorized use or disclosure of HCSD Protected Information and Data. Vendor shall take reasonable steps to minimize or mitigate the risk of harmful or potentially harmful effects resulting from said actual or suspected unauthorized use or disclosure.
