To access material, start machines and answer questions login.
Few mechanisms are as deceptively simple as Registry Run Keys, a handful of registry values that tell Windows what to execute at logon or startup.
Attackers have relied on them for decades precisely because they are easy to plant, hard to spot among legitimate entries, and survive reboots without any additional effort. In this room, you will approach the topic from a perspective, learning how to identify, analyze, and validate Run Key-based persistence during real-world investigations.
Learning Objectives
This room focuses on:
- Understanding how Windows Run Keys are used for persistence.
- Identifying suspicious and malicious Run Key entries.
- Detecting Run Key abuse using Windows Event Logs and .
- Learning DFIR workflows for investigating AutoStart persistence mechanisms.
- Practicing the analysis of Run Key persistence in real-world scenarios.
Prerequisites
Before starting this room, you should be familiar with:
- Basic Windows internals
- Windows Registry structure
- Windows Event Logs and Sysmon
- Fundamental Incident Response concepts
- Previous Windows -focused rooms
Machine Access
Launch DefenseBox by clicking Start DefenseBox and use this machine for practical exercises. You can also connect over OpenVPN and using the credentials below.
DefenseBox Credentials
Set up your virtual environment
For all DFIR tasks, we highly recommend accessing DefenseBox and the target over OpenVPN and connecting via RDP. This speeds up triage and makes switching between the VMs easier.
Let's go!
Ready to learn Cyber Security?
The Detecting Persistent AutoStart Run Keys room is only available for Premium or Max subscribers. Signup now to access more than 500 free rooms and learn cyber security through a fun, interactive learning environment.
Already have an account? Log in
