Microsoft Foundry High Request and Token Volume
Detects one caller IP sending a high number of requests and consuming a high number of tokens against the same Foundry deployment and operation during the rule lookback. That rate fits a script or a stolen key…
Description
Detects one caller IP sending a high number of requests and consuming a high number of tokens against the same Foundry deployment and operation during the rule lookback. That rate fits a script or a stolen key burning quota. The rule uses RequestResponse logs and does not need the prompt text. Tune the request count and token sum in the query.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
Known benign triggers
- Approved batch jobs, evaluation harnesses, and user-facing apps that fan out from one NAT. Exclude that caller IP prefix and deployment, or raise the thresholds to sit above the normal 9-minute peak.
- Foundry masks the last octet of caller_ip_address, so unrelated users behind the same network prefix are counted together.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| learn.microsoft.com/en-us/azure/ai-foundry/openai/how-to/monitor-openai | Only this detection cites it |
| www.elastic.co/docs/reference/integrations/azure_ai_foundry | 5 |
From the source
- At source
- Open at source
- Upstream identifier
- bb2bc0e2-bc6f-4f6b-a6cc-7deb99fe2588
- Tagged by the source as
- Mitre Atlas: AML.T0029Data Source: Microsoft FoundryDomain: CloudDomain: GenAIPlatform: AzureResources: Investigation GuideRule Type: ES|QLService: Azure AI FoundryTactic: ImpactUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Oct 6, 2026
- Version
- 1