Isms and Security Management Plan Sample Clauses

Isms and Security Management Plan. Introduction Throughout the Term the Service Provider shall develop, implement, comply with (and ensure that all service provider personnel and Sub-Contractors implement and comply with) and maintain and continuously improve and maintain an ISMS which shall, without prejudice to Paragraphs 2.2 above and 4.1 below, be: approved by the Authority; tested in accordance with Paragraph 4; and periodically updated and audited in accordance with ISO/IEC 27001. The Service Provider shall develop and maintain a Security Management Plan in accordance with this Schedule to apply during the Term (and after the end of the Term as applicable) in both this Framework Agreement and all Call-Off Agreements. The Service Provider shall comply with its obligations set out in the Security Management Plan and the other elements of this Framework Agreement relevant to security (including the Security Requirements). Both the ISMS and the Security Management Plan shall, unless otherwise specified in writing by the Authority, aim to protect all aspects of the Services and all processes associated with the delivery of the Services, including the Sites, the Service Provider System and any ICT, information and data (including the Contracting Body Confidential Information) to the extent used by the Authority, the Contracting Body or the Service Provider in connection with this Framework Agreement. The Service Provider is responsible for monitoring and ensuring that it is aware of changes to the Security Policy Framework. The Service Provider shall keep the Security Management Plan up-to-date with the Security Policy Framework as amended from time to time. Development Within thirty (30) Working Days after the Commencement Date (or such other period specified in the Implementation Plan or as otherwise agreed by the Parties in writing) and in accordance with Paragraphs 3.3 and 3.4 below, the Service Provider shall prepare and deliver to the Authority and (if required by the Authority) the Pan-Government Accreditor for approval a fully complete and up-to-date Security Management Plan, relating specifically to the Services provided under this Framework Agreement. In this instance the “Pan Government Accreditor” refers to the service provided by CESG, the National Technical Authority for Information Assurance, concerned with effective management of information risk associated with adoption of pan-government shared services If the Security Management Plan or any subsequent revision to it in acc...
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Isms and Security Management Plan. Introduction The Contractor shall develop, implement, operate, maintain and continuously improve and maintain an ISMS which will, without prejudice to paragraph 2.2, be approved, by the Authority, tested in accordance with the schedule relating to testing procedures (if applicable), periodically updated and audited in accordance with ISO/IEC 27001. The Contractor shall develop and maintain a Security Management Plan in accordance with this Schedule to apply during the term of this Agreement. The Contractor shall comply with its obligations set out in the Security Management Plan. Both the ISMS and the Security Management Plan shall, unless otherwise specified by the Authority, aim to protect all aspects of the Services and all processes associated with the delivery of the Services, including the Authority’s premises, the Sites, the Contractor System and any information and communications technology, information and data (including the Authority Confidential Information and the Authority Data) to the extent used by the Authority or the Contractor in connection with this Agreement. Development Within 20 Working Days after the date of the contract to which these Supplementary Conditions apply and in accordance with paragraph (Amendment and Revision), the Contractor will prepare and deliver to the Authority for approval the full and final Security Management Plan which will be based on the draft Security Management Plan set out in Appendix 1. If the Security Management Plan, or any subsequent revision to it in accordance with paragraph 3.4, is approved by the Authority it will be adopted immediately and will replace the previous version of the Security Management Plan at Appendix 1. If the Security Management Plan is not approved by the Authority the Contractor shall amend it within [10] Working Days of a notice of non-approval from the Authority and re-submit to the Authority for approval. The parties will use all reasonable endeavours to ensure that the approval process takes as little time as possible and in any event no longer than [15] Working Days (or such other period as the parties may agree in writing) from the date of its first submission to the Authority. If the Authority does not approve the Security Management Plan following its resubmission, the matter will be resolved in accordance with any procedures for resolving disputes set out in the General Conditions. No approval to be given by the Authority pursuant to this paragraph of this schedule may...
Sample 1
Isms and Security Management Plan. 5.1 The Contractor shall develop an ISMS and a Security Management Plan which covers the End to End Solution.
Sample 1
Isms and Security Management Plan 
Sample 1Sample 2Sample 3See All (27)

Related to Isms and Security Management Plan

  • Security Management The Contractor shall comply with the requirements of the DOD 5200.1-M and the DD Form 254. Security of the Contractor’s electronic media shall be in accordance with the above documents. Effective Program Security shall require the Contractor to address Information Security and Operations Security enabled by the Security Classification Guides. The Contractor’s facility must be able to handle and store material up to the Classification Level as referenced in Attachment J-01, DD Form 254.

  • Project Management Plan 1 3.4.1 Developer is responsible for all quality assurance and quality control 2 activities necessary to manage the Work, including the Utility Adjustment Work.

  • Patch Management All workstations, laptops and other systems that process and/or 20 store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or 21 transmits on behalf of COUNTY must have critical security patches applied, with system reboot if 22 necessary. There must be a documented patch management process which determines installation 23 timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable 24 patches must be installed within thirty (30) calendar or business days of vendor release. Applications 25 and systems that cannot be patched due to operational reasons must have compensatory controls 26 implemented to minimize risk, where possible.

  • Construction Management Plan Contractor shall prepare and furnish to the Owner a thorough and complete plan for the management of the Project from issuance of the Proceed Order through the issuance of the Design Professional's Certificate of Material Completion. Such plan shall include, without limitation, an estimate of the manpower requirements for each trade and the anticipated availability of such manpower, a schedule prepared using the critical path method that will amplify and support the schedule required in Article 2.1.5 below, and the Submittal Schedule as required in Article 2.2.3. The Contractor shall include in his plan the names and resumés of the Project Superintendent, Project Manager and the person in charge of Safety.

  • Management Plan The Management Plan is the description and definition of the phasing, sequencing and timing of the major Individual Project activities for design, construction procurement, construction and occupancy as described in the IPPA.

  • Procurement Plan 8. The Borrower shall update the Procurement Plan as needed throughout implementation of the Project, and on each anniversary of the Effective Date, the Borrower shall in consultation with ADB determine whether the Procurement Plan needs to be updated. The Borrower shall implement the Procurement Plan in the manner in which it has been approved by ADB.

  • DATA HANDLING AND SECURITY It will always be the responsibility of the selected Contractor to manage data transfer and to secure all data appropriately during the project to prevent unauthorized access to all data, products, and deliverables.

  • Procurement of Goods and Services (a) If the HSP is subject to the procurement provisions of the BPSAA, the HSP will abide by all directives and guidelines issued by the Management Board of Cabinet that are applicable to the HSP pursuant to the BPSAA.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Procurement and Property Management Standards The parties to this Agreement shall adhere to the procurement and property management standards established in 2 CFR 200, Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards, and to the Texas Uniform Grant Management Standards. The State must pre-approve the Local Government’s procurement procedures for purchases to be eligible for state or federal funds.

Time is Money Join Law Insider Premium to draft better contracts faster.