Win2K Internet Server Security Building Guide (E) (IIS article)

iis| Security | After the server completes these tasks, it can be said that the server is a "quasi-Internet server". The reason for saying "yes" is that the following two important supplementary programmes are needed:

1, the establishment of audit routine procedures

Before the site is open to the outside, we must configure an audit program for this server to determine in a timely and comprehensive manner whether the server is under attack or threat. Log file is like a site's ears, do not let it become a device, every day to schedule a certain amount of time to view the log, check whether there are unusual activities occur. Also, some business tools can be used to collect and collate related log information conveniently, timely, or regularly, with a view to checking them more effectively.

The following are the events that must be focused on:

Failed logins
Failed file and object access
Use of failed user rights
Failed security Policy modifications
Failed user and Group Policy modifications

Here are the events to be concerned about:

All access to scripts and the bin folder
All folders that contain Web publishing files

2. Data protection

It is also important to protect data that is exposed to the Internet on the server. In addition to setting the appropriate permissions, establishing a formal backup strategy, regular tape backup is necessary. The backup strategy should determine the following:

Who is responsible for backup of data and server configuration?
How often do you make a backup?
Where is the default placement location for backup storage media?
Who has the right to restore system data?
Is there a copy of the backup data outside the site?
Who is responsible for maintaining copies of backup data outside the site?

With this in place, you need to identify backup locations and backup methods further:

In most cases, a local backup is better than a network backup because there is no need to establish a network connection when performing a backup.
When the system is installed, the first thing to do is to make a full backup of the server.
Determine the frequency and type of backup. Do you make a backup every day? Is the daily backup a full, incremental, or differential backup?

Four, the conclusion above discusses in detail the IIS Security Configuration Guidance section that uses Win2K and IIS5 to build secure Internet web sites, and if you look at IIS in strict accordance with these steps, you can say that you have basically managed to intercept intruders ' attacks from the "air part". Combined with the "Win2K Internet Server Security Building Guide (Win2K)", we can now say: "No matter the enemy from the ground or the air, you will be in our surveillance"!

However, I would also like to remind you that it is impossible to make a system that exists on a public basis completely immune from attack, and what you can do is to make the system as strong as possible and force attackers to search for other systems that are more vulnerable to attack. Oh, evasive, discard difficult from easy it!