I had the same thing come up on a recent scan and haven't yet had time to build a second security server for testing possible fixes, so if you do discover a procedure that fixes the problem without affecting functionality, I'd greatly appreciate you posting it here.
Thanks,
Geoff