detecting-api-enumeration-attacks

# Detecting API Enumeration Attacks ## Overview API enumeration attacks occur when attackers systematically probe API endpoints with sequential or predictable identifiers to discover and access unauthorized resources. Broken Object Level Authorization (BOLA), ranked as API1:2023 in the OWASP API Security Top 10, is the most critical API vulnerability. Attackers manipulate object identifiers (user IDs, order numbers, account references) in API requests to bypass authorization and access other users' data. Detection requires monitoring for patterns of rapid sequential access attempts, authorization failures, and abnormal API usage behavior. ## When to Use - When investigating security incidents that require detecting api enumeration attacks - When building detection rules or threat hunting queries for this domain - When SOC analysts need structured procedures for this analysis type - When validating security monitoring coverage for related attack techniques ## Prerequisites - API gateway or reverse proxy with logging enabled (Kong, AWS API Gateway, Apigee) - SIEM platform (Splunk, Elastic SIEM, or Microsoft Sentinel) - Access to API server logs with request details - Web Application Firewall (WAF) with API protection capabilities - Understanding of the API's authorization model and object identifier schemes ## Attack Patterns to Detect ### 1. Sequential ID Enumeration Attackers iterate through numeric or predictable identifiers: ``` GET /api/v1/users/1001 -> 200 OK G...