[
https://issues.apache.org/jira/browse/CASSANDRA-12151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466880#comment-16466880
]
Jason Brown commented on CASSANDRA-12151:
-----------------------------------------
bq. Would it not make sense to maintain audit whitelist permissions next to all
other permissions in Cassandra?
This is an intersting idea. However, I'm reticent to introduce CQL grammar
changes this late into this ticket. As a followup, I think this could be worth
exploring.
bq. would it make sense to use the existing Permission type (SELECT, MODIFY,
CREATE...) and IResource (Data, Role, Function...)?
While there's some conceptual overlap, I don't think it's a good idea to try to
force the concepts of 'audit logging' and 'auth' onto one another here.
[~eperott]'s other comments I agree with.
> Audit logging for database activity
> -----------------------------------
>
> Key: CASSANDRA-12151
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12151
> Project: Cassandra
> Issue Type: New Feature
> Reporter: stefan setyadi
> Assignee: Vinay Chella
> Priority: Major
> Fix For: 4.x
>
> Attachments: 12151.txt, CASSANDRA_12151-benchmark.html,
> DesignProposal_AuditingFeature_ApacheCassandra_v1.docx
>
>
> we would like a way to enable cassandra to log database activity being done
> on our server.
> It should show username, remote address, timestamp, action type, keyspace,
> column family, and the query statement.
> it should also be able to log connection attempt and changes to the
> user/roles.
> I was thinking of making a new keyspace and insert an entry for every
> activity that occurs.
> Then It would be possible to query for specific activity or a query targeting
> a specific keyspace and column family.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
