Analyzing API Gateway Access Logs
SkillCloud & infraThis skill lets your AI parse access logs from AWS API Gateway, Kong, and Nginx. Once added, your AI can read raw log files and turn them into structured entries, so you can ask about your API gateway traffic instead of reading logs line by line.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding the skill, give your AI an access log from one of the supported gateways and ask it to parse the entries.
Then ask your AI: use the Analyzing API Gateway Access Logs skill
What your AI can do with it
- Read access logs from AWS API Gateway, Kong, and Nginx
- Parse raw log lines into structured entries
- Answer questions about the log entries it has parsed
What this skill tells your AI
The instructions your AI receives, as published by 26zl/cybersec-toolkit in .claude/skills/analyzing-api-gateway-access-logs/SKILL.md and read by ahel’s review.
When to Use
- When investigating security incidents that require analyzing api gateway access logs
- 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
- Familiarity with security operations concepts and tools
- Access to a test or lab environment for safe execution
- Python 3.8+ with required dependencies installed
- Appropriate authorization for any testing activities
Instructions
Parse API gateway access logs to identify attack patterns including broken object level authorization (BOLA), excessive data exposure, and injection attempts.
import pandas as pd
df = pd.read_json("api_gateway_logs.json", lines=True)
# Detect BOLA: same user accessing many different resource IDs
bola = df.groupby(["user_id", "endpoint"]).agg(
unique_ids=("resource_id", "nunique")).reset_index()
suspicious = bola[bola["unique_ids"] > 50]
Key detection patterns:
- BOLA/IDOR: sequential resource ID enumeration
- Rate limit bypass via header manipulation
- Credential scanning (401 surges from single source)
- SQL/NoSQL injection in query parameters
- Unusual HTTP methods (DELETE, PATCH) on read-only endpoints
Examples
# Detect 401 surges indicating credential scanning
auth_failures = df[df["status_code"] == 401]
scanner_ips = auth_failures.groupby("source_ip").size()
scanners = scanner_ips[scanner_ips > 100]
Signals
- GitHub stars
- 54
- Forks
- 10
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
analyzing-api-gateway-access-logs- Source
- github.com/26zl/cybersec-toolkit