Documentation (audit logs) — Firezone

Cited by

Facts read from this source

• Audit logs plan availability Report an error

  “Audit Logs Available on: all plan levels”

• Audit log streams Report an error

  “Firezone captures four audit log streams, and each one answers a different question”

• Audit log id format Report an error

  “a log_id, a 96-bit identifier written as 24 lowercase hex characters whose first character tells you which stream the entry belongs to”

• Audit log change logs ordering Report an error

  “For Change Logs it encodes a timestamp and a per-account counter, which means Change Log IDs always increase and sorting by them reproduces the exact order in which changes were committed”

• Audit log location resolution Report an error

  “resolved from the source IP using MaxMind's GeoLite2 City database at the moment the entry is recorded”

• Audit log flow logs no location Report an error

  “Flow Logs attribute traffic to an actor, Policy, and Resource, but carry no location data”

• Audit log delivery guarantee Report an error

  “Delivery to a sink is at-least-once, meaning an entry is never skipped but may occasionally arrive twice, so use log_id as your deduplication key”

• Audit logs rest API Report an error

  “the REST API's /logs endpoint lists entries for a given stream with type set to change, session, flow, or api_request, and supports filtering by time range and actor”

• Log sinks Report an error

  “To stream audit logs to your SIEM or log management platform, set up a Log Sink.”

2 facts read from this page are not shown because they could not be confirmed on the page as captured.

Scores citing this record

• The DevOps Engineer Logs, audit trail & incident response
• The IT Lead Logs, audit trail & incident response
• The MSP Technician Logs, audit trail & incident response
• The Operations Manager Logs, audit trail & incident response
• The Information Security Officer Logs, audit trail & incident response
• The Skeptic Logs, audit trail & incident response