Skip to main content
Book a demo

Connect Drata to Zed

Give Zed governed access to Drata’s 38 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Zed setup guide

Set up

Add Drata to Zed in four steps

Admins approve the server once. Everyone in Zed then gets it through the same governed connection.

  1. 1

    Approve Drata in Runlayer

    Add Drata from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Zed to Runlayer

    Users add the Runlayer Plugin to Zed by following Runlayer’s setup guide. Zed reaches Drata’s 38 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Zed setup guide
  3. 3

    Sign in to Drata

    Sign in the way Drata requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Drata from Zed

    Drata’s approved tools appear in Zed. Every call is checked against policy and recorded.

Tools

38 Drata tools in Zed

Runlayer policy decides which of these Zed users can call.

  • Create background check

    File a Background Check for a personnel record, evidenced by a URL.

  • Create control

    Create a new compliance control in a workspace.

  • Create evidence

    Register a new evidence bucket in Drata's reusable Evidence Library.

  • Create risk

    Create a new custom risk in a risk register.

  • Create vendor

    Create a new third-party vendor for the account (TPRM).

  • Delete evidence

    Permanently delete an ENTIRE evidence bucket -- the folder AND every file in it, plus all version history and control linkages.

  • Delete evidence artifact

    Permanently delete ONE file from an evidence bucket, including that file's entire version history.

  • Delete risk

    Permanently delete a single risk from a risk register.

See all 38 Drata tools

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 Drata 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

Find another combination