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

# Security overview

## Introduction to Glesys security commitment

Glesys incorporates security into the design and operation of its platform. Security is managed through a single Integrated Management System (IMS), which also includes sustainability and quality, ensuring consistent processes across the organization.

The Security Policy defines the management of physical security in data centers, fire protection, information security, business continuity, and related areas. It aligns with ISO/IEC 27001 and is reviewed regularly to reflect current risks, regulations, and industry standards. Glesys provides transparency regarding its security practices.

## Contact and responsible disclosure

If you identify a vulnerability or have concerns about a potential security issue in a Glesys service, report it to <security@glesys.com>.

Glesys provides [Responsible disclosure and vulnerability reporting](/security/security-overview/responsible-disclosure-and-vulnerability-reporting.md) and encourages ethical security research. All reports are reviewed by the security team, and responses are issued as promptly as possible.


---

# 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.glesys.com/security/security-overview.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.