> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/object-storage/concepts/resilience-and-security.md).

# Resilience and security

Triple replication, offsite copy, encryption, and compliance that protect your data.

Durability and security are built into the service design; they aren't something you add on later.

This is what protects what you store.

### Triple replication

Each object is stored three times, on three disks across three different servers. If a disk or a server fails, the other copies keep the data available.

Also, by default at least one of those copies is kept in a **different data center**, so the data survives even the loss of an entire location.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FeM2p11o7z8tKpZZZ6ogi%2Fdiagram-object-storage-triple-replication.png?alt=media&amp;token=5195b13a-d5f9-4303-8f74-f5fe03c8ca68" alt="Diagrama de triple réplica: cada objeto se guarda en tres servidores, uno de ellos en otro centro de datos"><figcaption><p>Each object is stored three times, with at least one copy in another data center: if a disk or a server fails, your data remains available</p></figcaption></figure>

> #### 📘 High durability by design
>
> Triple replication and the copy in another location are designed for very high data durability. Even so, versioning remains your best defense against deletions or overwrites, because those errors are replicated just like the good data.

### Encryption and access

| Layer      | Protection                                               |
| ---------- | -------------------------------------------------------- |
| In transit | Access to the repository is encrypted via HTTPS          |
| At rest    | Objects are stored encrypted                             |
| Access     | Through S3 credentials, which you control and can rotate |

### Compliance

The service falls within the platform's certifications and regulations, designed for the different markets in which we operate.

| Framework | What it certifies                         | Scope          |
| --------- | ----------------------------------------- | -------------- |
| ISO 27001 | Information security management           | International  |
| ENS       | National Security Scheme                  | Spain          |
| HDS       | Health Data Hosting Provider, health data | France         |
| GDPR      | General Data Protection Regulation        | European Union |

### Where to continue

* How you recover previous versions: [Buckets and objects.](https://docs.plenit.com/docs-en/productos/object-storage/concepts/buckets-and-objects.md)
* Who and what accesses the repository: [S3 access: users and credentials.](https://docs.plenit.com/docs-en/productos/object-storage/concepts/s3-access-users-and-credentials.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plenit.com/docs-en/productos/object-storage/concepts/resilience-and-security.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
