Supplier Security Requirements Addendum
Last Modified: March 7, 2025
These Supplier Security Requirements apply to Supplier when it provides Services to Hex. Terms used here but not defined here are defined in the Agreement. These Security Requirements are hereby incorporated by reference and shall be bound by all terms of the Agreement, unless otherwise explicitly set forth herein. These Security Requirements are intended to supplement the Agreement. Where there is a conflict between the provisions of these Security Requirements and the Agreement, the provisions of these Security Requirements shall apply.
1. Third-Party Testing and Validation.
1.1. General Testing.
a. Periodic Tests. Supplier shall allow Hex, or Hex's delegate, to periodically test the security of the Services. When testing Hex or its delegate shall: (i) carefully conduct tests that are reasonably designed to safely uncover possible vulnerabilities without undue risk; and (ii) make commercially reasonable efforts to tailor the tests as needed to specifically achieve the purpose of the test.
b. Timing. Hex or its delegate may conduct the security tests in Section 1.1 at any time during the term of the Agreement. Hex will: (i) provide Supplier with reasonable notice prior to conducting the tests; (ii) promptly inform Supplier of any findings; and (iii) delay further disclosure until Supplier has had reasonable time to resolve issues identified in the findings.
1.2. Vulnerability Disclosure Policy.
a. Generally. Supplier shall publish a Vulnerability Disclosure Policy ("VDP") on its public website. This VDP shall: (i) welcome arbitrary security research; (ii) include all internet-facing assets in scope; (iii) provide safe harbor from the Computer Fraud and Abuse Act ("CFAA") and the Digital Millennium Copyright Act ("DMCA") (and any similar or successor legislation) actions for all good faith research; and (iv) permit responsible disclosure of any vulnerability findings, save that any such disclosure does not violate the confidentiality of Supplier's customers' data.
b. Contact and Service Level Agreement. Supplier shall: (i) post a method by which the public can contact Supplier to report security vulnerabilities; and (ii) use best efforts to respond to these reported security vulnerabilities within a commercially reasonable period of time based on the severity and impact of the vulnerability.
c. Bug Bounty Program. Supplier agrees that Hex may make deliverables or results of the Services subject to Hex's own Bug Bounty Program ("BBP"). Hex will notify Supplier of any material security-related vulnerabilities in the Services or deliverables identified through its BBP. Supplier understands that research and disclosures are governed by Hex's BBP, which requires good faith and responsible behavior by participants.
1.3. Application and Network Penetration Testing.
a. Annual Testing. Supplier shall, at least once per year, perform a suite of independent third-party tests. These tests will be performed upon: (i) the Services; (ii) all aspects of Supplier's internet-facing perimeter; and (iii) systems supporting the Services (such as build/release infrastructure). Supplier will supply Hex with full details (not just executive summaries) of all third-party tests from the previous year, including names of third-party testers, number of person hours used, severity of any identified issues, and current remediation status for such issues.
b. Sharing Results. Supplier shall, upon Hex's request and under suitable non-disclosure obligations, share with Hex: (i) confirmation that the tests required by this Section 1.3 were performed; and (ii) the third-party tests results from Sections 1.3(a)(i) and (ii) above.
1.4. Fixing Issues.
Supplier will fix all critical and high severity vulnerabilities that could affect the security of Hex Data, of which Supplier becomes aware, within thirty days of becoming aware of the vulnerability. If Supplier cannot fix the vulnerability within thirty days, Supplier will promptly inform Hex, including all details of the risk to Hex arising from Supplier's inability to fix the vulnerability.
2. Technical Security Measures.
2.1. Transport Encryption.
Supplier will maintain an SSL Server Test rating (please see https://www.ssllabs.com/ssltest/) of at least "A" for any external website used to store or access Hex Data. If Supplier's rating falls below "A," Supplier will: (a) notify Hex if this rating is below "A" for two months; and (b) have two months from the date it notifies Hex within which to increase its rating back to an "A."
2.2. SAML/OIDC Authentication Integration.
If the Services include a SaaS service, Supplier will integrate the Services with SAML 2.0 or OIDC authentication for Hex's user authentication needs. This SAML 2.0 / OIDC authentication integration will be the only method by which Hex users log in to the Services.
2.3. Multi-factor Authentication.
Supplier will use a multi-factor authentication ("MFA") login solution for the Services, provided that text or phone call are not acceptable factors. MFA must be used for: (a) any VPN connections into the Supplier's internal networks; (b) any connections into Supplier's production environment; (c) Supplier's e-mail, if it can be accessed from the internet; and (d) any services Supplier uses that contain Hex Data.
2.4. Patching.
Supplier will promptly apply any high or critical severity security patches to their production servers, endpoints, and endpoint management systems.