Document being finalised. Lines marked
to be completedhave not yet been validated and are no commitment of TW3 PARTNERS. Only the measures explicitly described are in place to date.
Purpose and scope
This document describes the technical and organisational measures implemented by TW3 PARTNERS ("TW3") to ensure a level of security suited to the risk, in accordance with article 32 of Regulation (EU) 2016/679 (the "GDPR").
It covers all processing carried out with the Citead solution (formerly DataGeo), whether data processed by TW3 as processor for its customers or data processed as controller.
It is Annex 2 of the data processing agreement concluded between TW3 and its customers and forms an integral part of it. TW3 may change the measures described, provided the overall level of security is not reduced.
Governance and organisation of security
| Measure | Implementation |
|---|---|
| Appointment of an information systems security officer | to be completed |
| Appointment of a data protection officer | Appointed and declared to the CNIL. Contact: dpo@tw3partners.com |
| Information systems security policy, formalised and approved by management | to be completed |
| IT charter binding on staff | to be completed |
| Periodic review of the security policy | to be completed |
| Record of processing activities kept in accordance with article 30 of the GDPR | Kept and updated |
| Data protection by design and by default (art. 25 GDPR) | Built into the design and release processes |
Awareness and human resources
| Measure | Implementation |
|---|---|
| Confidentiality undertaking signed by staff and contractors | Always, before any access |
| Awareness of data protection and IT security | to be completed |
| Awareness of the risks of using artificial intelligence systems (art. 4 of the AI Act) | to be completed |
| Arrival and departure procedure creating and revoking access | Revocation on the day of actual departure |
| Periodic review of permissions | to be completed |
Access control and authentication
Access of the solution's users
| Measure | Implementation |
|---|---|
| Named accounts, sharing of credentials prohibited | Required by the terms |
| Storage of passwords as hashes | Salted scrypt hash (better-auth implementation); no password stored in clear |
| Password policy in line with the CNIL recommendation of 21 July 2022 | 12 characters minimum and 128 maximum, including an upper-case letter, a lower-case letter, a digit and a special character. The password cannot contain the account's e-mail address. Rule applied at signup, change and reset |
| Check against lists of compromised passwords | Systematic check with Have I Been Pwned, by k-anonymity query: only the first five characters of the SHA-1 hash leave the server, never the password. A password found in a known breach is refused; if the check service cannot be reached, the password is refused rather than accepted without check |
| Authentication through a third-party identity provider | Google sign-in available as an alternative to the password |
| Multi-factor authentication | to be completed |
| Lockout after a set number of failed sign-ins | to be completed (first requires passing on the real IP address behind the hosting proxy) |
| Automatic expiry of sessions | Session and access token valid for seven (7) days, then re-authentication required |
| Management of roles and permissions in the customer area | Administrator and user roles |
| API keys: generation, rotation and revocation by the customer from its area | to be completed |
| Rate limiting of API calls and detection of abnormal behaviour | Rate limiting applied at the API level |
Access of TW3 staff
| Measure | Implementation |
|---|---|
| Principle of least privilege | Permissions limited to what is strictly necessary |
| Multi-factor authentication for access to production environments and to the hosting console | to be completed |
| No permanent access to production data | to be completed |
| Prohibition on using production data in test and development environments | Anonymised data or synthetic test sets |
| Encrypted workstations, automatic locking, protection against malicious code | to be completed |
| Remote access through encrypted channels | Administrator access through an authenticated SSH tunnel |
Encryption and protection of data
| Measure | Implementation |
|---|---|
| Encryption of data in transit | TLS 1.2 minimum for all flows, including API calls and exchanges with model providers |
| Encryption of data at rest | Native encryption of the host's services (AES-256) |
| Customer-managed keys (CMEK) | to be completed |
| Management of secrets and keys | Secrets stored outside the source code, in the environment variables of the deployment platform; to be completed for the use of a dedicated secrets vault |
| Logical separation of data between customers | Application-level separation by account identifier, checked on every request |
| Minimisation of data sent to third-party models | Only the data needed to carry out the request is sent |
| No retention of data by model providers for training | Covered by contract and by configuration |
Security of the infrastructure and hosting
| Measure | Implementation |
|---|---|
| Hosting | Scaleway SAS, France, fr-par region (Paris) |
| Certifications of the host | ISO/IEC 27001, 27017, 27018 and HDS, according to the certificates in force for the services actually used |
| Physical security of the data centres | Provided by the host: biometric access control, video surveillance, guarding, power and cooling redundancy |
| Network segmentation and filtering of flows | Virtual private network, firewall rules, databases not publicly exposed |
| Protection against denial-of-service attacks and application filtering | to be completed |
| Hardening of configurations and management of images | Deployment by containers, maintained base images; to be completed for automated scanning of images |
| Identity and access management of the infrastructure | Dedicated service accounts, minimal scope of authorisation |
Development and security maintenance
| Measure | Implementation |
|---|---|
| Separation of development, acceptance and production environments | Distinct environments, separate databases |
| Code review before merge | Peer review on production branches |
| Automated analysis of code and dependencies | to be completed |
| Management of vulnerabilities of third-party components and application of patches | to be completed |
| Change management procedure and possibility of rollback | Versioned deployment with possible return to the previous version |
| Measures specific to the risks of artificial intelligence systems: filtering of instructions, protection against prompt injection, control of outputs, limitation of actions the model can trigger | to be completed |
Logging and monitoring
| Measure | Implementation |
|---|---|
| Logging of data access and administrative operations | Application logs and logs of the hosting platform. No third-party monitoring tool receives customer data |
| Logging of API calls and processing carried out | Timestamp, account identifier, volumes processed |
| Protection of logs against modification and deletion | to be completed |
| Retention period of logs | Six (6) months for routine logs; twelve (12) months for security events |
| Monitoring and alerting on security events | to be completed |
| Periodic review of administration logs | to be completed |
Backup, continuity and recovery
| Measure | Implementation |
|---|---|
| Regular backups of production data | Daily backup |
| Encryption and separation of backups | Native encryption of the host |
| Retention period of backups | Thirty (30) days on a rolling rotation cycle |
| Location of backups | European Union |
| Restore tests | to be completed |
| Redundancy of the infrastructure | to be completed |
| Recovery time and recovery point objectives (RTO, RPO) | to be completed |
Management of incidents and data breaches
| Measure | Implementation |
|---|---|
| Security incident management procedure | Detection, qualification, containment, remediation, lessons learned |
| Internal point of contact and reporting channel | dpo@tw3partners.com. Customer support goes through contact@tw3partners.com; no third-party ticketing tool is used |
| Internal record of data breaches, in accordance with article 33(5) of the GDPR | Kept and documented |
| Notification to customers who are controllers | Without undue delay and at the latest 48 hours after becoming aware of it |
| Assistance to customers for their own notifications | Provided for in the data processing agreement |
| Notification to the CNIL of breaches affecting processing for which TW3 is controller | Within 72 hours, in accordance with article 33 of the GDPR |
Use of third parties
| Measure | Implementation |
|---|---|
| Prior assessment of the guarantees offered by sub-processors | Analysis of security commitments, certifications and location of processing |
| Contractual framework in line with article 28(4) of the GDPR | Processing agreements concluded with each sub-processor |
| Framework for transfers outside the European Union | Adequacy decision or standard contractual clauses, supplemented where necessary by additional measures |
| Keeping and publishing an up-to-date list of sub-processors | Annex 3 of the data processing agreement |
| Periodic monitoring of the commitments of artificial intelligence model providers | to be completed |
Deletion and end of life of data
| Measure | Implementation |
|---|---|
| Deletion of data at the end of the contract | As provided in the data processing agreement and the terms |
| Automated purge when retention periods expire | to be completed |
| Secure erasure of media | Provided by the host's procedures |
| Certificate of deletion issued on request | Provided for in the data processing agreement |
Correspondence with article 32 of the GDPR
| Requirement of article 32 | Section of this document |
|---|---|
| Pseudonymisation and encryption of data (art. 32.1.a) | Encryption and protection of data; Development and security maintenance |
| Confidentiality, integrity, availability and resilience of systems (art. 32.1.b) | Access control; Encryption; Infrastructure; Logging; Backup |
| Restoring the availability of and access to data after an incident (art. 32.1.c) | Backup, continuity and recovery |
| Process for regularly testing and evaluating the effectiveness of the measures (art. 32.1.d) | Governance; Development; Backup |
| Taking account of the risks of the processing (art. 32.2) | Governance; Management of incidents |
| Processing on instructions only (art. 32.4) | Awareness; Access of TW3 staff |
Review
This document is reviewed at least once a year and at each significant change of the technical architecture, the scope of processing or the applicable regulations.