Operating System Access Control Sample Clauses

Operating System Access Control. OneStream will: (i) Require secure login procedures to access operating systems; (ii) Require that users use unique user IDs; (iii) Restrict the use of utility programs that can override system and application controls to circumstances where such use is required; and (iv) Shut down inactive sessions after a defined period of inactivity.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Operating System Access Control. To protect against unauthorized access or misuse of Company Data or Confidential Information residing on Supplier Information Processing Systems, Supplier will: (a) Ensure that access to operating systems is controlled by a secure log-on procedure; (b) Ensure that Supplier Information Processing System users have a unique identifier (user ID); (c) Ensure that the use of utility programs that are capable of overriding system and application controls are highly restricted and tightly controlled. Ensure that inactive sessions are shut down after a defined period of inactivity; and (d) Employ restrictions on connection times to provide additional security for high risk applications.
Sample 1Sample 2Sample 3See All (4)
Operating System Access Control. To protect against unauthorized access or misuse of Sensitive Information residing on Service Provider Information Processing Systems, Service Provider will: Ensure that access to operating systems is controlled by a secure log-on procedure and limited to role based necessity. Ensure that Service Provider Information Processing System users have a unique identifier (user ID). This account is used to identify each person’s activity on Service Provider’s Information Processing Systems network, including any access to employee or City data. Ensure that the use of utility programs that are capable of overriding system and application controls are highly restricted and tightly controlled, with access limited to those employees whose specific job function requires such access. Ensure that inactive sessions are automatically terminated when technically possible after a defined period of inactivity. Employ idle time-based restrictions on connection times when technically possible to provide additional security for high risk applications. Ensure that current industry best practice standard authentication mechanisms for wireless network users and equipment are in place and updated as necessary. Ensure authentication methods are used to control access by remote users, with unique User Identifiers.
Sample 1Sample 2Sample 3See All (4)
Operating System Access Control. To protect against unauthorized access or misuse of Recipient Confidential Information residing on Provider Information Processing Systems, Provider will: 9.4.1 Ensure that access to operating systems is controlled by a secure log-on procedure. 9.4.2 Ensure that Provider Information Processing System users have a unique identifier (user ID) or that a documented and approved exception request exists. 9.4.3 Ensure that the use of utility programs that are capable of overriding system and application controls are highly restricted and tightly controlled. 9.4.4 Ensure that inactive sessions are shut down after a defined period of inactivity.
Sample 1Sample 2
Operating System Access Control. To protect against unauthorized access or misuse of Protected Information, TrueCar will: i. Control access to operating systems by use of a secure log-on procedure. ii. Use unique identifiers (e.g., user IDs) to uniquely identify Information Processing System users. iii. Monitor and control access to utility programs that are capable of overriding system and application controls. iv. When technically possible and reasonable, shut down inactive sessions after a defined period of time. [***] Information has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. v. When technically possible and reasonable, employ restrictions on connection times to high risk applications.
Sample 1
Operating System Access Control. To protect against unauthorized access or misuse of ADT Data residing on Xxxxx.xxx Information Processing Systems, Xxxxx.xxx will: a. Ensure that access to operating systems is controlled by a secure log-on procedure; [***] = CONFIDENTIAL TREATMENT REQUESTED b. Ensure encrypted communications (SSH, HTTPS, etc.) are used for administrative access to production systems and applications when not physically present at the device; and c. Ensure that the use of utility programs that are capable of overriding system and application controls are highly restricted and tightly controlled.
Sample 1
Operating System Access Control. Flo Recruit implements operating system access controls that reasonably protect the systems from compromise. Protections shall include but are not limited to appropriate system authorization and management.
Sample 1
AutoNDA by SimpleDocs
Operating System Access Control. Sisense implements operating system access controls that reasonably protect the systems from compromise. Protections shall include but are not limited to appropriate system authorization and management.
Sample 1

Related to Operating System Access Control

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization.

  • 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.

  • Data Access Control Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage.

  • Access Control Supplier will maintain an appropriate access control policy that is designed to restrict access to Accenture Data and Supplier assets to authorized Personnel. Supplier will require that all accounts have complex passwords that contain letters, numbers, and special characters, be changed at least every 90 days, and have a minimum length of 8 characters.

  • 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.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Physical Access Control Unauthorized persons are prevented from gaining physical access to premises, buildings or rooms where data processing systems that process and/or use Personal Data are located.

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Access Controls The system providing access to PHI COUNTY discloses to 20 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 21 must use role based access controls for all user authentications, enforcing the principle of least privilege.

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