Hosting Environment. Collectively the platform, environment, and conditions on, in, or under which the Licensed Software is intended to be installed and operate, as set forth in this Contract and the Contract Exhibits, including such structural, functional and other features, conditions and components as hardware, operating software, System architecture and configuration.
Hosting Environment. HMH will provide all hardware, software, telecommunication services and other items necessary for the proper operation and hosting of the Software and Customer Materials (the “Hosting Environment”). The Hosting Environment is part of the “System,” as such term is defined in the Agreement. Customer is responsible for providing client-side computers, equipment, Internet connections, software and other system requirements.
Hosting Environment. Scholastic will provide all hardware, software, telecommunication services and other items necessary for the proper operation and hosting of the Software and Customer Materials (the “Hosting Environment”). Customer is responsible for providing client-side computers, equipment, Internet connections, software and other system requirements.
Hosting Environment. Digital Sandbox’s Hosting environment consists of the following elements:
(i) an IIS web server with authentication provided through the use of digital certificates, (ii) a dual hardware firewall architecture to create a “demilitarized zone” (“DMZ”), and (iii) a dedicated client network environment comprised of the Licensed Software, web server, database and reporting servers. Only required/authorized applications will be installed within the dedicated client network environment and on the servers employed to host the Licensed Software on Customer’s behalf. If the Order Form indicates a dedicated server will be used for Customer, access to such dedicated servers will be limited to those Registered Users with a need for access and Digital Sandbox employees providing technical services to Customer or Registered Users.
Hosting Environment. OPIE will provide all hardware, software, materials, Internet connections, telecommunication services and other items necessary for the proper operation and hosting of the Software utilizing one (1) set of servers for production use (the “Hosting Environment”). OPIE will apply application patches as requested at no additional charge. OPIE will own all right, title, and interest in and to such items. Customer is responsible for providing client-side computers and software meeting the technical requirements OPIE provides for the Software being hosted hereunder.
Hosting Environment. The CCRS solution will be hosted on a combination of private and public cloud solutions. All hosting environments are in the Continental United States. The private Optum Cloud environment is hosted in Optum-owned data centers and meets the requirements for HiTRUST-certification levels of privacy and security. Commercial public cloud infrastructure is FedRAMP compliant. Connection to the States system by the Contractor’s solution will be in alignment with the State’s Enterprise Architecture Framework (please refer to the California Enterprise Architecture Framework located at xxxxx://xxx.xx.xxx/services/wp-content/uploads/sites/2/sites/2/2017/04/EA- California-Enterprise-Architecture-CEAF2-Framework-V2.pdf) [A1]. Contractor plans to transition components of the CCRS solution from the Optum Private Cloud to a Commercial Cloud (Azure) aligned with the requirements defined in this Statement of Work.
Hosting Environment xxxx agrees to provide the following services: • Redundancy. At least two (2) servers are used in conjunction on more than one location, to ensure that website content will still be served, should one server fail. • Backups are stored off-site, i.e. not on the web/mail server itself. Although great care is taken to ensure that scheduled backups run as planned, clients are encouraged to also take their own backups on a regular basis. • Disaster Recovery o In the unlikely event of a COMPLETE disaster at the primary premises, recovery from a total application loss, all DNS registrations will have to be re-executed. Due to the global propagation, nature of this process recovery could be delayed by up to 48 hours. • Services o The following are some standard services we will be providing on our Linux servers. ▪ Web Services ▪ SMTP/POP/IMAP/ email services ▪ FTP Service ▪ MySQL Server ▪ More online at xxxxx://xxx.xxxxxxx.xxxx • No guarantees are provided with regards to bandwidth. We are part of a larger infrastructure that varies in activity. We are, however, confident that we meet and often exceed industry standards. • All information is treated as confidential. This includes the files, client details, data and other information. No information is shared, sold, or exposed by Xxxxxxx.xxxx in any way unless requested by the client in writing. • Where possible all software security patches get applied and procedures are followed to ensure the highest level of security and uptime can be guaranteed. • Due to the nature of the Internet and the Linux platform, Xxxxxxx.xxxx is not responsible for any breaches in security of those systems. We will however respond diligently to any possible threat. Where not otherwise specified, either party requires a 30-calendar day cancellation notice.
Hosting Environment. 4.2.1 It is anticipated that the take up of the service will be gradual with the user and data volumes increasing over the 4 year life of the framework after the initial marketing campaign in quarter 2/3 of 2008. The Service Provider shall provide a hosting environment that has the potential to cater for the increase in these volumes. For guidance only, an early indication of potential customers is approximately 40 Government Departments each with approximately 5 users.
Hosting Environment. All data is kept in Google Cloud Platform servers. Their security whitepaper is here: xxxxx://xxxxx.xxxxxx.xxx/security/overview/whitepaper All data is kept in the cloud in the Google Cloud Platform in the us-central region (Iowa) xxxxx://xxxxx.xxxxxx.xxx/compute/docs/regions-zones. However web pages and APIs are served with geo-redundancy to CDNs closest to our customers, and some data may be cached in other regions of the world in a transient manner for performance reasons. All customer access keys are kept in a database separate from the code, which can only be accessed from within the application. We currently use Google Cloud Scanner xxxxx://xxxxx.xxxxxx.xxx/security-command-center/docs/how-to- web-security-scanner-custom-scans to perform daily automated penetration testing against xxxxx://xxx.xxxxxxxxx.xxx and all public APIs, as we as our staging environments. Any vulnerabilities introduced by code or third party libraries are dealt with as Priority 1 issues and are solved as soon as possible. Blinkfire does not allow login through username or passwords, but only through third party login mechanisms of Facebook, Twitter, Google, or Microsoft. We rely on your security policies with those platform to protect your login to Xxxxxxxxx.xxx Blinkfire Analytics supports 2 Factor Authentication, though it is not required. It is recommended that all customers require their users of Blinkfire to turn on 2 Factor Authentication. Xxxxxxxxx.xxx does not store any user passwords.
Hosting Environment. As between Customer and Provider, Provider is, and will remain, the sole and exclusive owner of all right, title, and interest in and to the Hosting Environment, including all Intellectual Property Rights therein. Provider hereby grants to Customer a nonexclusive, royalty-free, irrevocable (except as provided herein) right and license throughout the world during the Term and use via such access the Hosting Environment in connection with the Hosting Services. Customer may grant sublicences in all or any of the foregoing to Customer Service Providers solely to enable such Customer Service Providers to perform services to Customer in connection with the Platform or the Hosting Services.
