detecting-api-enumeration-attacks

Featured

Detect and prevent API enumeration attacks including BOLA and IDOR exploitation by monitoring sequential identifier access patterns and authorization failures.

AI & Automation 36,355 stars 4443 forks Updated 2 months ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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...

Details

Author
mukul975
Repository
mukul975/Anthropic-Cybersecurity-Skills
Created
8 months ago
Last Updated
2 months ago
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

API & Backend Listed

detect-api-business-logic-abuse

Detection and response methodology for API business logic abuse - BOLA / IDOR (OWASP API1:2023), request-rate abuse (API4:2023), and out-of-order workflow attacks against REST and GraphQL APIs (MITRE ATT&CK T1190, with high-volume enumeration resembling T1595). Works off API gateway and reverse-proxy access logs (nginx, Apache, AWS ALB / API Gateway, Azure APIM and Front Door, Cloudflare) plus WAF and application audit logs. Gives the method for spotting one principal touching object IDs across many owners, per-principal velocity spikes, and workflow step-skipping, plus public rule sources and object-level-authorization hardening. Use when investigating suspicious API access, hunting for IDOR or BOLA enumeration, triaging a spike of 403 or 404 responses from one token, building rate or sequence anomaly detection, or hardening an API against BOLA.

0 Updated 5 days ago
umbrasec-labs
AI & Automation Listed

analyzing-api-gateway-access-logs

Parses API Gateway access logs (AWS API Gateway, Kong, Nginx) to detect BOLA/IDOR attacks, rate limit bypass, credential scanning, and injection attempts. Uses pandas for statistical analysis of request patterns and anomaly detection. Use when investigating API abuse or building API-specific threat detection rules.

100 Updated 2 weeks ago
adriannoes
AI & Automation Listed

analyzing-api-gateway-access-logs

Parses API Gateway access logs (AWS API Gateway, Kong, Nginx) to detect BOLA/IDOR attacks, rate limit bypass, credential scanning, and injection attempts. Uses pandas for statistical analysis of request patterns and anomaly detection. Use when investigating API abuse or building API-specific threat detection rules.

100 Updated yesterday
26zl