03:12:04
The session is recorded.
app_batch is a service account that normally connects during business hours from the same application server. In this scenario it connects from a previously unseen IP address, using a desktop SQL client.
QubeSight maintains a behavioural baseline for every account by time, source and client, and records any deviation from it.
03:12:09
The event enters the pipeline.
The activity record arrives from IBM Guardium via syslog, SNMP or archive, or from the database's native audit log. Vector parses it, Redpanda queues it, the worker analyses it and ClickHouse stores it.
The pipeline is designed to be lossless: new records are never deleted, even when disk capacity runs out.
03:12:10
The SQL statement is parsed.
The worker parses each statement into a syntax tree rather than matching text, identifying every object accessed, including tables in joins and subqueries.
The sensitive data catalogue recognises the national_id and pan columns and maps them to the applicable regulation, such as PCI DSS.
03:12:11
Rules are evaluated.
Each record is evaluated against the rule set as it is written. Built-in detections cover brute-force attempts, SQL injection, bulk deletion, privilege escalation and insider data exfiltration, and organisation-specific rules can be added.
In this example all four conditions are met, so the event is classified as critical.
03:12:12
The right teams are notified.
The alert is delivered through the configured channels: email, syslog over TLS to your SIEM, or webhook. Notifications can be sent in English or Turkish.
A false positive can be turned into a suppression rule in a single step, using the link in the alert email.
03:14
The incident is investigated in one view.
Mindmap shows the user's sessions with their open and close times, the statements in each session, the tables accessed and any violations, all in a single view.
Security operations teams can assess the scope of an incident in minutes, without sifting through raw logs.
09:00
Audit evidence is ready.
Records are retained in an immutable archive, and Guardium archives are verified with SHA-256. A signed evidence pack can be provided directly in response to an audit request.
Evidence for PCI DSS and data-protection audits is available from the moment the event occurs.