# Block vs Detect: definition and example

URL: https://airuntimesecuritytools.com/glossary/block-vs-detect/
Updated: 2026-11-16

Block versus detect is the choice between stopping an action before it completes and only raising an alert. Blocking prevents harm but risks stopping legitimate work. Detecting keeps work flowing but leaves the response to people or automation after the fact.

## Example

Noma says it detects runtime behavior patterns that indicate credential theft, data exfiltration and AI memory tampering, and no block was stated for those detections.

## Sources

- [Noma Security page](https://www.prnewswire.com/news-releases/noma-labs-discovers-critical-vulnerability-in-widely-adopted-open-source-ai-agent-platform-ruflo-302837494.html) (prnewswire.com), read 2026-11-16

## Related pages

- [Inline Enforcement](/glossary/inline-enforcement/)
- [False Positive Budget](/glossary/false-positive-budget/)
- [SOAR Playbook](/glossary/soar-playbook/)
- [AI Runtime Security vs Guardrails vs Red Teaming](/guides/ai-runtime-security-vs-guardrails-vs-red-teaming/)
- [Inline or Out-of-Band Runtime Enforcement](/guides/inline-or-out-of-band-runtime-enforcement/)
- [Runtime Security Metrics: False Positives and Blocks](/guides/runtime-security-metrics-false-positives-and-blocked-rate/)
- [All glossary terms](/glossary/)
- [Behavioral Baseline](/glossary/behavioral-baseline/)
- [Canary Token](/glossary/canary-token/)
- [Guides](/guides/)
