> 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-measures/incident-management.md).

# Incident management

Glesys maintains documented procedures to detect, report, assess, respond to, and learn from incidents affecting network and information systems.

### Key elements:

* **Detection and reporting**: Incidents are detected via monitoring tools, logs, and user reporting, and are reported through established internal channels.
* **Categorization & prioritization:** Incidents are categorized (e.g., Security/PII/IT) and prioritized using urgency/impact with target response and resolution times.
* **Roles and escalation:** Security incidents involve the Security Manager; PII incidents involve the DPO; responsibilities are defined for managers and staff.
* **Root cause & continual improvement:** Post-incident reviews are performed and corrective actions are tracked to prevent recurrence.


---

# 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-measures/incident-management.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.