In simple words logon is a process of gaining access to local or remote systems using valid credentials. The user information is validated by Local Security Authority (LSA).
<aside>
❗ LSA is an ecosystem, a concept. The associated operating system-level process we will see is called LSASS.exe
</aside>
If successful, a logon session (in dashed pink) will be created with which an Access Token will be associated.
When I am logged onto a machine with an interactive session and I run the runas
command with another user's credentials, the moment they pass the validation stage a new interactive session is opened for a different user:
However, when the runas
command is run with the parameter \\netonly
, a new logon session is created but the identity for accessing local resources remains the same (in the example prod\user1) but if I need to access remote resources, I will use the user specified in the runas
command (in the example you can see that you can do the dir of C$ on the Domain Controller since for remote resources we are for all intents and purposes the Administrator user):
Classic RDP