'rate-limiting' 검색 결과

Use when working with Redis - in-memory database, caching, pub/sub, sessions, rate limiting, RESP3, asyncio, Redis Stack

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Identify and exploit flaws in API rate limiting enforcement. Use this skill when encountering HTTP 429 Too Many Requests errors during password brute-forcing, OTP validation, credential stuffing, or enumeration attacks. These bypasses leverage IP spoofing, parameter manipulation, and edge-case application logic.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement rate limiting on APIs. Per-IP, per-user, sliding window patterns. Express and framework-agnostic.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cloudflare Workers, KV, Durable Objects, and edge computing development. Use for serverless APIs, caching, rate limiting, real-time features. Activate on "Workers", "KV", "Durable Objects", "wrangler", "edge function", "Cloudflare". NOT for Cloudflare Pages configuration (use deployment docs), DNS management, or general CDN settings.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

API gateway and reverse proxy configuration with Kong, Nginx, Traefik, routing, and auth middleware. Activate on: API gateway, reverse proxy, Kong, Nginx, Traefik, load balancer, ingress, auth middleware. NOT for: rate limiting algorithms (use api-rate-limiting-throttling-expert), service mesh (use service-mesh-microservices-expert).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use for API-key health checks, rotation, and monitoring.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert en API gateway v2 (Kong, Traefik, rate limiting, auth, routing, observabilité)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert en API gateways (Kong, Traefik, nginx, rate limiting, auth, routing, plugins)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert en scalabilité des agents IA (scaling horizontal, load balancing, gestion de files, rate limiting)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Securing API Gateway endpoints with AWS WAF by configuring managed rule groups for OWASP Top 10 protection, creating custom rate limiting rules, implementing bot control, setting up IP reputation filtering, and monitoring WAF metrics for security effectiveness.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

bu skill covers Dağıt:ing and tuning Web Application Firewall rules on AWS WAF, Azure WAF, and Cloudflare to protect cloud-hosted applications against OWASP Top 10 attacks. It details configuring managed rule sets, creating custom rules for business logic protection, implementing rate limiting, Dağıt:ing bot management, and reducing false positives through rule tuning and logging analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implements security controls at the API gateway layer including authentication enforcement, rate limiting, request validation, IP allowlisting, TLS termination, and threat protection. The engineer configures API gateways (Kong, AWS API Gateway, Azure APIM, Apigee) to act as a centralized security enforcement point that validates, throttles, and monitors all API traffic before it reaches backend services. Activates for requests involving API gateway security, API management security, gateway a...

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs and audits data retention and file compaction for an embedded SQLite datastore in a long-lived service — a unified retention registry (one declared policy per table), TTL / absolute-age / row-count-cap policies, a fail-loud coverage guard, WAL/checkpoint tuning, and auto_vacuum/incremental-vacuum so pruning actually shrinks the file. Use when a SQLite DB grows unbounded, a table has an index but no DELETE, a pruned DB never shrinks on disk, metrics are stored as raw events forever, or a new table needs bounding. Keywords retention policy, TTL, reaper, prune, VACUUM, auto_vacuum, incremental_vacuum, WAL checkpoint, freelist, DB bloat, row cap, per-tenant quota. NOT for Postgres/MySQL/server-DB partitioning or TTL, log-line rate-limiting/sampling, backup/replication, schema migrations, or query-performance indexing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cloudflare Workers, KV, Durable Objects, and edge computing development. Use for serverless APIs, caching, rate limiting, real-time features. Activate on "Workers", "KV", "Durable Objects", "wrangler", "edge function", "Cloudflare". NOT for Cloudflare Pages configuration (use deployment docs), DNS management, or general CDN settings.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

API gateway and reverse proxy configuration with Kong, Nginx, Traefik, routing, and auth middleware. Activate on: API gateway, reverse proxy, Kong, Nginx, Traefik, load balancer, ingress, auth middleware. NOT for: rate limiting algorithms (use api-rate-limiting-throttling-expert), service mesh (use service-mesh-microservices-expert).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implements rate limiting and abuse prevention with per-route policies, IP/user-based limits, sliding windows, safe error responses, and observability. Use when adding "rate limiting", "API protection", "abuse prevention", or "DDoS protection".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Okta-as-IdP red-team attack chain — tenant discovery, user enumeration (multiple vectors), authentication flow analysis (factors enumeration, push-notification fatigue, SMS bypass), password spray with lockout discipline, Okta-specific phishing primitives (kits, FastPass abuse, OIDC redirect_uri tampering), MFA enumeration, post-compromise admin API surface. Many enterprise orgs use Okta instead of (or alongside) Entra ID. Distinct endpoints, distinct rate-limiting, distinct factor flows. Use when recon shows `<tenant>.okta.com`, `<tenant>.okta-emea.com`, `<tenant>.oktapreview.com`, or autodiscover-style records pointing at Okta IdP.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.