OOB Access and No OOB Access Sample Clauses

Open Split View

Download

Share

Cite

OOB Access and No OOB Access. Managed Devices under Cloud-Controlled Routing do not require OOB Access.

Sample 1

Save

Copy

Related to OOB Access and No OOB Access

• ICANN Access Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC.

• Additional Access Rights For the avoidance of doubt any grant of Access Rights not covered by the Grant Agreement or this Consortium Agreement shall be at the absolute discretion of the owning Party and subject to such terms and conditions as may be agreed between the owning and receiving Parties.

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

• EU Access SAP will use only European Subprocessors to provide support requiring access to Personal Data in the Cloud Service and SAP shall not export Personal Data outside of the EEA or Switzerland unless expressly authorized by Customer in writing (e-mail permitted) on a case by case basis; or as excluded under Section 9.4.

• Technology Access A. Contractor expressly acknowledges that state funds may not be expended in connection with the purchase of an automated information system unless that system meets certain statutory requirements relating to accessibility by persons with visual impairments. Accordingly, Contractor represents and warrants to System Agency that the technology provided to System Agency for purchase (if applicable under this Contract or any related Solicitation) is capable, either by virtue of features included within the technology or because it is readily adaptable by use with other technology, of:

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

• Service Access Access to the clinical parts of our Site is restricted to Users. Users of our Site are provided with unique User IDs by the Clinic with which they are associated and must choose a password of their choice to sign on to our Site. Users must provide personal contact information, and you must ensure that your information is kept up to date at all times. User IDs and passwords constitute an electronic signature and will be used by us to authenticate access to our Site. If a User opts to sign onto Xxxxxx.xxx, the User will be able to take advantage of the non- public sections of our Site. If a User opts not to sign onto our Site, their access to our Site will be restricted to the public sections of our Site only. If you are provided with a User ID, password or any other piece of information as part of our security procedures, you must treat such information as confidential, and you must not disclose it to any third party. We have the right to disable any User ID at any time, if in our opinion, you have failed to comply with any of the provisions of this Agreement. You may only use our Site as set out in this Agreement. Any illegal or unauthorized use of our Site shall constitute a violation of this Agreement. You do not have permission to access our Site in any way that violates this Agreement or breaches any applicable law. You agree to keep your and your Patients’ Data accurate, current and complete. You may print off or download extracts of page(s) from our Site for your use in Patient care or insertion into a Patient’s electronic health records only.

• Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except:

• Parent Right to Access and Challenge Student Data The LEA shall establish reasonable procedures pursuant to which a parent, as that term is defined in 105 ILCS 10/2(g), may inspect and/or copy Student Data and/or challenge the accuracy, relevance or propriety of Student Data, pursuant to Sections 5 and 7 of ISSRA (105 ILCS 10/5; 105 ILCS 10/7) and Section 33 of SOPPA (105 ILCS 85/33). The Provider shall respond to any request by the LEA for Student Data in the possession of the Provider when Provider cooperation is required to afford a parent an opportunity to inspect and/or copy the Student Data, no later than 5 business days from the date of the request. In the event that a parent contacts the Provider directly to inspect and/or copy Student Data, the Provider shall refer the parent to the LEA, which shall follow the necessary and proper procedures regarding the requested Student Data.

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