Developer workflow

What is Runtime / Production Monitoring?

Observing the application in production to detect or block attacks and confirm which vulnerabilities are actually exposed.

Runtime context answers the question static analysis cannot: is this vulnerable code path actually reachable in the deployed system, behind authentication, or exposed to the internet? That reorders a backlog fast.

Some tools go further and block malicious requests in-process. That is a different operational commitment from scanning, since it sits in the request path, so latency and failure behaviour become your concern.

Top 6 Runtime / Production Monitoring tools

Every tool in the directory documented as supporting Runtime / Production Monitoring, with what its own documentation says.

Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.

  1. 1
    CodacyQuality PlatformBusiness

    DAST scans deployed web apps and APIs on a schedule; Business plan only.

  2. 2
    AikidoCode Security PlatformEnterprise

    Zen Firewall runtime WAF (sidecar, reverse proxy, inline library); Advanced/Enterprise plan only

  3. 3
    CodeAnt AIPR Review

    CSPM continuously monitors live cloud environments and scans VMs for runtime vulnerabilities.

  4. 4
    CorgeaCode Security Platform

    AI Pentesting against live targets; needs admin enablement

  5. 5
    SnykCode Security PlatformEnterprise

    Kubernetes Connector reads live workloads; cloud scans of deployed resources are Enterprise; DAST scans live apps.

  6. 6
    VeracodeCode Security Platformadd-on

    DAST scans live apps/APIs; Quick scan safe in production; EASM discovers external assets

What to look for

  • Whether it observes only or actively blocks
  • Deployment model, such as sidecar, agent, or in-process library, and its overhead
  • Whether runtime signals feed back into finding prioritisation
  • Failure behaviour if the runtime component becomes unavailable

Related terms

Real-Time IDE FeedbackAI Agent Guardrails (MCP)Local CLI / Pre-CommitPR Inline ReviewMerge Gate / BlockingFull Repo Scan

FAQ

What is Runtime / Production Monitoring?

Observing the application in production to detect or block attacks and confirm which vulnerabilities are actually exposed.

How many tools support Runtime / Production Monitoring?

6 of the 20 tools tracked in this directory support Runtime / Production Monitoring, including Codacy, Aikido, CodeAnt AI, Corgea, Snyk. Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.

What should you look for in Runtime / Production Monitoring?

Whether it observes only or actively blocks. Deployment model, such as sidecar, agent, or in-process library, and its overhead. Whether runtime signals feed back into finding prioritisation. Failure behaviour if the runtime component becomes unavailable.