Technical support to change Windows 2003 network security settings
Windows 2003 Enhanced Security Configuration established a configuration for your server and for Microsoft Internet Explorer that decreases the exposé of your server to potential attacks that can occur through Web content and application scripts. As a result, some Web sites may not show or execute as projected.
This article describes to change Windows 2003 network security settings
The Windows Server 2003 Security Guide focus on providing a set of easy to understand guidance, tools, and templates to help secure Windows Server 2003 in many environments. While the product is very secure from the default installation, there are a number of security options that can be further configured base on specific requirements. This guidance not only provides recommendations, but also the background information on the risk that the setting is used to ease as well as the impact to an environment when the option is configured.
Network Mapping Software
Windows Server 2003 provides enhanced network security with support for standardized 802.1x protocols, an integrated public key infrastructure (PKI), password or certificate-based access, and other services. mutually, these create a more secure environment for doing business.
- Guest only
If 'Network access: Sharing and security model for local accounts' is set to 'Guest only', anybody connecting to the computer remotely will be given the similar level of access as the Guest account. They will not be able to execute any administrative tasks remotely.
If the computer is not joined to a area, this sharing and security model will allow shared folders to be accessed by everybody, with either 'full' or 'read-only' access. Access to shared folders can be restricted to users of a computer.
- Classic
If 'Network access: Sharing and security model for local accounts' is set to Classic, anybody linking to the computer remotely will be allocated a level of access according to their user recommendation on the remote computer.
If the computer is not linked to a domain, this sharing and security model will allow shared folders to be accessed either by everybody, or by specific users. If the file system is NTFS, file and folder permissions can give even better manage over shared resources
Windows 2003 member server
• Go to- Administrative Tools and select 'Local Security Policy.
• select 'Local Policies/ SecurityOptions/Network access: Sharing and security model for local accounts'
• enable:Define this policy setting:'
• select 'Classic - local users validate as themselves'
• click on'OK'.
Windows 2003 domain controller
• Go to- Administrative Tools and select 'Domain Controller Security Policy'
• Select 'Local Policies/Security Options/Network access: Sharing and security model for local accounts'
• click'Define this policy setting:'
• Select 'Classic - local users authenticate as themselves'
• Click on 'OK'.
In this article, we will go over options that you have as you maneuver through the Security Configuration Wizard, starting with the options to manipulate the security policies. We will also cover key areas that are target by the Wizard, Including services, Network security, Registry settings, Administration and other server responsibilities.
Getting to the Security Configuration Wizard
The Security Configuration Wizard is not installed by default after install Windows Server 2003. You will need to go to through the Add/Remove Windows Components menu in Control Panel to install the Wizard.
After the Wizard is installed, you access easily by going to the Administrative Tools menu off the Start Menu.
Security Configuration Wizard welcome screen
You should note the message that is highlighted with the yellow sign. The message indicates that the wizard will findout inbound ports that being used by this server. This requires all applications that use inbound ports running before you run the Wizard and create the security policy.
Working With Security Policies
Once you launch the Wizard, you will first prompted to make a decision about the security policy you going to be working with. You can create new policy, edit an existing policy, apply an existing policy, or rollback last applied policy.
You need to make initial decision as to what you need to do with security policy
Security policies are created as XML file;using the XML file extension. The default security policy storage location C:\Windows\Security\msscw\policies. You can provide a description in each security policy, which is extremely useful if you have a multitude of policies.
When you work with the security policy XML file, you won't be working with the file as a whole; you will be working with the file's different sections. These sections are organized and referenced within Security Configuration Wizard interface using a security configuration database structure. You can view the security configuration database using SCW Viewer.
Configuring the Security Policy
Once security configuration database is generated, you will work with the Security Configuration Wizard to make the security settings desired for server or group of servers. The Wizard will gently walk you through assortment of sections related to the roles, functions that the server is responsible for. The following is summary of the different sections that you will encounter that you configure the security policy.
Network Security - This section is designed for configure inbound ports using Windows Firewall. The configurations will based on the roles and administration options that were selected the previous section. You will also be able to restrict entering to ports and configure port traffic to be signed or encrypted using IPSec. The selection of ports are based on ports and applications that use specific ports.
Network Security controlled by configuring the ports on the server
Registry Settings - This section is designed to configure protocols used for communicate with computers on the network. Security for communication protocols isvery important due to legacy Windows operating systems requiring protocols that are vulnerable to password cracking and man-in-the-middle attacks. The key areas are targeted in this section include:
- SMB Security Signatures
- LDAP Signing
- Outbound Authentication Protocols
- Inbound Authentication Protocols