A Look at Data Auditing in DataStax Enterprise 3.0

DataStax Enterprise (DSE) 3.0 and above supports data auditing on a database cluster, allowing administrators to understand user activity such as who looked at what/when and who changed what/when. Auditing is implemented via the log4J mechanism, providing flexibility in controlling what is audited, where the data is written, and how it is presented. It is disabled by default and can be enabled by editing the log4j-server.properties file. The granularity of auditing can be controlled using the ActiveCategories setting. Audit logs can be written to a table/column family with DSE's built-in encryption for sensitive data. Hadoop and Solr user activities can also be audited in DataStax Enterprise.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.