Skip to main content
Book a demo

Connect CrowdStrike Falcon to Claude Cowork

Give Claude Cowork governed access to CrowdStrike Falcon’s 169 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude Cowork setup guide

Set up

Add CrowdStrike Falcon to Claude Cowork in four steps

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

  1. 1

    Approve CrowdStrike Falcon in Runlayer

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

  2. 2

    Connect Claude Cowork to Runlayer

    Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, CrowdStrike Falcon’s 169 tools show up in Claude Cowork’s own tool list.

    Claude Cowork setup guide
  3. 3

    Sign in to CrowdStrike Falcon

    An admin adds CrowdStrike Falcon credentials to Runlayer once. They never sit in the client’s configuration.

  4. 4

    Use CrowdStrike Falcon from Claude Cowork

    CrowdStrike Falcon’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.

Tools

169 CrowdStrike Falcon tools in Claude Cowork

Runlayer policy decides which of these Claude Cowork users can call.

  • Add case alert evidence

    Attach alert evidence to an existing case.

  • Add case event evidence

    Attach LogScale event evidence to an existing case.

  • Add IOC

    Create one or more custom IOCs.

  • Aggregate case access tags

    Count case access tags grouped by a field.

  • Aggregate case file details

    Report the files attached to cases, grouped and counted by a field.

  • Aggregate case notification groups

    Count case notification groups grouped by a field.

  • Aggregate case slas

    Count case SLA definitions grouped by a field.

  • Aggregate case templates

    Count case templates grouped by a field.

See all 169 CrowdStrike Falcon tools

Control

What Runlayer can see and stop in Claude Cowork

Some controls apply to every client at the gateway. Others depend on what Claude Cowork exposes to Runlayer.

  • Gateway policy (available)

    Every CrowdStrike Falcon call from Claude Cowork passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude Cowork as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.

  • OTLP telemetry (available)

    Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude Cowork prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.

In Claude Cowork

  • Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.

Frequently asked questions

Connect more

Find another combination