Union Access 54. The Union shall have reasonable access to all work locations to verify that the terms and conditions of this Agreement are being carried out and for the purpose of conferring with employees provided that access shall be subject to such rules and regulations immediately below, as well as to such rules and regulations as may be agreed to by the department and the Union.
System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.
Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.
User Access Transfer Agent shall have a process to promptly disable access to Fund Data by any Transfer Agent personnel who no longer requires such access. Transfer Agent will also promptly remove access of Fund personnel upon receipt of notification from Fund.
System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.
Network Services Local Access Services In lieu of any other rates and discounts, Customer will pay fixed monthly recurring local loop charges ranging from $1,200 to $2,000 for TDM-based DS-3 Network Services Local Access Services at 2 CLLI codes mutually agreed upon by Customer and Company.
REMOTE ACCESS SERVICES ADDENDUM The Custodian and each Fund agree to be bound by the terms of the Remote Access Services Addendum hereto.
Collateral Access Agreements Such Grantor shall use commercially reasonable efforts to obtain a Collateral Access Agreement, from the lessor of each leased property, mortgagee of owned property or bailee or consignee with respect to the operator of any warehouse, processor or converter facility or other location (each of which is identified on Exhibit B hereto), where Collateral in excess of $1,000,000 is stored or located at any given time (other than (i) company-owned facilities and (ii) retail stores), which agreement or letter shall provide access rights, contain a waiver or subordination of all Liens or claims that the landlord, mortgagee, bailee or consignee may assert against the Collateral at that location, and shall otherwise be reasonably satisfactory in form and substance to the Administrative Agent. With respect to such locations or warehouse space leased as of the Effective Date and thereafter where Collateral in excess of $1,000,000 is stored or located (other than (i) company-owned facilities and (ii) retail stores), if the Administrative Agent has not received a Collateral Access Agreement as of the Effective Date (or, if later as of the date such location is acquired or leased), the Borrower’s Eligible Inventory at that location shall be subject to such Reserves as may be established by the Administrative Agent. After the Effective Date, no real property or warehouse space shall be leased by such Grantor (other than retail stores) and no Inventory shall be shipped to a processor or converter under arrangements established after the Effective Date, unless and until a satisfactory Collateral Access Agreement shall first have been obtained with respect to such location or if it has not been obtained, the Borrower’s Eligible Inventory at that location shall be subject to the establishment of Reserves acceptable to the Administrative Agent. Such Grantor shall timely and fully pay and perform its obligations under all leases and other agreements with respect to each leased location or third party warehouse where any Collateral is or may be located.
Network Access TENANT may find it necessary to purchase a network interface card, wireless PC card or other hardware in order to connect to the internet service. LANDLORD is not responsible for the purchase of these items and LANDLORD cannot guarantee compatibility with any device TENANT may have. The computer and network card must have software installed that supports the Internet Protocol commonly referred to as TCP/IP. Any conflicts between the software compatibility of the network and the TENANT’S computer operating system or any other feature will be the responsibility of the TENANT to resolve. LANDLORD will not be responsible for software issues related to the user’s personal computer.
Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.
