Page 7 - index

You must always assess your post-patch status by running a comprehensive report that tells
you which computers did and did not install the updates, those that rebooted, failed to
reboot, etc.

10. Document and repeat
The complexity of the patch process differs depending on your organization’s size and
business requirements, but simplifying it is always a good idea.

To do so, document the entire process following every successful patch deployment, which
will simplify and streamline subsequent patches.

Following these steps to establish or streamline an effective patch management process can help
you ensure you’re able to answer with confidence the next time you are asked how regularly you’re
performing security updates, how quickly you can react to an emergency patch and how effective
your overall process is.

Of course, even more important is that you can have confidence your infrastructure is safe from
attack and your organization will be free of the hefty non-compliance related fines that could come
from unpatched software.

And if you’re wondering how to best tackle these steps, remember that patch management tools
can help automate them, relieving the burden on you to carry out each step manually.

About the Author

Naren Vaideeswaran, Product Marketing Manager, Security, SolarWinds

Naren Vaideeswaran is a product marketing manager at SolarWinds for the
company’s security portfolio. A technology enthusiast, he has worked in the
IT and security industries for over a decade in both technical and marketing
roles.

7 Cyber Warnings E-Magazine – September 2015 Edition
Copyright © Cyber Defense Magazine, All rights reserved worldwide