AWS Bedrock Invocations without Guardrails Detected by a Single User Over a Session
Identifies multiple AWS Bedrock executions in a one minute time window without guardrails by the same user in the same account over a session. Multiple consecutive executions implies that a user may be intentionally…
Description
Identifies multiple AWS Bedrock executions in a one minute time window without guardrails by the same user in the same account over a session. Multiple consecutive executions implies that a user may be intentionally attempting to bypass security controls, by not routing the requests with the desired guardrail configuration in order to access sensitive information, or possibly exploit a vulnerability in the system.
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.
Known benign triggers
- Users testing new model deployments or updated compliance policies without Amazon Bedrock guardrails.
MITRE ATT&CK mappings
Not mapped to ATT&CK.
References
| Reference | Cited by |
|---|---|
| atlas.mitre.org/techniques/AML.T0051 | 8 |
| atlas.mitre.org/techniques/AML.T0054 | 7 |
| docs.aws.amazon.com/bedrock/latest/userguide/guardrails-components.html | 8 |
| www.elastic.co/security-labs/elastic-advances-llm-security | 21 |
From the source
- At source
- Open at source
- Upstream identifier
- f2c653b7-7daf-4774-86f2-34cdbd1fc528
- Tagged by the source as
- Data Source: AWS BedrockData Source: AWS S3Domain: LLMMitre Atlas: T0051Mitre Atlas: T0054Resources: Investigation GuideUse Case: Policy Violation
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Aug 27, 2026
- Version
- 1