AWS Bedrock Guardrail Deleted or Weakened
Description
Detects deletion, weakening, or version management of AWS Bedrock guardrails via the DeleteGuardrail, UpdateGuardrail, DeleteEnforcedGuardrailConfiguration, or PutEnforcedGuardrailConfiguration APIs. Bedrock guardrails enforce content, topic, word, and sensitive-information policies on model invocations. Deleting a guardrail, loosening its policies, removing or overwriting the organization-enforced guardrail configuration, or creating a new version to enforce a weakened configuration allows an adversary to bypass these protections — the cloud control-plane equivalent of disabling a security tool. This activity should be validated against approved change management and the responsible identity.
Query · kuery
data_stream.dataset: "aws.cloudtrail"
and event.provider: "bedrock.amazonaws.com"
and event.action: (
"DeleteGuardrail" or
"UpdateGuardrail" or
"DeleteEnforcedGuardrailConfiguration" or
"PutEnforcedGuardrailConfiguration"
) and event.outcome: "success"
and not user_agent.original: (*Terraform*)
Investigation fields
Pivot points the source recommends for triage.
@timestampuser.nameuser_agent.originalsource.ipaws.cloudtrail.user_identity.arnaws.cloudtrail.user_identity.typeaws.cloudtrail.user_identity.access_key_idevent.actionevent.providerevent.outcomecloud.account.idcloud.regionaws.cloudtrail.request_parametersaws.cloudtrail.response_elements
Known false positives
- Platform or ML engineering teams may legitimately tune, iterate on, or decommission guardrails as part of normal development. If this is expected in your environment, the responsible identities can be exempted from the rule.
Analyst notes
Investigating AWS Bedrock Guardrail Deleted or Weakened
AWS Bedrock guardrails enforce content, topic, word, and sensitive-information policies on model
invocations. Adversaries who gain access to the Bedrock control plane may delete a guardrail (DeleteGuardrail),
loosen its policies (UpdateGuardrail), remove or overwrite the organization-enforced guardrail
configuration (DeleteEnforcedGuardrailConfiguration / PutEnforcedGuardrailConfiguration) to then enforce it on
model deployments. This detection identifies those control-plane changes so responders can confirm
intent before accepting the change.
Possible investigation steps
- Identify the actor and context
- Review
aws.cloudtrail.user_identity.arn,aws.cloudtrail.user_identity.type,aws.cloudtrail.user_identity.access_key_id,source.ip, anduser_agent.original. - Confirm a related change request exists and that the identity is authorized to manage guardrails.
- Validate the change
- For
UpdateGuardrail/PutEnforcedGuardrailConfiguration, inspectaws.cloudtrail.flattened.request_parametersandaws.cloudtrail.response_elementsto determine which content, topic, word, or sensitive-information policies were removed or weakened. - For
DeleteGuardrail/DeleteEnforcedGuardrailConfiguration, identify the targeted guardrail or org configuration and whether protected workloads still reference it. - Correlate activity
- Look for surrounding Bedrock
InvokeModel/Converseactivity and other defense-impairing actions (e.g., logging or detector changes) from the same identity. - Check for prior enumeration such as
ListGuardrailsorGetGuardrail.
Response and remediation
- If unauthorized, restore the guardrail and/or org-enforced configuration to its approved state and re-associate it with affected Bedrock workloads.
- Disable the access key in
aws.cloudtrail.user_identity.access_key_idand review the actor's recent activity; rotate credentials if compromise is suspected. - Restrict
bedrock:DeleteGuardrail,bedrock:UpdateGuardrail, and the enforced-configuration permissions to a small set of admin roles, and enforce guardrail state via AWS Config or SCPs.