-
Notifications
You must be signed in to change notification settings - Fork 258
feat(storage): add doc on hosting health data MTA-6713 #5786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 9 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
fd2ac7c
feat(storage): add doc on hosting health data MTA-6713
SamyOubouaziz 5b2eeaf
feat(storage): update
SamyOubouaziz 48363c4
feat(storage): update
SamyOubouaziz e19df90
feat(storage): update
SamyOubouaziz 6791175
feat(storage): update
SamyOubouaziz 922bba7
feat(storage): update
SamyOubouaziz 76318bb
feat(storage): update
SamyOubouaziz 7af64d3
feat(storage): update
SamyOubouaziz 7daaecf
Apply suggestions from code review
SamyOubouaziz 33bf816
feat(storage): update
SamyOubouaziz 04b9935
feat(storage): update
SamyOubouaziz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
366 changes: 366 additions & 0 deletions
366
pages/block-storage/reference-content/storage-shared-responsibility-model.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,366 @@ | ||
| --- | ||
| title: Scaleway storage services shared responsibility model | ||
| description: Learn about the shared responsibility model for Scaleway Block Storage and Scaleway Object Storage, outlining the roles of Scaleway and users in managing data encryption security, and healthcare data hosting (HDS) compliance. | ||
| tags: storage shared responsibility model compliance hds health data hosting | ||
| dates: | ||
| created: 2025-11-12 | ||
| validation: 2025-11-12 | ||
| --- | ||
|
|
||
| This document outlines the roles and responsibilities for maintaining and securing your Scaleway storage services, Block Storage and Object Storage including Glacier. Our shared responsibility model clarifies the division of duties between Scaleway and our users, ensuring clarity in managing availability, backups, configurations, and security measures for your storage solutions. By understanding this shared responsibility, you can optimize the performance, reliability, and security of your Scaleway storage services. | ||
|
|
||
| ## Service Provision | ||
|
|
||
| Scaleway is responsible for the operational maintenance of all components essential to providing the Service. These include: | ||
SamyOubouaziz marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| * **Physical Infrastructure:** Managing the physical sites that house the hardware infrastructure used for the Service. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| * **Hardware Infrastructure:** Maintaining the underlying hardware. Monitors resource utilization rate and updates its capacity plan. | ||
|
|
||
| * **Virtual Infrastructure:** Ensuring the functionality of the virtualized environment. | ||
|
|
||
| * **Hosting Platform:** Operating the application and database hosting platform. | ||
|
|
||
| * **Network:** Establishes storage space connectivity in its default configuration. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| * **Applications and Databases:** Maintaining the applications and databases themselves. | ||
|
|
||
| Furthermore, Scaleway procures the necessary licenses and usage rights for any third-party solutions that are either used by Scaleway in delivering the Service or made available to the client as part of the Service. It provides the client with necessary information regarding the characteristics and conditions of use of the Service. It also plans and implements updates to the various Service components also considering third-party products used within the Service. | ||
SamyOubouaziz marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| You are responsible of ensuring that users comply with the Service's terms of use. | ||
|
|
||
| Scaleway is responsible for monitoring, managing, and forecasting the Services APIs and physical clusters capacity. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| You are responsible for informing Scaleway ahead of time for significant changes in your storage capacity forecast. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ## Logs and Monitoring | ||
|
|
||
| Scaleway is responsible for the proper monitoring of the Service, including: | ||
|
|
||
| * Retaining access logs and event traces related to the use and administration of the Services, such as objects and storage spaces (volumes, buckets) creation and deletion, server configuration (including physical and software resource configuration), and user and access rights additions and deletions. | ||
|
|
||
| * Making access logs and event traces available to the client upon request. | ||
|
|
||
| ### Your Responsibilities | ||
|
|
||
| * Retain access logs and event traces provided by the Service Provider. | ||
|
|
||
| * Ensure the successful completion of tasks performed while using the Service (e.g., volume creation for Block Storage, implementing integrity checksums for Object Storage). | ||
|
|
||
| * Monitoring the available and remaining space within your provisionned volumes. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ## Product Resiliency | ||
|
|
||
| ### Availability and Steadiness | ||
|
|
||
| Scaleway ensures high availability through resilient infrastructure, technical and organizational measures, including monitoring service health and incident detection for the data hosted within the Service. Scaleway provides and maintains the operational condition of the control plane and APIs. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| Scaleway is responsible for: | ||
|
|
||
| * Implementing resiliency for the Services at least within an Availability Zone (AZ), and for multi-AZ storage tiers only across multiple Availability Zones. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| * Monitoring service health, performance, and balancing the load of use of the Service. | ||
|
|
||
| You are responsible for: | ||
|
|
||
| * Implementing technical and organizational measures to ensure the continuity of your activities, taking into account the conditions of use and characteristics of the Service, including the nature and criticality of data stored. | ||
|
|
||
| * Configuring the Service in accordance with your needs, particularly in terms of availability. | ||
|
|
||
| * Monitoring and notifying breaches of Service Level Agreement concerning the availability of the service. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| #### Performance | ||
|
|
||
| You are responsible for optimizing your applications' use of Storage Services. Scaleway monitors and optimize infrastructure-level performance, but note that: | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| * Glacier cold storage data access requires object restoration and can incur delays, | ||
|
|
||
| * For Object Storage Service, multipart uploads and concurrent requests should be used for large files. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| **Data Integrity** | ||
|
|
||
| For all Storage Services, you are responsible for: | ||
|
|
||
| * Verifying the successful completion of read and write operations. | ||
|
|
||
| * Verifying the successful completion and integrity of backups. | ||
|
|
||
| For the Object Storage Service, Scaleway provides a checksum of each uploaded object allowing the client to perform integrity control or control the integrity of the checksum provided to the client at the time of upload, if applicable. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| You are responsible for: | ||
|
|
||
| * Verifying the successful completion of the upload via a checksum control. | ||
|
|
||
| * Controlling the availability and integrity of objects, and restoring damaged objects. | ||
|
|
||
| ## Backups and Replication | ||
|
|
||
| While Scaleway provides internal resiliency mechanisms and features, it is your responsibility to implement a backup strategy appropriate to your needs and the criticality of your activities, including: | ||
|
|
||
| * External backups. | ||
|
|
||
| * Replication to other regions (as allowed by regulations). | ||
|
|
||
| * Management over your backups and snapshots, and regular control of their integrity. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| Internal resilience does not protect against accidental deletions or application-level corruption. | ||
|
|
||
| ## Configuration and Management | ||
|
|
||
| Scaleway is responsible for the configuration of API and dataplane settings. | ||
|
|
||
| You are responsible for managing the state of your storage spaces and objects. This includes monitoring and configuring service-level features and policies available for your storage space. | ||
|
|
||
| You are responsible for: | ||
|
|
||
| * Creating storage spaces (buckets, volumes) | ||
|
|
||
| * Provisioning additional space or storage spaces according to your needs | ||
|
|
||
| * Managing volumes attachment, detachment and deletion according to your needs | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| * Managing snapshots and snapshots deletion according to your needs | ||
|
|
||
| ### Object Storage Class & Lifecycle Rules | ||
|
|
||
| You are responsible for selecting appropriate storage classes, cleanup unnecessary parts or data, and using lifecycle rules according to your needs. Note that a delay may occur if transitioning or expiring a high number of objects through lifecycle rules per day. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ### Access Control | ||
|
|
||
| Scaleway provides versioning, IAM, and specific Service-level access control tools (ACLs, bucket policies.) | ||
|
|
||
| You are responsible for managing authorizations and access of your personnel to the Service (Console, API and storage spaces), also ensuring the security of your personnel's authentication means. Your responsibilities include: | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| * Ensuring public visibility settings align with your intentions. | ||
|
|
||
| * Regularly reviewing access rules and permissions. | ||
|
|
||
| * Activating two-factor authentication (2FA). | ||
|
|
||
| * Configuring bucket policies (access limitation under certain conditions such as IP with white list and black list (allow or deny, IP range)). | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| Scaleway enforces your configurations but does not intervene in their definition or maintenance. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ### Versioning | ||
|
|
||
| You are responsible for | ||
|
|
||
| * Enabling or deactivating versioning for data recovery. | ||
|
|
||
| * Managing versioned object lifecycle according to your needs. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ## Encryption and Data Deletion | ||
|
|
||
| ### Encryption | ||
|
|
||
| You are responsible for using the encryption methods provided by Scaleway or other third-party encryption solutions. | ||
|
|
||
| For client-side encryption or customer-managed encryption keys, you are responsible for: | ||
|
|
||
| * Managing your encryption keys securely, including activating HTTPS for secure transit. | ||
|
|
||
| * Guaranteeing availability, resiliency, or backups for your keys. | ||
|
|
||
| * Handling key lifecycle management, rotation, and secure storage. | ||
|
|
||
| * Ensuring data becomes permanently inaccessible when keys are destroyed. | ||
|
|
||
| ### Encryption in Transit | ||
|
|
||
| Scaleway provides secure HTTPS endpoints. You must: | ||
|
|
||
| * Ensure clients use HTTPS. | ||
|
|
||
| * Avoid transmitting unencrypted data. | ||
|
|
||
| * Validate certificates and enforce TLS in custom tools. | ||
|
|
||
| ### Data Deletion | ||
|
|
||
| Deletion is initiated only by you, manually or via configured retention rules. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| Scaleway: | ||
|
|
||
| * Deletes volumes/snapshots/objects upon request, or after the configured retention period. | ||
|
|
||
| * Does not check volume/snapshots/object content before deletion. | ||
|
|
||
| * Cannot recover data if versioning is not enabled. | ||
|
|
||
| ## Data Residency | ||
|
|
||
| * The customer is responsible for selecting the data location at the time of volume/bucket creation. | ||
|
|
||
| * Scaleway commits not to modify the geographical location of data without the prior agreement of the customer. | ||
|
|
||
| * The Glacier class systematically stores objects in Paris, regardless of the Region chosen for the bucket. | ||
|
|
||
| ## Identity and Access Management | ||
|
|
||
| Scaleway provides tools for access control (IAM, ACLs, and policies). You are responsible for: | ||
|
|
||
| * Defining and regularly auditing permissions. | ||
|
|
||
| * Following least-privilege principles. | ||
|
|
||
| * Managing and protecting API keys and credentials. | ||
|
|
||
| * Detecting and responding to unauthorized access. | ||
|
|
||
| ## Platform and Service Security | ||
|
|
||
| ### Scaleway Responsibilities | ||
|
|
||
| Scaleway ensures: | ||
|
|
||
| * Physical and network security of datacenters. | ||
|
|
||
| * Resiliency according to storage class criteria and DDoS protections. | ||
|
|
||
| * Risk analysis and mitigation related to the implementation and provision of services. | ||
|
|
||
| * Detecting security threats or data violations. | ||
|
|
||
| Scaleway manages the authorizations, controls and secures the access of its personnel to the Service management interfaces, API, servers, network equipment and other components used within the Service. Scaleway ensures the security of its personnel's authentication means. | ||
|
|
||
| Scaleway manages and monitors vulnerabilities related to the provision of its Services (infrastructure, OS, software, etc.) and implements corrective measures. | ||
|
|
||
| See Security & Resilience and Trust Center. | ||
|
|
||
| ### User Responsibilities | ||
|
|
||
| You are responsible for: | ||
|
|
||
| * Securing your applications and clients. | ||
|
|
||
| * Conducting risk analysis and mitigation related to your use of the Service. | ||
|
|
||
| * Controlling and protecting access to hardware infrastructures and hosting sites that are not under Scaleway's control and responsibility. | ||
|
|
||
| * Implementing proper error handling. | ||
|
|
||
| * Monitoring your usage, logs and patterns. | ||
|
|
||
| * Conducting periodic vulnerability tests, and applying corrective measures, also for third-party and open-source products | ||
|
|
||
| * Communicating known vulnerabilities, security incidents, or detected anomalies to Scaleway. | ||
|
|
||
| ## Service termination | ||
|
|
||
| You determine when to terminate using the Service and are responsible for: | ||
|
|
||
| * Planning and implementing reversibility operations. | ||
|
|
||
| * Recovering all data. | ||
|
|
||
| * Ensuring the complete finalization of reversibility operations before triggering the deletion of objects, snapshots or storage spaces (volumes, buckets). | ||
|
|
||
| * Confirming the successful deletion of storage resources at the end of the reversibility process. | ||
|
|
||
| Scaleway undertakes to: | ||
|
|
||
| * Maintain the availability of the Service until the effective termination date to ensure the smooth progress of reversibility operations. | ||
|
|
||
| * Make available to the Client, upon simple request, its reversibility policy as well as any relevant information for the execution of these operations. | ||
|
|
||
| * Guarantee the effective deletion of storage resources upon deletion request. Scaleway is responsible for deleting all data from the storage material before disposal and destroying the storage media. | ||
|
|
||
| * Provide a data deletion certificate upon request. | ||
|
|
||
| ## HDS specifics (Hébergement de Données de Santé) | ||
|
|
||
| This section outlines the specific requirements and responsibilities for hosting healthcare data in compliance with the HDS regulatory framework. | ||
|
|
||
| ### HDS Compliance Requirements | ||
|
|
||
| When storing healthcare data within Scaleway Storage Services, the client is responsible for: | ||
|
|
||
| * Signing Scaleway's HDS contract. | ||
|
|
||
| * Ensuring access is restricted to authorized personnel. | ||
|
|
||
| * Creating new volumes, snapshots, or buckets specifically for uploading HDS-compliant data. | ||
|
|
||
| * Following Scaleway’s documentation on ensuring HDS compliance. | ||
|
|
||
| * Using authorized storage classes only and not using the object lifecycle rules feature. | ||
|
|
||
| Scaleway undertakes to provide HDS-certified infrastructure, and commits to maintain this certification. The loss of said certification may result in the termination of Scaleway’s commercial relationship with the HDS client. The aforementioned elements are included in the HDS contract signed by the client. | ||
|
|
||
| ### Data Residency | ||
|
|
||
| Scaleway guarantees that data remains within the authorized datacenters in Paris and does not access personal health data hosted by the client. | ||
|
|
||
| You must: | ||
|
|
||
| * Create storage spaces (volumes, buckets, snapshots) containing healthcare data in France only. | ||
|
|
||
| * Configure replication within the authorized geographical perimeter (France) only. | ||
|
|
||
| * Ensure backups residency remains within the authorized geographical perimeter (France only) | ||
|
|
||
| You must not configure replication, snapshots, backups or transfer data to regions outside the authorized perimeter. | ||
|
|
||
| ### HDS-compliant Resources Identification | ||
|
|
||
| You are responsible for: | ||
|
|
||
| * Knowing which Storage resources are HDS or not. | ||
|
|
||
| * Attaching volumes to HDS-compliant Instances only. | ||
|
|
||
| ### Block Storage Encryption and Data deletion | ||
|
|
||
| Encryption at rest is mandatory for Volumes hosting healthcare data. Deleted data cannot be restored. | ||
|
|
||
| When using Block Storage, you are required to: | ||
|
|
||
| * Encrypt volumes | ||
|
|
||
| * Ensure secure key deletion after deleting data within your volumes to meet compliance requirements. | ||
|
|
||
| Scaleway is responsible for: | ||
|
|
||
| * Encrypting at rest the physical disks on which volumes are stored with state-of-the-art compliant encryption keys. | ||
|
|
||
| * Managing the lifecycle, rotation and deletion of the disk encryption keys to access the underlying instances. | ||
|
|
||
| ### Object Storage Encryption and Data deletion | ||
|
|
||
| Encryption at rest is mandatory for Object Storage buckets hosting healthcare data, with HDS-compliant key handling by Scaleway. Scaleway provides HDS-compatible mechanisms to encrypt data at rest and guarantee HDS-compliant data deletion. | ||
|
|
||
| When using the Object Storage service, you are required to: | ||
|
|
||
| * Follow the guidelines detailed in the documentation in order to enforce the additional encryption mechanisms required for HDS compliance. | ||
|
|
||
| * Ensuring client-side data encryption or relying on existing encryption methods provided by Scaleway Object Storage. | ||
|
|
||
| * Enforcing additional encryption mechanisms to guarantee HDS-compliant data deletion as described in documentation. | ||
|
|
||
| #### Data deletion | ||
|
|
||
| * Deletion of data stored in HDS-compliant buckets is irreversible: keys are destroyed using compliant crypto-shredding methods, | ||
|
|
||
| * Deleted data cannot be restored, | ||
|
|
||
| * The client must ensure backups before deletion. If SSE-C is used, the client must ensure secure key deletion to meet compliance requirements. | ||
|
|
||
| Scaleway must maintain technical guarantees for secure deletion of healthcare data. | ||
|
|
||
| ### HDS-compliant Storage Classes and Prohibited Features | ||
|
|
||
| For the Object Storage service: | ||
|
|
||
| * You must use authorized HDS-certified storage classes only (Standard, One Zone). Glacier class is not HDS-compliant and must not be used by the client to store healthcare data. | ||
|
|
||
| * You must not use the lifecycle rules feature that is not permitted for HDS-compliant buckets hosting healthcare data. | ||
|
|
||
| For the Block Storage service: | ||
|
|
||
| * You must not use legacy Block volumes and snapshots to host your HDS-compliant healthcare data. | ||
|
|
||
| * If exporting/importing snapshots to and from Scaleway Object Storage, you must ensure to follow the above guidelines for end-to-end compliance across the Services. | ||
|
|
||
| <Message type="important"> | ||
| This documentation must be read in conjunction with Scaleway's HDS contract and current certifications. In case of doubt, contact HDS support for clarification. | ||
| </Message> | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.