RDP guesses, then a logon that worked
Use Get-WinEvent on an exported Security log to count failed RDP logons, find the source, and spot the account that finally got in with administrator-level privileges.
- Terminal mission
- Beginner
- 4 questions
- 0 of 4 solved
Your goal
Your goalCount failed Remote Desktop logons, find their source, and the account that finally got in.
FS-01 is a file server with RDP open to the internet by mistake. You are on a PowerShell prompt with its Security log loaded.
Event 4625 is a failed logon and 4624 a successful one. Logon type 10 means Remote Desktop. 4672 right after a 4624 means the new session got special privileges. Get-WinEvent returns the newest events first.
What’s on screen
- Briefing
- the story: what happened and what evidence you were handed.
- Terminal
- the dark box. It is a pretend PowerShell window that runs in your browser. Type a command and press Enter. Nothing you type touches a real system.
- Walkthrough
- the numbered path. Each step says what to type and what you should see. Hints open one at a time.
- Answer boxes
- under each question step. Type what you found and press Check.
Words to know
- RDP
- Remote Desktop Protocol, remote login to Windows
- IP
- Internet Protocol address, the number that identifies a machine on a network
FS-01 · Windows event logs
Type help for the command list and objectives for your tasks. Everything runs in this browser.
Up and down arrows walk your history. Ctrl+L clears the screen. Try help, ls, and objectives.
Read first
More in Windows event logs
The whole walkthrough
Every step in order: 293 words, about 2 min. It gives away every answer, so try the steps first.