Audit Logs

Overview

Audit logs provide a complete, immutable record of all activity within Peridot.

They are critical for governance, compliance, and incident investigation.

What Is Logged

Peridot captures:

• User actions

• Policy evaluations and enforcement

• Data access and movement

• Model usage and routing decisions

• API interactions

Why Audit Logs Matter

Audit logs enable organizations to:

• Reconstruct events during incidents

• Demonstrate compliance with regulations

• Verify policy enforcement

• Analyze system behavior

How Logging Works

Every AI interaction generates a trace:

1. Request metadata is captured

2. Policies and decisions are recorded

3. Actions and outcomes are logged

4. Logs are stored and indexed

Example

For a single request, logs may include:

• User identity

• Input data classification

• Model selected

• Policy decisions

• Enforcement actions

• Final outcome

In Production

• Logs are generated in real time

• Data is stored securely and immutably

• Logs can be queried and exported

• Integration with SIEM systems is supported

Security and Compliance

Audit logs support:

• SOC 2

• ISO 27001

• Internal compliance frameworks

Best Practices

• Integrate logs with SIEM tools

• Retain logs based on compliance requirements

• Regularly review audit trails

Next Steps

• Connect logs to your observability stack

• Use logs in incident investigations