Intelligent Rate Limiting for API: Multi-Level Protection

A single scraper can take down an entire API — 10,000 requests per second are enough to exhaust backend resources in 30 seconds. IP-based blocking often affects legitimate users: 80% of attacks use an address pool, so IP filtering is ineffective. Rate limiting solves this by analyzing IP, user ID, API key, endpoint, and request history. For example, for a fintech platform we implemented adaptive rate limiting — incidents dropped by 90%, average response time decreased by 30%, saving $500 monthly on cloud resources. We deploy a multi-level system that dynamically adjusts limits, maintaining availability for 99% of clients even during an attack. With over 5 years of experience in API security and 50+ successful implementations, our team ensures robust protection.

Why Multi-Level Control?

A single IP-based level is insufficient: scrapers can use an address pool. We introduce three levels: by user (authenticated), by IP (others), and global (DDoS protection). For example, during a registration attack, we block IPs but leave authenticated users untouched — 99% of legitimate traffic passes without delays. Multi-level approach reduces false positives by 80% and saves up to 40% server resources. Our rate limiting configuration includes Redis and adaptive algorithms for API protection from scrapers.

How Sliding Window Works in Redis

import redis
import time
from functools import wraps

r = redis.Redis(host='localhost', decode_responses=True)

def sliding_window_rate_limit(key: str, limit: int, window: int) -> bool:
    """
    key: unique identifier (user_id, ip, api_key)
    limit: max requests per window seconds
    window: window size in seconds
    Returns True if request is allowed
    """
    now = time.time()
    window_start = now - window

    pipe = r.pipeline()
    pipe.zremrangebyscore(key, 0, window_start)  # remove old entries
    pipe.zadd(key, {str(now): now})              # add current request
    pipe.zcard(key)                              # count in window
    pipe.expire(key, window)                    # TTL for cleanup
    results = pipe.execute()

    count = results[2]
    return count <= limit

This code uses Redis Sorted Set to store request timestamps. Each request is added with a score equal to the current time. Old entries are removed, and the count is compared to the limit.

Comparison: Token Bucket vs Sliding Window in Practice

Sliding Window is twice as accurate as Fixed Window under peak loads and provides smoother limiting.

Adaptive Rate Limit Reduction by Risk

class AdaptiveRateLimiter:
    def get_risk_score(self, request) -> float:
        """Score request risk from 0.0 (low) to 1.0 (high)"""
        score = 0.0

        # Suspicious User-Agent
        ua = request.headers.get('User-Agent', '')
        if not ua or 'python-requests' in ua.lower() or 'curl' in ua.lower():
            score += 0.3

        # Missing browser headers
        if not request.headers.get('Accept-Language'):
            score += 0.2

        # Recent error history (many 404, 401)
        error_count = r.get(f"errors:{request.remote_addr}") or 0
        if int(error_count) > 10:
            score += 0.3

        # Requests from Tor/VPN IP (check against list)
        if self.is_known_proxy(request.remote_addr):
            score += 0.2

        return min(score, 1.0)

    def get_effective_limit(self, base_limit: int, risk_score: float) -> int:
        """Reduce limit for suspicious clients"""
        multiplier = 1.0 - (risk_score * 0.8)  # up to 80% reduction
        return max(int(base_limit * multiplier), 1)

For clients with high risk scores, the limit drops by up to 80% (1 out of 5 requests allowed). This continues servicing but heavily restricts attackers.

Which Metrics to Monitor?

We integrate with Prometheus/Grafana: track rejected requests, Redis load, latency. When a threshold is exceeded, an alert triggers in Telegram or Slack. We recommend monitoring the rejected request ratio (no more than 5%) and Redis response time (under 1 ms).

Typical Rate Limiting Implementation Mistakes

1. Fixed Window on high-traffic endpoints — causes limit spikes at window boundaries. Sliding Window eliminates this.
2. Missing TTL for Redis keys — memory overflow. Always set expire.
3. IP-only limits — not effective against distributed attacks. Use multi-level control.
4. Ignoring X-RateLimit headers — clients cannot adapt. Add headers per RFC 6585.

Redis vs In-memory for Rate Limiting

Redis provides 10x better scalability than in-memory solutions for distributed systems.

Implementation Process and Timeline

Implementation Steps

