Security Services Addendum

1. INTRODUCTION

The Security Services offering by Phoenix NAP provides Clients with a scalable information security solution, capable of detecting and notifying on potential security threats against a Client’s environment. This proprietary set of systems and processes utilizes state of the art hardware, software, and security industry professionals to observe and monitor Client network(s), endpoint(s), and other related events to detect anomalous actions and security threats.

2. AGREEMENT

This Security Services Addendum (“SSA”) sets forth the specific terms and conditions under which Phoenix NAP (“PNAP”) shall supply Information Security Services to Client. The Master Service Agreement entered into between PNAP and Client, fully incorporates the terms herein and provides that this SSA, and Client’s execution of the Master Services Agreement constitutes acceptance of the terms and conditions stated herein. Capitalized terms used but not defined herein shall have the meanings set forth in the Master Services Agreement. The Initial Term length for this Service is set forth on the applicable Service Order Form (“SOF”), executed by PNAP and Client, referring to these Services. As referred to herein, “Agreement” means this Security Services Addendum, together with the MSA and all policies and addenda that are incorporated herein by reference, including the Statement of Work (SOW), Responsibility Matrix (“RM”), Service Level Agreement (SLA), Acceptable Use Policy (“AUP”), and Privacy Policy (“PP”). This Agreement sets forth the terms and conditions that apply to the Security Services Addendum.

3. GENERAL

PNAP will examine the Client’s current computer networking platform, its hosting, and data security requirements to the extent Client has provided PNAP access, and confirms that the agreed upon Service(s) may interact and operate with the Client’s platform and provide a secure environment in accordance with the specifications, and in accordance with industry standards set forth in the agreed upon Statement of Work (SOW).

If the agreement between PNAP and the Client is terminated or expires, Client shall have the option to either renew the agreement or replace the PNAP Security Services with a third-party provider of its choosing. Upon request, PNAP shall undertake commercially reasonable efforts to transition Client to the new provider as quickly, economically and efficiently as possible and if possible, will do so in a way that provides the most seamless and secure transition with minimal business interruptions to Client.

4. SERVICES AND FEATURES

Service Description
Threat Management Platform This product offering utilizes client provided security event logs from different sources (such as firewalls, switches, and servers) and correlates those logs with threat signatures, where once identified activity that may signal the operators of a potential threat event. These threat behavior patterns are gathered from, and updated based on subscribed industry threat intelligence feeds, proprietary threat intelligence, or other data provided by the Client.
Critical Environment Recovery The Critical Environment Recovery or Disaster Recovery Service is a long-standing offering that is now integrated into Data Security Cloud (DSC). As there is no such thing as a 100% secure and resilient network, the Critical Environment Recovery service allows for the tools and techniques to be used to recover and operationalize the environment quickly, be accessible and ready in your time of need.
Firewall Switch Management Many organizations do not have the skill and/or expertise on industry best practices to appropriately manage their firewalls and switches. Especially for companies using more advanced layer 7 application protection and routing methods. Internal personnel may not have adequate training or resources to effectively maintain and monitor these devices as designed. Additionally, when internal administrators do make changes to their firewalls and switches, they frequently do so without keeping adequate history of the changes, therefore not having the proper documentation required for compliance reasons. PNAP’s Firewall/Switch Management offering will include both the appropriate management of the firewalls and switches, as well as the necessary documentation, including managing and tracking the authentication for users making changes, as well as tracking the prior configurations to allow for the roll-back of changes if needed.
Vulnerability Assessment The Vulnerability Assessment offering scans Client approved internal networks, using automated tools that utilize known threat vectors to test for known vulnerabilities. Executed on a monthly basis, a comprehensive report is provided via encrypted email to the customer, based on the findings of this tool. This report should then be used as a pathway to mitigate these vulnerabilities or provide justification for moving relevant projects up the priority list that will eliminate these vulnerabilities.
Performance Monitoring Performance Monitoring includes reporting on performance trends, proactive monitoring of alerts, and conducting analyses on performance metrics, such as up/down frequency & bandwidth usage, processors, memory, and storage utilization.
End Point Security The End Point Security Service is designed to maintain the sanctuary of server and end-user devices. Partnered with Sophos, we provide a holistic solution offering that protects the customer utilizing advanced anti-malware signature and AI based tools, advanced analytical tools, and EDR functionality. Using similar tools on server platforms and workstation platforms, supplemented by the availability of integrated firewalls, we can track and detect vulnerabilities quicker, allowing for faster action towards mitigation. Resulting in a greatly limited breach or minimal downtime.

