Security Operations

RDRS real-time monitoring

Reading RDRS runtime status...
Threat posture · latest recorded detection
Recorded score, not a continuous risk estimate.
Detection signals & assessment
Incident investigation queue
Analyst context

Review Critical detections first. Incident records preserve affected files, process observations and simulation evidence.

Process attribution is heuristic. Alert totals are recorded history; acknowledgement and active-status tracking are not available.

Threat Score
0.0
Threat Level
Normal
File Events
0
Alerts
0
Incidents
0
Recent Process CPU Distribution

The latest persisted process observations, ordered from lower to higher CPU usage.

Entropy History

Entropy recorded on recent file events, from oldest to newest.

Recent Events
Action Path Time
No events
Recent Alerts
Severity Message Time
No alerts
Top Modified Files
No modified-file data
Recent Processes
PID Name CPU % Memory %
No process telemetry
Process Snapshots
0
Cumulative rows recorded across every capture cycle — not the number of processes running now.
Score Reason
No score recorded
Last Score Update
—
File System Events

Action Path File Type Entropy Time
No events
Process Telemetry
PID Name CPU % Memory % Disk Writes Executable Parent
No process telemetry
Alerts
Severity Message Score Time
No alerts
Incidents
ID Severity Status Score Time
No incidents
Incident Reports
Loading incidents...
Runtime Settings

Enabled — durable SQLite history. Events, process snapshots, alerts, incidents and scores are written to persistence.db_path and survive an application restart.
Disabled — in-memory runtime data only. Everything works while RDRS is running, including stop/start of monitoring, but the history is lost when the application exits.
Switching to Disabled does not delete the existing database file, and switching back to Enabled makes the previously recorded history visible again.

Incident investigation