Marketplace
LIVE FOUNDATIONSecurity / security

Threat Detection & Runtime Security

Detect abusive behavior at the edge, visualize it, scan the software supply chain and optionally enforce runtime policy in the kernel.

Review my build
Intrusion prevention, the reverse-proxy bouncer, the honeypot and the threat map are live. The vulnerability scanner runs as a scheduled scan, not a resident service. Runtime security enforcement is optional and currently disabled pending an observe/enforce redesign; it is never marketed as active.
Live workload cutawayArchitecture in context
Threat Detection & Runtime Security
Signal path active7 deployment units

What this replaces

A private AI stack can still be scanned, attacked, misconfigured or compromised through vulnerable images and runtime behavior.

What your team gains

Layered security using behavioral detection, application remediation, deception, vulnerability scanning and optional eBPF runtime observability/enforcement.

What is inside the blueprint

Behavioral intrusion-prevention decisions
Layer 3/4 and Layer 7 remediation options
Reverse-proxy/WAF-capable remediation patterns
Virtual patching/application-layer protections where configured
Honeypot/deception endpoints
GeoIP threat visualization
Scheduled vulnerability scanning
Secret scanning
IaC/misconfiguration scanning
License scanning
SBOM input scanning
eBPF process/file/network/security observation
Tracing-policy hooks including kprobes, tracepoints, uprobes, LSM and USDT
In-kernel filtering
Runtime actions such as signals/return-value override where supported and intentionally enabled

How it fits the platform

Traffic/code/runtime -> reverse proxy/intrusion prevention + scheduled vulnerability scans + optional runtime security -> decisions/findings/events -> threat map, alerts and operations workflows.

Included services

Intrusion prevention, Reverse proxy bouncer, honeypot, threat-map, Vulnerability scanner, Runtime security (optional/disabled today), telegram-gateway

Platform requirements

From prerequisites to operation

Prerequisites
  1. Ingress logs
  2. Security policy
  3. Scan targets
  4. Kernel/eBPF compatibility for runtime security
Deployment
  1. Enable intrusion-prevention collections and remediation
  2. Connect reverse-proxy logs/bouncer
  3. Deploy honeypot/threat map
  4. Schedule vulnerability scans
  5. Introduce runtime security first in observe mode before enforcement
Configuration
  1. Detection/remediation rules
  2. WAF/AppSec options
  3. Scan severities/scanners
  4. Custom secret rules
  5. Runtime tracing policies/actions
  6. Alert routing
Operations
  1. False-positive review
  2. Bouncer availability
  3. Vulnerability triage
  4. Rule updates
  5. Kernel-policy safety testing
  6. Threat retention

What this unlocks with other layers

Zero-Trust Edge & Identity + Threat Detection & Runtime Security

Zero-Trust AI Service

Remote AI access without exposing origin service ports, with centralized authentication and behavioral remediation.

Threat Detection & Runtime Security + AI Operations Center

Security Operations Story

Edge attacks, software vulnerabilities and runtime behavior feed one alert and response narrative.

Technology behind this capability

Reverse proxyIntrusion preventionVulnerability scannerRuntime securityTelegram gatewayAICORTEX nativeHoneypotAICORTEX nativeThreat mapAICORTEX native