SEISMIC
INFORMATION SECURITY ADDENDUM
Last Updated: March 6, 2026
This Information Security Addendum (“InfoSec Addendum”) describes the controls and measures that Seismic has established with respect to its online products and services (“Services”), which are designed to protect the integrity, confidentiality, and availability of Customer Content while using Services in accordance with the terms of the Seismic Main Services Agreement (“MSA”). For avoidance of doubt, this InfoSec Addendum and related commitments do not apply to (i) Professional Services, Non-Seismic Products, Trials, and Third-Party Content made available by Seismic, or used or provided by Customer, (ii) data in Customer’s VPN, own Customer Property, or a third-party network; (iii) any data processed by Customer or its Users in violation of the MSA and (iv) any financial data of individuals or companies, health data of individuals, and/or other sensitive data as described in any applicable Laws. If not defined separately in this InfoSec Addendum, capitalized terms used herein will have the specified meanings provided in the MSA.
Seismic has established and maintains a documented information security management system (“ISMS”) that defines policies, procedures, and standards designed to safeguard information assets and establishes administrative, technical, and physical safeguards that are appropriate to (a) the size, scope and type of Seismic’s business and Services; (b) the amount of resources available to Seismic; (c) the type of Customer Content that Customer is permitted to use with the Services and that Seismic will process; and (d) the need for security and protection from unauthorized disclosure of such Customer Content. Seismic reviews its ISMS annually and may update it and the measures set forth in this InfoSec Addendum to address changes in legal and regulatory requirements, new and evolving security technologies, changes to industry standard practices, changes to Seismic Service offerings, and changing security threats, provided that no such update will materially reduce the overall level of commitments or protections provided to Customer as described herein.
The Services are operated in a multitenant architecture that is designed to segregate and restrict Customer Content access based on business needs. The architecture provides a logical data separation for different Customers via Customer-specific “Tenant IDs” (each, a “Tenant”) and allows the Customer to define role-based access privileges within its Tenant. Additional data segregation may be provided by establishing separate environments for distinct functions (e.g., testing and production).
Only authorized Seismic information security staff can grant, modify and revoke Seismic personnel access to its information systems that process or store Customer Content. Access rights are implemented adhering to the “least privilege” approach and using multi-factor authentication (“MFA”). Seismic administration procedures define user roles and their privileges, how access is granted, changed and terminated, address appropriate segregation of duties, and define the logging/monitoring requirements and mechanisms.
The following current Seismic security and privacy-related audits and certifications, as set forth at the Seismic Trust Center are applicable to one or more of the Services (“Audit Reports”):
Where Seismic has obtained an ISO 27001 certification or SSAE 18 Service Organization Control (SOC) Type 2 report for a particular Service, Seismic agrees to maintain this certification or audit report, or comparable alternatives or successors thereof, for the duration of the relevant Customer Order Form term for the same applicable Service. Seismic will provide evidence of its Audit Reports upon Customer’s written request no more frequently than once every twelve-month period.
Seismic processes personal data on Customer’s behalf during a Service Term in accordance with the terms of this Data Processing Addendum here (“DPA”), unless the Parties have separately executed a DPA, in which case such terms will control.
• User access log entries will be maintained, containing date, time, user ID, URL executed, or entity ID operated on, operation performed and source IP address.
• Data center physical access logs, system infrastructure logs, and application logs with User activity will be securely kept by Seismic and its third-party providers in accordance with their respective procedures.
• Authorization is granted through a roles-based authorization system. Seismic supports standards-based federated ID capability through SAML 2.0 and OAUTH.
• MFA is available through single sign-on.
• Seismic hardens all components to provide only necessary ports, protocols, and services to meet business needs and have supporting technical controls. Baseline configurations are reviewed quarterly.
• A designated Seismic employee is responsible for overseeing and implementing the Seismic ISMS.
Seismic performs regular, and no less than quarterly, vulnerability scans on its applications and infrastructure components of its production and development environments. For applications, scans are also performed after any major feature changes or architectural modification to the Services. Vulnerabilities are ranked using the Common Vulnerability Scoring System and remediated on a risk basis that considers the types of applications and infrastructure systems on which they are found.
All Seismic employees are required to undergo security and privacy awareness training, at the time of hiring, and annually thereafter. Seismic also requires additional role-based security training for those employees with access to Customer Content or the application that processes and stores Customer Content. All Seismic employees and contractors are contractually obligated to maintain the confidentiality of Customer Content, in accordance with applicable Laws, Customer agreement terms, and Seismic’s Privacy Policy.
Seismic performs background checks on all employees who have access to Customer Content in accordance with its standard operating procedures, and subject to applicable Laws.
Seismic maintains a third-party risk management program designed to assess and manage security risks associated with its vendors that access or otherwise process Customer Content.
Seismic uses encryption to protect Customer Content in-transit (e.g., TLS 1.2 or greater) and at-rest (e.g., AES 256). Customer
Seismic maintains the following development controls:
Seismic employs then-current industry-standard measures designed to detect and remediate Malicious Elements designed to negatively impact the operation or performance of the Services.
Seismic engages third parties to conduct annual penetration tests of the Services and to issue a report of their findings (“Testing Report”). Evidence of Seismic’s then-current Testing Report, and summary reports of relevant remediation plans are available to a Customer upon its written request.
Seismic has implemented and will maintain a device management program for Seismic- owned, provided or managed devices, including laptops, tablets, and other endpoints that access or process Customer Content. Seismic reviews its device management program at least annually to address evolving threats and industry best practices for services and products similar to the Services.
Seismic maintains policies and procedures for managing changes to production systems, applications, and databases. Such policies and procedures include: (i) a process for documenting, testing and approving the promotion of changes into production; (ii) security patching process that requires patching systems in a timely manner based on a risk analysis; and (iii) process for Seismic to perform security assessments of changes into production.
Seismic's production data centers used to provide the Services are equipped with industry-standard physical security measures, including access controls, surveillance systems, and environmental monitoring. These physical access controls are established and maintained by the applicable provider in accordance with their respective standard procedures. As examples, a summary of current physical access controls of (i) Microsoft Azure are here, (ii) AWS are found here, and (iii) OCI are found here.
