Anybody have a best practice for spotting policies that are running out of control?
Occasionally we will find a mis-configured policy that runs every day or every week with no control. Short of spot inspecting policy logs, is there a way anyone knows of to find these kinds of errors?
Thanks.
-c
