windows server 2012 remote desktop lock screen

Windows server 2012 remote desktop lock screen how to#
Windows server 2012 remote desktop lock screen software#

The user will not be able to run prohibited programs, but the fact that they are attempting to run them should raise a red flag for action.

Using technologies like AppLocker can help greatly in this situation. If a user suddenly starts to use programs you wouldn't normally see them running, it could be an indicator of compromise. Especially when you have users who can stay in disconnected or idle states for long periods of time, you need to monitor what is being executed so that you can identify a potentially compromised session. It's also important to build a profile of what is executed within a user session.

They may need to initiate long-running data tasks that could take hours or even days to complete. But also, potentially identify users who may have real business reasons to operate in this fashion. If you have users who routinely keep virtual sessions logged in for very long periods of time, begin to educate them in the importance of logging off at the end of a session. Now, this isn't to say that you should work around an insecure method-for instance, users leaving sessions connected for weeks on end just so they can reconnect to them is not desirable from a security or indeed from a financial standpoint-but you need to understand their behavior so you can adapt it if necessary. You need to routinely assess and map out how your users are operating to provide the right security settings.

Windows server 2012 remote desktop lock screen software#

Software monitoring of some sort is important to help you understand this, but so is actively seeing how your users make use of the platforms they are provided. Are they leaving applications running active tasks for long periods of time? Do they open RDSH connections and then lock them before changing locations? Do they often rely on reconnecting to RDSH or VDI sessions so that they can 'pick up where they left off?' Do they actually log out at the end of the day?

This is another example of trying to strike a balance between user experience and security-how do you manage to provide an acceptable level of protection yet ensure that users don't get interrupted in their work processes? User profiling ^įirst, you need to understand your users' practices. This becomes even trickier in remote working scenarios, as you don't have any control of where the user is connecting from-it could be any public place with a WIFI connection.

Windows server 2012 remote desktop lock screen how to#

There are many aspects to this 'low-hanging fruit,' but one of the more difficult ones to cover is how to lock a user's session after inactivity to ensure an attacker can't take advantage of an unattended workstation. It is very important to pay attention to the basic tenets of security to restrict an intruder's ability to penetrate deeper into the infrastructure. Missing basic security checkboxes can often result in data exfiltration, lateral movement, and privilege escalation, allowing attackers to gain a further foothold into networks and increase the scope of the compromise. In any environment, but particularly so in RDSH or virtual desktop solutions, making sure that the 'low-hanging fruit' of security is picked off is particularly vital.