Connect Cloudflare Audit Logs to Zed
Give Zed governed access to Cloudflare Audit Logs through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Cloudflare Audit Logs to Zed in four steps
Admins approve the server once. Everyone in Zed then gets it through the same governed connection.
- 1
Approve Cloudflare Audit Logs in Runlayer
Add Cloudflare Audit Logs from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Zed to Runlayer
Users add the Runlayer Plugin to Zed by following Runlayer’s setup guide. Zed reaches Cloudflare Audit Logs’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Zed setup guide - 3
Sign in to Cloudflare Audit Logs
Sign in the way Cloudflare Audit Logs requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Cloudflare Audit Logs from Zed
Cloudflare Audit Logs’s approved tools appear in Zed. Every call is checked against policy and recorded.
Tools
Cloudflare Audit Logs tools in Zed
Cloudflare Audit Logs reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in Zed
Some controls apply to every client at the gateway. Others depend on what Zed exposes to Runlayer.
Gateway policy (available)
Every Cloudflare Audit Logs call from Zed passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Zed as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Zed yet, so control happens at the gateway.
Frequently asked questions
Connect more