Web Security

Runtime security guides

Enforcing security decisions while the application runs, in the path of the action, with application context.

What these guides cover

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.

Risks

  • Attacks arriving in live traffic that pre-deployment testing cannot see
  • Authorization decisions made without user or object context
  • Consequential actions on paths that never cross the network perimeter
  • Controls that fail open silently or fail closed indiscriminately

Control priorities

  • Enforcement in application code, in the path of the action
  • Decisions using authenticated identity, route, object, and tenant
  • Coverage of tool calls, queue consumers, and background jobs
  • Dry-run measurement and per-action failure behavior

Recommended reading order

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.

Guides in this collection