ClickHouse Security Cloud Preview Security Terms

NOT FOR EDITING

Last Updated: Oct 16, 2026

This ClickHouse Security Cloud Preview Security Terms (the “Addendum”) sets forth the technical and organizational measures for Customer Data processed by the ClickHouse Security Cloud Component (“Security Cloud Customer Data”). Capitalized terms not defined in this Addendum shall have the meanings set forth in the applicable agreement, including applicable Product Addenda, between Customer and ClickHouse for use of the ClickHouse Security Cloud Component (the “Agreement”).

ClickHouse shall maintain an information security program that is designed to protect the security, confidentiality, and integrity of Security Cloud Customer Data (the "ClickHouse Information Security Program"). The ClickHouse Information Security Program will be implemented on an organization-wide basis. The ClickHouse Information Security Program will be designed to ensure ClickHouse’s compliance with data protection laws and regulations applicable to ClickHouse’s performance under the applicable Agreement (including any Data Processing Addendum), and shall include the safeguards set out below (the “ClickHouse Information Security Controls”).

1. SHARED RESPONSIBILITY

1.1. Shared Responsibility Model. ClickHouse is responsible for the security of the infrastructure and software used to host and operate the ClickHouse Security Cloud Component. Customer is responsible for configuring and securing the ClickHouse Database Product within Customer’s control, including its users, roles and network access settings, and for the credentials Customer provides to enable the ClickHouse Security Cloud Component to access the ClickHouse Database Product, including rotating or revoking those credentials. Security of the ClickHouse Database Product is otherwise governed by the applicable Product Addendum and the ClickHouse Security Standards.

2. CUSTOMER DATA STORAGE LOCATION

2.1. ClickHouse Security Cloud Component. Security Cloud Customer Data is hosted in cloud providers and regions chosen and managed by ClickHouse. Security Cloud Customer Data, including data temporarily staged before delivery to the ClickHouse Database Product, is processed in these regions, which may differ from the region of the ClickHouse Database Product.

3. ORGANIZATIONAL CONTROLS

3.1. Governance. ClickHouse assigns to an individual or a group of individuals appropriate roles for developing, coordinating, implementing, and managing ClickHouse’s administrative, physical, and technical safeguards designed to protect the security, confidentiality, and integrity of Security Cloud Customer Data.

3.2. Security Personnel. ClickHouse uses data security personnel that are sufficiently trained, qualified, and experienced to be able to fulfill their information security-related functions.

3.3. Risk Assessments. ClickHouse conducts periodic risk assessments designed to analyze existing information security risks, identify potential new risks, and evaluate the effectiveness of existing security controls.

3.4. Risk Prioritization. ClickHouse maintains risk assessment processes designed to evaluate likelihood of risk occurrence and material potential impacts if risks occur.

3.5. Information Security Policies. ClickHouse creates information security policies, approved by management, published and acknowledged by all employees.

3.6. Information Security Policy Review. ClickHouse reviews and updates policies at planned intervals to maintain their continuing suitability, adequacy, and effectiveness.

3.7. Data Classification. ClickHouse maintains a data classification standard based on data criticality and sensitivity.

3.8. Data Retention and Destruction. ClickHouse maintains policies establishing data retention and secure destruction requirements.

3.9. Asset Ownership. ClickHouse implements procedures to clearly identify assets and assign ownership of those assets.

3.10. Compliance. ClickHouse establishes procedures designed to ensure all applicable statutory, regulatory, and contractual requirements are adhered to across the organization.

4. PEOPLE CONTROLS

4.1. Information Security Policy Acknowledgement. ClickHouse creates information security policies, approved by management, published and acknowledged by all employees.

4.2. Information Security Awareness Training. ClickHouse requires all employees to undergo security awareness training on an annual basis.

4.3. Personnel Agreements. ClickHouse requires personnel to sign confidentiality agreements and acknowledge ClickHouse’s information security policy, which includes acknowledging responsibilities for reporting security incidents involving Security Cloud Customer Data.

5. PHYSICAL SECURITY

5.1. Cloud Service Providers. For the ClickHouse Security Cloud Component, ClickHouse uses hosting service providers that have:

5.1.1. Physical Security. Implemented controls designed to restrict unauthorized physical access to areas containing equipment used to provide the ClickHouse Security Cloud Component.

