7.3 WaiverThe waiver by either party of any breach or failure of the other party to breach or comply with any provision of this Agreement shall not be construed as a waiver of any subsequent breach of the same or any other provision, or the delay or omission of either party in exercising or exercising any right. Any authority or privilege it has or may have hereunder shall be deemed a waiver of any breach or default of the other party. 2.6 Obligations of the relying partyAs a relying party, you must ensure that a certificate is valid and will not be revoked before relying on that certificate. SSL.com provides information about certificate validity through its repository. The repository is available “as is” and “as available” on publicly available networks. SSL.com disclaims all warranties as to the availability of the repository and reserves the right to exclude or close access to the repository at any time without notice. Comments on specific definitions should be sent to the authors of the linked source publication. For NIST publications, there is usually an email in the document. 5.3 DisclaimerYou will not be liable for any special, indirect, incidental or consequential damages that may arise out of this Agreement or the use of a Certificate. This waiver includes any damages for loss of profits, revenue, use or data. This limitation applies even if SSL.com is aware of the possibility of such damages.

SSL.com does not warrant that certificates, services, or repository information will meet your requirements or expectations, or that access to the repository or certificates will be uninterrupted, timely, secure, or error-free. SSL .com`s maximum liability to you is limited to the warranty associated with the certificate as set forth in the SSL.com relying party warranty. IMPORTANT – Do not rely on SSL.com certificate services and use this Relying Party Agreement (“Agreement”). 7.10 Third Party BeneficiariesThere are no Third Party Beneficiaries under this Agreement. Subscribers are not considered relying parties or persons covered by this Agreement. The SSL agreement .com relying party applies to any company or person that depends on the use of a SSL.com service or product. These services and products include: An entity that relies on the validity of binding the subscriber`s name to a public key to verify or establish the identity and status of a person, role, system, or device; the integrity of a digitally signed message; the identity of the creator of a message; or confidential communications with the subscriber. Source(s): CNSSI 1300 INSN 4009-2015 A company that relies on the subscriber`s authenticator(s) and credentials or an auditor`s declaration of identity of a requester, typically to process a transaction or provide access to information or a system. Source(s): NIST SP 1800-17b under Relying Party NIST SP 1800-17c under Relying Party NIST SP 800-63-3 under Relying Party (RP) NISTIR 8149 under Relying Party (RP) of NIST SP 800-63-3 A part that depends on the validity of the digital signature process. Source(s): NIST SP 800-102 on relying party NIST SP 800-89 on relying party In this notice, a party that relies on the security and authenticity of a key or key pair to apply cryptographic protection and remove or verify the protection applied. This includes parties that rely on the public key in a public key certificate and parties that share a symmetric key. Source(s): NIST SP 800-152 under Relying Party An entity that relies on subscriber credentials, typically to process a transaction or provide access to information or a system.

Source(s): NIST SP 800-73-4 to the relying party An entity that relies on the certificate and the certificate authority that issued the certificate to verify the identity of the subject and/or owner of the certificate; the validity of the public key, associated algorithms and all relevant parameters; and the subject`s possession of the corresponding private key. Source(s): NIST SP 800-57 Part 2 Rev.1 under Relying Party An entity that relies on the certificate and the certificate authority that issued the certificate to verify the identity of the certificate owner and the validity of the public key, associated algorithms, and all relevant certificate settings, and the ownership of the owner of the corresponding private key. Source(s): NIST SP 800-175B Rev. 1 Under Relying Party A party that relies on the security and authenticity of a key or key pair to enforce cryptographic protection and/or remove or verify the protection applied. This includes parties that rely on the public key in a public key certificate and parties that share a symmetric key. Source(s): NIST SP 800-57 Part 1 Rev. 5 under the Relying Party 7.6 Governing Law and JurisdictionThis Agreement shall be construed in accordance with the laws of the United States, without regard to conflict of law provisions. Any claim or action brought by either party against the other arising out of this Agreement shall be brought in the courts of the United States.

Both parties hereby submit to the jurisdiction and venue of such court. 7.5 ImpossibilityNeither party shall be liable for any failure to perform any provision of this Agreement rendered impossible by law or by any act of any government or political subdivision having jurisdiction over the Party or any parent company of the Party. 7.4 Force majeure and Internet weaknesses Delays or failures by a party in performing any obligation under this Agreement shall be excused to the extent such failure or delay is caused by events beyond that party`s reasonable control, including acts of God, storms, hurricanes, earthquakes, riots, wars (declared or not), acts of sabotage, interruptions or failures of telecommunications or digital. Transmission connections, Internet slowdowns or outages, power outages and other causes that cannot reasonably be foreseen or controlled by this party. Each party acknowledges that the Internet consists of a number of networks that are subject to failures and failures. In no event shall either party be liable for or as a result of such failures or errors. Relying Party Agreement: The relying party agreement is an agreement that must be read and accepted by a relying party before validating, relying on, or using a certificate, or accessing or using the QuoVadis repository.