Every operating system should have security controls deployed, and Linux is no exception. Having a lock screen policy<\/a> is even more of a consideration with a remote workforce where team members could be using a local coffee shop or other unsecured locations as an \u201coffice,\u201d which increases the odds that bad actors could obtain physical access to devices. JumpCloud has created an easy-to-deploy policy to configure lock screen settings for Linux throughout your fleet, providing consistent governance and a scalable method for a secure OS configuration.<\/p>\n\n\n\n
Policies can be bound to a defined Linux device group<\/a> that will immediately deploy changes through a point-and-click management interface. Other pre-configured Linux policies<\/a> can be found by searching for \u201cLinux.\u201d The JumpCloud PowerShell module can also execute custom commands<\/a> with Sudo device access, extending what\u2019s possible through the platform.<\/p>\n\n\n\n
Setting up the lock screen policy for Linux is simple, but first verify whether you already have a lock screen policy established for your Windows devices in JumpCloud\u2019s Policy Management. The existing policy name<\/strong> must first be changed from the default to something novel <\/strong>\u2014<\/strong> e.g., \u201clock screen Windows\u201d <\/strong>\u2014<\/strong> to avoid an error.<\/strong> There\u2019s a text field underneath the heading \u201cPolicy Name.\u201d You may then proceed to the following steps once that change has been made, if it\u2019s required.<\/p>\n\n\n\n
IT Garage – How to do a Linux Lockscreen YT – jumpcloud-1<\/a><\/p>\n\n\n\n
Try JumpCloud\u2019s Policy Management feature for Linux for easy, scalable deployment of security controls. New users may try the platform for free<\/a> for 10 devices and users with complimentary 24×7-365 chat support for the initial 10 days following your account creation.<\/p>\n","protected":false},"excerpt":{"rendered":"