Step 1: Map your network |
 |
By Chip Andrews, Contributor
21 Mar 2005 | SearchSQLServer.com |
|
|
Prepare a set of IP address ranges to scan for SQL Server instances. The most important thing to remember is to never exclude IP addresses in the scan based on the assumption that SQL Servers should not be among them. Second, you should always plan to perform the scan from multiple directions where applicable.
For example, when scanning machines in a demilitarized zone (DMZ), be sure to scan from both the internal network and the Internet. Never assume that traffic coming from another direction is inherently safe. Finally, make sure the appropriate personnel are aware of your scans so you don't set off any alarms and unnecessarily force security administrators into a panic.
HOW TO PATCH SQL SERVER, PART 1
 Home: Introduction
Step 1: Map your network
Step 2: Perform an active scan
Step 3: Check for SQL registrations
Step 4: Probe remote services
Step 5: Probe for SSNetlib.dll versions
Step 6: Directly request version information
Go to: How to patch SQL Servers, part 2
| ABOUT THE AUTHOR: |
|
Chip Andrews, CISSP
Chip Andrews is the director of research and development for Special Ops Security Inc. and the founder of the SQLSecurity.com Web site, which focuses on Microsoft SQL Server security topics and issues. He is also the author of SQL Server Security.
Copyright 2005 TechTarget
|
|
|
|
|
|
