Common use of Testing of MNDR Services Clause in Contracts

Testing of MNDR Services. Customer may test MNDR Services by scheduling and staging simulated or actual adversarial activity. These activities may be conducted by the Customer or a third party contracted by the Customer. Testing of MNDR Services should be communicated to Arista in advance of such activity in writing or email to ensure that Arista have been properly notified of such activities. During this period SCA’s and reporting activities may not apply. In addition, Customer is obligated to share the result of all such tests with Arista and will maintain the results as Confidential Information disclosing the results only to such parties having a need to know who are subject to confidentiality obligations consistent with the Agreement. This Appendix A to the Awake Security Services Exhibit supplements Arista’s Standard Warranty with respect to Arista Software Products that are provided as a part of the Awake Security Platform. Customer has the option to purchase upgraded support see Arista’s A-Care offering description at: ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇.▇▇▇/assets/data/pdf/A-CareServicesOverview.pdf 1. Customer Responsibilities. To facilitate the identification and correction of Defects, Customer is required to assist Arista’s Customer Support Team until the Defect is resolved. Required Customer activities may include, but are not limited to, the following: (i) granting access to Arista to log into Customer’s systems for diagnosis of problems; (ii) downloading and installing of patches and updates; (iii) collecting and sending system logs/files to Arista; (iv) modification of Software configuration; (v) re-installation of existing Software; and (vi) assistance with installation of, and participating in, tests for updates. Customer acknowledges and agrees the success and scheduling of the Software Support depends substantially on the participation of Customer staff. Any delay caused by unavailability of scheduled Customer resources or failure to notify Arista of any previously known issues or scheduled activities that could reasonably be expected to impact the Software Support schedule are the Customer’s responsibility. Further, any such delays may increase the cost or duration of providing Software Support.

Testing of MNDR Services. Customer may test MNDR Services by scheduling and staging simulated or actual adversarial activity. These activities may be conducted by the Customer or a third party contracted by the Customer. Testing of MNDR Services should be communicated to Arista in advance of such activity in writing or email to ensure that Arista have been properly notified of such activities. During this period SCA’s and reporting activities may not apply. In addition, Customer is obligated to share the result of all such tests with Arista and will maintain the results as Confidential Information disclosing the results only to such parties having a need to know who are subject to confidentiality obligations consistent with the Agreement. This Appendix A to the Awake Security Services Exhibit supplements Arista’s Standard Warranty with respect to Arista Software Products that are provided as a part of the Awake Security Platform. Arista’s Standard Warranty, a copy of which is located at ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇.▇▇▇/assets/data/pdf/Warranty.pdf/. Customer has the option to purchase upgraded support see Arista’s A-Care offering description at: ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇.▇▇▇/assets/data/pdf/A-CareServicesOverview.pdf 1. Customer Responsibilities. To facilitate the identification and correction of Defects, Customer is required to assist Arista’s Customer Support Team until the Defect is resolved. Required Customer activities may include, but are not limited to, the following: (i) granting access to Arista to log into Customer’s systems for diagnosis of problems; (ii) downloading and installing of patches and updates; (iii) collecting and sending system logs/files to Arista; (iv) modification of Software configuration; (v) re-installation of existing Software; and (vi) assistance with installation of, and participating in, tests for updates. Customer acknowledges and agrees the success and scheduling of the Software Support depends substantially on the participation of Customer staff. Any delay caused by unavailability of scheduled Customer resources or failure to notify Arista of any previously known issues or scheduled activities that could reasonably be expected to impact the Software Support schedule are the Customer’s responsibility. Further, any such delays may increase the cost or duration of providing Software Support.

Testing of MNDR Services. Customer may test MNDR Services by scheduling and staging simulated or actual adversarial activity. These activities may be conducted by the Customer or a third party contracted by the Customer. Testing of MNDR Services should be communicated to Arista in advance of such activity in writing or email to ensure that Arista have been properly notified of such activities. During this period SCA’s and reporting activities may not apply. In addition, Customer is obligated to share the result of all such tests with Arista and will maintain the results as Confidential Information disclosing the results only to such parties having a need to know who are subject to confidentiality obligations consistent with the Agreement. This Appendix A to the Awake Security Services Exhibit supplements Arista’s Standard Warranty with respect to Arista Software Products that are provided as a part of the Awake Security Platform. Hardware Support. Support for the Hardware portion of the Awake Security Platform shall be provided in accordance with Arista’s Standard Warranty, a copy of which is located at ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇.▇▇▇/assets/data/pdf/Warranty.pdf/. Customer has the option to purchase upgraded support see Arista’s A-Care offering description at: ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇.▇▇▇/assets/data/pdf/A-A- CareServicesOverview.pdf 1. Customer Responsibilities. To facilitate the identification and correction of Defects, Customer is required to assist Arista’s Customer Support Team until the Defect is resolved. Required Customer activities may include, but are not limited to, the following: (i) granting access to Arista to log into Customer’s systems for diagnosis of problems; (ii) downloading and installing of patches and updates; (iii) collecting and sending system logs/files to Arista; (iv) modification of Software configuration; (v) re-installation of existing Software; and (vi) assistance with installation of, and participating in, tests for updates. Customer acknowledges and agrees the success and scheduling of the Software Support depends substantially on the participation of Customer staff. Any delay caused by unavailability of scheduled Customer resources or failure to notify Arista of any previously known issues or scheduled activities that could reasonably be expected to impact the Software Support schedule are the Customer’s responsibility. Further, any such delays may increase the cost or duration of providing Software Support.