Elastic low stable kql

AWS Bedrock Unauthorized Foundation Model Access Attempt

Identifies failed, access-denied attempts to enable account-level access to an Amazon Bedrock foundation model, either by granting a foundation-model entitlement, submitting a use case for model access, or creating a foundation-model agreement (accepting the EULA). These account-level "model access" actions unlock a foundation model so that it can subsequently be invoked. A principal that is repeatedly denied when attempting these actions may be a compromised or under-privileged identity probing for the ability to unlock expensive models (LLMjacking) or to establish a durable ability to invoke models. Unlike the companion rule that detects successful model-access grants, this rule surfaces the attempt itself, which is a high-signal indicator of credential boundary-testing even though access was not granted.

View Source

Detection Logic

data_stream.dataset: "aws.cloudtrail"
    and event.provider: "bedrock.amazonaws.com"
    and event.action: (
        "PutFoundationModelEntitlement" or
        "PutUseCaseForModelAccess" or
        "CreateFoundationModelAgreement"
    )
    and event.outcome: "failure"
    and aws.cloudtrail.error_code: (
        "AccessDenied" or
        "AccessDeniedException"
    )

False Positives

⚠ Access-denied errors can result from benign permission gaps: a newly created role or user whose IAM policy has not yet been provisioned, automation pipelines running ahead of permission grants, or ML teams experimenting in non-production accounts during onboarding. Verify that the principal, source IP, and user agent are expected before escalating. Recurring denials from known onboarding or provisioning workflows can be exempted for specific users or roles.

Field Validations

Loading…

Comments (0)

Loading comments...