Remote Access Sample Clauses

Remote Access. As applicable, if Netsync requires remote access to County Systems for support, installation, integrations, configurations, and/or maintenance of Netsync’s Services, except as otherwise agreed by the parties and approved by the County’s Director of Information Technology and Chief Information Officer in writing, the below requirements must be met before Netsync is granted remote access to County Systems: (A) Netsync will adhere to the restricted and monitored channels that are provided by the County, or other technologies approved in advance in writing by the County’s Director of Information Technology and Chief Information Officer. (B) Netsync will neither implement nor deploy a remote access solution which bypasses and/or is designed to bypass County provided or approved controls. Netsync will not access County Systems via unauthorized methods. (C) Netsync’s remote access to County Systems will only be requested and activated on as-needed basis and disabled when not in use. (D) Remote access is restricted only to County Systems necessary for Netsync to conduct their services and/or provide Services to County pursuant to this Agreement. (E). Netsync will allow only its Workforce approved in advance by County to access County Systems. Netsync will promptly notify County whenever an individual member of Netsync's Workforce who has access to County Systems leaves its employ or no longer requires access to County Systems. Netsync will keep a log of access when its Workforce remotely accesses County Systems. Netsync will supply County with evidence of access logs concerning remote access to County Systems upon written request from County. Such access logs will be provided to County, within three business days from the date of County’s request. These requests may be used to confirm compliance with these terms and/or to investigate a security incident. (F) If any member(s) of Netsync’s Workforce is provided with remote access to County Systems, then Netsync’s Workforce will not remotely log-in to County Systems from a public internet access device (e.g., airport computer terminal, or Internet café). This is due to the possibility of sensitive information being monitored by video or computer surveillance in public areas. (G) Failure of Netsync to comply with this Section may result in Netsync and/or Netsync’s Workforce losing remote access to County Systems. County reserves the right at any time to disable remote access to protect County Systems. (H) For purposes...

Remote Access. Vendor or an Associate, when providing services under the Assurance Plan, as part of Premium Technical Support or in connection with other services, may need to remotely connect to, and take control of, your equipment in order to resolve the issues that you are experiencing. In connection with this remote connection session: (a) The Associate may need to run various scripts on your equipment, make changes to its configuration, install and uninstall software, and make other changes to the equipment and/or software settings of such equipment as may be necessary to address your issues. You understand that the Associate may, but is not obligated to, install and remove various proprietary or third party software tools where the Associate deems it necessary to assist you with the issues that you are experiencing. Elements of such software are protected by law, including copyright. (b) You acknowledge and agree that, by authorizing the Associate to establish a remote connection session, you grant Vendor (and partners and contractors acting on Vendor’s behalf) full or limited access to your equipment, software and network (depending on your equipment, software and network configuration), and authorize Vendor to make such modifications as described above or as otherwise advised by the Associate during delivery of the Solution. You acknowledge and agree that the Associate, or you acting on the Associate’s direction may alter, delete or corrupt software or data on your equipment, change equipment, software or network settings, or otherwise interfere with the proper operation of your equipment, software or network. (c) You acknowledge and agree that the Associate may have access to any information stored on your Device. Associates are trained not to access more information than necessary to resolve the issues for which you are requesting the Associate’s support. You must nevertheless remain in front of your Device screen to observe the actions of the Associate while he or she delivers the Solution on your Device. You will have the opportunity to end the live support session at any time by advising the Associate or disconnecting the remote connection session.

Remote Access. Remote access to the Coinbase network by authorized personnel is encrypted and requires multifactor authentication (MFA) for remote access, including X509 certificate and username/password login credentials. For production infrastructure access, use of VPN is also enforced. Coinbase’s network follows zero trust principles; any non-Coinbase devices that may access the network have no privileged access and must rely on strong identity controls to access Coinbase resources. Coinbase office networks are treated as untrusted by default. While WPA-PSK encryption is required to access office Wi-Fi, devices on this network are not automatically granted access to corporate or production systems. Users that wish to have corporate email on their mobile devices must enroll in Coinbase’s mobile device management (MDM) solution. Rooted devices are not permitted. Company-owned computers are managed and kept up-to-date with the latest operating system, antivirus, and productivity software updates. All hard drives are encrypted. Upon return and prior to reissuance of an authorized laptop, the laptop must be completely wiped.

Remote Access. Users may access the licensed device from another device using remote access technologies, but only on devices separately licensed to run the same or higher edition of this software.

Remote Access. The ISP will restrict remote access to BNY Mellon systems to authorized users using multifactor authentication or equivalent safeguard, and will require such access to be logged.

Remote Access. As applicable, if HRS requires remote access to County Systems for support, installation, integrations, configurations, and/or maintenance of HRS’s product Services, except as otherwise agreed by the parties and approved by the County’s Director of Information Technology and Chief Information Officer in writing, the below requirements must be met before HRS is granted remote access to County Systems: 26.1 HRS will adhere to the restricted and monitored channels that are provided by the County, or other technologies approved in advanced in writing by the County’s Director of Information Technology and Chief Information Officer. 26.2 HRS will neither implement nor deploy a remote access solution which bypasses and/or is designed to bypass County provided or approved controls. HRS will not access County Systems via unauthorized methods. 26.3 HRS’s remote access to County Systems will only be requested and activated on as- needed basis and disabled when not in use. 26.4 Remote access is restricted only to County Systems necessary for HRS to provide Services to County pursuant to this Addendum. 26.5 HRS will allow only its Workforce approved in advance by County to access County Systems. HRS will promptly notify County whenever an individual member of HRS's Workforce who has access to County Systems leaves its employ or no longer requires access to County Systems. HRS will keep a log of access when its Workforce remotely accesses County Systems. HRS will supply County with evidence of access logs concerning remote access to County Systems upon written request from County. Such access logs will be provided to County, within three business days from the date of County’s request. These requests may be used to confirm compliance with these terms and/or to investigate a security incident. 26.6 If any member(s) of HRS’s Workforce is provided with remote access to County Systems, then HRS’s Workforce will not remotely log-in to County Systems from a public internet access device (e.g., airport computer terminal, or Internet café). This is due to the possibility of sensitive information being monitored by video or computer surveillance in public areas. 26.7 Failure of HRS to comply with this Section may result in HRS and/or HRS’s Workforce losing remote access to County Systems. County reserves the right at any time to disable remote access to protect County Systems. 26.8 For purposes of this Section, “Workforce” means employees, agents, subcontractors (where permitted...

Remote Access. In order to assist DI in meeting the commitments above, ▇▇▇▇▇▇▇▇ agrees to provide an approved remote method to the devices running the Software with connectivity to the Software and access that permits connectivity and administration using Software’s administration tools accessing the database engine.

Remote Access. Customer must provide necessary remote access, required information, and support for the Equipment to connect to Philips Remote Service (PRS). PRS is the basis for Services delivered under this Exhibit. Customer waives all rights to services and service deliverables under this agreement unless PRS connectivity is enabled and maintained.

Remote Access. No more than once every 90 days, you may designate a single user who physically uses the licensed device as the licensed user. The licensed user may access the licensed device for a period of up to 365 days from the last physical use. Other users, at different times, may access the licensed device from another device using remote access technologies, but only on devices separately licensed to run the same or higher edition of this software.