1. Audit current API — analyze endpoints, client types, peak loads. Determine baseline (e.g., 1000 rps for public endpoints).
2. Design policies — define limits for each endpoint and control levels.
3. Implementation — write middleware, connect Redis, set up multi-level checking.
4. Testing — load testing with simulated scenarios (scraping at 10,000 rps, DDoS, normal operation).
5. Deployment and monitoring — roll out to staging, then production, configure alerts.

Estimated Timelines

Basic implementation with Redis Sliding Window and multi-level limits takes 1–2 working days. Full implementation with adaptive scoring and Kong integration — up to 5 days. We provide an exact estimate after auditing your API.

What You Get and How to Start

As part of the work, you receive code with decorators and middleware (Python/Node.js/PHP — based on your stack), deployment and configuration documentation, integration with existing infrastructure (Redis, Kong, Nginx), monitoring and alert setup, and team training. We guarantee stability for a month post-launch.

We offer a turnkey solution: code, deployment, and training. Contact us for a free audit of your API. We'll assess the load and propose an optimal configuration. Order implementation and get stable protection in a couple of days. Get a consultation today — we'll explain how adaptive rate limiting solves your problems. Our service includes everything: code, deployment, monitoring, and support.

Web Application Security: HTTPS, CSP, XSS, CSRF, WAF, DDoS Protection

A website breach rarely looks like in movies. More often it's: a bot finds an unprotected /admin/export endpoint, downloads the customer database, and closes the connection. Or: through an outdated WordPress plugin, a web shell is uploaded, and the server starts sending spam. Or quieter: an XSS in a comment field allows stealing admin session cookies, unnoticed for months. We have analyzed dozens of such cases — each vulnerability could have been fixed at the development or audit stage.

Web application security is not a single setting. It's layers of protection, each closing a separate class of attacks. Order an audit — we'll assess the project and deliver a turnkey plan within 2–4 weeks.

How do we ensure comprehensive web application security?

HTTPS and Proper TLS Configuration

HTTPS is the minimum mandatory level. But having an SSL certificate and having a properly configured TLS are different things.

In Nginx/Apache configuration we check:

• Protocols: only TLS 1.2 and TLS 1.3, SSLv3 and TLS 1.0/1.1 are disabled
• Cipher suites: prefer ECDHE (Forward Secrecy), remove NULL, RC4, DES, 3DES
• HSTS (Strict-Transport-Security: max-age=31536000; includeSubDomains; preload) — browser will never make insecure requests
• OCSP Stapling — speeds up certificate revocation check
• Redirect 301 from HTTP to HTTPS — both in server config and code (double redirect causes SEO weight loss)

Check: SSL Labs (ssllabs.com/ssltest) should show A or A+. If B, the configuration is weak.

Let's Encrypt + Certbot for production is standard. Automatic renewal via certbot renew in cron. Wildcard certificates for subdomains via DNS-01 challenge.

Content Security Policy: The Most Powerful and Complex Protection

CSP is an HTTP header that tells the browser which sources are allowed to load resources. A properly configured CSP completely blocks most XSS attacks, even if the vulnerability exists in the code.

The problem: breaking the site with an incorrect CSP is easy. default-src 'none' — and fonts, images, JS stop working. So we start with Content-Security-Policy-Report-Only — CSP logs violations but does not block anything. We monitor reports for 2–4 weeks, refine the policy, then switch to enforcement mode.

Example of a real policy for a site with Google Analytics, Google Fonts, and Stripe:

Content-Security-Policy:
  default-src 'self';
  script-src 'self' https://www.googletagmanager.com https://js.stripe.com 'nonce-{random}';
  style-src 'self' https://fonts.googleapis.com 'unsafe-inline';
  font-src 'self' https://fonts.gstatic.com;
  frame-src https://js.stripe.com;
  img-src 'self' data: https://www.google-analytics.com;
  connect-src 'self' https://api.stripe.com https://www.google-analytics.com;
  report-uri /csp-report;

nonce — a random string generated server-side per request. Inline scripts with the correct nonce are allowed; without nonce, they are blocked. This completely breaks XSS via <script>alert(1)</script>.

'unsafe-inline' in style-src is a compromise for inline styles. It's better to remove it by moving all styles to CSS files, but that requires refactoring.

Why XSS Remains the Most Common Vulnerability?

