Data Processing Agreement (DPA)
pursuant to Art. 9 of the Swiss Federal Act on Data Protection (FADP, SR 235.1)
Contracting Parties
Controller (Client):
The customer pursuant to the main contract between the parties regarding the use of the ExposIQ platform (hereinafter “Controller”)
Processor:
ExposIQ, Andriu Isenring
8152 Glattbrugg, Switzerland
E-mail: info@exposiq.ch
(hereinafter “Processor” or “ExposIQ”)
The Controller and the Processor are hereinafter individually referred to as a “Party” and collectively as the “Parties”.
Preamble
The Processor provides vulnerability management services to the Controller as Software-as-a-Service (SaaS). In the course of providing these services, the Processor processes personal data on behalf of the Controller. This Data Processing Agreement (hereinafter “DPA”) specifies the data protection rights and obligations of the Parties pursuant to the Swiss Federal Act on Data Protection (FADP) and the Ordinance on Data Protection (FADPO).
This DPA is an integral part of the main contract concluded between the Parties regarding the use of the ExposIQ platform (hereinafter “Main Contract”). In the event of any conflict between this DPA and the Main Contract, the provisions of this DPA shall prevail with regard to the protection of personal data.
1. Subject Matter and Duration of Processing
1.1 The subject matter of this DPA is the processing of personal data by the Processor on behalf of and in accordance with the instructions of the Controller in connection with the provision of services under the Main Contract.
1.2 The duration of processing corresponds to the term of the Main Contract. This DPA commences upon conclusion of the Main Contract and terminates automatically upon its termination, subject to the post-contractual obligations set out in this DPA (in particular Section 7).
1.3 Processing shall take place exclusively in Switzerland, unless expressly agreed otherwise in this DPA.
2. Nature and Purpose of Processing
2.1 The Processor processes personal data exclusively for the purpose of providing the agreed vulnerability management services. This includes in particular:
- Conducting automated vulnerability scans on the infrastructure configured by the Controller (IP addresses, domains, networks)
- Detection and classification of security vulnerabilities (CVEs, severity levels)
- Collection and analysis of network topology, service and software version information
- Generation of reports and dashboards with scan results
- Storage and management of user accounts for platform use
- Provision of historical scan data for trend analysis and compliance documentation
2.2 The types of processing include the collection, storage, use, retrieval, analysis, provision and deletion of personal data within the framework of automated data processing on the ExposIQ platform.
3. Types of Personal Data and Categories of Data Subjects
3.1 Types of Personal Data
The following categories of personal data are processed in the course of the commissioned processing:
- User account data: Name, e-mail address, company affiliation, login credentials (hashed passwords), roles and permissions
- Infrastructure data: IP addresses, hostnames, domain names, ports, network ranges (CIDR) attributed to the Controller
- Scan results: Detected vulnerabilities (CVE identifiers), severity levels, affected services, software versions, open ports
- Network topology data: Information about the network structure, service configurations and connections of the scanned infrastructure
- Usage data: Platform usage log data, timestamps, actions performed
3.2 Categories of Data Subjects
- Platform users: Employees of the Controller who access the ExposIQ platform (administrators, analysts, report recipients)
- IT administrators: Persons who may be identifiable in scan results as technical contacts or system operators
- Third parties: Persons whose personal data may be indirectly contained in the scanned infrastructure data (e.g. in WHOIS registrations, SSL certificates)
4. Obligations of the Controller
4.1 The Controller is responsible for compliance with data protection provisions, in particular for the lawfulness of processing and the safeguarding of the rights of data subjects.
4.2 The Controller has the right and the obligation to issue instructions to the Processor regarding the nature, scope and procedure of data processing. Instructions shall generally be issued in writing or in text form. Oral instructions shall be confirmed in writing without undue delay.
4.3 The Controller shall ensure that it is authorised to commission the processing described in the Main Contract and in this DPA and that it has a sufficient legal basis for the data processing.
4.4 The Controller shall ensure that only infrastructure for which it has authorisation is scanned. ExposIQ accepts no liability for unauthorised scans.
4.5 The Controller shall inform the Processor without undue delay if it identifies errors or irregularities when reviewing the processing results.
5. Obligations of the Processor
5.1 Processing in Accordance with Instructions
5.1.1 The Processor shall process personal data exclusively within the scope of the Controller’s instructions and for the agreed purpose pursuant to this DPA and the Main Contract, unless processing is required by Swiss law.
5.1.2 The Processor shall inform the Controller without undue delay if it is of the opinion that an instruction of the Controller violates data protection provisions. The Processor shall be entitled to suspend the execution of the relevant instruction until it is confirmed or amended by the Controller.
5.2 Confidentiality
5.2.1 The Processor shall ensure that all persons entrusted with the processing of personal data are bound by confidentiality obligations or are subject to an appropriate statutory duty of secrecy.
5.2.2 The confidentiality obligation shall continue to apply after the termination of the engagement.
5.3 Technical and Organisational Measures (TOMs)
5.3.1 The Processor shall implement appropriate technical and organisational measures pursuant to Art. 8 FADP and Art. 1-4 FADPO in order to ensure an adequate level of protection for personal data. The measures shall be commensurate with the risk to the privacy and fundamental rights of data subjects.
5.3.2 The technical and organisational measures in place at the time of conclusion of the contract are described in Annex A of this DPA.
5.3.3 The Processor shall be entitled to adapt the technical and organisational measures during the term of the contractual relationship, provided that the contractually agreed level of protection is not reduced. Material changes shall be communicated to the Controller.
5.4 Sub-processors
5.4.1 The Processor may only engage sub-processors with the prior written consent of the Controller. The Controller hereby grants general consent to the engagement of sub-processors under the conditions of this Section 5.4.
5.4.2 At the time of conclusion of the contract, the Processor engages the following sub-processors:
- Hosting provider (Switzerland): Operation of the server infrastructure and data storage in Switzerland. The hosting provider is subject to Swiss data protection law and has committed to compliance with appropriate technical and organisational measures.
5.4.3 The Processor shall inform the Controller in writing of any intended change regarding the engagement of new or the replacement of existing sub-processors and shall grant the Controller a period of 30 days to object to the change.
5.4.4 If the Controller raises a justified objection against a new sub-processor, the Parties shall endeavour to reach an amicable solution. If no agreement can be reached, the Controller shall be entitled to terminate the Main Contract with 30 days’ notice for cause.
5.4.5 The Processor shall ensure that a contract is concluded with each sub-processor imposing at least equivalent data protection obligations as those set out in this DPA. The Processor shall be liable to the Controller for compliance with data protection obligations by its sub-processors.
5.5 Assistance with Data Subject Rights
5.5.1 The Processor shall assist the Controller, as far as possible, with appropriate technical and organisational measures in fulfilling its obligation to respond to requests from data subjects (in particular the right of access pursuant to Art. 25 FADP, the right to data portability pursuant to Art. 28 FADP, rectification and erasure).
5.5.2 If a data subject contacts the Processor directly, the Processor shall forward the request to the Controller without undue delay, provided that attribution to the Controller is possible.
5.5.3 The Processor shall be entitled to charge the Controller a reasonable fee for assistance with the fulfilment of data subject rights, provided that the effort exceeds the scope of standard services.
5.6 Assistance with Data Security
5.6.1 The Processor shall assist the Controller in complying with the obligations pursuant to Art. 8 FADP (data security), Art. 22 FADP (data protection impact assessment) and Art. 24 FADP (notification of data security breaches), to the extent possible taking into account the nature of the processing and the information available to the Processor.
5.7 Deletion and Return of Personal Data
5.7.1 Upon termination of the Main Contract, the Processor shall delete all personal data processed on behalf of the Controller, unless a statutory retention obligation exists. At the Controller’s request, the data shall be provided in a common, machine-readable format prior to deletion.
5.7.2 Deletion shall take place within 90 days of termination of the Main Contract. The Processor shall confirm complete deletion in writing upon request.
5.7.3 Data in backups shall be deleted in the course of the regular backup rotation, but no later than 180 days after the end of the contract.
5.8 Right of Audit
5.8.1 The Processor shall make available to the Controller all information necessary to demonstrate compliance with the obligations set out in this DPA.
5.8.2 The Controller shall be entitled to conduct audits or to have them conducted by an independent auditor bound by confidentiality obligations. Audits shall be announced with at least 30 days’ advance notice and shall be conducted during normal business hours. The Controller shall ensure that audits do not unreasonably disrupt the Processor’s business operations.
5.8.3 The Controller shall bear the costs of an audit, unless the audit reveals material breaches by the Processor of the provisions of this DPA.
5.8.4 Alternatively, the Processor may provide the Controller with current certifications, audit reports or inspection reports from independent bodies. The Controller shall accept such evidence as equivalent, provided that it covers the scope under review.
6. Notification of Data Security Breaches
6.1 The Processor shall notify the Controller of any data security breach within the meaning of Art. 24 FADP without undue delay, but no later than 48 hours after becoming aware of it.
6.2 The notification shall contain at least the following information, to the extent available at the time of notification:
- The nature of the data security breach, including the categories and approximate number of data subjects and data records affected
- A description of the likely consequences of the breach
- A description of the measures taken and proposed to remedy the breach and mitigate its consequences
- The name and contact details of the responsible contact person at the Processor
6.3 Where it is not possible to provide all information at the same time, the Processor shall provide the information in stages and without undue delay.
6.4 The Processor shall assist the Controller in fulfilling its notification obligations towards the Federal Data Protection and Information Commissioner (FDPIC) and towards the data subjects.
7. Liability
7.1 Each Party shall be liable for damages caused by a breach of the provisions of this DPA or the applicable data protection legislation in accordance with the statutory provisions and the Main Contract.
7.2 The Processor shall not be liable for damages attributable to the fact that the Controller has issued incorrect, incomplete or unlawful instructions or has configured unauthorised infrastructure for scanning.
7.3 The limitation of liability provisions of the Main Contract shall apply to this DPA accordingly, to the extent permitted by law.
8. Term and Termination
8.1 This DPA enters into force upon conclusion of the Main Contract and applies for the duration of the Main Contract. It terminates automatically upon termination of the Main Contract, regardless of the reason.
8.2 Provisions which by their nature are intended to survive the termination of this DPA, in particular the confidentiality obligations (Section 5.2), the deletion and return obligations (Section 5.7) and the liability provisions (Section 7), shall remain in effect after the termination of the DPA.
8.3 A separate termination of this DPA without simultaneous termination of the Main Contract is not possible.
9. Final Provisions
9.1 Governing law: This DPA is governed exclusively by Swiss law, in particular the Federal Act on Data Protection (FADP, SR 235.1) and the Ordinance on Data Protection (FADPO, SR 235.11).
9.2 Jurisdiction: The exclusive place of jurisdiction for all disputes arising out of or in connection with this DPA is Zurich, Switzerland. Mandatory statutory places of jurisdiction remain reserved.
9.3 Written form: Amendments and supplements to this DPA require written form. This also applies to the waiver of the written form requirement.
9.4 Severability clause: Should any provision of this DPA be or become wholly or partially invalid or unenforceable, the validity of the remaining provisions shall not be affected. The invalid or unenforceable provision shall be replaced by a valid provision that most closely approximates the economic and data protection purpose of the invalid provision.
9.5 Precedence: In the event of any conflict between the provisions of this DPA and those of the Main Contract, the provisions of this DPA shall prevail with regard to the protection of personal data.
9.6 Cross-border data transfer: Transfer of personal data to countries without an adequate level of data protection pursuant to the list issued by the Federal Council shall only take place with the prior written consent of the Controller and in compliance with the requirements of Art. 16-17 FADP (in particular standard data protection clauses, consent of the data subject or other statutory exceptions).
Annex A: Technical and Organisational Measures (TOMs)
The Processor has implemented the following technical and organisational measures pursuant to Art. 8 FADP and Art. 1-4 FADPO in order to ensure a level of protection commensurate with the risk. The measures are reviewed regularly and adapted to the state of the art as necessary.
A.1 Physical Access Control
Measures to prevent unauthorised persons from gaining physical access to data processing facilities:
- Server infrastructure is operated exclusively in professional data centres in Switzerland
- Data centres are equipped with access control systems (key cards, biometric systems, mantraps)
- Access authorisation limited to authorised personnel of the hosting provider
- Video surveillance and logging of access at the data centre
- Visitor registration and escort by authorised personnel
A.2 System Access Control
Measures to prevent unauthorised use of data processing systems:
- Authentication via individual user accounts with strong password policies
- Multi-factor authentication (MFA) for administrative access
- Automatic lockout after failed login attempts
- Encrypted remote access exclusively via SSH and VPN
- Regular review and revocation of access rights no longer required
- Centralised management of user accounts and permissions
- Automatic session timeout upon inactivity
A.3 Data Access Control
Measures to ensure that authorised users can only access data within the scope of their access rights:
- Role-based access control (RBAC) with the principle of least privilege
- Tenant separation: Each customer has access exclusively to their own data
- Differentiated user roles with tiered permissions (administrator, analyst, viewer)
- Logging of all access to personal data
- Regular review of access permissions
- Immediate deactivation of access upon personnel changes
A.4 Data Transfer Control (Encryption)
Measures to ensure that personal data cannot be read, copied, altered or removed by unauthorised persons during electronic transmission or transport:
- Encryption of all data in transit using TLS 1.2 or higher
- Encryption of all stored data (encryption at rest) using AES-256 or equivalent methods
- Encrypted connections for all API interfaces (HTTPS)
- Secure key management with regular key rotation
- No unencrypted transmission of personal data via e-mail or other insecure channels
- VPN tunnels for administrative access to the infrastructure
A.5 Input Control (Audit Trail)
Measures to ensure that it is possible to verify and determine retrospectively which personal data has been entered, modified or removed, at what time and by whom:
- Comprehensive logging of all processing operations (audit trail / audit log)
- Logging of user actions with timestamp, user identifier and type of action
- Immutability of log data (append-only logs)
- Retention of log data for a minimum of 12 months
- Regular review of log data for anomalies
- Access to log data restricted to authorised administrators
A.6 Processing Control
Measures to ensure that personal data processed on behalf of the Controller is processed only in accordance with the Controller’s instructions:
- Written specification of the engagement and instructions in this DPA and in the Main Contract
- Contractual obligation of all employees to comply with instructions
- Regular training of employees on data protection and information security
- Careful selection and oversight of sub-processors
- Contractual binding of sub-processors to equivalent data protection measures
- Documented processes for the processing and escalation of instructions
A.7 Availability Control
Measures to ensure that personal data is protected against accidental destruction and loss:
- Regular, automated data backups following the 3-2-1 principle
- Geo-redundant storage of backups at a separate location in Switzerland
- Regular data restoration tests (restore tests)
- Uninterruptible power supply (UPS) and emergency power generators at the data centre
- Fire protection and climate control systems at the data centre
- Monitoring of system availability and automatic notification in the event of disruptions
- Documented disaster recovery plan with defined recovery times
- Protection against malware through up-to-date antivirus software and intrusion detection systems
A.8 Separation Control (Multi-tenancy)
Measures to ensure that data collected for different purposes is processed separately:
- Strict logical tenant separation: Each customer’s data is stored in separate, logically isolated database areas
- Tenant isolation at the application level: API access is always restricted to the customer’s own tenant
- Separate authentication and authorisation per tenant
- No cross-tenant data queries or analyses possible
- Regular testing of tenant separation as part of internal security reviews
- Separation of production, testing and development environments
- No use of production data in testing and development environments
Signatures
____________________________________
Controller (Client)
Place, date: ___________________________
Name: ___________________________
Function: ___________________________
Signature: ___________________________
____________________________________
Processor (ExposIQ)
Place, date: ___________________________
Andriu Isenring
Owner
Signature: ___________________________