> 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/strategy-for-security-of-network-and-information-systems.md). # Strategy for security of network and information systems Glesys maintains a documented security strategy and governance model to protect the confidentiality, integrity, and availability of information systems and supporting infrastructure. ### Key elements: * **Governance and accountability:** Defined roles and responsibilities across the organization, including Security Manager, System Owners, Information Owners, and Technical Experts. * **Policy framework:** A company-wide Security Policy establishes principles and objectives, including proactive defence, resilience, and continuous improvement. * **Documented control system:** Policies and guidelines are version-controlled, approved, and reviewed annually within the IMS document management process. * **System inventory & classification:** Systems are registered and managed in a centralized System Inventory with assigned ownership, criticality, and information classification. --- # 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/strategy-for-security-of-network-and-information-systems.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.