Create an integration
Register a system from your company (SIEM, EDR, inventory or other) so it sends its events to the platform.
On this page
An integration represents an external system that sends information to the platform: for example, your production Wazuh or your vulnerability scanner. When you create it, you choose what that system provides and, if you want, the address where it will send its events is generated right away.
Before you start
You need the Administrator role in your company. With another role, the New integration button is disabled and, when you hover over it, it says Only an administrator can create integrations.
Have the system's API address at hand (if you want to test the connection from the platform) and its credentials, if it requires them.
Steps
Go to Settings → Integrations.
Press New integration (or Create an integration if you don't have any yet).
Fill in the system details:
Name: how you'll recognize it on the platform, for example "Wazuh production".
Category: SIEM, SOC, EDR, Vulnerability scanner, Inventory / CMDB, CRM, Help desk (ITSM), Monitoring, Argunis Monitoring or Other.
Provider: the product, for example
wazuh. Below the field, suggestions appear based on the category (for example, for SIEM: wazuh, splunk, sentinel, qradar, elastic); press one to use it. You can also type another. It is saved in lowercase.Base URL (optional): the system's API address. It is used to test the connection.
Health path (optional): the path queried when testing the connection, for example
/health. If you leave it empty, the base URL is queried.
In Authentication, choose how the platform identifies itself to the system and fill in its fields. We explain this in Access credentials. If the system will only send events and you don't need to test the connection, leave No authentication.
In What this integration provides, check what the system will send: Assets for the inventory, Alerts, Incidents or Vulnerabilities. Alerts is checked by default.
If you want the most serious events handled without waiting, check Open an incident automatically for critical events: critical-severity alerts and incidents are escalated to an incident automatically.
Leave Receive events by webhook checked if the system will send its events to the platform (the usual case). It generates a URL and a signing secret. If you uncheck it, you can enable it later from the card.
Press Save. The button is enabled once you've entered the Name and the Provider.
If you left Receive events by webhook checked, when you save the Webhook enabled window opens with the URL and the Signing secret. The secret is shown only once: copy it before closing. Continue in Enable the webhook and send events.
Check Assets for the inventory only on inventory or discovery systems. If it isn't checked, asset events are stored but don't add discovered assets.
What happens next
You'll see Integration created. and a new card in the Integrations tab, with Active status. The card shows:
The category and the provider.
What it provides (or No capabilities selected) and Automatic incident, if you checked it.
Authentication, with the hint of the saved credential.
Webhook: Active or Disabled.
Last event and Last sync (at first, Never).
Base URL and Webhook URL, with a button to copy it.
When the system sends its first event, Last event is updated and the event appears in Received events.