Understanding RTR Sessions
RTR uses sessions to execute commands on hosts. Sessions can be:- Single-host sessions: Interactive session with one host
- Batch sessions: Execute commands across multiple hosts simultaneously
Session Types and Permissions
1
Read-Only Commands
Requires
Real time response: Read permission. Commands like ls, ps, netstat.2
Active Responder Commands
Requires
Real time response: Write permission. Adds get, cp, rm, mkdir.3
Admin Commands
Requires
Real time response (admin): Write permission. Adds put, run, runscript, kill.Starting RTR Sessions
Single-Host Session
Batch Session
The
-QueueOffline parameter queues the session for offline hosts. They will execute commands when they come online.Executing Commands
Read-Only Commands
Active Responder Commands
Admin Commands
Batch Command Execution
Execute Commands Across Multiple Hosts
Batch File Retrieval
Target Specific Hosts in Batch
Managing RTR Assets
Put Files
Put files are uploaded to CrowdStrike and can be deployed to hosts:Custom Scripts
Upload and manage custom scripts for RTR:FalconScript Library
CrowdStrike provides pre-built scripts in the FalconScript library:Session Management
List Active Sessions
Queued Sessions
Close Sessions
Sessions automatically timeout after inactivity. Always close sessions when finished to free resources.
Command Confirmation
Confirm command execution status:Practical Investigation Workflow
1
Identify Suspicious Host
2
Start RTR Session
3
Gather Process Information
4
Check Network Connections
5
Retrieve Suspicious File
6
Contain Host
7
Close Session
Next Steps
Managing Policies
Configure prevention and response policies
Working with Hosts
Query and organize your host inventory