Recon
Searching Falcon Intelligence Recon notifications, monitoring rules, and exposed-data records
API Scopes
Section titled “API Scopes”- Monitoring rules (Falcon Intelligence Recon): READ
falcon_aggregate_recon_exposed_data_records
Section titled “falcon_aggregate_recon_exposed_data_records”Required scopes: Monitoring rules (Falcon Intelligence Recon): READ
Count and group Falcon Intelligence Recon exposed-data records into summary buckets.
Use this to answer how many, top, most common, per day, or over time questions about
leaked credentials and PII — which sites leak the most, the newly-versus-previously
reported mix, or exposure volume over time — without retrieving individual rows.
Consult falcon://recon/exposed-data-records/aggregate-guide for the restricted field
list and falcon://recon/exposed-data-records/search/fql-guide before writing a filter.
Returns one entry per aggregation, each with a name and buckets keyed on label
and count.
Example prompts:
- “Which sites leak the most of our credentials?”
- “How many exposed credentials are newly reported vs previously reported?”
- “Show exposed data record volume per day”
falcon_aggregate_recon_notifications
Section titled “falcon_aggregate_recon_notifications”Required scopes: Monitoring rules (Falcon Intelligence Recon): READ
Count and group Falcon Intelligence Recon notifications into summary buckets.
Use this to answer how many, top, most common, per day, or over time questions about
recon notifications — the mix of statuses, the noisiest monitoring rules, or the
typosquatting trend — without retrieving individual records. Consult
falcon://recon/notifications/aggregate-guide for aggregatable fields and
falcon://recon/notifications/search/fql-guide before writing a filter. Returns one
entry per aggregation, each with a name and buckets keyed on label and count.
Example prompts:
- “How many recon notifications are there by status?”
- “What are the top 10 noisiest recon monitoring rules this month?”
- “Show recon notification volume per day for the past 30 days”
- “Break down typosquatting notifications by priority”
falcon_preview_recon_rule
Section titled “falcon_preview_recon_rule”Required scopes: Monitoring rules (Falcon Intelligence Recon): READ
Estimate how many notifications a prospective Recon monitoring rule would generate.
Use this before creating a monitoring rule to judge how noisy it would be, or to
compare candidate filters — a high total means the rule needs tightening. Consult
falcon://recon/rules/preview-guide for the rule-filter dialect, since filter is a
rule definition rather than a notification search filter; to summarize notifications
that already exist, use falcon_aggregate_recon_notifications instead. Returns a
fixed breakdown of channel, count, and site aggregations with label/count
buckets.
Example prompts:
- “How noisy would a rule monitoring example.com be?”
- “Preview how many notifications a brand rule for Acme would generate in the past 30 days”
- “Estimate the notification volume before I create this monitoring rule”
falcon_search_recon_exposed_data_records
Section titled “falcon_search_recon_exposed_data_records”Required scopes: Monitoring rules (Falcon Intelligence Recon): READ
Search Falcon Intelligence Recon exposed-data records and return their full details.
Use this to find leaked credential and PII rows associated with recon notifications —
emails, login IDs, password hashes, domains, and breach metadata. Consult
falcon://recon/exposed-data-records/search/fql-guide before constructing filter
expressions. These records are part of the external cyber risk monitoring capability of
CrowdStrike Counter Adversary Operations (CAO). Returns full records including credential
fields, location data, and associated notification context.
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:
- “Find exposed credentials for example.com”
- “Show leaked credentials from the past 7 days”
- “Find exposed data records for a specific notification”
falcon_search_recon_notifications
Section titled “falcon_search_recon_notifications”Required scopes: Monitoring rules (Falcon Intelligence Recon): READ
Search Falcon Intelligence Recon notifications (also called recon alerts) and return their full details.
Use this for dark web matches, leaked credentials, typosquatting matches, and breach
summaries triggered by your monitoring rules. Consult
falcon://recon/notifications/search/fql-guide before constructing filter expressions.
This serves the external cyber risk monitoring capability of CrowdStrike Counter Adversary
Operations (CAO). For endpoint, XDR, or NG-SIEM alerts, use falcon_search_detections
instead. Returns full notification records with a nested notification object
containing status, rule metadata, breach_summary, and item details.
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 recon alerts from the past 7 days”
- “Show me new recon alerts with high priority”
- “Find recon notifications for domain monitoring rules”
- “Show typosquatting recon alerts”
- “Find leaked credential notifications from stealer logs”
falcon_search_recon_rules
Section titled “falcon_search_recon_rules”Required scopes: Monitoring rules (Falcon Intelligence Recon): READ
Search Falcon Intelligence Recon monitoring rules and return their full details.
Use this to list the rules that generate your recon notifications — find rules by
topic (domain, email, typosquatting, brand), priority, status, or whether breach
monitoring is enabled. Consult falcon://recon/rules/search/fql-guide before
constructing filter expressions. These monitoring rules power the external cyber risk
monitoring capability of CrowdStrike Counter Adversary Operations (CAO). Returns full
rule definitions including topic, priority, filter expressions, and notification settings.
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:
- “List all active Recon monitoring rules”
- “Show typosquatting monitoring rules”
- “Find Recon rules with breach monitoring enabled”
- “List high priority domain monitoring rules”
Resources
Section titled “Resources”falcon://recon/notifications/search/fql-guide: Contains the guide for thefilterparam of thefalcon_search_recon_notificationstool.falcon://recon/rules/search/fql-guide: Contains the guide for thefilterparam of thefalcon_search_recon_rulestool.falcon://recon/exposed-data-records/search/fql-guide: Contains the guide for thefilterparam of thefalcon_search_recon_exposed_data_recordstool.falcon://recon/notifications/aggregate-guide: Contains the aggregatable fields and usage guide for thefalcon_aggregate_recon_notificationstool.falcon://recon/exposed-data-records/aggregate-guide: Contains the aggregatable fields and usage guide for thefalcon_aggregate_recon_exposed_data_recordstool.falcon://recon/rules/preview-guide: Contains the rule-filter dialect, valid topics, and lookback values for thefalcon_preview_recon_ruletool.