5. BEST PRACTICES

PNAP shall implement the following best practices with regard to development and deployment of the Products and Services. PNAP shall maintain appropriate systems security for the PNAP’s Service in accordance with commercially reasonable industry standards and practices designed to protect all data and information provided by or on behalf of Client that is input into, displayed on or processed by the PNAP’s Service and all output therefrom (“Client Data”) from theft, unauthorized disclosure and unauthorized access. Such systems security includes, among other things: (1) implementation of application vulnerability tests and mitigation processes; (2) direct all PNAP-Client electronic communications via a secure web portal, a secure file share, or encrypted email; and (3) the following safeguards:

  1. Authentication
    • All access is authenticated, communication secured using industry best practices, and logged.
    • Systems identity is tied to an individual user by the use of credentials and by a second factor authentication mechanism.
    • Reasonable authentication controls that conform to industry recognized standards are provided.
  2. Authorization
    • Ensure that authorized users are only allowed to perform actions within their privilege level.
    • Control access to protected resources based upon role or privilege level.
    • Mitigate and defend against privilege escalation attacks as feasible, to available technology standards and best practices.
  3. Password and Account Management
    • Passwords conform to best practices, including:
      • Encrypting passwords using “hashing” and “salting” techniques.
      • Enforcing password complexity.
      • Limiting failed attempts before account lockout.
      • Not allowing storage and transmittal of passwords in clear text.
      • Password reset does not send credentials.
    • Where appropriate, PNAP shall securely log (with time and date) commands requiring additional privileges to enable a complete audit trail of activities.
  4. Data Security
    • Data at Rest
      • Client Data is encrypted using industry best practices.
      • Backups of Client Data have the same controls as production data.
    • Data in Transit
      • Client Data in transit to or from Client will be encrypted (e.g., SSL, VPN, SFTP, certificate-based authentication).
    • Client Data sent over browser should use SSLv3 or better.
  5. Multi-Tenancy
    • In a multi-tenant environment, PNAP shall provide appropriate security controls and robust cryptographic methods to protect and isolate Client Data from other tenants.
  6. Administrative Access and Environmental Segregation
    • Applying Principle of Least Privilege: Proper controls should be in place to ensure that access is limited to personnel who must see Client Data in order to fulfill their job functions.
    • Where possible, confidential data should be masked with one-way hashing algorithms.
    • Client Data should not be replicated to non-production environments.
  7. Threat Management
    • Intrusion Detection
    • PNAP shall implement and maintain an intrusion detection monitoring process at the network and host level to protect PNAP Services and to detect unwanted or hostile network traffic. PNAP shall update its intrusion detection software continuously, on a scheduled basis following the availability of updates by the chosen software provider. PNAP shall implement measures to ensure that PNAP is alerted when the system or service detects unusual or malicious activity. PNAP shall notify Client within twenty four (24) hours of any significant intrusion that involves a breach of customer’s data.

    • Penetration Tests
    • PNAP shall conduct penetration tests at least once per year on its Client-wide computing environment through a 3rd party Qualified Security Assessor (QSA), and appropriately dispose of the risks identified. Due to the high-risk nature of these reports, the reports and findings will not be publicly disclosed, or made available for client inspection. PNAP will however make available upon request, a letter from the QSA of satisfactory disposition of identified threat concerns. Clients will not be authorized to conduct vulnerability scans, assessments, or penetration tests against the PNAP service infrastructure.

    • Infrastructure Security
    • PNAP shall configure the infrastructure (e.g., servers and network devices) and platforms (e.g., OS and web servers) to be secure following these best practices:

      • Audit Logging: Client authorizes PNAP to collect, use, store, transfer, monitor and otherwise process logs from all systems subscribed to PNAP’s Service. These log types include, but is not limited to, security logs, web server logs, application logs, system logs and network event logs. PNAP monitors its networks 24/7 using the latest SIEM and behavioral analytics technologies. The Client acknowledges that these logs can contain source and destination IP addresses, user accounts used, bad passwords attempted, click and screen entries, and other personally identifiable data elements.
      • Duplicate copies of these logs will be maintained, and an offsite archival copy will reduce risk of loss due to tampering.
    • Network Security
      • PNAP shall comply with industry standards, separating perimeter networks from endpoints hosted in the private network using industry standard firewalls or micro-segmentation techniques based on Software Defined Networking technologies. PNAP shall update and maintain it’s infrastructure using an industry standard maintenance and change control methodology.
      • PNAP shall monitor and test its perimeter devices on a regular basis, and, if deficiencies are discovered, PNAP shall promptly troubleshoot and remediate these deficiencies.
    • Vulnerability Management
    • In addition to the third-party vulnerability assessments described above, PNAP shall implement commercially reasonable processes designed to protect Client Data from system vulnerabilities, including:

      • Perimeter Scanning: PNAP shall perform perimeter scanning through the use of embedded sensors within PNAP’s infrastructure providing information to our centralized SIEM tool.
      • Internal Infrastructure Scanning: PNAP shall perform internal infrastructure scanning through the use of embedded sensors within PNAP’s infrastructure providing information to our centralized SIEM tool.
      • Malware Scanning: Where possible PNAP utilizes an advanced behavior and signature based anti-virus/anti-malware (APT) tool, along with application whitelisting techniques to protect its infrastructure from the threat of unauthorized malicious software.
    • Secure Configuration
    • PNAP utilizes an industry standard methodology for platform hardening and secure configuration, in order to reduce attack scope and surface. Through the use of micro-segmentation techniques, lateral communication is further restricted to known communication pairs and patterns.

  8. Security Procedures
    • Incident Response
    • PNAP shall maintain security incident management policies and procedures, including detailed security incident escalation procedures. In the event of a breach of PNAP’s security or confidentiality obligations, impacting a client's environment or data, PNAP agrees to notify affected Client(s) by telephone and email of such an event within twenty-four (24) hours of discovery. PNAP will also promptly perform an investigation into the breach, take appropriate remedial measures, and assign a Single-Point-of-Contact (SPoC). This SPoC or their designee, will be available for security questions or concerns twenty-four (24) hours per day, seven (7) days per week, during the scope of PNAP’s investigation.

    • Patch Management
    • PNAP shall use a patch management process and tool set to keep all servers up to date with appropriate security and feature patches.

    • Documented Remediation Process
    • PNAP shall use a documented remediation process designed to timely address all identified threats and vulnerabilities with respect to the PNAP Service.

  9. Employee Termination Procedures
    • PNAP shall promptly terminate all credentials and access to privileged password facilities, such as Identity and Access Management Systems, upon termination of employment.
  10. Governance
    • Security Policy
    • PNAP shall maintain a written information security policy that is approved annually by PNAP and published and communicated to all PNAP employees and relevant third parties. PNAP shall maintain a dedicated security and compliance function to design, maintain and operate security in support of its “trust platform” in line with industry standards. This function shall focus on system integrity, risk acceptance, risk analysis and assessment, risk evaluation, risk management and treatment statements of applicability and PNAP management.

    • Security Training
    • PNAP shall ensure, at no expense to Client, that all PNAP employees and Clients complete relevant training required to operationalize the procedures and practices outlined herein, including security awareness training, on at least an annual basis.

    • Security Reviews
    • PNAP and Client may meet at least once annually to discuss: (1) the effectiveness of the PNAP’s security platform; and (2) any updates, patches, fixes, innovations or other improvements made to electronic data security by other commercial providers or for other customers of PNAP that PNAP or Client believe will improve the effectiveness of the PNAP’s security platform for Client.

    • Third-Party Audits and Compliance Standards
      • PNAP shall provide Client with a copy of SOC2 or similar audit results, in no more than thirty (30) days after PNAP receives the results or reports. Client has the right to, or to engage a third party on its behalf to, visit PNAP’s offices up to four (4) times per calendar year in order to conduct due diligence and auditing procedures on PNAP’s business operations related to the PNAP’s Service in terms of technical infrastructure, system interaction, organization, quality, quality control, personnel involved with services for Client, and general resources in terms of skills and personnel.
      • PNAP will furnish evidence of a successful SSAE No. 18 audit upon Client request to the extent permitted by law and subject to applicable regulatory restrictions and confidentiality obligations. PNAP must verify that the audit certifies all infrastructure and applications that support and deliver services to Client Data.
      • PCI-DSS Compliance
      • PNAP shall maintain policies, practices and procedures sufficient to comply with the Payment Card Industry Data Security Standard, as the same may be amended from time to time, with respect to the PNAP’s Service.

      • Vulnerability Assessments
      • PNAP shall conduct application vulnerability assessments at least annually. These assessments will be conducted with a 3rd party Qualified Security Assessor (QSA). Due to the high-risk nature of these reports, the reports and findings will not be publicly disclosed, or made available for client inspection. PNAP will however make available upon request, a letter from the QSA of satisfactory disposition of identified threat concerns. Clients will not be authorized to conduct vulnerability scans, assessments, or penetration tests against the PNAP application platforms.

  11. Physical Security
  12. PNAP shall limit access to its facilities utilized in performing the PNAP’s Service to employees and authorized visitors using commercially reasonable industry standard physical security methods. At a minimum, such methods shall include visitor sign-ins, restricted access key cards and locks for employees; limited access to server rooms and archival backups; and burglar/intrusion alarm systems.

  13. Business Continuity
  14. PNAP shall have a business continuity plan in place for the restoration of critical processes and operations of the PNAP’s Service at the location(s) from which the PNAP’s Service is provided. PNAP shall also have an annually tested plan in place to assist PNAP in reacting to a disaster in a planned and tested manner. PNAP shall provide Client with a copy of its then-current plan promptly following Client’s written request for same.

  15. PNAP Internal Systems Backup Management
    • PNAP shall perform full backups of internal systems and database(s) containing Client Data no less than once per day without interruption of the PNAP Service. PNAP shall also provide off-site archival storage on no less than a weekly basis of all backups of the internal systems and database(s) containing Client Data on secure server(s) or other commercially acceptable secure media. Such data backups will be encrypted, sent off-site to a secure location each business day and stored/retained for seven (7) years.
    • In order to recover from a Datacenter failure Incident, the required backed-up data will be replicated over at least two (2) geographically dispersed data centers at any point in time. Backup snapshots may be periodically sent to another data center. Data retention for an in-datacenter failure Incident will utilize twenty-four (24) hourly snapshots, fourteen (14) daily backups and three (3) monthly backups. This backup policy is designed to support both a partial or full recovery of the system expediently.
  16. Right to Audit
  17. Client has the right to, or to engage a third party on its behalf to, at its own expense, visit PNAP’s offices once per calendar year in order to conduct due diligence and auditing procedures on PNAP’s business operations related to the PNAP’s Service in terms of technical infrastructure, systems interaction, organization, quality, quality control, personnel involved with services for customers, and general resources in terms of skills and personnel. Understanding the proprietary and intellectual property nature of this access, Client agrees to execute and abide by a Non-Disclosure Agreement, and limit the documentation or removal of this information from PNAPs premises.

