> 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/risk-management-strategy.md). # Risk management strategy Glesys applies structured risk management to identify, assess, prioritize, treat, and monitor risks that may impact network and information system security. ### Key elements: * **Enterprise risk governance:** A consolidated Enterprise Risk Register and defined approach to evaluating impact/probability, prioritization, ownership, treatment and quarterly executive review. * **Risk-based decision-making:** Risk management is integrated with audits, BIAs, supplier assessments, incidents, and major changes. * **Risk-aware change handling:** Changes affecting systems, services or controls are recorded, assessed proportionally, approved at the right level, and reviewed after implementation. --- # 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/risk-management-strategy.md?ask=&goal= ``` `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.