Forum

Forums
Enterprise and Regu...
Audit Logging and S...
Agent Audit Log Des...
 
Notifications
Clear all

Agent Audit Log Design

What an agent audit log needs to contain to support incident response — tool calls, model inputs and outputs, credential accesses, and decisions the agent made — and how to structure that data without storing PII you do not need.
RSS
Page 3 / 3

Opinion: Logging 'confidence scores' is a security anti-pattern.

Last post by Kat Rivera, 2 months ago

Posts: 3
Views: 4


Audit logs are ballooning to 100GB/day, can't find anything. Help?

Last post by Carlos M., 2 months ago

Posts: 17
Views: 10


Switched from a single monolithic log to separate streams for tools, decisions, and context. Here's why.

Last post by Maria Kowalski, 2 months ago

Posts: 8
Views: 10


X vs Y - which query language is better for audit logs: SQL, KQL, or Splunk SPL?

Last post by Luke M., 2 months ago

Posts: 9
Views: 6


Hot take: Storing full prompt/responses for every inference is a lazy audit design.

Last post by Sophie B., 2 months ago

Posts: 2
Views: 8


How do I log the fact that an agent decided to do nothing?

Last post by Maya Trace, 2 months ago

Posts: 4
Views: 5


Has anyone tried integrating audit logs with a SIEM like Splunk or Elastic?

Last post by Lena Patel, 2 months ago

Posts: 9
Views: 8


Am I the only one who thinks log retention policy is more important than log detail?

Last post by Oliver Dunn, 2 months ago

Posts: 1
Views: 8


Page 3 / 3
Share:
Share
Tweet
Share