So, once again Microsoft's Patch Tuesday is breaking all records and we're in a quandry. We can either accept the risk of applying 28 untested (by us) patches to fix 49 vulnerabilities or we can accept the security risks of not applying the patches. Both choices are difficult but in the end, I'm always going to accept the "upgrade risk" versus the "security risk". Gone are the old days So, why don't we just delay it a bit and test it all out? In the old days (and certainly in a much larger company) this would have been possible but right now, we only have a small IT department and a constantly shifting Standard Operating Environment (SOE). As I've said before - there is no longer such a thing as a SOE in today's computing environment. We start out with an idea of the software to be loaded and the options and location in which it gets loaded, that's standard. Then, all the applications upgrade themselves at different intervals and sudde