Shared Security Responsibilities Clause Samples
The Shared Security Responsibilities clause defines how security duties are divided between the parties involved, typically in a service or technology arrangement. It outlines which aspects of security each party is responsible for, such as the service provider managing infrastructure security while the customer handles user access controls and data protection. This clause ensures that both parties understand and fulfill their respective roles, reducing the risk of security gaps and clarifying accountability in the event of a security incident.
Shared Security Responsibilities. Without diminishing Snowflake's commitments in this Security Addendum, Customer agrees:
9.4.1. Snowflake has no obligation to assess the content of Customer Data to identify information subject to any specific legal, regulatory or other requirement and Customer is responsible for making appropriate use of the Service to ensure a level of security appropriate to the particular content of Customer Data, including, where appropriate, implementation of encryption functionality, such as the "tri-secret secure" feature (as described in the Documentation), pseudonymization of Customer Data, and configuration of the Service to back-up Customer Data;
9.4.2. to be responsible for managing and protecting its User roles and credentials, including but not limited to (i) requiring that all Users keep credentials confidential and not share such information with unauthorized parties, (ii) reporting to Snowflake any suspicious activities in the Account or if a user credential has been compromised, (iii) appropriately configuring User and role-based access controls, including scope and duration of User access, taking into account the nature of its Customer Data, and
Shared Security Responsibilities. Without diminishing eGain's commitments in this Security Policy, Customer agrees:
8.4.1. eGain does not assess the content of Customer Data to identify information subject to any specific legal, regulatory, or other requirement and Customer is responsible for making appropriate use of the Service to ensure a level of security appropriate to the particular content of Customer Data, including, where appropriate, purchasing and maintaining the applicable eGain Cloud Service Add- On;
8.4.2. to be responsible for managing and protecting its User roles and credentials, including but not limited to (i) requiring that all Users keep credentials confidential and not share such information with unauthorized parties, (ii) reporting to eGain any suspicious activities in the Account or if a user credential has been compromised, (iii) appropriately configuring User and role-based access controls, including scope and duration of User access, taking into account the nature of its Customer Data, and (iv) maintaining appropriate password uniqueness, length, complexity, and expiration;
8.4.3. when using the eGain mail services, Customer must configure their SPF records to allow eGain to deliver email on behalf of their domain for us to maintain IP reputation for our mail servers. eGain will remove or block any non-compliant domain from our service and eGain will not be liable for any loss of service as a result.
8.4.4. to ensure the protection of the API keys issued by eGain to the Customer.
Shared Security Responsibilities. Without diminishing Snowflake's commitments in this Security Policy, ▇▇▇▇▇▇▇▇ agrees:
8.4.1. Snowflake does not assess the content of Customer Data to identify information subject to any specific legal, regulatory or other requirement and Customer is responsible for making appropriate use of the Service to ensure a level of security appropriate to the particular content of Customer Data, including, where appropriate, implementation of encryption functionality, such as the "tri-secret secure" feature (as described in the Documentation), and the pseudonymization of Customer Data;
8.4.2. to be responsible for managing and protecting its User roles and credentials, including but not limited to (i) requiring that all Users keep credentials confidential and not share such information with unauthorized parties,
Shared Security Responsibilities. Without diminishing Slope's commitments in this Security Policy, ▇▇▇▇▇▇▇▇ agrees:
7.1.1. Slope has no obligation to assess the content of Customer Data to identify information subject to any specific legal, regulatory or other requirement and Customer is responsible for making appropriate use of the Service to ensure a level of security appropriate to the particular content of Customer Data;
▇.▇.▇. ▇▇ be responsible for managing and protecting its User credentials, including but not limited to (i) requiring that all Users keep credentials confidential and not share such information with unauthorized parties, (ii) reporting to Slope any suspicious activities in the Account or if any Users credential are compromised, and (iii) maintaining appropriate password uniqueness, length, complexity, and expiration;
▇.▇.▇. ▇▇ appropriately manage and protect any Customer-managed encryption keys to ensure the integrity, availability, and confidentiality of the key and Customer Data encrypted with such key.
Shared Security Responsibilities. Without diminishing Snowflake's commitments in this Security Addendum, ▇▇▇▇▇▇▇▇ agrees:
9.4.1. Snowflake has no obligation to assess the content or accuracy of Customer Data, including to identify information subject to any specific legal, regulatory or other requirement and Customer is responsible for making appropriate use of the Service to ensure a level of security appropriate to the particular content of Customer Data, including, where appropriate, implementation of encryption functionality, such as the "tri-secret secure" feature (as described in the Documentation), pseudonymization of Customer Data, and configuration of the Service to back-up Customer Data;
9.4.2. Customer is responsible for managing and protecting its User roles and credentials, including but not limited to (i) ensuring that all Users keep credentials confidential and not share such information with unauthorized parties, (ii) promptly reporting to Snowflake any suspicious activities related to Customer’s Account (e.g., a user credential has been compromised), (iii) appropriately configuring User and role-based access controls, including scope and duration of User access, taking into account the nature of its Customer Data, and (iv) maintaining appropriate password uniqueness, length, complexity, and expiration;
9.4.3. to appropriately manage and protect any Customer-managed encryption keys to ensure the integrity, availability, and confidentiality of the key and Customer Data encrypted with such key; and
9.4.4. to promptly update its Client Software whenever Snowflake announces an update. This Snowflake Support Policy and Service Level Agreement (“Policy”) describes Snowflake’s support offering (“Snowflake Support”) in connection with Customer reported bugs, defects, or errors in the Service (“Error(s)”). Snowflake Support shall be provided in accordance with the Snowflake Reseller Public Sector Access Terms (“Access Terms”). Customer shall receive Premier Support or Priority Support as designated in the applicable Order Form (“Support Level”). This Policy may be updated by Snowflake from time to time. Capitalized terms not defined in this Policy shall have the meaning given to them in the Access Terms. This Policy is made available at ▇▇▇.▇▇▇▇▇▇▇▇▇.▇▇▇/▇▇▇▇▇-▇▇▇. Any references made to the “Agreement” in this Policy shall refer to the “Access Terms”.
I. Support