provided for in this article, deliver software maintenance services for the period of execution of tasks under the FWC. Such service shall be subject to one or several specific contracts under this FWC. 

Any deliverable provided by the Contractor under the FWC will be quality controlled by the Contractor, in the place of performance, before delivery. On the request of the contracting authority, the Contractor has to be in a position to show that the outcome of the quality control was positive. 

## I.16. ACCEPTANCE 

The acceptance procedure outlined in Annex I (Section 6.3 of the Technical Specifications) of the FWC shall apply for software and non-software Deliverables. 

Following the acceptance of a Deliverable, the contracting authority will issue a documented statement or Certificate of Acceptance. 

Without prejudice to other contractual remedies (liquidated damages in the Service Level Agreement in Annex I and in Article II.15), if the contracting authority does not accept the deliverables related to the performance of the tasks foreseen in a specific contract, the contractor will be given a formal notice in writing with acknowledgement of receipt to comply within a reasonable period, specifying the nature of the alleged failure. After being given the opportunity to remedy the failure, if the Contractor fails to comply within the given period, the Agency can terminate the specific contract. 

## I.17. CONFIDENTIALITY AND SECURITY 

I.17.1. The Contractor may only utilise the information contained in the material encountered during the duration of the FWC and any specific contract (including any data on any Agency network) for the purposes identified in the FWC, in accordance with the terms and conditions of the Non-Disclosure Agreement (NDA) in Annex VII. 

I.17.2. The Contractor shall take all appropriate steps for each deliverable, provided under the FWC, in order to ensure that the data and the media upon which they are stored are safely preserved. The deliverables provided shall not contain any mechanism (for example viruses) which could compromise their proper operation and that of other products. The cost of repairing the deliverable(s) and any resulting damage for the contracting authority caused by such a mechanism shall be borne by the Contractor in conformity with Article II.6. 

I.17.3. The Contractor undertakes to inform the contracting authority in writing as soon as he has any knowledge of faults in his products that endanger the security of the configurations of which they form a part. The Contractor shall immediately take any measures necessary to restore the security of the configurations and correct the faults. 

I.17.4. The Contractor shall provide the services in accordance with the technical specifications for the FWC and with technical norms, standards and procedures based on best professional practice in the field of information security. The Contractor may be requested by the contracting authority to put in place systems or procedures, such that the Contractor can securely remotely access the contracting authority’s systems. The Contractor undertakes to put in place such systems and procedures in accordance with ISO27001 (or equivalent standards or measures). Failure to meet the relevant security requirements of Annex I of the FWC may be considered by the contracting authority as 

