Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
Có một số cách để giữ cho các con mắt tò mò của một thu thập thông tin Web từ đào quá sâu vào trang web của bạn. Tuy nhiên, nhớ rằng một máy chủ Web được thiết kế để lưu trữ dữ liệu đó là có nghĩa là cho tiêu dùng công cộng. Mặc dù tất cả những bảo vệ tốt nhất, thông tin rò rỉ xảy ra | Protecting Yourself from Google Hackers Chapter 12 481 Web Server Safeguards There are several ways to keep the prying eyes of a Web crawler from digging too deeply into your site. However bear in mind that a Web server is designed to store data that is meant for public consumption. Despite all the best protections information leaks happen. If you re really concerned about keeping your sensitive information private keep it away from your public Web server. Move that data to an intranet or onto a specialized server that is dedicated to serving that information in a safe responsible policy-enforced manner. Don t get in the habit of splitting a public Web server into distinct roles based on access levels. It s too easy for a user to copy data from one file to another which could render some directory-based protection mechanisms useless. Likewise consider the implications of a public Web server system compromise. In a well thought out properly constructed environment the compromise of a public Web server only results in the compromise of public information. Proper access restrictions would prevent the attacker from bouncing from the Web server to any other machine making further infiltration of more sensitive information all the more difficult for the attacker. If sensitive information were stored alongside public information on a public Web server the compromise of that server could potentially compromise the more sensitive information as well. We ll begin by taking a look at some fairly simple measures that can be taken to lock down a Web server from within. These are general principles they re not meant to provide a complete solution but rather to highlight some of the common key areas of defense. We will not focus on any specific type of server but will look at suggestions that should be universal to any Web server. We will not delve into the specifics of protecting a Web application but rather we ll explore more common methods that have proven especially and .
