dcsimg

Before, During and After Patch Tuesday: A Survival Guide

  • Before, During and After Patch Tuesday: A Survival Guide-
    Before you can implement any patches, you have to know what you’re patching. Figure out what systems you’re running on what machines. Categorize everything to make it easier to understand later. Identify the critical systems based on the functions performed, assets housed in the system and their vulnerability to attack.

1 | 2 | 3 | 4 | 5 | 6 | 7

Before, During and After Patch Tuesday: A Survival Guide

  • 1 | 2 | 3 | 4 | 5 | 6 | 7
  • Before, During and After Patch Tuesday: A Survival Guide-2
    Before you can implement any patches, you have to know what you’re patching. Figure out what systems you’re running on what machines. Categorize everything to make it easier to understand later. Identify the critical systems based on the functions performed, assets housed in the system and their vulnerability to attack.

It’s been said that there are only two types of companies left in the world: those who know they’ve been hacked and those who don’t. We have to hope that there’s still a third group: those who have not been hacked. You can be sure those who belong to the third group are those who are rigorously implementing security features and, more importantly, keeping them updated.

Patching is not a highlight of the job, but it is a key – some might even say the key – to mitigating risk to your system and remediating vulnerabilities. Despite its importance, it is easy to let it fall by the wayside. To help make patching easier, Paul Henry, security and forensic analyst at Lumension, has come up with some simple tips to help your Patch Tuesday go by a little smoother and keep your systems up to date.