Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).
Technical and Organisational Measures (1) Before the commencement of processing, the Supplier shall document the execution of the necessary Technical and Organisational Measures, set out in advance of the awarding of the Order or Contract, specifically with regard to the detailed execution of the contract, and shall present these documented measures to the Client for inspection. Upon acceptance by the Client, the documented measures become the foundation of the contract. Insofar as the inspection/audit by the Client shows the need for amendments, such amendments shall be implemented by mutual agreement. (2) The Supplier shall establish the security in accordance with Article 28 Paragraph 3 Point c, and Article 32 GDPR in particular in conjunction with Article 5 Paragraph 1, and Paragraph 2 GDPR. The measures to be taken are measures of data security and measures that guarantee a protection level appropriate to the risk concerning confidentiality, integrity, availability and resilience of the systems. The state of the art, implementation costs, the nature, scope and purposes of processing as well as the probability of occurrence and the severity of the risk to the rights and freedoms of natural persons within the meaning of Article 32 Paragraph 1 GDPR must be taken into account. [Details in Appendix 1] (3) The Technical and Organisational Measures are subject to technical progress and further development. In this respect, it is permissible for the Supplier to implement alternative adequate measures. In so doing, the security level of the defined measures must not be reduced. Substantial changes must be documented.
Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.
Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.
Dependencies HP’s ability to deliver services will depend on Customer’s reasonable and timely cooperation and the accuracy and completeness of any information from Customer needed to deliver the services.
Vulnerability Management BNY Mellon will maintain a documented process to identify and remediate security vulnerabilities affecting its systems used to provide the services. BNY Mellon will classify security vulnerabilities using industry recognized standards and conduct continuous monitoring and testing of its networks, hardware and software including regular penetration testing and ethical hack assessments. BNY Mellon will remediate identified security vulnerabilities in accordance with its process.
Deactivation Computershare applications shall automatically deactivate a User ID after a specified number of unsuccessful log-in attempts. Sessions must be restricted or timed out after a defined period of inactivity and require Users to re-authenticate. User IDs for Computershare Personnel with access to Customer Confidential Information shall be deactivated immediately upon changes in job responsibilities that render such access unnecessary, or upon termination of employment.
Underutilization Underutilization of Interconnection Trunks and facilities exists when provisioned capacity of trunks in service for more than six (6) months is greater than the current need. This over-provisioning is an inefficient deployment and use of network resources and results in unnecessary costs. Those situations where more capacity exists than actual usage will be handled in the following manner: a. If a final trunk group is under seventy-five percent (75%) of CCS capacity or a high usage trunk group is under 90% of CCS capacity on a monthly average basis, for each month of any three (3) consecutive months period, either Party may request the issuance of an order to resize the trunk group, which shall be left with not less than twenty-five percent (25%) excess capacity. In all cases POI requirements and grade of service objectives shall be maintained. b. CLEC will send an ASR to CenturyLink to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment.
Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case. 2. Nothing in this Article and Articles 25A to 25G shall affect the fulfilment of wider obligations with respect to the arbitration of unresolved issues arising in the context of a mutual agreement procedure resulting from other conventions to which the Contracting States are or will become parties.”.
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.