Runtime Protection (CWPP & CNAPP)
ATT&CK-mapped runtime threat detection rules and cloud-native risk correlation, surfacing findings that are running, reachable, exposed, and over-privileged all at once.
Runtime Protection (CWPP & CNAPP)
Runtime protection evaluates runtime events against detection rules and correlates the results with the rest of your posture, so risk that is actually live rises above theoretical risk.
Runtime threat detection (CWPP)
Safeguard ships a runtime rule engine that detects suspicious workload behavior - shells spawned in containers, sensitive file access, unexpected network activity, privilege changes - and maps each rule to the relevant MITRE ATT&CK technique so alerts arrive with adversary context.
Event source. The rule engine evaluates the runtime events (process execution, network and file activity) supplied to it. Safeguard does not ship its own runtime collector.
Detection rule packs
Managed rule packs each map to an ATT&CK technique:
| Rule pack | Triggers on | ATT&CK |
|---|---|---|
| Reverse shell | A shell whose input/output is wired to a network connection | T1059 |
| Crypto-miner | Connection to a known mining pool, or sustained high CPU with miner-class arguments | T1496 |
| Container escape | Known container-escape techniques - namespace breakout, privileged mounts, and host-root access | T1611 |
| Fileless / in-memory | Execution of a payload that runs from memory without ever touching disk | T1620 |
| Privilege escalation | Escalation to root, and anomalous sudo / pkexec use | T1548 |
| LOLBin chain | Download tools piped into a shell; scheduled-task writes from a workload | T1105 |
Per-workload allow-lists suppress benign shells (for example in interactive dev containers), and tenants can add custom rules in the same schema, tenant-scoped and audited on load. Rules raise alerts and findings; they do not block or terminate workloads.
Cloud-native risk correlation (CNAPP)
The CNAPP layer correlates findings across dimensions to identify the risks that matter most - a workload that is simultaneously:
- Running - actually executing, not just defined,
- Reachable - exposed on a network path,
- Exposed - accessible from an untrusted boundary, and
- Over-privileged - holding more permission than it needs.
A finding that lights up all four is prioritized far above one that lights up only one. This correlation flows into the unified findings model and shares correlation keys with SAST, DAST, and Red Team so a confirmed, reachable, exploitable issue is treated as such.
Findings
Runtime findings land in the unified findings view as runtime findings, tenant/org-scoped end to end, with the ATT&CK mapping and the correlation dimensions that fired.
Configuration
Runtime protection is admin-toggleable via a feature flag, enforced server-side. The rule engine evaluates the runtime events supplied to it (see the event source note above).
Related
- Unified Findings & Feature Flags - where runtime findings land and how the engine is toggled.
- Reachability Analysis - the reachability dimension of the correlation.
- Red Team - emulation that validates whether runtime detections fire.
- SecOps (SIEM) - runtime events feed the SIEM event store.
Data Security Posture Management (DSPM)
Discover and classify sensitive data - PII, PHI and payment-card data - with an enforced redaction mandate so raw sensitive data is never stored.
Package Firewall
Stop malicious and typosquatted dependencies at install time - inline allow / warn / block enforcement for typosquats, dependency confusion, and known-malicious packages.