Can I export iDBQuery audit logs to my SIEM?
Yes. iDBQuery keeps audit logs of user activity that you can export or forward to your own SIEM or log platform, so iDBQuery events sit alongside the rest of your security monitoring. In self-hosted deployments the logs are already in your environment, ready to ship to your existing pipeline.
Getting iDBQuery's audit trail into your SIEM lets your security team monitor it with everything else.
- Full activity record - audit logs capture sign-ins, queries, data-source and permission changes, and administrative actions.
- Export and forward - pull logs out or forward them to your SIEM or log store so they feed your existing dashboards, alerts, and investigations.
- Self-hosted advantage - in a VPC or on-prem install, the logs already reside in your infrastructure, so shipping them to your pipeline is straightforward.
- Retention on your terms - keep a working window in iDBQuery and long-term history in your SIEM, matching your configurable retention policy.
For example, your SOC can alert when an account queries a sensitive source outside business hours by correlating iDBQuery audit events with identity and network logs it already collects. Centralising the trail matters for access reviews and incident response, where a scattered log is a slow log. This complements iDBQuery's access architecture - SSO, RBAC, and row-, column-, and field-level controls - by giving you the evidence of how those controls were exercised, all over encryption in transit and at rest. The audit trail is the accountability layer on top of query-in-place data access. Contact us for the log export formats and integration options for your deployment.
Updated 2026-06-22