Custom Hosting Terms

Custom Hosting Terms 

These Custom Hosting Terms are applicable to Cyver Core Subscribers who have opted into the Cyver Core SaaS Subscription with Managed Deployment Add-on with either custom hosting in the Subscriber’s Azure cloud subscription or custom hosting on premises in the Subscriber’s Azure stack environment. 

The nature of this custom hosting means that Cyver is not capable of maintaining the standard terms delivered under our ToS, Subscription Agreement, or Premium Service Level Agreement. Therefore, by selecting the Managed Deployment Add-on, you are opting into the following custom terms. 

Under the Custom Hosting Terms, the Cyver Core application is installed by the Cyver team on either the Subscriber’s Azure cloud subscription or custom hosting on premises in the Subscriber’s Azure stack environment. 

Cyver Core is responsible for: 

• Installing and deploying the Cyver Core application 
• Code and platform maintenance and updates 
• Monitoring the application and delivering that data to the Subscriber 
• Providing advice on capacity and resource needs to the Subscriber 

The Subscriber is responsible for: 

• Maintaining compliance and meeting security requirements in their environment.
• Maintaining performance and uptime. 
• Providing access to the Cyver team so the Cyver team can deliver updates and maintenance 
• Providing the necessary resources for the platform to run.

Changes to the Premium SLA 

Deploying the Cyver Core application on the Subscriber’s Azure cloud subscription or in the Subscriber’s Azure stack environment changes the nature of how Cyver is able to deliver our Premium SLA. With that in mind, Subscribers opting into the Managed Deployment Add-On agree to the following changes to the SLA: 

• Subscriber takes on full responsibility for Application availability with the exception of code and platform-related issues
• Category 10 from the Premium SLA is not applicable 
• Data Traffic is not applicable 

View the full Premium SLA here. 

Cyver will build and deliver access to a monitoring dashboard to the Subscriber. However, the Subscriber is fully responsible for acting on data. 

Changes to Security and Compliance Terms 

Cyver cannot maintain security and settings necessary for SOC2 compliance for a Cyver Core application deployed in the Subscriber’s Azure cloud subscription or in the Subscriber’s Azure stack environment. The Subscriber’s compliance fully depends on security and settings on the Subscriber’s Azure technologies. 

Opting for the Managed Deployment Add-on means that Cyver Core will cede responsibility for items from the Security Policy to the Subscriber. These include: 

• Security of Facilities 
• Network Security 
• Network Architecture
• Network Vulnerability Scanning 
• Third-party penetration tests 
• Intrusion detection and prevention 

Cyver will continue to maintain the rest of the security policy, providing we have adequate access to the Subscriber’s environment to do so. In addition, Cyver will set up and maintain the same security measures as on our own Azure stack. 

Infrastructure and Resources

The Subscriber commits to taking full responsibility for providing the needed resources and infrastructure for the Cyver Core application. The Cyver team will advise on resource needs. However, the Subscriber is fully responsible for providing the resources and for infrastructure including paying any associated fees for those resources. Cyver will not pay for or reimburse for the cost of those resources. 

Cyver will set up and maintain Infrastructure in full accordance with Cyver’s standards and designs. 

In the case the Subscriber makes changes to the infrastructure or settings resulting in damage or impact to the application, Cyver Core can offer assistance, for an additional professional services fee. 

Product Updates and Access 

Cyver commits to maintaining the application including product updates, bug fixes, and other necessary changes. However, the Subscriber is responsible for ensuring that Cyver has adequate access to do so. 

This includes: 

• A full access account during initial installation, which should be deactivated after installation. The Subscriber will commit to reactivating this full access account on-demand to enable special maintenance. 
• A service account for product updates, which should be always active 

This maintenance is covered under the cost of the Managed Deployment Add-on fee and will be included as part of the Subscription Agreement. However, if the Subscriber does not provide Access for updates and service, Cyver will not be held liable or responsible for providing it. 

Intellectual Property 

The Cyver Core application is installed on the Subscriber’s Azure cloud subscription or in the Subscriber’s Azure stack environment. This means that the Subscriber has full access to the infrastructure and the code. The Subscriber is not licensed to inspect, modify, or copy the code outside of what is necessary to host the Cyver Core application on its Azure environment. The Subscriber remains bound by the intellectual property terms of the Terms of Service. 

Cyver’s code, application settings, infrastructure settings are confidential and may not be disclosed outside of the Subscriber’s organization or outside of a need-to-know basis for normal application usage and maintenance. The Subscriber commits to maintaining confidentiality of Cyver properties with all persons and entities granted access to Cyver confidential data. 

 If The Subscriber makes any changes to the code, it is against the Terms of Service of Cyver Core and at their own risk. 

By opting for a Managed Deployment Add-on, you automatically agree to these updated Custom Hosting Terms.