Aurva Database Activity Monitoring vs Libelle DataMasking

Aurva Database Activity Monitoring is a paid, self-hosted product for monitoring database queries from people, service accounts, and AI agents. It identifies the responsible actor and shows role, application, and access path. For AI agents, it builds behavioral baselines and alerts when activity deviates from expected patterns. Policies can govern access by identity, data sensitivity, location, and time, including blocking access or redacting columns. Aurva describes a passive, out-of-band architecture that monitors traffic without sitting in the query path and says it adds 0 ms of application latency. Deployment options include agent, agentless, combined, cloud, on-premises, and hybrid setups. Named coverage includes PostgreSQL, MySQL, MongoDB, Snowflake, BigQuery, DynamoDB, Kafka, and other stores, with integrations including Databricks, Amazon Athena, Aurora, Redis, and Microsoft SQL Server. Aurva lists audit logging and sensitive-data monitoring aligned with SOC 2 and ISO 27001 objectives. Pricing is custom and available on request.

Libelle DataMasking has no write-up on Specifiction yet; its figures are above.