Configuring an Integration with GLPI
It is possible to send data from Cyberwatch to the IT service management tool GLPI using a micro-proxy provided by Cyberwatch.
This integration allows you, for example, to automatically generate a GLPI ticket from a security alert detected on an asset, or to create one manually from the Cyberwatch interface.
The goal is to simplify vulnerability management by integrating Cyberwatch into your GLPI workflow.
Prerequisites
To use this integration, you need:
- A GLPI instance with the REST API enabled.
- The required API tokens (app_token and user_token) for authentication.
- Access to the machine hosting Cyberwatch to deploy the micro-proxy.
All technical setup steps are available in the GitHub documentation linked at the bottom of this page.
Use Case Examples
Manually create a GLPI ticket from Cyberwatch
A user can trigger a GLPI integration directly from an asset’s patch management page. This allows the creation of a ticket containing the details of the vulnerabilities affecting the machine, along with a proposed update.
Automatically create a GLPI ticket from an alert
The integration can be linked to a Cyberwatch alert to create a daily ticket in GLPI if new critical CVEs are detected on your infrastructure. This helps automate communication between security and IT teams.
Setting Up the Integration
The integration is based on a lightweight micro-service developed by Cyberwatch, which acts as a proxy between Cyberwatch and your GLPI instance.
The following GitHub repository contains all the technical instructions to configure this integration: