oh yeah, my example query was just showing more info for debugging purposes.
SELECT 1 FROM processes WHERE NOT EXISTS (SELECT name from processes WHERE name = "Google Chrome") LIMIT 1;
from your perspective ?
09/06/2022, 6:45 PM
I cleaned up the example a little more 🙂
09/06/2022, 6:46 PM
perfect - thanks!!
09/06/2022, 6:53 PM
Since the whole "Double positive to prove a negative" thing is a little confusing....IF the policy is "Google Chrome is not running" and you want a pass when it is not or a fail if it is, that's the right query.
09/06/2022, 6:57 PM
yes, just for full clarity I'm trying to create a policy that passes if your version of Chrome is up to date OR google chrome isn't running (because you likely don't use it)
09/06/2022, 6:58 PM
Thanks! Can never be too careful with twisty logic.
I actually did look at that one and cribbed a little from it.
Our issue is that we deliver all laptops with Google Chrome (and Firefox) - so users have a choice.. but I don't want your policy to fail if your chrome is out of date but you aren't actively using Chrome
09/06/2022, 7:12 PM
Totally makes sense. I think you're querying the right thing here, assuming that you've got an integration or webhook set up for your policies so that you aren't just relying on whether they were running Chrome when the most recent policy check happened. Though if people are using Chrome it's usually always running, so that may just be a made up concern 😃
09/06/2022, 7:13 PM
you are following my thoughts exactly. The query isn't perfect but I'm most likely to catch "active" Chrome users with out of date browsers
do you know of any way to dynamically grab the latest version in these queries?
I was thinking of maybe using the API for Fleet and the API for endoflife.date and modifying the policy queries that way
but maybe there is an easier way
09/06/2022, 7:16 PM
I feel like I ran across someone before that was using a cron job to periodically query endoflife and update the policy with either the API or