6. CLIENT RESPONSIBILITIES

Client shall document and promptly report all errors or malfunctions of a system covered under this agreement to PNAP. PNAP shall provide all necessary spare parts and/or other hardware to maintain equipment owned by it necessary to the fulfillment of any service under this Schedule.

Client shall not use anything whether tangible or intangible which is appurtenant to and/or provided by this agreement for any unlawful purpose or for any purpose which is prohibited by PNAP’s Network Abuse Policy and/or Acceptable Use Policy as is posted on its website.

Customer acknowledges that PhoenixNAP performance and delivery of the Services are contingent upon: (A) Customer providing safe and hazard-free access to its personnel, facilities, equipment, hardware, network and information, and (B) Customer’s timely decision-making and provision of timely, accurate and complete information and reasonable assistance, including, granting of approvals or permissions, as (A) and (B) are deemed reasonably necessary and reasonably requested for PhoenixNAP to perform, deliver and/or implement the Services. Customer will promptly obtain and provide to PhoenixNAP any required licenses, approvals or consents necessary for PhoenixNAP’s performance of the Services. PhoenixNAP will be excused from its failure to perform its obligations under this Addendum to the extent such failure is caused solely by Customer’s delay in performing or failure to perform its responsibilities under this MSA and/or the Service Order/SOW.

