Myrmex does not store your logs. There is no SIEM-style event repository
here: Myrmex reads your systems in real time, on demand, and never ingests or
retains their telemetry. The only logs Myrmex keeps are its own audit logs —
the actions taken through Myrmex itself. To query events from a connected SIEM,
operate that tool live through its integration.
What Gets Recorded
The audit log captures the meaningful actions taken through Myrmex — by users and by the AI agents acting on their behalf — for example:Access & session activity
Sign-ins and account activity within the platform.
Changes to your environment
Devices and integrations added, edited, authorized, or removed; configuration
changes applied through Myrmex.
Approvals & executions
Change approvals and rejections, actions run on hosts and integrations, and
automations executed.
Administration
Role, policy, user, and organization changes made in settings.
Using the Audit Log
The audit log opens as a tab in the Workspace, scoped to the context or organization you’re reviewing. Use it to reconstruct a sequence of events, confirm who authorized a change, or export a trail for an auditor.Audit logging is part of Myrmex’s governance capabilities and is an
Enterprise feature — a full trail of the actions users perform through
Myrmex. See Plans & Licensing.
Audit Logs vs. AI-driven Audits
These sound alike but are different tools:Audit Logs (this page)
A trail of actions performed in Myrmex — who did what, when. About
accountability.
AI-driven Audits
Ask the AI to audit a system’s security and it builds an interactive
assessment. About the state of your environment.