Also, what technical information do you need from these people to help you with your testing? Information like IP addresses, specific production servers, Windows user accounts and passwords, and locations are necessary items to have. They may also be able to tell you which systems are critical for production and may be sensitive to the wear and tear of security testing. Bonus: When you get others involved in this capacity, they're more likely to help you when trouble arises.
Setting your Windows security assessment expectations
Step 1: Determine the business goals
Step 2: Get input and information from others
Step 3: Let everyone know that problems will likely occur
Step 4: Let your testing be known and keep people in the loop
Step 5: Report what happened
About the author: Kevin Beaver is an independent information security consultant, speaker and expert witness with Atlanta-based Principle Logic LLC. He has more than 19 years of experience in IT and specializes in performing information security assessments involving compliance and IT governance. Kevin has authored/co-authored six books on information security including Hacking For Dummies and Hacking Wireless Networks For Dummies (Wiley) as well as The Practical Guide to HIPAA Privacy and Security Compliance (Auerbach). He also created the Security On Wheels series of audiobooks. Kevin can be reached at email@example.com.