STIGhubSTIGhub
STIGsSearchCompareAbout

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • VPAT
  • DISA STIG Library
STIGs updated 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Application Programming Interface (API) Security Requirements Guide

V-274523

CAT II (Medium)

The API must monitor the usage of API keys to detect any anomalies.

Rule ID

SV-274523r1143516_rule

STIG

Application Programming Interface (API) Security Requirements Guide

Version

V1R1

CCIs

CCI-000130

Discussion

Monitoring the usage of API keys to detect anomalies is crucial for maintaining security, preventing abuse, and ensuring only authorized users or applications are accessing the system. API keys are used to authenticate and authorize requests to APIs, and if misused, can become a significant security vulnerability. By monitoring API key usage, unusual patterns can be detected quickly. Anomalies could indicate potential issues like compromised API keys, unauthorized third-party access, or bot activity. Early detection of such anomalies allows for timely action preventing further exploitation. Monitoring also helps enforce usage limits and detect overuse or abuse of API resources, which could impact system performance.

Check Content

Verify the platform provides features to monitor API key usage, including tracking requests made with each key and flagging anomalies such as unexpected request patterns, usage from unusual geographic locations, abnormal request rates, or access to unauthorized endpoints. 

If API key usage is not being monitored for anomalies, this is a finding.

Fix Text

Build or configure the API to monitor API key usage and flag anomalies:

Enable Logging: Log all API key usage, including timestamps, IP addresses, endpoints accessed, and request rates.

Define Normal Behavior: Establish a baseline for expected usage patterns (e.g., typical request rate, endpoints used, geographic regions).

Set Thresholds: Configure thresholds for detecting anomalies such as excessive requests, access to unusual resources, or use from unexpected locations.

Integrate Monitoring Tools: Use API management or SIEM tools to analyze logs and trigger alerts on anomalous activity.

Automate Alerts: Set up real-time notifications or automated actions (e.g., temporary blocking) when anomalies are detected.