> 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/en/underwriting/regular-backups.md).

# Regular backups

Do insureds create backup copies of the data and critical elements of their computer systems at least once a week? These backups must be stored:

* on a physical backup medium that belongs to an insured and is disconnected from the rest of the computer system (offline backup). This includes USB drives, external hard drives, and computers that are never connected to the internet or to any other element of the insureds' computer system; or
* on a backup medium that is part of the insureds' computer system, whose data cannot be altered or deleted due to the immutable nature of the backup copy (immutable backup); or
* on a computer system that meets the following conditions:
  * The computer system is not part of a Windows domain;
  * All credentials usable on this system are unique within the infrastructure, or multi-factor authentication (MFA) is required to access this system (and the data/backups on it).

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


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stoik.io/broker/en/underwriting/regular-backups.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.