Open ubergeek42 opened 3 months ago
Confirmed, everyone in our company has this setting enabled via the GUI (default) but CriticalUpdateInstall
is unset. Given how widespread this is, my guess is it's not a "broken" state. Drata should modify their agent to assume unset == enabled.
We are hitting this as well at my company.
Please contact our support team as we have a workaround command for this specific issue on MacOS.
I'm not sure what went wrong, but this query was not returning the proper information on my Sonoma 14.6.1 machine.
https://github.com/drata/drata-agent/blob/e04e0c16c799cd058b23096e02a56195a30592ac/src/main/services/system-query/macos-system-query.service.ts#L124-L127
I installed osquery and ran the query manually to see what it returned:
Hmm, no
CriticalUpdateInstall
response. Querying the first plist directly returned:So it's not a query issue. I then went and toggle on and off all the checkboxes in system settings related to updates, then ran the above query again.
Hey, look at that, CriticalUpdateInstall is present now, and the Drata check is passing (it had started failing a few days ago, probably related to the new compliance check for gatekeeper/xprotect).
I unfortunately did not check the other plist files to see what they contained, and I'm not sure how to get it into the broken state my machine was in (I suspect OS upgrades and never touching the settings directly). But at least it seems that looking for
CriticalUpdateInstall
is not a true reflection of whether the functionality is actually enabled or not.