What Is Runtime Application Security?
Runtime application security enforces controls while the application runs, at the point untrusted input meets your code, with context that pre- and post-runtime tools do not have.
Read guideWeb Security
Enforcing security decisions while the application runs, in the path of the action, with application context.
Runtime security enforces policy while an application is executing, at the moment untrusted input reaches code or an action is about to take effect. It is distinct from pre-deployment scanning, which never sees live input, and from monitoring, which reports after the fact. The defining property is that a decision arrives before the effect: the application receives an allow, block, redact, or limit result and branches on it. Effective runtime controls need both speed and context, because a decision in the request path must be fast enough to keep, and a decision worth making requires knowing the user, the route, the target object, and the operation. Controls must also define explicit behavior when a security dependency is slow or unavailable, per action rather than globally.
Start with runtime application security for the definition, lifecycle position, and comparison against network and gateway controls. Use pre-runtime vs post-runtime tooling to separate detection from enforcement when evaluating vendors, then read the LLM runtime security guide for AI-specific failure modes and the local inspection guide for data residency.
Runtime application security enforces controls while the application runs, at the point untrusted input meets your code, with context that pre- and post-runtime tools do not have.
Read guideSDK-based security vs WAF vs API gateway: what each layer sees, why indie teams import a library instead of pointing DNS at Cloudflare, and how to add bots, rate limits, and attack blocking in a few lines of code.
Read guideThe rule ships with the feature and runs in the request path. How in-code enforcement works, and how to roll it out safely.
Read guideDetect injection, abuse, exfiltration, and agent manipulation in the handler, then deny before the query, the charge, or the model. Keep the body in process.
Read guide