Enhanced descriptions from Syndetics:

Administrators, more technically savvy than their managers, have started to secure the networks in a way they see as appropriate. When management catches up to the notion that security is important, system administrators have already altered the goals and business practices. Although they may be grateful to these people for keeping the network secure, their efforts do not account for all assets and business requirements Finally, someone decides it is time to write a security policy. Management is told of the necessity of the policy document, and they support its development. A manager or administrator is assigned to the task and told to come up with something, and fast! Once security policies are written, they must be treated as living documents. As technology and business requirements change, the policy must be updated to reflect the new environment--at least one review per year. Additionally, policies must include provisions for security awareness and enforcement while not impeding corporate goals. This book serves as a guide to writing and maintaining these all-important security policies.

Table of contents provided by Syndetics

• I Starting the Policy Process (p. 1)
• 1 What Information Security Policies Are (p. 3)
• About Information Security Policies (p. 3)
• Why Policies Are Important (p. 4)
• When Policies Should Be Developed (p. 5)
• How Policies Should Be Developed (p. 6)
• Summary (p. 9)
• 2 Determining Your Policy Needs (p. 11)
• Identify What Is to Be Protected (p. 11)
• Identify From Whom It Is Being Protected (p. 14)
• Data Security Considerations (p. 15)
• Backups, Archival Storage, and Disposal of Data (p. 18)
• Intellectual Property Rights and Policies (p. 20)
• Incident Response and Forensics (p. 22)
• Summary (p. 24)
• 3 Information Security Responsibilities (p. 27)
• Management Responsibility (p. 27)
• Role of the Information Security Department (p. 31)
• Other Information Security Roles (p. 33)
• Understanding Security Management and Law Enforcement (p. 34)
• Information Security Awareness Training and Support (p. 36)
• Summary (p. 37)
• II Writing the Security Policies (p. 39)
• 4 Physical Security (p. 41)
• Computer Location and Facility Construction (p. 41)
• Facilities Access Controls (p. 45)
• Contingency Planning (p. 47)
• General Computer Systems Security (p. 48)
• Periodic System and Network Configuration Audits (p. 49)
• Staffing Considerations (p. 50)
• Summary (p. 51)
• 5 Authentication and Network Security (p. 53)
• Network Addressing and Architecture (p. 53)
• Network Access Control (p. 59)
• Login Security (p. 61)
• Passwords (p. 66)
• User Interface (p. 68)
• Access Controls (p. 70)
• Telecommuting and Remote Access (p. 70)
• Summary (p. 73)
• 6 Internet Security Policies (p. 77)
• Understanding the Door to the Internet (p. 78)
• Administrative Responsibilities (p. 85)
• User Responsibilities (p. 86)
• World Wide Web Policies (p. 89)
• Application Responsibilities (p. 94)
• VPNs, Extranets, Intranets, and Other Tunnels (p. 96)
• Modems and Other Backdoors (p. 96)
• Employing PKI and Other Controls (p. 98)
• Electronic Commerce (p. 98)
• Summary (p. 100)
• 7 Email Security Policies (p. 103)
• Rules for Using Email (p. 103)
• Administration of Email (p. 104)
• Use of Email for Confidential Communication (p. 107)
• Summary (p. 109)
• 8 Viruses, Worms, and Trojan Horses (p. 111)
• The Need for Protection (p. 111)
• Establishing the Type of Virus Protection (p. 113)
• Rules for Handling Third-Party Software (p. 114)
• User Involvement with Viruses (p. 115)
• Summary (p. 116)
• 9 Encryption (p. 117)
• Legal Issues (p. 118)
• Managing Encryption (p. 120)
• Handling Encryption and Encrypted Data (p. 121)
• Key Generation Considerations (p. 122)
• Key Management (p. 122)
• Summary (p. 125)
• 10 Software Development Policies (p. 129)
• Software Development Processes (p. 130)
• Testing and Documentation (p. 134)
• Revision Control and Configuration Management (p. 136)
• Third-Party Development (p. 138)
• Intellectual Property Issues (p. 140)
• Summary (p. 140)
• III Maintaining the Policies (p. 145)
• 11 Acceptable Use Policies (p. 147)
• Writing the AUP (p. 148)
• User Login Responsibilities (p. 149)
• Use of Systems and Network (p. 150)
• User Responsibilities (p. 150)
• Organization's Responsibilities and Disclosures (p. 151)
• Common-Sense Guidelines About Speech (p. 152)
• Summary (p. 153)
• 12 Compliance and Enforcement (p. 155)
• Testing and Effectiveness of the Policies (p. 156)
• Publishing and Notification Requirements of the Policies (p. 156)
• Monitoring, Controls, and Remedies (p. 157)
• Administrator's Responsibility (p. 160)
• Logging Considerations (p. 161)
• Reporting of Security Problems (p. 162)
• Considerations When Computer Crimes Are Committed (p. 165)
• Summary (p. 166)
• 13 The Policy Review Process (p. 169)
• Periodic Reviews of Policy Documents (p. 169)
• What the Policy Reviews Should Include (p. 171)
• The Review Committee (p. 172)
• Summary (p. 173)
• IV Appendixes (p. 175)
• A Glossary (p. 177)
• B Resources (p. 185)
• Incident Response Teams (p. 185)
• Other Incident Response Information (p. 186)
• Virus Protection (p. 186)
• Vendor-Specific Security Information (p. 187)
• Security Information Resources (p. 188)
• Security Publications (p. 188)
• Industry Consortia and Associations (p. 188)
• Hacker and "Underground" Organizations (p. 189)
• Health Insurance Portability and Accountability Act (p. 189)
• Survivability (p. 190)
• Cryptography Policies and Regulations (p. 190)
• Security Policy References (p. 191)
• C Sample Policies (p. 193)
• Sample Acceptable Use Policy (p. 195)
• Sample Email Security Policy (p. 197)
• Sample Administrative Policies (p. 199)
• Index (p. 203)

