AWS Bedrock Guardrails Detected Multiple Violations by a Single User Over a Session

  1[metadata]
  2creation_date = "2024/05/02"
  3integration = ["aws_bedrock"]
  4maturity = "production"
  5updated_date = "2025/09/25"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10Identifies multiple violations of AWS Bedrock guardrails by the same user in the same account over a session. Multiple
 11violations implies that a user may be intentionally attempting to cirvumvent security controls, access sensitive
 12information, or possibly exploit a vulnerability in the system.
 13"""
 14false_positives = ["Legitimate misunderstanding by users or overly strict policies"]
 15from = "now-60m"
 16interval = "10m"
 17language = "esql"
 18license = "Elastic License v2"
 19name = "AWS Bedrock Guardrails Detected Multiple Violations by a Single User Over a Session"
 20note = """## Triage and analysis
 21
 22### Investigating AWS Bedrock Guardrails Detected Multiple Violations by a Single User Over a Session
 23
 24Amazon Bedrock Guardrail is a set of features within Amazon Bedrock designed to help businesses apply robust safety and privacy controls to their generative AI applications.
 25
 26It enables users to set guidelines and filters that manage content quality, relevancy, and adherence to responsible AI practices.
 27
 28Through Guardrail, organizations can define "denied topics" to prevent the model from generating content on specific, undesired subjects,
 29and they can establish thresholds for harmful content categories, including hate speech, violence, or offensive language.
 30
 31#### Possible investigation steps
 32
 33- Identify the user account that caused multiple policy violations over a session and whether it should perform this kind of action.
 34- Investigate the user activity that might indicate a potential brute force attack.
 35- Investigate other alerts associated with the user account during the past 48 hours.
 36- Consider the time of day. If the user is a human (not a program or script), did the activity take place during a normal time of day?
 37- Examine the account's prompts and responses in the last 24 hours.
 38- If you suspect the account has been compromised, scope potentially compromised assets by tracking Amazon Bedrock model access, prompts generated, and responses to the prompts by the account in the last 24 hours.
 39
 40### False positive analysis
 41
 42- Verify the user account that caused multiple policy violations by a single user over session, is not testing any new model deployments or updated compliance policies in Amazon Bedrock guardrails.
 43
 44### Response and remediation
 45
 46- Initiate the incident response process based on the outcome of the triage.
 47- Disable or limit the account during the investigation and response.
 48- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
 49    - Identify the account role in the cloud environment.
 50    - Identify if the attacker is moving laterally and compromising other Amazon Bedrock Services.
 51    - Identify any regulatory or legal ramifications related to this activity.
 52- Review the permissions assigned to the implicated user group or role behind these requests to ensure they are authorized and expected to access bedrock and ensure that the least privilege principle is being followed.
 53- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
 54- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 55"""
 56references = [
 57    "https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails-components.html",
 58    "https://atlas.mitre.org/techniques/AML.T0051",
 59    "https://atlas.mitre.org/techniques/AML.T0054",
 60    "https://www.elastic.co/security-labs/elastic-advances-llm-security",
 61]
 62risk_score = 47
 63rule_id = "0cd2f3e6-41da-40e6-b28b-466f688f00a6"
 64setup = """## Setup
 65
 66This rule requires that guardrails are configured in AWS Bedrock. For more information, see the AWS Bedrock documentation:
 67
 68https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails-create.html
 69"""
 70severity = "medium"
 71tags = [
 72    "Domain: LLM",
 73    "Data Source: AWS Bedrock",
 74    "Data Source: AWS S3",
 75    "Resources: Investigation Guide",
 76    "Use Case: Policy Violation",
 77    "Mitre Atlas: T0051",
 78    "Mitre Atlas: T0054",
 79]
 80timestamp_override = "event.ingested"
 81type = "esql"
 82
 83query = '''
 84from logs-aws_bedrock.invocation-*
 85
 86// Filter for compliance violations detected
 87| where gen_ai.compliance.violation_detected
 88
 89// keep relevant ECS + model fields
 90| keep
 91  user.id,
 92  gen_ai.request.model.id,
 93  cloud.account.id
 94
 95// count violations by user, model, and account
 96| stats
 97    Esql.ml_violations_count = count(*)
 98  by
 99    user.id,
100    gen_ai.request.model.id,
101    cloud.account.id
102
103// Filter for repeated violations
104| where Esql.ml_violations_count > 1
105
106// sort descending by violation volume
107| sort Esql.ml_violations_count desc
108'''