Overview

Oracle Audit Vault and Database Firewall (AVDF) raises alerts for suspicious database activity. AVDF sends alerts by email and syslog rather than by webhook, so the reliable way into SQIBS is through the log platform that already receives your syslog: it alerts on the AVDF messages and sends that alert to SQIBS.

You need
AVDF with admin access, a syslog receiver or log platform, and a SQIBS API token
Setup time
About 30 minutes
Result
AVDF alerts open SQIBS incidents

How it works

AVDF
Alert fires
An alert policy matches database activity.
AVDF
Sends a webhook
AVDF sends the alert to syslog; your log platform forwards it.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
The log platform's SQIBS filter opens it.

Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.

Step 1: Send AVDF alerts to syslog

  1. In the AVDF console, configure the syslog destination (your log platform's syslog receiver) in the system settings.
  2. Turn on alert forwarding to syslog, and make sure your alert policies have the right severity, so the log platform can tell critical alerts apart.

Step 2: Alert on AVDF messages and send them to SQIBS

In your log platform, create an alert on the AVDF syslog messages (for example, any AVDF alert with critical severity) and send it to SQIBS. Follow the SQIBS page for your platform:

That page shows the SQIBS filter and the JSON key creator for the platform's alert format.

Fix known issues automatically

Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, when AVDF flags repeated failed logins for a database account, SQIBS can run a workflow that locks the account and adds the source address to the incident.

Incident opens
Workflow starts
SQIBS runs the automation workflow linked to the filter.
Fixed
Incident resolved
The issue is fixed before anyone has to step in.
Not fixed
Escalated to the engineer
After the waiting time you set, the escalation policy pages on-call as usual.

Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.

To set it up, in the same API filter:

  1. Select Workflow: choose the automation workflow to run when this filter opens an incident.
  2. If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
  3. Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.

Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.

Learn more: