Skip to main content

Audit Logs

An audit log is a chronological record of security-relevant actions that occur in a system. It is used to store evidence of a specific operation, procedure or event. Many enterprise customers of SaaS businesses require an audit log of access, administrative and system events. Companies that have compliance requirements (e.g. SOC 2) may be required to keep such logs in order to produce an official record when obligated to produce proof of compliance. Additionally, developers use audit logs to do root cause analysis of how a complex system produced a failure or arrived in an unexpected state.

Phase Two has built an audit logging system that is used by default internally. All access, administrative and system events are recorded in the audit log and made available to the customer to fulfill their requirements.

The Phase Two audit logging system is also available to the customer to add their system's actions and events. A single API method with a simple event format allows flexibility in storing context about the action or event. Both Phase Two and customer events are available in the administrative application to be searched, filtered and exported for external consumption.

Do I need to enable events?

No. On a hosted cluster, access, administrative, and system events are captured automatically and delivered to the Phase Two platform, where they are available in the dashboard. You do not need to turn on event storage in your realm's settings for this to happen, and the realm-level event expiration setting does not limit what Phase Two retains.

You only need to configure something in your realm if you want events pushed to your systems as they happen. In that case, enable the webhook event listener and register an endpoint.