Written for Web site administrators, developers, and end users, this book is a readable, real-world guide to securing your Web site with the latest in security technology, techniques, and tools. Lincoln D. Stein, keeper of the official Web Security FAQ, addresses your most pressing concerns and tells you exactly what you need to know to make your site more secure. He offers concise explanations of essential theory; helps you analyze and evaluate the risks that threaten your site and the privacy of your clients; and provides concrete, step-by-step solutions, checklists of do's and don'ts, on-line and off-line resources, and hardware and software tools that guard your site against security breaches.
Web Security approaches the topic from three different points of view--protecting the end user's confidentiality and the integrity of his or her machine, protecting the Web site from intrusion and sabotage, and protecting both from third-party eavesdropping and tampering.
You will learn about
In addition, the book offers practical advice on configuring the operating system securely and eliminating unnecessary features that increase vulnerability. CGI scripts introduce many of the security problems that plague the Web, and this book shows how to avoid these breaches with safe CGI-scripting techniques. You will also learn how to avoid denial-of-service attacks and prevent LAN break-ins through the Web server.
After reading this book, you will have the practical knowledge you need to ensure that your Web site, and your clients' interests, are safe from attack.
Click below for Source Code related to this title:
1. What Is Web Security?
The Three Parts of Web Security.
The Layout of This Book.
I. DOCUMENT CONFIDENTIALITY.2. Basic Cryptography.
How Cryptography Works.
Public Key Cryptography.
Printed Resources.3. SSL, SET, and Digital Payment Systems.
Secure Sockets Layer.
SET and Other Digital Payment Systems.
SET and Other Digital Money Systems.
II. CLIENT-SIDE SECURITY.4. Using SSL.
SSL at Work.
Printed Resources.5. Active Content .
Bad by Design or Bad by Accident? .
Traditional Threats .
Helper Applications and Plug-Ins .
The Browser as a Security Hole.
What Can You Do?
Changing Active Content Settings.
Resources.6. Web Privacy.
What Web Surfing Reveals.
Advice for Users.
Advice for Webmasters.
III. SERVER-SIDE SECURITY.7. Server Security.
Why Are Websites Vulnerable?
Frequently Asked Questions about Web Server Security.
Overview: Steps to Securing a Website.
Online Resources.8. UNIX Web Servers.
Hardening a UNIX Web Server.
Configuring the Web Server.
Monitor the Integrity of System Files and Binaries.
Back Up Your System.
Printed Resources.9. Windows NT Web Servers.
NT Security Concepts.
Windows NT Security Risks.
Securing a Windows NT Web Server.
Configuring the Web Server.
Printed Resources.10. Access Control.
Types of Access Control.
Access Control Based on IP Address or Host Name.
Access Control Based on User Name and Password.
Other Types of Access Control.
Access Control and CGI Scripts.
Online Resources.11. Encryption and Certificate-Based Access Control.
SSL-Enabled Web Servers.
Using Client Certificates for Access Control.
Using Client Certificates for Web Server Access Control.
Becoming Your Own Certifying Authority.
Printed Resources.12. Safe CGI Scripting.
Introduction to CGI Scripts and Server Modules.
Common Failure Modes.
Safe Scripting in Perl.
Printed Resources.13. Remote Authoring and Administration.
Degrees of Trust.
Controlling Access to the Web Server Host.
Remote Authoring Via FTP.
The HTTP PUT Protocol.
An Upload Staging Area.
Administering the Web Server Remotely.
Access to the Server for Web Developers.
Printed Resources.14. Web Servers and Firewalls.
What Is a Firewall?
Selecting a Firewall System.
Configuring a Firewall.
Automatic Proxy Configuration for Browsers.
Examining Firewall Logs for Signs of Server Compromise.
This is the "how not to shoot yourself in the foot" book about Web security. Enough theory to be interesting, but not so much that it gets dry and academic. Enough war stories to be fun, but not so many that they overwhelm the rest. No political agenda. No favoritism. You'll find here nothing but practical, commonsense advice for sidestepping the hoard of little gotchas that currently plague the Web, plus you'll find a framework for deciding for yourself how to handle all the gotchas that are yet to be.
Who is this book for? The first third of the book deals with problems that are relevant to anyone who uses the Web: privacy threats, the potential of the Web to spread viruses and other malicious software, the practice and pitfalls of electronic commerce. The remainder gives advice directed to Webmasters, system administrators, system security officers, and others who worry that their organizations' Web sites might be broken into or that their local area network can be compromised by nasty stuff brought in by their employees' Web surfing. If you already run a Web site, you'll want to read this book through. If you're a casual Web surfer, read the first part now and save the rest for later. If current trends continue, everyone will have a Web site and will have to worry about keeping it safe.
Web Security: A Step-by-Step Reference Guide began life about two years ago as the World Wide Web Security FAQ. I was concerned that new Web sites were going up at an amazing rate, with little appreciation for the security implications. I was dismayed that much of the advice being dispensed was incomplete or simply misinformed. So I put together 30 or so frequently asked questions (with answers) to advise Webmasters on how to keep their sites safe from attack by unwanted intruders, and I posted it on my Web site. Over a period of months, the FAQ grew considerably as readers mailed in requests for more information, suggestions, and in some cases contributed their own questions and answers. To the original sections on server-side security, I added sections dealing with client-side (browser) security, privacy issues, sections on cryptography and digital money, and an ever-growing list of security holes in specific pieces of software. In 1996, the first of an epidemic of Web site break-ins shook the Web; in its aftermath, the number of "hits" on the FAQ grew tremendously. The FAQ is now mirrored on five continents and has been translated into Russian, Italian, and Chinese.
When my editor initially suggested I turn the FAQ into a book, I was skeptical. First of all, the information was already on line. Second, the Web is changing so rapidly that any book on security issues is out of date by the time it hits the shelves. Finally, the whole FAQ was less than 50 typeset pages and I was dubious that it could be bulked up into a full-length book. To the first two objections, my editor responded that printed books and the Web are complementary. Printed books provide depth and comprehensiveness. The Web provides vast breadth and information that is always (we hope) up to date. As for my last objection, the weighty answer to that is in your hands.
At the MIT Genome Center, many thanks to Lois Bennett and Susan Alderman, two tirelessly cheerful system administrators who never seemed to mind my turning the Web site and LAN into a laboratory bench for every new scheme I wanted to try out. I gravely promise to them that I will never again rip out all the server software and replace it with "new and improved" code at the start of a four-day weekend.
At Addison Wesley Longman, I am indebted to Carol Long, my first editor and the one who convinced me to launch this project, to Karen Gettman, who took over the project when Carol's career took her elsewhere, and to Mary Harrington, who kept everything from unraveling during the transition. Thanks also to Marilyn Rash, who coordinated the production effort.
Last, many thanks to Jean Siao, who blinked not an eye as her Macintosh was slowly swallowed by tangled mats of network cabling and spare parts. Yes, you can play SimCity now without fear of electrocution.Nanjing