5.1.2. Environmental Security. Maintained equipment used to host the ClickHouse Security Cloud Component in physical locations that are designed to be protected from natural disasters, theft, unlawful and unauthorized physical access, problems with ventilation, heating or cooling, and power failures or outages.

6. TECHNOLOGICAL CONTROLS

6.1. Logical Access Control. ClickHouse maintains technical, logical, and administrative controls designed to limit access to Security Cloud Customer Data processed by the ClickHouse Security Cloud Component. Unique usernames and passwords are required for authentication.

6.2. Privileged Access Restriction. ClickHouse restricts privileged access to the Security Cloud Customer Data to authorized users with a business need.

6.3. Access Review. ClickHouse reviews personnel access rights on a regular and periodic basis. Access to production environments is reviewed at least quarterly.

6.4. Access Revocation. ClickHouse maintains policies requiring termination of access to Security Cloud Customer Data within 24 hours of employee termination.

6.5. Multi-Factor Authentication. ClickHouse implements access controls designed to authenticate users and limit access to Security Cloud Customer Data, including multi-factor authentication.

6.6. Cryptographic Key Management. ClickHouse implements encryption key management procedures.

6.7. Encryption in Transit. ClickHouse encrypts Security Cloud Customer Data in transit using a minimum of SSL with SHA 256 or TLS 1.2 with strong ciphers.

6.8. Encryption at Rest. ClickHouse encrypts Security Cloud Customer Data at rest using a minimum of AES-256 with strong ciphers.

6.8.1. Encryption Key Rotation. ClickHouse utilizes hosting service provider managed keys that are rotated at least annually.

6.9. Separation of Environments. ClickHouse requires internal segmentation to isolate production systems hosting the ClickHouse Security Cloud Component from non-production environments.

6.10. Vulnerability Testing. ClickHouse performs periodic network, infrastructure, and application vulnerability testing.

6.11. Penetration Testing. ClickHouse performs network and application penetration testing at least annually.

6.12. Technical Vulnerability Management. ClickHouse implements commercially reasonable efforts to document and address vulnerabilities discovered during vulnerability and penetration tests.

6.13. Network Security Reviews. ClickHouse requires periodic reviews and testing of network controls.

6.14. Workstation Security. ClickHouse centrally manages workstations via endpoint security solutions for deployment and management of end-point protections, including: (i) full-disk encryption; (ii) anti-malware software; (iii) automatic screen lock after 15 minutes of inactivity; (iv) secure VPN; and (v) data loss prevention (DLP) controls for external drives and network shares.

6.15. Logical Separation of Customer Environments. For the ClickHouse Security Cloud Component, customer environments are logically separated.

6.16. Change Management. ClickHouse assigns responsibility for security, changes and maintenance for all information systems processing Security Cloud Customer Data.

6.17. Change Authorization. For the ClickHouse Security Cloud Component, ClickHouse tests, evaluates and authorizes major information system components prior to implementation in the production environment.

6.18. Secure Development. ClickHouse maintains and follows a secure development lifecycle for the development of the software that is hosted and made available via the ClickHouse Security Cloud Component.

6.19. System Monitoring. ClickHouse monitors the access, availability, capacity and performance of the ClickHouse Security Cloud Component, and related system logs and network traffic using various monitoring software and services. Intrusion detection tools log certain activities and changes within the ClickHouse Security Cloud Component, which are monitored, analyzed for anomalies, and securely stored for at least one year.

6.20. Security Incident Reporting. If ClickHouse becomes aware of a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Security Cloud Customer Data processed by the ClickHouse Security Cloud Component (“Security Incident”), ClickHouse shall notify Customer without undue delay, and in any case, where feasible, notify Customer within 48 hours after becoming aware and in accordance with Section 7 of the Data Processing Addendum.

6.21. Security Incident Response Procedures. ClickHouse maintains incident response procedures for identifying, reporting, and acting on Security Incidents.

6.22. Security Incident Response Tabletop. ClickHouse exercises the incident response process on a periodic basis.

6.23. Security Incident Response Improvement. ClickHouse implements plans to address gaps discovered during incident response exercises.

6.24. Incident Response Team. ClickHouse establishes a cross-disciplinary security incident response team.