LoFP / provisioned throughput changes may be performed by platform, ml, or finops teams as part of capacity planning, scaling for production demand, or cost optimization. infrastructure-as-code pipelines and automation roles may also create, update, or delete provisioned throughput during deployments. verify that the user identity, user agent, and source ip correspond to known administrators or automation and that a corresponding change request exists. if known behavior is causing false positives, it can be exempted from the rule.

Techniques

• T1496

Sample rules

AWS Bedrock Provisioned Model Throughput Tampering

• source: elastic
• technicques:
  • T1496

Description

Detects creation, modification, or deletion of AWS Bedrock Provisioned Model Throughput via the CreateProvisionedModelThroughput, UpdateProvisionedModelThroughput, and DeleteProvisionedModelThroughput APIs. Provisioned Throughput reserves dedicated, billed model capacity for Amazon Bedrock. An adversary who scales this capacity up can drive large, unauthorized cost (cloud resource/bill hijacking), while deleting reserved throughput can cause denial of service to production workloads that depend on that committed capacity. These control-plane changes should be validated against approved capacity-planning and change-management processes.

Detection logic

data_stream.dataset: "aws.cloudtrail" and
    event.provider: "bedrock.amazonaws.com" and
    event.action: (
        "CreateProvisionedModelThroughput" or
        "UpdateProvisionedModelThroughput" or
        "DeleteProvisionedModelThroughput"
    ) and
    event.outcome: "success"