Events and decisions
Every protected transaction creates evidence that can be reviewed, audited, alerted on, and metered.
Transaction event
A transaction event is the runtime record sent by your application when a protected action is evaluated. It includes operation key, actor, resource, request summary, score, reasons, and normalized signals.
Events are the basis for usage metering. An evaluated transaction counts when TxnShield receives and records a protected runtime evaluation.
Decision log
A decision log is the security outcome for the event. Typical decisions are allow, allow_redacted, step_up_required, throttle, and deny.
Use decision logs to investigate why a user was blocked, why data was redacted, or why a challenge was required.
Why this matters
Auth logs usually prove that a user signed in. TxnShield logs explain whether a specific sensitive transaction was safe enough to run in its runtime context.
Next steps