Requests with a shelf life.
Defeat tampering, man-in-the-middle, and replay attacks, and define how long a request may live — so a captured or altered call is rejected, not executed.
1. Three attacks on the request in flight
Between client and server, a request can be tampered with (a field changed), captured and replayed, or intercepted by a man in the middle. TLS protects the channel, but the application still needs its own integrity guarantees — because the dangerous changes are often made by a legitimate-looking client, and the dangerous replays carry valid credentials.
2. A defined request lifetime
Giving each request a defined lifetime is the simplest powerful control here: a signed timestamp and a short expiry window mean a captured request is worthless within seconds, and a nonce means even a fast replay is caught. Combined with a payload-covering signature, tampering and man-in-the-middle modification both fail to verify.
3. How B5 Secure handles it
B5 Secure lets you define request lifetime and enforces integrity and replay protection in the pipeline, so tampered, stale, or replayed requests are rejected before they reach your logic. It is the same machinery behind the signed schemes, applied as an attack-resistance guarantee.