Skip to main content
Book a demo

Connect CrowdStrike Falcon to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

Add CrowdStrike Falcon to GitHub Copilot in four steps

Admins approve the server once. Everyone in GitHub Copilot 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 GitHub Copilot to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches CrowdStrike Falcon’s 169 tools through the plugin’s search and execute tools.

    GitHub Copilot 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 GitHub Copilot

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

Tools

169 CrowdStrike Falcon tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot 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 GitHub Copilot

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination