Operating System Security Sample Clauses

Operating System Security. 1. Do you have procedures for “hardening” your systems against vulnerabilities? Yes. A base configuration is approved and this is used as a template for all further configurations. All unnecessary services are removed and all unnecessary programs are stopped and removed from startup. 2. Do you perform routine vulnerability scanning of your customer environment? If so, what tools are used? Yes. Nessus, Nikto, nmap and GFI languard are used. 3. Do you have a patch management process? Yes. Windows systems use a MS patching server Unix systems are patched quarterly or as needed. 4. Is anti-virus software deployed on systems and how often are virus definitions updated? Yes. We use Symantec updates are scheduled weekly.
AutoNDA by SimpleDocs
Operating System Security. Customer shall maintain virus and malware protection and operating system security updates to network connected computing systems which run Software Products and for backing up any information generated by the Hardware.
Operating System Security. The Bourse will: (i) install, configure, maintain and update firewalls, anti-virus and anti-spyware on all devices; (ii) manage the Bourse’s network security infrastructure components used for the connection of the AP and Bourse networks; (iii) establish procedures for logging, alarming and reporting of network security violations;‌ (iv) manage and maintain firewalls and gateway devices that connect the Bourse network to the AP network; (v) employ 24 x 7 network intrusion detection on Bourse network used for LOPR; (vi) limit access to Bourse-managed software that monitors, manages, manipulates or modifies network configurations and traffic to prevent unauthorized interventions in network operations; (vii) provide network access control, authentication, authorization and accounting of access to network resources (e.g. routers/firewalls/L3 switches); (viii) on an ongoing basis, monitor for known vulnerabilities and apply appropriate patches in a timeline that accords with the level of criticality involved and the direction of the relevant third party software provider, and in all cases apply patches in accordance with the software providers’ instructions; (ix) periodically review the Bourse’s information risk management requirements for the outsourcing arrangement; and (x) ensure that all Bourse systems are configured in accordance with industry standards.

