Audit logging
A reviewable record of administrative and access events for your databases and account.
Silos keeps an audit log — a record of significant administrative and access events — so you can see who did what, and when. The audit trail is available in the Console under your account's activity view.
What gets recorded
Audit events capture the kinds of actions that change your resources or access them:
Database lifecycle
Creating, suspending, resuming, and deleting databases.
Branch operations
Creating, restoring, and deleting branches.
Access & credentials
API key creation and revocation, and authentication-related events.
Configuration changes
Changes to settings such as IP allowlists and account configuration.
Reviewing the log
Open the activity / audit view in the Console to browse events. Each entry records what happened, the resource it affected, and when it occurred, so you can trace a change back to its source.
Make audit review part of your routine — periodically scanning for unexpected database creations, key changes, or configuration edits is a cheap, high-value security habit.
Good practice
- Review regularly. Look for resource changes you don't recognize, especially around API keys and database deletion.
- Pair with least privilege. The fewer principals that can perform sensitive actions, the easier the audit log is to reason about.
- Rotate on suspicion. If an audit entry looks wrong, revoke the relevant API key and rotate credentials — see Authentication.