XSS (Cross-Site Scripting) — injection of JS code through user input. According to OWASP, XSS is in the top 3 web application vulnerabilities. Three types:

Protection: never insert user input into HTML without escaping. In PHP — htmlspecialchars() with ENT_QUOTES. In Laravel Blade templates — {{ $var }} is safe, {!! $var !!} is dangerous. In React — {variable} is safe, dangerouslySetInnerHTML is dangerous. For Rich Text — use htmlpurifier on PHP or DOMPurify in the browser.

CSRF: Protecting Forms and APIs

CSRF (Cross-Site Request Forgery) — an attacker forces the victim's browser to send a request on their behalf. Example: a user is logged into a bank, opens a malicious page, which makes fetch('https://bank.ru/transfer?to=evil&amount=50000') — if the bank is unprotected, money is transferred.

CSRF tokens — standard protection for forms: the server generates a random token, stores it in the session, and inserts it as a hidden field in the form. On POST request, the token is verified. The attacker does not know the token. Laravel does this automatically with @csrf.

SameSite cookies — modern protection: SameSite=Strict or SameSite=Lax prevents the browser from sending cookies in cross-site requests. Works in all modern browsers.

API without sessions (JWT, Bearer tokens) — CSRF is irrelevant if the token is not stored in a cookie (but in the Authorization header or localStorage). However, localStorage is vulnerable to XSS — so for sensitive data, HttpOnly cookies with SameSite are preferable.

WAF and DDoS Protection

WAF (Web Application Firewall) filters HTTP traffic for attacks: SQL injection, XSS, path traversal, known exploit patterns. Options:

• Cloudflare WAF — cloud-based, OWASP Top 10 rules out of the box, custom rules via expressions. Managed Rules automatically block new threats.
• ModSecurity (Nginx/Apache) — self-hosted, OWASP Core Rule Set (CRS). Flexible but requires tuning and monitoring of false positives.
• AWS WAF — for infrastructure on AWS, integrates with CloudFront and ALB.

DDoS protection. Cloudflare at L3/L4/L7 is the de facto standard for most sites. Automatic mitigation of volumetric attacks, Under Attack Mode during active attacks. For critical infrastructure — Cloudflare Magic Transit or specialized solutions (Qrator, StormWall for the Russian market).

Rate Limiting at the application level — an additional layer. Laravel ThrottleRequests middleware: 60 requests per minute per IP for general endpoints, 5 for /login and /password/reset. Redis as a counter store — mandatory for horizontally scalable systems (otherwise limits are not synchronized between servers).

Other Mandatory Measures

Security headers. Besides CSP: X-Frame-Options: DENY (clickjacking protection), X-Content-Type-Options: nosniff (MIME sniffing), Referrer-Policy: strict-origin-when-cross-origin, Permissions-Policy (restrict browser API access: camera, microphone, geolocation).

SQL injection. Prepared statements everywhere. No concatenation of user input into SQL strings. ORM (Eloquent, Doctrine) protects by default. $wpdb->prepare() in WordPress is mandatory.

Dependency updates. composer audit and npm audit in CI/CD pipeline. Dependabot or Renovate for automatic PRs with updates. Critical CVEs — patch within 24 hours.

Secrets and configuration. .env — never in Git. Secrets in production — via CI/CD environment variables (GitHub Secrets, GitLab CI Variables) or HashiCorp Vault. Leak detection: git-secrets, truffleHog in pre-commit hooks.

How We Work

1. Audit — code scanning, configuration review, dependency analysis, manual business logic verification.
2. Planning — vulnerability remediation plan, stack selection (CSP, WAF, rate limiting).
3. Implementation — TLS setup, CSP configuration, headers, Rate Limiting, WAF.
4. Testing — re-penetration test, load testing, false positive check.
5. Deployment and Monitoring — enable production CSP, set up alerts, train the team.

What's Included

• Report with found vulnerabilities and recommendations (PDF + code snippets)
• Ready TLS configuration (Nginx/Apache)
• CSP policy with Report-Only and production versions
• WAF and Rate Limiting setup
• Dependency update plan
• Access to monitoring tools (Sentry, Datadog)
• 30 days of post-audit support (consultations, fixes)

Timeline and Cost

The budget is calculated individually — contact us for a project evaluation.