Related to Operating System Security

  • System Security (a) If any party hereto is given access to the other party’s computer systems or software (collectively, the “Systems”) in connection with the Services, the party given access (the “Availed Party”) shall comply with all of the other party’s system security policies, procedures and requirements that have been provided to the Availed Party in advance and in writing (collectively, “Security Regulations”), and shall not tamper with, compromise or circumvent any security or audit measures employed by such other party. The Availed Party shall access and use only those Systems of the other party for which it has been granted the right to access and use. (b) Each party hereto shall use commercially reasonable efforts to ensure that only those of its personnel who are specifically authorized to have access to the Systems of the other party gain such access, and use commercially reasonable efforts to prevent unauthorized access, use, destruction, alteration or loss of information contained therein, including notifying its personnel of the restrictions set forth in this Agreement and of the Security Regulations. (c) If, at any time, the Availed Party determines that any of its personnel has sought to circumvent, or has circumvented, the Security Regulations, that any unauthorized Availed Party personnel has accessed the Systems, or that any of its personnel has engaged in activities that may lead to the unauthorized access, use, destruction, alteration or loss of data, information or software of the other party hereto, the Availed Party shall promptly terminate any such person’s access to the Systems and immediately notify the other party hereto. In addition, such other party hereto shall have the right to deny personnel of the Availed Party access to its Systems upon notice to the Availed Party in the event that the other party hereto reasonably believes that such personnel have engaged in any of the activities set forth above in this Section 9.2(c) or otherwise pose a security concern. The Availed Party shall use commercially reasonable efforts to cooperate with the other party hereto in investigating any apparent unauthorized access to such other party’s Systems.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Interconnection Service Interconnection Service allows the Interconnection Customer to connect the Large Generating Facility to the Participating TO’s Transmission System and be eligible to deliver the Large Generating Facility’s output using the available capacity of the CAISO Controlled Grid. To the extent the Interconnection Customer wants to receive Interconnection Service, the Participating TO shall construct facilities identified in Appendices A and C that the Participating TO is responsible to construct.

  • DTC DIRECT REGISTRATION SYSTEM AND PROFILE MODIFICATION SYSTEM (a) Notwithstanding the provisions of Section 2.04, the parties acknowledge that the Direct Registration System (“DRS”) and Profile Modification System (“Profile”) shall apply to uncertificated American Depositary Shares upon acceptance thereof to DRS by DTC. DRS is the system administered by DTC pursuant to which the Depositary may register the ownership of uncertificated American Depositary Shares, which ownership shall be evidenced by periodic statements issued by the Depositary to the Owners entitled thereto. Profile is a required feature of DRS which allows a DTC participant, claiming to act on behalf of an Owner of American Depositary Shares, to direct the Depositary to register a transfer of those American Depositary Shares to DTC or its nominee and to deliver those American Depositary Shares to the DTC account of that DTC participant without receipt by the Depositary of prior authorization from the Owner to register such transfer. (b) In connection with and in accordance with the arrangements and procedures relating to DRS/Profile, the parties understand that the Depositary will not verify, determine or otherwise ascertain that the DTC participant which is claiming to be acting on behalf of an Owner in requesting a registration of transfer and delivery as described in subsection (a) has the actual authority to act on behalf of the Owner (notwithstanding any requirements under the Uniform Commercial Code). For the avoidance of doubt, the provisions of Sections 5.03 and 5.08 shall apply to the matters arising from the use of the DRS. The parties agree that the Depositary’s reliance on and compliance with instructions received by the Depositary through the DRS/Profile System and in accordance with this Deposit Agreement shall not constitute negligence or bad faith on the part of the Depositary.

  • Developer Attachment Facilities Developer shall design, procure, construct, install, own and/or control the Developer Attachment Facilities described in Appendix A hereto, at its sole expense.

  • Installation Services The Bitstream 2a Service includes a Standard Install as set out below (in each case to the extent that the relevant provisioning works are not already complete for the relevant Service Order).1

  • Construction Services 4,500 thousand SDR for Japan Post in Group A 15,000 thousand SDR for all other entities in Group A 4,500 thousand SDR for entities in Group B Architectural, engineering and other technical services covered by this Agreement: 450 thousand SDR

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

  • Provisional Interconnection Service Upon the request of Interconnection Customer, and prior to completion of requisite Interconnection Facilities, Network Upgrades, Local Upgrades, or system protection facilities Interconnection Customer may request limited Interconnection Service at the discretion of Transmission Provider based upon an evaluation that will consider the results of available studies, which terms shall be memorialized in the Interconnection Service Agreement. Consistent with Tariff, Part VI, Subpart B, section 212.4, Interconnection Customer may execute the Interconnection Service Agreement, request dispute resolution or request that the Interconnection Service Agreement be filed unexecuted with the Commission. Transmission Provider shall determine, through available studies or additional studies as necessary, whether stability, short circuit, thermal, and/or voltage issues would arise if Interconnection Customer interconnects without modifications to the Generating Facility or the Transmission System. Transmission Provider shall determine whether any Interconnection Facilities, Network Upgrades, Local Upgrades, or system protection facilities that are necessary to meet the requirements of NERC, or any applicable Regional Entity for the interconnection of a new, modified and/or expanded Generating Facility are in place prior to the commencement of Interconnection Service from the Generating Facility. Where available studies indicate that such Interconnection Facilities, Network Upgrades, Local Upgrades, and/or system protection facilities that are required for the interconnection of a new, modified and/or expanded Generating Facility are not currently in place, Transmission Provider will perform a study, at the Interconnection Customer’s expense, to confirm the facilities that are required for Provisional Interconnection Service. The maximum permissible output of the Generating Facility shall be studied and updated annually and at the Interconnection Customer’s expense. The results will be communicated to the Interconnection Customer in writing upon completion of the study. Interconnection Customer assumes all risk and liabilities with respect to the Provisional Interconnection Service, including changes in output limits and Interconnection Facilities, Network Upgrades, Local Upgrades, and/or system protection facilities cost responsibilities.

  • Monitoring System In each case in which the Custodian has exercised delegated authority to place Assets with a Foreign Custodian, the Custodian shall establish a system, to re-assess or re-evaluate selected Foreign Custodians, at least annually in accordance with Rule 17f-5(c)(3).

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!