Skip to content →
Log in

Audit

Search and inspect security, identity, and network events.

Use Security → Audit to find and inspect individual events: administrative changes, posture decisions, access decisions, exit traffic and content filter verdicts. Authentication audit lives here too, even when you reach it from Authentication settings.

Audit page with the Audit category tab active, window controls, the event volume histogram, the search and filter bar, and administrative event rows

With the Audit tab active the table holds administrative events only; the histogram, window controls and Export act on the same filtered set.

Before you start#

  • Viewing needs audit:view (audit.read on the control plane). Owners and admins have it by default. Changing Logging Settings needs audit:configure.
  • Traffic categories have short history. All, Access and Content Filter only offer 1h and 24h windows, and the page notes “Traffic history is limited to 24h”. The other categories offer up to 30d.
  • Every query is capped at 31 days by the control plane. Retention is set per tenant (see below). Events older than retention are gone.
  • Content Filter events are kept for 30 days regardless of the tenant retention setting.

Investigate an event#

  1. Open Security → Audit.
  2. Pick a category: All, Audit, Posture, SCIM, Exit, Access or Content Filter. Changing category resets the window to 24h.
  3. Pick a window: 1h, 24h, 7d or 30d. To look at an earlier period, set Window ending (UTC). This pauses live polling.
  4. Add filters with Filter. Choose a field, an operator (is, is not or contains) and a value, then click Apply. Type free text in the search box to match across event, actor, destination and metadata fields.
  5. Click an event name to open the Event details drawer. Polling pauses while it is open.
  6. Click Export and choose Export as CSV or Export as JSON to download the rows currently loaded.

You should see a status line such as “100 shown · 2,340 total · live every 15s”. Above the table, a histogram shows event volume across the window.

Audit filter bar with a Decision is Deny chip applied and the Filter menu open listing Event, Event Class, Decision, Protocol, Actor, Target User, Agent, Gateway and Dest IP

Applied filters appear as chips in the search box and the Filter menu lists the available fields; the histogram and status line reflect the filtered set.

Change logging settings#

  1. Click the Logging settings gear icon.
  2. Set Exit Node Logging: Off - No exit traffic logging, Metadata - IPs, ports, protocols only, or Full - Include hostnames when available.
  3. Set Retention Period (days) between 7 and 365.
  4. Click Save Settings.

You should see “Logging settings saved”.

Logging Settings dialog with Exit Node Logging set to Metadata and Retention Period set to 90 days

Logging Settings holds the exit node logging level and the retention period; the note at the top explains which categories the retention applies to.

Reference#

Categories#

TabCategory valueWhat it holds
AuditauditAdministrative actions, including authentication and configuration changes
PosturepostureDevice posture decisions
SCIMscimAudit rows whose event starts with scim
Exitexit_trafficExit node connection logs
AccessaccessAccess decisions made by gateways
Content Filtercontent_filterSecure Web verdicts

Two further categories, exit_policy and failover, have no tab. They appear under All.

Table columns#

Time, Event, Decision, Actor, Destination, Agent, Gateway, Category, Protocol.

Filter fields#

FieldValues
EventFree text, for example exit_connection
Event ClassDNS, Web, Malware
DecisionAllow, Deny, Compliant, Non-compliant
ProtocolTCP, UDP
Actor, Target UserA user
Agent, GatewayA device or gateway
Dest IP, Dest PortFree text

Repeated filters are combined with AND. contains is case-insensitive. is not also matches rows where the field is empty. The control plane accepts at most 20 filters and a search of at most 256 bytes.

Event details#

The drawer shows the actor, affected user, device, gateway, destination, resource and threat where present, then Policy decision (matched by, policy, category, fail mode, reason), Recorded changes (before and after), and a collapsible Technical details section with raw references, IPs, ports, protocol, event class, DNS query type, SHA-256 and scan engine.

Event details drawer for a Device revoked audit event showing the actor, device, destination and resource, a Policy decision reason and a collapsed Technical details section

The Event details drawer opens on the right with the people and objects involved, the recorded reason, and Technical details collapsed below.

For a denied Content Filter event, users with content_filtering:update see Create tenant exception. Users with content_filtering:baseline_override also see Override security baseline.

Paging, polling and export#

  • 100 rows per page. When the total exceeds 10,100 the page notes “First 10,100 results shown”. Narrow the category, window or filters.
  • Live polling refreshes every 15 seconds. It pauses when you click pause, move past page 1, open the drawer, open settings, or change the window end.
  • Export covers only the current loaded page. For a full-window export use Reports → Exports → Audit.
  • CSV columns: Event ID, Tenant ID, Subject, Timestamp, Category, Event, Event Class, Threat, SHA-256, Scan Engine, Actor, Target User, Agent, Gateway, Resource, Decision, Destination IP, Destination Port, Protocol, Message, IP Address, User Agent, Metadata.

Retention#

A daily job deletes audit, posture, failover, access and exit traffic rows older than the tenant’s Retention Period. The control plane default is 30 days. Content Filter rows are purged on a fixed 30-day schedule. Retention is a policy setting, not a guarantee of durability. Keep required records in your approved external system.

Troubleshooting#

  • “Audit unavailable: …” with Retry. The first load failed. Retry, then narrow the window.
  • “Could not refresh. Showing the last successful results.” A poll failed; the table is stale. Retry.
  • “Audit request timed out. Retry or narrow the window.” Reduce the window or add filters.
  • “queries including access or content-filter traffic support at most 24 hours; choose an earlier end time for historical events”. Switch to Audit, Posture or SCIM, or set Window ending (UTC) with a 24h window.
  • “Logging settings could not be loaded. Retry before making changes.” Do not save until the current values load.
  • A link from Authentication settings opens Audit without a category. Pick Audit manually.
  • Analytics for aggregate block trends.
  • Reports for full-window audit export.
  • Secure Web to manage exceptions created from blocked events.
  • Device posture for the policies behind posture decisions.
  • SSO for authentication configuration.