# Inline Enforcement: definition and example

URL: https://airuntimesecuritytools.com/glossary/inline-enforcement/
Updated: 2026-11-16

Inline enforcement means the security check sits in the path of the request, so the action waits for a verdict and can be blocked. Out-of-band tools read a copy of the traffic or a log and can only alert. Inline checks add delay and create a failure-mode question, which is why latency and fail-open behavior are assessed apart.

## Example

Cisco's DefenseClaw documentation says its guardrail checks a prompt, a shell command or a tool call before the agent acts and answers allow, alert, ask or block.

## Sources

- [Cisco page](https://cisco-ai-defense.github.io/defenseclaw/docs/guardrail/) (cisco-ai-defense.github.io), read 2026-11-16

## Related pages

- [Fail Open](/glossary/fail-open/)
- [Fail Closed](/glossary/fail-closed/)
- [Block vs Detect](/glossary/block-vs-detect/)
- [Inline or Out-of-Band Runtime Enforcement](/guides/inline-or-out-of-band-runtime-enforcement/)
- [All glossary terms](/glossary/)
- [False Positive Budget](/glossary/false-positive-budget/)
- [Input Filtering](/glossary/input-filtering/)
- [Guides](/guides/)
