In the Zip Console reports page, you're able to track your fleets' compliance over time. You may notice that for certain controls, compliance may change suddenly. We've outlined common reasons for sudden compliance changes below.
Changes in the OS Version Control or CrowdStrike Sensor Version Control
This is most likely due to a recent version release for macOS, Windows, or CrowdStrike. When a new version is released, devices will drop out of compliance. As devices update to the latest available versions, they will naturally move back into compliance over the next few days.
Changes in other controls
This is most likely due to a parameter or compliance framework change for a certain control. For instance, if you previously had screen lock set to 15 minutes, and changed the default to 10 minutes, devices will not be compliant until they update their screen lock policies (causing a sudden change). You can see the history of all changes made in your Zip Console in the audit log of the reports page.
Occasionally, the Zip team may also push changes that can impact your compliance. You can see the history of changes the Zip Console has pushed in our product updates page.