Solutions

Monitoring, audit and access control, and column encryption, each as its own product.

01 Audit and access

AUDIGATE

After a connection pool, the database usually sees a shared application account. AUDIGATE binds the authenticated person and the WAS session to the database session, and turns privileges on only for an approved window.

AUDIT

Audit the objects and columns you named ahead of time. A light agent injects the real user and the WAS session id. SQL, object, and column land on one audit event. On Oracle, DBMS_FGA covers columns that Unified Audit does not.

GATE

Instead of a standing GRANT: request, approval, a per-job AUTH-KEY, then apply_my_roles in the session to enable a dynamic role. The role is taken back when the window or the session ends. Connect with DBeaver, SQL Developer, or PL/SQL Developer.

02 Monitoring

ILYX

Agents collect metrics. The browser console draws live charts over WebSocket. Oracle sessions, locks, ASH, AWR, and SQL Monitor; PostgreSQL realtime and ASH; WAS transactions and threads; host CPU, disk, and NIC — one server.

Databases: Oracle, PostgreSQL
Applications: WAS (J2EE) transactions, threads, URIs
Host: CPU, filesystem, NIC
Server: 3.2.7 as of October 2026

03 Column encryption

AUDICIPHER

Encrypt chosen columns, not the whole table. A data key (DEK) locks the value. A key-encryption key (KEK) wraps the DEK. Applications that present a session token keep their SQL. A direct connection without a token sees ciphertext.

Databases: PostgreSQL, MySQL, SQL Server
Algorithm: AES-256-GCM
Keys: DEK / KEK envelope encryption
Rotation: Policy schedule: 30, 60, 90, 180, or 365 days