{"id":58186,"date":"2022-01-18T11:00:00","date_gmt":"2022-01-18T16:00:00","guid":{"rendered":"https:\/\/jumpcloud.com\/?p=58186"},"modified":"2024-02-20T18:43:16","modified_gmt":"2024-02-20T23:43:16","slug":"linux-lock-screen-policy","status":"publish","type":"post","link":"https:\/\/jumpcloud.com\/blog\/linux-lock-screen-policy","title":{"rendered":"Linux Lock Screen Policy Enables Consistent Device Governance"},"content":{"rendered":"\n

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

The policy is a free addition to the JumpCloud platform, delivering consistent cross-OS governance from a centralized directory. IT admins would otherwise have to configure settings on a 1-to-1 basis using the Linux settings panel, implementing a plug-in, or remembering to use the CLI to force a device lock security command. JumpCloud\u2019s approach delivers security at scale, saving time and money.<\/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

How Do I Set Up a Lock Screen Policy for Linux?<\/h2>\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