7. STATEMENT OF WORK; RESPONSIBILITY MATRIX

A Statement of Work (“SOW”) and Responsibility Matrix (“RM”) shall be used to specify the specific duties, scope, locations, deliverables, standards, activities, and general requirements for any Information Security Service offered by PNAP to a Client.

8. DISCLAIMERS

  1. No Product Warranty
  2. PNAP makes no express or implied warranties of product merchantability or fitness for any particular purpose. While all services are designed to be resilient, it is up to the Client to plan for disasters and it is always recommended to keep an off-site backup of critical data in event of critical failure or disaster.

  3. Disclaimer of Warranty
  4. PNAP WILL NOT BE LIABLE FOR ANY LOSS OR DAMAGE CAUSED BY A DISTRIBUTED DENIAL-OF-SERVICE ATTACK, VIRUSES OR OTHER TECHNOLOGICALLY HARMFUL MATERIAL THAT MAY INFECT YOUR COMPUTER EQUIPMENT, COMPUTER PROGRAMS, DATA NETWORK OR OTHER PROPRIETARY MATERIAL RESULTING FROM YOUR USE OF THE SERVICES, PHOENIX NAP’S WEBSITE OR THE SERVICE OR ITEMS PURCHASED OR OBTAINED THROUGH THE WEBSITE OR THE SERVICE OR TO YOUR DOWNLOADING OF ANY MATERIAL POSTED ON IT, OR ON ANY WEBSITE LINKED TO IT. NEITHER PHOENIX NAP NOR ANY PERSON ASSOCIATED WITH PHOENIXNAP MAKES ANY WARRANTY OR REPRESENTATION TO ANY USER WITH RESPECT TO THE COMPLETENESS, SECURITY, RELIABILITY, QUALITY, FUNCTIONALITY OR AVAILABILITY OF THE SERVICES. WITHOUT LIMITING THE FOREGOING, NEITHER PHOENIX NAP NOR ANYONE ASSOCIATED WITH PHOENIXNAP REPRESENTS OR WARRANTS THAT THE SERVICE WILL BE RELIABLE, ERROR-FREE, INTRUSION PROOF OR UNINTERRUPTED, THAT DEFECTS WILL BE CORRECTED, FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS OR THAT THE SERVICES WILL OTHERWISE MEET THE NEEDS OR EXPECTATIONS OF CLIENTOR ANY USER. EXCEPT FOR THE WARRANTY SET FOR ABOVE, PHOENIXNAP PROVIDES THE SERVICE, AND ALL ON AN “AS IS” AND “AS AVAILABLE” BASIS, WITHOUT ANY WARRANTIES. PHOENIX NAP HEREBY DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR PARTICULAR PURPOSE.

    PHOENIX NAP’S AGGREGATE LIABILITY (WHETHER IN CONTRACT, TORT OR OTHERWISE) FOR ALL CLAIMS OF LIABILITY ARISING OUT OF, OR IN CONNECTION WITH, THE AGREEMENT SHALL NOT EXCEED THE AMOUNTS PAID BY CLIENTFOR THE SERVICES GIVING RISE TO A CLAIM FOR LIABILITY. THE FOREGOING DOES NOT AFFECT ANY WARRANTIES WHICH CANNOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW. THIS SECTION SHALL SURVIVE ANY EXPIRATION OR TERMINATION OF THE AGREEMENT.

    IN NO EVENT WILL PHOENIX NAP, ITS AFFILIATES OR THEIR LICENSORS, SERVICE PROVIDERS, EMPLOYEES, AGENTS, OFFICERS OR DIRECTORS BE LIABLE FOR DAMAGES OF ANY KIND, UNDER ANY LEGAL THEORY, ARISING OUT OF OR IN CONNECTION WITH YOUR USE, OR INABILITY TO USE, THE SERVICES OR ANY WEBSITES ASSOCIATED WITH IT, INCLUDING ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO, PERSONAL INJURY, PAIN AND SUFFERING, EMOTIONAL DISTRESS, LOSS OF REVENUE, LOSS OF PROFITS, LOSS OF BUSINESS OR ANTICIPATED SAVINGS, LOSS OF USE, LOSS OF GOODWILL, LOSS OF DATA, AND WHETHER CAUSED BY TORT (INCLUDING NEGLIGENCE), BREACH OF CONTRACT OR OTHERWISE, EVEN IF FORESEEABLE. THE FOREGOING DOES NOT AFFECT ANY LIABILITY WHICH CANNOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW.

  5. Limitation on Time to File Claims
  6. Any cause of action or claim You may have arising out of or relating to these terms of use, the service or the website must be commenced within one (1) year after the cause of action accrues, otherwise, such cause of action or claim is permanently barred.

  7. Notice of Loss
  8. PNAP is not liable for any loss or corruption of data. Clients are always encouraged to retain a copy of data. In the event of loss or destruction of or damage to Client data, PNAP will provide notification to Client via e-mail to an address provided by the Client. Client must ensure that the e-mail address is valid.