Author notes provided by Syndetics

Scott Barman is currently an information Security and Systems Architecture Analyst for The MITRE Corporation (http://www.mitre.org). He has been involved with information security for almost 20 years, nurturing the evolution of systems and their security requirements for commercial organizations and government agencies. Since the explosion of the Internet and prior to joining MITRE, he had focused on various areas of security and policy development for many organizations in the Washington, D.C. area. The inspiration for this book came from his SANS '99 presentation. He earned his undergraduate degree from the University of Georgia and a Masters of Information Systems Management from Carnegie Mellon University (http://www.mism.cmu.edu).

The reviewers contributed their considerable hands-on expertise to the entire development process for Writing Information Security Policies. As the book was being written, these dedicated professionals reviewed all the material for technical content, organization, and flow. Their feedback was critical to ensuring that Writing Information Security Policies fits our reader's need for the highest-quality technical information.

David Neilan has been working in the computer/network industry for over 10 years, the last six dealing primarily with network/Internet connectivity and security. From 1991 to 1995, he worked for Intergraph, dealing with graphics systems and networking. From 1995 to 1998, he was with Digital Equipment, working with DEC firewalls and network security. From 1998 to 2000, he was with Online Business Systems, doing LAN/WAN and Internet security. David is currently running a business, Security Technologies, in the network/security realm; he is working with local companies to enable and secure their networks. He is designing network infrastructures to support secure LAN/WAN connectivity for various companies utilizing Microsoft 2000 and Cisco products and the Internet to create secure Virtual Private Networks. David also has been beta testing Microsoft operating systems since Windows For Workgroups, WFW3.11, and has worked part-time as a technical editor on many Microsoft/networking/security books.

Larry Paccone is a Principal National/Systems Security Analyst at Logicon/TASC. As both a technical lead and project manager, he has worked in the Internet and network/systems security arena for more than eight years. He has been the technical lead for several network security projects supporting a government network/systems security research and development laboratory. Prior to that, Larry worked for five years at The Analytical Sciences Corporation (TASC) as a national security analyst assessing conventional military force structures. He has an M.S. in Information Systems, an M.A. in International Relations, and a B.A. in Political Science. He also has completed eight professional certifications in network and systems security, internetworking, wide area networking, Cisco routing/switching, and Windows NT.