> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/security-safeguards/report-security-event.md).

# Report a Security Event

This Reporting Guideline will provide information and recommendations on reporting an information security event to IONOS CLOUD.

At <code class="expression">space.vars.ionos\_cloud</code>, we take the security of our customers' data very seriously. We support a responsible disclosure process and appreciate reports by well-intentioned, ethical security researchers. We are committed to thoroughly investigating all reported **information security events** and resolving issues to protect our customers. This document outlines how <code class="expression">space.vars.ionos\_cloud</code> collaborates with its partners, customers, and the security community. It details the scope and the process involved.

### What is an information security event?

An information security event refers to any occurrence that has the potential to impact the security of an organization's information technology systems or data. It includes:

* [<mark style="color:blue;">Malfunctions and Security Incidents</mark>](/cloud/security-safeguards/report-security-event/malfunctions-and-incidents.md)
* [<mark style="color:blue;">Vulnerabilities</mark>](/cloud/security-safeguards/report-security-event/vulnerabilities.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.ionos.com/cloud/security-safeguards/report-security-event.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.