@Grigory Emelianov Like so many other concepts (eg. Firewall, Disk Encryption), there is no one-size-fits-all way to track the concept of 'screenlock' across all of Linux. There are many different packages and utilities a distribution or variant of Linux might use to configure and manage when a device will require authorization after a period of inactivity. For example on Linux devices using Gnome, this setting may be configured via

gsettings

, but there is nothing to guarantee that this same device would not use something like

swaylock

instead. In order to reliably ascertain the configuration of screenlock in a reasonably diverse Linux ecosystem, an organization would need to decide on a set of acceptable pathways to configuring a screenlock policy on Linux devices, and then you would check for those specific items.

and what about windows?

see: https://osquery.slack.com/archives/C08V7KTJB/p1639494018254900

As Fritz alludes to, this is a surprisingly large question

update: based on fritz's feedback we decided just to focus on a specific use case for GNU, it solved the range of problems for now. Thanks

@Grigory Emelianov glad to hear you got something working for your environment, it's definitely a big problem to tackle and breaking it into more approachable pieces is the only reasonable way.