ConnectRequest demo

Overview

Use CrowdStrike as a governed source or destination in a Context runbook. Configure the exact records and actions each agent can access.

  • · Vendor-supported OAuth or scoped service credentials
  • · Read and write access configured separately
  • · Tool calls and outcomes recorded per run
Connector contract

Control what agents can do in CrowdStrike.

Exact authentication methods and available scopes depend on your CrowdStrike plan and deployment. Context keeps the connector configuration explicit.

Read

Resolve the users, groups, resources, and policies needed for authorization.

Act

Apply changes only through the policy and approval path you configure.

Verify

Record the principal, requested action, authorization, and outcome.

Set up the connection

  1. 01

    Authenticate

    Connect CrowdStrike with an admin-approved OAuth flow or scoped credential supported by the vendor.

  2. 02

    Choose scope

    Select the accounts, workspaces, projects, or resources available to the runbook.

  3. 03

    Map policy

    Set read and write permissions, reviewer gates, and the identity used for each action.

  4. 04

    Test a run

    Verify one read, one permitted action, and the resulting audit record before rollout.

Build with CrowdStrike

CrowdStrike can be added to any Context runbook. Start from a prebuilt agent, then choose the resources and actions it needs. Browse all agents →

More in Identity & security

OktaAzure ADAuth0OneLoginPing IdentityDuo Security

Connect CrowdStrike to Context.

Request demo