Explanation of three measures to protect IS Server

Most websites are designed to provide visitors with instant access to information in the most acceptable way. By marking security policies for IIS server security levels and availability, the network administrator can easily deploy various software tools on different operating systems.

Set a complex password for the IIS server:

I recently entered the classroom and found many possible hackers from the event viewer. He or she entered the lab with a domain structure deep enough to run password cracking tools on any user. If a user uses a weak password (such as "password" or changeme "or any dictionary word), hackers can quickly and easily intrude into these user accounts.

Reduce/exclude sharing on the IIS server:

If the network administrator is the only person with write permissions on the IIS server, there is no reason to make any sharing exist. Sharing is the greatest temptation for hackers. In addition, by running a simple cyclic batch processing file, hackers can view an IP address list and use the \ command to find the sharing of Everyone/full control permissions.

Disable NetBIOS in the TCP/IP protocol on the IIS server:

This is cruel. Many users want to access the IIS server through the UNC path name. As NETBIOS is disabled, they cannot do so. On the other hand, as NETBIOS is disabled, hackers cannot view resources on your LAN. This is a double-edged sword. If the network administrator deploys this tool, the next step is to educate Web users how to publish information when NETBIOS fails.

Last tip: log on to your IIS server and run netstat-an on the command line. Observe how many IP addresses are trying to establish a connection with your port, and then you will have a lot of research and research to do.