Secryn provides comprehensive logging across user activity, API access, system actions, and MCP integrations. Logs are designed for traceability, auditing, security monitoring, and compliance.
All log types support filtering and CSV export for analysis or external archiving.
Secryn includes four primary log categories:
Audit Logs track changes made within the workspace.
They record who performed an action, what action occurred, and which resource was affected.
Audit logs can be exported as CSV.
Request Logs record incoming API calls made to Secryn.
These logs help monitor integrations, automation usage, and API access patterns.
Request logs can be exported as CSV.
User Logs track authentication and session activity.
They provide visibility into login attempts and account usage.
User logs can be exported as CSV.
MCP Logs record activity related to the Secryn MCP server.
This includes initialization attempts, resource access via MCP, and system-level integration events.
Logs are stored within your Secryn deployment.
All log types support CSV export.
Retention is managed by your deployment configuration and backups.
For long-term archival or compliance requirements, it is recommended to:
Request logs and MCP logs do not include secret values or private keys. Audit entries can store before and after values, encrypted with Laravel encryption keyed by APP_KEY.
Log rows are not hash-chained or signed. Someone with database access can change or delete them.
Access to logs in the web interface is limited to admins.