Event banner
AMA: Device Health Attestation - security benefits and integrations
Event Ended
Thursday, Oct 27, 2022, 11:00 AM PDTEvent details
Ensuring that a platform is healthy and trustworthy is a fundamental vertical in today’s zero trust approach, and this has become one of the keys focuses of recent times. Pre-OS boot continues to rem...
Heather_Poulsen
Updated Dec 27, 2024
Ali11CH
Oct 27, 2022Iron Contributor
I hear it said to apply compliance policies to Users (or am i picking that up wrong), however if in the case of Windows compliance policy applied to Users makes devices non compliant unless a user has logged on.
The device is non compliant because there is no compliance policy assinged to it.
Great session by the way.
Oct 27, 2022
compliance policies and the devices or user targeting... always a nice topic and fun when you end up with a non compliant device because of the the system account
https://call4cloud.nl/2021/06/blood-sweat-and-built-in-compliance-policies/
- Ali11CHOct 27, 2022Iron ContributorThanks Rudy, That is a great in depth view on the compliance policies. We used to deploy our Windows compliance policy to All Users but found that many devices were non-compliant due to the Has compliance policy assigned being non compliant. We have now deployed it to devices and the non-compliance has dramatically reduced. (The bulk of our devices are multi user (Education) with only staff devices being assinged a Primary User. The biggest cause of non-compliance we have now is the "is Active" setting.
- DanielRatliffOct 27, 2022Brass ContributorIt gets even more fun when you want to validate compliance before sending device to user. https://twitter.com/PotentEngineer/status/1582740457117085696