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.

226<br />

Part IV: Hacking Operating Systems<br />

I recommend running authenticated scans as a regular local or domain user<br />

and as an administrator or any other user type you might have. This will<br />

show you who has access to what in the event that a vulnerability is present.<br />

You’ll likely be surprised to find out that a large portion of vulnerabilities,<br />

such as those listed in Figure 11-21, are accessible via a standard user<br />

account. You don’t necessarily need to run authenticated scans every time<br />

you test for security flaws, but doing so at least once or twice per year is not<br />

a bad idea.<br />

You can also use Microsoft Baseline Security Analyzer (MBSA) to check for<br />

basic vulnerabilities and missing patches. MBSA is a free utility from Microsoft<br />

that you can download at www.microsoft.com/technet/security/tools/<br />

mbsahome.mspx. MBSA checks all Windows 2000 and later (Windows 8 is not<br />

yet supported) operating systems for missing patches. It also tests Windows,<br />

SQL Server, and IIS for basic security settings, such as weak passwords. You<br />

can use these tests to identify security weaknesses in your systems.<br />

With MBSA, you can scan either the local system you’re logged in to or<br />

computers across the network. One caveat: MBSA requires an administrator<br />

account on the local machines you’re scanning.

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

Saved successfully!

Ooh no, something went wrong!