The Mindset
Remote access on Windows matters in two directions:- Getting in — RDP, WinRM, SMB, and PsExec are how you move to and between Windows hosts using credentials you’ve found
- What you get once you’re in — the type of session (interactive vs non-interactive) determines whether credentials are cached in memory for you to steal
RDP — Remote Desktop Protocol
RDP gives you a full graphical desktop session. It listens on TCP 3389 by default. To use it you need valid credentials and the account must be in the Remote Desktop Users group (or be an admin).Connecting from Linux
Checking if RDP Is Available
WinRM — Windows Remote Management
WinRM is the protocol behind PowerShell Remoting. It listens on TCP 5985 (HTTP) and 5986 (HTTPS). The account needs to be in the Remote Management Users group or be an admin.Connecting from Linux
From Windows (PowerShell Remoting)
Checking if WinRM Is Available
PsExec — Remote Execution via SMB
PsExec (Sysinternals) executes commands on a remote host over SMB (TCP 445). It’s the classic admin-credential-to-SYSTEM-shell tool.-s flag runs as SYSTEM. PsExec needs admin credentials on the target because it creates and starts a service remotely — which also makes it noisy and easily detected.
Interactive vs Non-Interactive Sessions
This is the concept that ties credential theft together. Windows logon types determine whether credentials are cached in memory.
Why this matters for you:
- An admin who RDPs in (interactive) leaves dumpable credentials in LSASS — wait for it, then dump
- Someone connecting over SMB or PsExec (network logon) typically does not leave reusable credentials behind
- Service accounts run continuously and their credentials sit in LSASS the whole time
Service Accounts
Service accounts run services and scheduled tasks. They’re worth understanding because they often have elevated privileges and their credentials persist in memory.Next: SMB & Network Shares — enumerating shares, mounting them, and the permission layers that decide what you can reach.