9. CONSENT

By entering this Agreement and by using the Services, Client consents to, and hereby agrees that Phoenix NAP may access Client’s networks and computer systems including the access to and use, disclosure, interception, transmission, receipt, analysis, processing, copying, editing, encryption, decryption, and storage of Client information and that of its employees, agents and those it authorizes to use the Services, whether encrypted or in clear text (“Client’s Information”) for the purpose of providing the Services, including, without limitation, analyzing Client’s network traffic, and for storage and retention of Client’s Information for future reference and analysis. Client represents and warrants that it complies with all applicable data collection and transfer laws and regulations of the countries in which it operates and that it has duly obtained all consents, permits or licenses, in writing or electronically that may be necessary under applicable laws from its employees, agents, and those it authorizes to use the Services in order to enable Phoenix NAP to provide the Services under the Agreement. Prior to using the Services, or at any other time reasonably determined by Phoenix NAP, Client will provide Phoenix NAP true and correct copies of such consents.

9. INDEMNITY

Client shall defend, indemnify and hold harmless the Phoenix NAP Indemnified Parties from and against any damages, orders, decrees, judgments, liabilities, claims, actions, lawsuits, costs and expenses (including, without limitation, costs of litigation and attorneys’ fees) (“Claims”) incurred by the Phoenix NAP Indemnified Parties or finally adjudicated against the Phoenix NAP Indemnified Parties arising out of or resulting from: (i) infringement of intellectual property rights, including, without limitation, copyright, trademark, trade secret, patent, and common law rights in connection with Client’s Information, networks, or computer systems; (ii) violation of applicable laws or policies by Client, including, without limitation in connection with Client Information, networks, or computer systems; (iii) failure by Client to secure all necessary consents, permits, and licenses, including without limitation, in connection with Customer’s Information, networks, or computer systems; (iv) breach of warranty by Client; (v) breach of this Agreement by Client; (vi) use of Services by Client or Client Affiliates; (vii) negligence, intentional misconduct or other wrongful acts or omissions by Customer; and (viii) Claims alleging that Phoenix NAP was not authorized to provide Services requested by Customer.

