liveBook · Manning

Velocity check

As explained in Secure APIs

A velocity check analyzes the speed and frequency of operations across contextual factors such as IP address, geolocation, device fingerprint, account, and resources.

A velocity check measures how quickly and how often operations occur, considering factors such as IP address, geolocation, device fingerprint, account, and resources. It helps identify brute-force attempts, payment fraud, resource exhaustion, and suspicious data access. section 5.1.2

Login and payment scenarios

A login endpoint can count attempts by IP and account, block an IP after a threshold, and lock an account after repeated failures. For payments, repeated attempts using one card can be evaluated alongside IP, location, and device data before treating them as fraudulent. section 5.1.2

How Secure APIs covers it

How deep it goes
Defines multidimensional frequency analysis and sketches counters, blocking, and adaptive thresholds without specifying a complete production design.
Examples
Uses a vulnerable login endpoint, IP and account counters, account locking, IP blocking, and repeated payment attempts on one card.
What it assumes
Assumes a basic API endpoint and request context while defining velocity analysis and demonstrating login protection from first principles.
What you can do after
Build it from scratch by counting attempts, correlating contextual factors, setting user-appropriate thresholds, and blocking or reviewing suspicious operations.
How it connects
Connects brute-force attacks, resource exhaustion, fraud detection, IP addresses, accounts, device fingerprints, and geolocation.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Secure APIs. The section links point to the parts of the book it draws on.