Huntress Managed CA Policies don't stay managed
in progress
J
Joel Biddle
I deployed a Huntress Managed CA Policy to my 365 tenant ([HUNTRESS] Block Downloads for Guest Users), then logged into the 365 tenant and manually changed settings on this policy (excluded 3 of the guest roles intended to be targeted), to test whether or not Huntress would revert my changes to bring the CA policy back into conformity with the Huntress recommendation. This did not happen.
My expectation is that a Huntress Managed CA policy will be managed by Huntress and kept in compliance with the Huntress standard. If I can "break" the policy manually directly in the tenant, and Huntress doesn't remediate that, then it's not truly managed.
Now I haven't tested this with other Huntress Managed CA Policies, so I don't know if this problem is unique to this specific Huntress Managed CA Policy.
But if Huntress isn't able to maintain conformity to this policy, then it isn't really managed.
Is it on the roadmap for the Huntress Managed CA Policies to revert back to compliant, if someone changes the policy within the tenant? It feels like the intention behind using a Huntress Managed CA Policy is to keep these policies to a known standard.
S
Scott Riley
marked this post as
in progress
Hey Joel, that is the expected behavior. We are in the process of getting this aligned correctly as part of our continued development of the CA management here. What you're seeing here is an Early Access limitation but we are definitely on this!
J
Joel Biddle
Scott Riley Thanks for the quick response!