CrowdStrike · Authentication Profile
Crowdstrike Authentication
Authentication
Every CrowdStrike Falcon API call is authenticated with an OAuth2 client-credentials bearer token. API clients (client_id + client_secret) are created inside the Falcon console under Support and resources > API Clients & Keys and are scoped at creation time; there is no anonymous, self-serve or delegated-user flow. Derived from the provider's own OAuth2 service-collection reference rather than an OpenAPI document — CrowdStrike publishes no spec.
CrowdStrike secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).
CybersecurityEndpoint SecurityEDRThreat IntelligenceCloud SecurityIdentity ProtectionVulnerability ManagementSIEMSecurity OperationsMCP
Methods: oauth2
Schemes: 1
OAuth flows: clientCredentials
API key in:
Security Schemes
FalconOAuth2 oauth2
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.