Arcjet from observe to enforce: first protect known legitimate use
Use two fictional check-in cards to review a false positive before adding a protection layer.
K-01 and K-02 are both labelled legitimate. The mock DRY_RUN flags K-02 for review.

Figure 1. Arcjet’s January 2025 guide describes two rule modes: DRY_RUN observes decisions without blocking, and LIVE enforces. Consider it alongside your existing application protections. If the current tool already provides a clear observation workflow, review history and an accountable owner, compare it before layering another service on top.
Check for false positives on ordinary use
Draw a fictional venue check-in desk. K-01 is a normal first check-in; K-02 is a staff member returning to review just-entered information. Both should finish normally. Use no real identifiers or traffic; run no requests or scans. If a mock K-02 result says it would block, log a false positive, have the maintainer explain it and defer enforcement. Include a card whose meaning is unclear and send it to review rather than labelling it abnormal.
Compare the same set with current defences. Require zero false blocks on known valid cards, explainable decisions and a named owner for review, changes and rollback. If evidence remains thin, keep observing, not enforcing just because a dashboard shows numbers. This is a paper-only defensive selection exercise.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:arcjet.com