UTC

AML.T0034

Cost Harvesting

Adversaries may deliberately drive a victim's AI services beyond normal operating capacity with the intent of increasing the cost of services. This may be achieved via high-volume, low-complexity queries (Excessive Queries) or low-volume, high-complexity queries (Resource-Intensive Queries).

  • Tactic Impact
  • Maturity: Feasible
  • Predictive AI
  • Generative AI
  • Agentic AI
Full entry on MITRE ATLAS →
Mitigations
  • Limit AI Service Query Volume and RateAML.M0004

    Limit the number and rate of requests that users can submit to an AI service. Apply limits by user, API key, tenant, device, or other authenticated identity. Use short-term rate, burst, and concurrency limits together with longer-term usage quotas.

    Technical - Cyber

  • Control Access to AI Models and Data in ProductionAML.M0019

    Require users to verify their identities before accessing a production model. Require authentication for API endpoints and monitor production model queries to ensure compliance with usage policies and to prevent model misuse.

    Policy

  • AI Red TeamAML.M0035

    Establish an AI red team responsible for conducting recurring, authorized, and threat-informed red-teaming exercises to identify and remediate vulnerabilities in AI-enabled systems before deployment and throughout operation.

    Policy · Technical - AI · Technical - Cyber

  • Limit AI Workload Resource ConsumptionAML.M0036

    Limit the resources that an AI request, inference job, or agent workflow can consume. Set bounds on input size, batch size, execution time, memory, compute, and output size. Generative AI services should also limit context and output tokens.

    Technical - AI

From MITRE ATLAS 2026.10, Copyright 2021-2026 MITRE, Apache License 2.0.