LoFP / cloud administrators and machine-learning teams routinely enable model access, submit use cases, and accept model end-user license agreements (eulas) during account onboarding or when adopting a new foundation model. verify that the principal, source ip, and user agent are expected and that the change aligns with a known onboarding or provisioning activity before escalating. if this activity is expected and authorized for specific principals, consider adding exceptions for those users or roles.

Techniques

• T1098

Sample rules

AWS Bedrock Foundation Model Access Enabled or Entitlement Granted

• source: elastic
• technicques:
  • T1098

Description

Identifies when access to an Amazon Bedrock foundation model is enabled at the account level, 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. Adversaries or a compromised principal may enable model access to abuse expensive models (LLMjacking), to establish a durable ability to invoke models within the account, or to bypass organizational controls. This activity is distinct from changes to a resource-based model invocation policy and is identified by the Bedrock control-plane API calls that grant model entitlements and agreements.

Detection logic

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