This Section states each party’s exclusive remedies for any third-party claim or action, and nothing in this Agreement or elsewhere will obligate either party to provide any greater indemnity to the other.

10. SUBCONTRACTING

Phoenix NAP may assign, subcontract or delegate in whole or in part this Agreement, or any rights, duties, obligations or liabilities under this Agreement, by operation of law or otherwise, provided that Phoenix NAP shall remain responsible for the performance of Services under this Agreement. Otherwise, neither party may assign this Agreement without the permission of the other party, which permission shall not be unreasonably withheld, conditioned or delayed.

11. CHARGES

The subsections of this section define the recurring and non-recurring charges and fees pursuant to this schedule.

  1. MONTHLY RECURRING FEES
  2. The Initial Monthly Recurring Charges are the initial monthly fees charged for this Schedule. This fee may be modified by mutual agreement of Client and Provider based on changes to the initial configurations, covered devices, or other similar environment variables.

  3. NON-RECURRING SERVICE FEES
  4. The non-recurring services and fees associated with this Schedule include but are not limited to any Out-of-Scope fees and/or the fees for any associated labor and other services provided under a Statement of Work or for the migration/installation/implementation of Client’s production environment from its current state to Provider’s Cloud/Hosting environment or for other purposes agreed to by Provider and Client, including, but not limited to, those defined in a Statement of Work as one time or non-recurring fees or services whether created at the time of or subsequent to the execution of this agreement.

  5. INITIAL SETUP FEES
  6. The initial setup fees and charges for this Schedule are the one-time non-recurring fees associated with the initial setup of Client’s services. This fee may be modified by mutual agreement of Client and Provider based on changes to the initial configurations, scope, covered devices or other similar environment variables. Initial Setup Fees do not include the charges for Data Migration. Data Migration Fees will be specified and covered under a separate Statement of Work or Project.

v.2; 04122019