Current modes:Documentation Index
Fetch the complete documentation index at: https://docs.esperr.com/llms.txt
Use this file to discover all available pages before exploring further.
Monitor: Observe matching traffic without taking an active step.Challenge: Ask the client to complete an additional verification step.Block: Stop the matching request from continuing.
Control-plane definition vs runtime decision
Esper separates:- the mitigation definition you create in the control plane
- the mitigation decision emitted after live policy evaluation
Edge enforcement
esper capture run --enforce can sync and enforce active mitigations locally.
Supported behavior today:
Block: request is dropped locally when the captured payload identifies the mitigated entityChallenge: surfaced as a matched mitigation, but not converted into a packet-level redirect or CAPTCHA flowMonitor: surfaced as a matched mitigation without blocking
Current limitation
Packet capture does not yet derive Esper entities from arbitrary traffic. Local enforcement therefore currently requires an Esper-managed opaqueX-Esper-Hybrid-Key header.
What you configure for a mitigation
When creating a mitigation, you choose:name: The label operators see in the console.description: Optional guidance on when to use this mitigation.mode: The response type Esper should apply, such as monitor, challenge, or block.