Activity Logs¶
Settings
Activity Logs provide a comprehensive audit trail of every action taken in your organization — who did what, when, and from where.
Overview¶
Compliance frameworks and auditors require evidence that security controls are not just configured but actively monitored and governed. Activity Logs capture:
- User sign-ins and sign-outs
- Integration connections and disconnections
- Finding status changes and assignments
- Settings modifications
- Role and member changes
- AI assistant interactions (summary level)
Why it matters¶
| Use case | How activity logs help |
|---|---|
| Audit evidence | Demonstrate who accessed what and when |
| Incident investigation | Trace actions leading to a security event |
| Compliance reporting | Prove continuous monitoring and governance |
| Accountability | Clear record of administrative actions |
What you'll see¶
Each log entry includes:
- Timestamp — When the action occurred
- User — Who performed the action
- Action — What was done (e.g. "Updated integration", "Resolved finding")
- Module — Which part of the platform (Findings, Settings, etc.)
- Details — Contextual information (sensitive fields are masked)
Sensitive data protection¶
Activity logs automatically mask sensitive information — passwords, tokens, and PII are never stored in plain text. This ensures logs are safe to review and share with auditors.
Who uses it¶
- Compliance managers — Audit evidence collection
- Organization admins — Monitoring team activity
- Auditors — Read-only review of governance actions