Concepts

Logs

Understand Secryn’s audit, request, user, and MCP logs.

Secryn records audit, request, user, and MCP logs for troubleshooting and review. Log rows are timestamped in UTC and visible only to admins. They are ordinary database records: they are not hash-chained, signed, or otherwise tamper-evident, and someone with database access can change or delete them.

Audit Logs

Capture security-sensitive actions such as user sign-ins, resource creation, role changes, public URL updates, backups/restores, and setup wizard events. Each entry records the actor, action, target, timestamp, and source IP. Before and after values stored on an audit entry are encrypted with Laravel encryption keyed by APP_KEY.

Request Logs

Track API activity, including endpoint, method, status code, timestamp, auth context (user or access key), and execution duration. Sensitive payload data is never logged.

User Logs

Show user-level events like authentication attempts, failed access, role changes, and actions performed within projects and vaults.

MCP Logs

Document MCP server lifecycle events, client handshakes, tool/resource requests, authorization outcomes, and errors. MCP logs never include secret values or private keys.

Retention & Security

  • timestamps are stored in UTC
  • retention follows system configuration
  • request logs do not store secret values
  • audit before and after values are encrypted with Laravel encryption keyed by APP_KEY
  • log access in the web interface is limited to admins
  • the rows are not tamper-evident

Use these logs to review activity and troubleshoot automation. They are not a tamper-evident audit trail, and Secryn has not completed a third-party audit or penetration test.