Force logoff of user during isolation of endpoint

[Noe.ortega]

Is there a way to force logoff of user during isolation of endpoint?  Want to make sure that if computer is infected, it prevents user from logging back in to computer.

[neelrohit · Accepted solution]

Hi @Noe.ortega ,

Thank you for writing to live community. 

Though there is no direct or automated way of doing this. However, if you have Cortex XDR Pro Per Endpoint license, you can technically do the following to achieve the objective from preventing user to log back in or system shutdown:

1. Run live terminal to run net user commands to delete username.
2. Run live terminal to run net user commands to change the user password from the system. If it is a domain user, then you can deactivate the user from AD and run shutdown /s command to shutdown the system.
3. Run endpoint scripts for the 1 and 2 using the script execution option.

I am sure live terminal would be an easy find, so guiding on scripts part as below:

1. Go to Action center> Agent Script Library.
2. You should be able to find a pre-defined script for execute commands
3. Enter your command from the above listed options( net commands for user based actions or shutdown /s command to shutdown the system)
4. Wait for script to execute.

There is also another way of automating this, and that is by automation rules. You can create automation rules for a specific type of incident generated (for eg ransomware activity for a specific known malicious SHA256 or some malicious vectors), then you can create one sequence for isolating the endpoint and other sequence could be to run custom endpoint script to perform the same set of activities as mentioned above.

Hope this helps.

Please mark the response as "Accept as Solution" if it answers your query.

[RoneyRajan123]

Thank you so much Neel for providing us the solution. Appreciating your efforts and Knowledge.

[neelrohit]

Just to add to the above @Noe.ortega , the solution suggested also assumes that you have collected all forensic data and memory artefacts for investigation before you shut the endpoint down as all the memory artefacts would be deleted after reboot.

You can attempt to restrict user logins if needed for the endpoints by restricting groups.: https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/restrict-use-one-domain-user-...