Saltar al contenido principal

SIEM export

Send your company's audit, security and sign-in events to your own security information system: Splunk, Elastic or Microsoft Sentinel. Open Admin, Settings, Integrations, SIEM export. Reading the page needs audit:read; saving, testing and removing need settings:write. The built-in Owner role has both.

Only your company's events are sent, never another company's. Passwords, tokens and keys are removed from every event before it leaves the PBX. A company has one destination.

What you need from your SIEM​

SIEMCreateEnter on the page
SplunkAn HTTP Event Collector (HEC) token, with the index you want.The HEC address (for example https://splunk.example.com:8088), the index (optional), the source type (optional) and the token.
ElasticAn API key that may create documents in an index or data stream.The address (for example https://es.example.com:9200), the index (lower case, optional) and the API key.
Microsoft SentinelAn app registration with a client secret, a data collection endpoint and a data collection rule with a custom stream.The endpoint, the rule ID (dcr-...), the stream name, the directory (tenant) ID, the application (client) ID and the client secret.

The address must start with https:// and be reachable from the internet. Private, local and loopback addresses are refused, and the address must not contain a user name, a password or a query. The credential is stored sealed with your company's key and is never shown again: leave the field empty when you change something else, and the stored one stays.

Test it​

Select Test to send one test event. A good result reads "The SIEM accepted the test event." A failure shows a short code:

CodeMeaning
unreachableThe PBX could not connect: wrong address, a firewall, a private address, or a time-out.
unauthorizedThe SIEM refused the credential.
not_foundThe address answered but the path, index or rule was not found.
rejectedElastic refused the event (check the index and the key's rights).
sign_in_failedMicrosoft could not sign the app in: check the tenant, application ID and client secret.

Testing the form does not save it. After you save, Test also records the result under Last test.

Status​

The status card shows whether the destination is Up, Down or still Starting, how many events were delivered and how many were lost since it started on this server. Events are lost when the SIEM does not answer for several tries or is too slow; the PBX is never slowed down by it. When events are being lost, your webhooks and the events stream receive integration.siem_events_dropped (at most once every five minutes per destination), and an AI assistant connected through MCP can read the same status with the tool getSiemSinkHealth.

Good to know​

  • Events flow only while the audit log is running on the server.
  • The counters start from zero when the server restarts.
  • Every change to the destination is recorded in the audit log, without the credential.
  • Removing the destination deletes the stored credential. Events already delivered stay in your SIEM.
  • A server runs at most 500 company destinations. If you see that limit, ask the server's administrator.