AWS Bedrock API Key Used for Destructive or Anti-Recovery Action
Identifies an Amazon Bedrock API key (bearer token) being used to perform a destructive or anti-recovery control-plane action, such as deleting a guardrail, deleting a custom or imported model, removing provisioned…
Description
Identifies an Amazon Bedrock API key (bearer token) being used to perform a destructive or anti-recovery control-plane action, such as deleting a guardrail, deleting a custom or imported model, removing provisioned throughput, or disabling model invocation logging. Bedrock API keys are bearer credentials intended for model invocation (InvokeModel, Converse); using one to delete Bedrock resources or disable logging is inconsistent with that purpose and is characteristic of LLMjacking or sabotage following key theft. Every Bedrock API key call is identifiable in CloudTrail by "additionalEventData.callWithBearerToken" being true. The rule matches regardless of outcome, because a destructive attempt via a bearer token is suspicious even when denied.
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
- Platform
- ContainersESXiIaaSIdentity ProviderLinuxmacOSNetwork DevicesOffice SuiteWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
Known benign triggers
- Automation that intentionally manages Bedrock resources using an API key could match. Confirm the principal in "aws.cloudtrail.user_identity.arn", the affected resource in "aws.cloudtrail.request_parameters", and whether the change was expected. Known maintenance principals can be excluded after validation.
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 |
|---|---|
| docs.aws.amazon.com/bedrock/latest/userguide/api-keys.html | 3 |
| www.beyondtrust.com/blog/entry/aws-bedrock-security-api-keys | 3 |
| www.beyondtrust.com/blog/entry/aws-bedrock-security-guide-api-keys-detection-response | 4 |
From the source
- At source
- Open at source
- Upstream identifier
- 89b68231-5134-4499-8eca-20e5d9c90cce
- Tagged by the source as
- Mitre Atlas: AML.T0012Data Source: Amazon BedrockData Source: Amazon Web ServicesData Source: AWSData Source: AWS BedrockData Source: AWS CloudTrailDomain: CloudDomain: GenAINoise: UnknownPerformance: NormalPlatform: AWSProfile: RecommendedResources: Investigation GuideRule Type: ES|QLService: AWS BedrockTactic: Defense EvasionTactic: ImpactThreat: Unauthorized AI UsageUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Oct 2, 2026
- Version
- 4