Secure Access to network resources
This tip, excerpted from InformIT, is derived from Chapter 14 of Roberta Bragg's book, MCSE Windows 2000 Network Security Design Training Guide,
To provide secure access from public networks to your private resources, you may want to determine the purpose of the access. Is it to allow the public access to your organization's public Web site? Do you want to exchange email with other companies via the Internet? Do you have databases to share with trusted partners? Are you engaging in business-to-business e-commerce?
To secure resources, use DACLs [Directory Access Control Lists] and auditing. Reduce user accounts on the exposed machines to the defaults. Protect these accounts with complex passwords. Use the "no access/no time/no where" practice on the Guest account. This practice makes sure that the Guest account is disabled but doesn?t rely on it. It does not let one little option stand between a secure network and one that can easily be penetrated. To lock down the Guest account, just follow these few extra steps:
- Change the permitted logon hours to none by selecting all hours in the GUI and marking them not allowed. Now the Guest account has no hours during which it can log on.
- Change the permission to log on from the following workstation to limit allowable workstation to the name of some workstation that does not exist. Because the workstation does not exist, there is no workstation the Guest account can use to log on.
- Choose an extremely complex password. The default is that the Guest account has no password whatsoever.
- Rename the Guest account. Set security templates accordingly and apply them using Group Policy.
To read more of this tip, click over to InformIT. You have to register, but registration is free.
To learn more about MCSE Windows 2000 Network Security Design Training Guide, or to buy this book, click here.
This was first published in February 2001