Security and Disaster Recovery Sample Clauses

Security and Disaster Recovery. (a) The Sub-Adviser has adopted policies and procedures reasonably designed to seek to ensure that all information relating to the Fund created, obtained and/or received by Sub-Adviser (“Fund Data”) is kept under secure conditions that protect it effectively from unauthorized access. (b) The Sub-Adviser has adopted recordkeeping policies and procedures reasonably designed to seek to ensure that back-up arrangements exist for all Fund Data (other than data held solely for back-up purposes) which, in the event of data loss, will enable any such data to be reconstructed from Sub-Adviser’s records accurately and as soon as reasonably practicable. If any Fund Data is lost, destroyed or corrupted whilst it is in the possession or under the control of the Sub-Adviser, the Sub-Adviser will, at its own expense, reconstruct that data as soon as reasonably practicable. (c) The Sub-Adviser has adopted a business continuity plan in accordance with good industry practice. This plan shall consist of supported continuity arrangements and shall be tested at least annually; the results of these tests shall be made available to the Adviser on request. (d) The Sub-Adviser will at all times maintain disaster recovery facilities in accordance with its business continuity plan and will ensure that, in the event of disaster affecting any premises or equipment used by the Sub-Adviser, those facilities will be sufficient to enable the performance of its duties and obligations under this Agreement to resume and to continue from suitable alternative facilities as soon as reasonably practicable.

Security and Disaster Recovery. 16.1 FDISG represents and warrants that, to the best of its knowledge, the various procedures and systems which FDISG has implemented with regard to the safeguarding from loss or damage attributable to fire, theft or any other cause (including provision for 24 hours a day restricted access) of the Fund's blank checks, certificates, records and other data and FDISG's equipment, facilities and other property used in the performance of its obligations hereunder are adequate, and that it will make such changes therein from time to time as in its judgment are required for the secure performance of its obligations hereunder. FDISG shall review such systems and procedures on a periodic basis and the Fund shall have access to review these systems and procedures.

Security and Disaster Recovery. 24.1. HealthGate will ensure that all documents, data and Software are kept under secure conditions with back up arrangements satisfactory to the Publishers, to protect them effectively from unauthorised access and so that they can be recovered from any malfunction of the System. 24.2. Should the Publishers' Content and/or data be lost or destroyed, HealthGate will be responsible for its prompt reconstruction as quickly as possible with high priority allocation of time and resources, having regard to the back-up frequency agreed with the Publishers in the Specification. 24.3. HealthGate will not without the written consent of the Publishers disclose any of the Publishers' data or Publishers' Content to any third party. 24.4. HealthGate will take all reasonable precautions to minimise the impact of any disaster relating to the Services.

Security and Disaster Recovery. The Supplier will: 5.1. Deploy security patches and upgrades to vulnerabilities within a maximum period from the public release of such patches within a maximum period of fourteen (14) days except where the Buyer agrees a different period after a case-by-case consultation with the Supplier. 5.2. Detect, analyse, and respond to service outages in accordance with the Service Level Agreement. Collaborating with the Buyer and the GDS team. 5.3. Perform incident management and reporting relating to outages and security up grades in accordance with the Service Level Agreement. 5.4. Apply fixes identified as part of incident management to prevent service degradation and to detect, analyse, and respond to service outages. 5.5. Undertake penetration testing at least once a year, or if a significant change to the infrastructure takes place. 5.6. Use the latest versions of anti-virus definitions and software from an industry-accepted software vendor to provide protections against and minimise the impact of cyber-attacks. 5.7. Monitor service interactions within the solution platform, ensuring they are traceable and monitored end to end. 5.8. Provide, and seek ▇▇▇▇▇’s approval of, their Business Continuity Plan in support of the Service and review and update at least once every 12 months. 5.9. In the event of a security breach, the Supplier will inform HMRC within a maximum of 24 hours of detection of such anomalous or unauthorised activity within their premises or environment and take all reasonable measures to remediate the position. 5.10. Work with the Buyer to identify potential impacts and interdependencies arising from changes with the Buyers other Customs system to the Online Trade Tariff tool and related service(s). Implement consequential changes as agreed with the Buyer.

Security and Disaster Recovery. DevFactory shall comply with Client’s reasonable information security requirements, including participating in an annual information security review with Client.

Security and Disaster Recovery