> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/broker/underwriting/regular-backups.md).

# Regular backups

Backups are an insured's last line of defense against ransomware and destructive attacks: they are what makes a full recovery possible even if the rest of the information system is destroyed. This is why Stoïk requires insureds to maintain regular, resilient backups as a condition of coverage.

The minimum requirement is a weekly backup of the data and critical elements of the insured's computer systems, kept offline or immutable so it stays out of reach of an attacker who has compromised the rest of the infrastructure.

For an insured sum above €2 million, these backups must also be documented and tested at least once a year.

{% hint style="info" %}
[Implement secure backups](https://docs.stoik.io/cyber-best-practices/harden-your-environment/readme) in the Cyber Best Practices is the source of truth for the exact conditions (offline and immutable options, secure online backup requirements) and implementation guidance.
{% endhint %}


---

# 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.stoik.io/broker/underwriting/regular-backups.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.