AWS Bedrock Model Invocation Logging Disabled or Modified
Description
Detects when an AWS Bedrock model invocation logging configuration is deleted or overwritten via the DeleteModelInvocationLoggingConfiguration or PutModelInvocationLoggingConfiguration API calls. Model invocation logging is the source that feeds the logs-aws_bedrock.invocation-* dataset relied upon by all data-plane Bedrock detections. An adversary who has gained access to a Bedrock environment can blind defenders by deleting this configuration, or by using the Put API to redirect logs to an attacker-controlled or non-monitored S3 bucket or CloudWatch log group. Because this single control-plane action can neutralize the entire data-plane detection stack, it is a high-value evasion technique that should be validated against expected administrative change activity.
Query · kuery
data_stream.dataset: "aws.cloudtrail" and
event.provider: "bedrock.amazonaws.com" and
event.action: ("DeleteModelInvocationLoggingConfiguration" or "PutModelInvocationLoggingConfiguration") and
event.outcome: "success"
Investigation fields
Pivot points the source recommends for triage.
@timestampuser.nameuser_agent.originalsource.ipsource.as.numberaws.cloudtrail.user_identity.arnaws.cloudtrail.user_identity.typeaws.cloudtrail.user_identity.access_key_idevent.actionevent.providerevent.outcomecloud.account.idcloud.regionaws.cloudtrail.flattened.request_parametersaws.cloudtrail.response_elements
Known false positives
- Cloud or security administrators may legitimately delete or reconfigure Bedrock model invocation logging during onboarding, log destination migrations, or compliance changes. Verify whether the user identity, user agent, and source IP are expected to make this change. For PutModelInvocationLoggingConfiguration, confirm that the destination S3 bucket or CloudWatch log group remains owned and monitored by your organization. Known, planned changes can be exempted from this rule.
Analyst notes
Investigating AWS Bedrock Model Invocation Logging Disabled or Modified
AWS Bedrock model invocation logging captures the prompts and responses processed by foundation models and delivers them
to an S3 bucket or CloudWatch log group. This data feeds the logs-aws_bedrock.invocation-* dataset that all data-plane
Bedrock detections depend on. Deleting the configuration stops this telemetry entirely, while overwriting it with Put
can silently redirect logs to a destination the defender does not monitor. Either action effectively blinds the
data-plane detection stack, making this a high-priority defense-evasion event.
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,user_agent.original, andsource.ip. - Determine whether the identity is an approved Bedrock administrator and whether a change request exists.
- Determine the exact action
- For
DeleteModelInvocationLoggingConfiguration, logging is being turned off entirely — confirm this is intentional. - For
PutModelInvocationLoggingConfiguration, inspectaws.cloudtrail.flattened.request_parametersfor the news3Configbucket name / key prefix andcloudWatchConfiglog group, and verify they are owned and monitored by your org. - Correlate surrounding activity
- Pivot on the same identity,
source.ip, andcloud.account.idfor prior enumeration (GetModelInvocationLoggingConfiguration) or follow-on Bedrock data-plane activity (model invocations) that would now be unlogged. - Check for parallel logging-tampering against CloudTrail, Config, or GuardDuty.
False positive analysis
- Planned changes: Logging migrations or compliance updates may legitimately reconfigure or remove the configuration. Validate against change tickets and infrastructure-as-code pipelines.
Response and remediation
- If unauthorized, restore model invocation logging to the approved destination and verify log delivery resumes into
logs-aws_bedrock.invocation-*. - Review and secure any attacker-specified S3 bucket or CloudWatch log group, and treat data sent there as exposed.
- Audit the actor's recent Bedrock and IAM activity and rotate credentials if compromise is suspected.
- Restrict
bedrock:DeleteModelInvocationLoggingConfigurationandbedrock:PutModelInvocationLoggingConfigurationto a small set of administrative roles and alert on changes.