19.04.2013 Views

2KKUU7ita

2KKUU7ita

2KKUU7ita

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

In This Chapter<br />

Chapter 17<br />

Plugging Security Holes<br />

▶ Determining which vulnerabilities to address first<br />

▶ Patching your systems<br />

▶ Looking at security in a new light<br />

A fter you complete your tests, you want to head down the road to<br />

greater security. However, you found some security vulnerabilities.<br />

(I hope not too many serious ones, though!) Plugging these security holes<br />

before a hacker exploits them is going to require a little elbow grease. You<br />

need to come up with your game plan and decide which security vulnerabilities<br />

to address first. A few patches might be in order and possibly even<br />

some system hardening. You might want to reevaluate your network design<br />

and security infrastructure as well. I touch on some of the critical areas in<br />

this chapter. You might also want to refer to the fine book Network Security<br />

For Dummies by Chey Cobb. Chey does a great job of covering each of these<br />

topics in depth.<br />

Turning Your Reports into Action<br />

It might seem that the security vulnerability to address first would be obvious,<br />

but it’s often not black and white. When reviewing the vulnerabilities that<br />

you find, consider the following variables:<br />

✓ Whether the vulnerability can be fixed<br />

✓ How easy the vulnerability is to fix<br />

✓ How critical the vulnerable system is<br />

✓ Whether you can take the system offline to fix the problem<br />

✓ Time, money, and effort involved in purchasing new hardware or software<br />

or retooling business processes to plug the holes

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!