Skip to content

Case Management

Managing CrowdStrike cases, including searching, creating, updating, and managing evidence and tags

  • Case Templates: READ
  • Cases: READ
  • Cases: WRITE

Required scopes: Cases: WRITE

Attach alert evidence to an existing case.

Provide alert composite_id values from the Alerts v2 API (e.g. from falcon_search_detections). Each case supports a maximum of 100 combined evidence items. Returns the updated case record.

Example prompts:

  • “Attach these detection alerts to the case”

Required scopes: Cases: WRITE

Attach LogScale event evidence to an existing case.

Provide event IDs obtained from falcon_search_ngsiem or the Falcon console. Each case supports a maximum of 100 combined evidence items. Returns the updated case record.

Example prompts:

  • “Add these NGSIEM event IDs to the case as evidence”

Required scopes: Case Templates: READ

Count case access tags grouped by a field.

Use this to see which access tags control case visibility in your tenant and how many of each exist. Access tags accept a narrower field set than the other case aggregates — only key, id, and cid. Consult falcon://cases/aggregates/fql-guide before constructing filter expressions. Returns buckets of label and count. Requires the Case Templates:read scope.

Example prompts:

  • “What access tags are used to restrict case visibility, and how many of each?”

Required scopes: Cases: READ

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

Use this whenever a question mentions files, attachments or screenshots on a case, including “what files are attached to case X” and “how many files does case X have” — pass the case IDs as case_ids. Case records from falcon_get_cases do not list attachments; their analysis_results.files field holds forensic artifacts from detections and is empty for cases that do have attachments. Consult falcon://cases/file-aggregates/fql-guide before constructing filter expressions. Returns buckets of label and count. Requires the Cases:read scope.

Example prompts:

  • “What file names show up most often across case attachments?”
  • “How many files are attached to these two cases?”

Required scopes: Case Templates: READ

Count case notification groups grouped by a field.

Use this to summarize the notification groups that receive case updates, such as how many are configured or who created them. Consult falcon://cases/aggregates/fql-guide before constructing filter expressions. Returns buckets of label and count. Requires the Case Templates:read scope.

Example prompts:

  • “How many case notification groups are configured?”
  • “Show notification group counts by creator”

Required scopes: Case Templates: READ

Count case SLA definitions grouped by a field.

Use this to summarize the SLA policies configured in your tenant — for example how many exist, or who created them — rather than to list them individually. Consult falcon://cases/aggregates/fql-guide before constructing filter expressions. Returns buckets of label and count. Requires the Case Templates:read scope.

Example prompts:

  • “How many case SLA policies do we have?”
  • “Break down our case SLAs by who created them”

Required scopes: Case Templates: READ

Count case templates grouped by a field.

Use this to summarize the case templates configured in your tenant, such as how many exist or which users author them; falcon_list_case_templates returns the individual template records instead. Consult falcon://cases/aggregates/fql-guide before constructing filter expressions. Returns buckets of label and count. Requires the Case Templates:read scope.

Example prompts:

  • “How many case templates has each person created?”
  • “Count the case templates added in the last 30 days”

Required scopes: Cases: WRITE

Create a new case in CrowdStrike.

Provide a name and severity at minimum. Optionally attach alert or event evidence, assign a user, apply a template, and set tags. Returns the created case record.

Example prompts:

  • “Create a critical case called ‘Suspicious lateral movement from WORKSTATION-42’”
  • “Open a high-severity case for the credential theft alerts and attach them as evidence”

Required scopes: Cases: READ

Retrieve details for case IDs you already have.

Use when you have specific case IDs from search results or external references. For discovering cases by criteria, use falcon_search_cases; for files attached to a case, use falcon_aggregate_case_file_details. Returns full case records. Their analysis_results.files field lists forensic artifacts from detections, not attachments, and is empty for cases that do have attachments.

Example prompts:

  • “Pull up the full details on that case”

Required scopes: Case Templates: READ

List available case templates.

Use to discover templates that can be applied when creating or updating cases. Returns template details including name, custom fields, and SLA configuration.

Example prompts:

  • “What case templates are available?”

Required scopes: Cases: WRITE

Add or remove tags on a case.

Set action to ‘add’ to attach new tags, or ‘remove’ to delete existing tags. Returns the updated case record.

Example prompts:

  • “Tag that case with ‘ransomware’ and ‘escalated’”
  • “Remove the ‘escalated’ tag from that case”

Required scopes: Cases: READ

Find cases by criteria and return their complete details.

Use this to discover cases by status, severity, assignee, time range, or evidence attributes. Consult falcon://cases/search/fql-guide before constructing filter expressions. Returns full case records including status, severity, evidence, assigned user, and analysis results. Responses include pagination.total (the total number of records matching the filter, or null when the API does not report a count) — use it to answer “how many” questions.

Example prompts:

  • “Show me any open cases with high severity or above”
  • “What cases have been created in the last 24 hours?”

Required scopes: Cases: WRITE

Update an existing case’s fields.

Provide the case ID and any fields to change. Use expected_version for optimistic concurrency control to prevent conflicting updates. Returns the updated case record with incremented version.

Example prompts:

  • “Set that case to in_progress and assign it to the analyst”
  • “Close the case — investigation is complete”
  • falcon://cases/search/fql-guide: Contains the guide for the filter param of the falcon_search_cases tool.
  • falcon://cases/aggregates/fql-guide: Contains the guide for the filter param of the falcon_aggregate_case_slas, falcon_aggregate_case_templates, falcon_aggregate_case_access_tags, and falcon_aggregate_case_notification_groups tools.
  • falcon://cases/file-aggregates/fql-guide: Contains the guide for the filter param of the falcon_aggregate_case_file_details tool.