000			03101cam a2200253 a 4500
008			100317s2002 inua b 001 0 eng
010			_a00105340
020			_a9781578702640
035			_a(Sirsi) u5198
040			_aEG-CaNU _c EG-CaNU _d EG-CaNU
042			_ancode
082	0	4	_a005.8 _2 22
100	1		_aBarman, Scott. _910392
245	1	0	_aWriting information security policies / _c Scott Barman.
260			_aIndianapolis, Ind. : _b New Riders, _c 2002.
300			_axviii, 216 p. : _b ill. ; _c 23 cm.
504			_aIncludes bibliographical references and index
505		0	_aWhat Information Security Policies Are -- Determining Your Policy Needs -- Information Security Responsibilities -- Physical Security -- Authentication and Network Security -- Internet Security Policies -- Email Security Policies -- Viruses, Worms, and Trojan Horses -- Encryption -- Software Development Policies -- Acceptable Use Policies -- Compliance and Enforcement -- The Policy Review Process --
520			_aAnnotation Learn how to protect your assets by starting with a good security policy. Written in a clear, easy-to-understand form that management can understand, without insulting the intelligence of the technical reader. Great foundational reference on security and the policy considerations that must be understood by everyone concerned with information security. Full of practical information on the current state of information security without being specific to a particular vendor. Almost every book on network security talks about developing a "security policy" as part of the security planning process. A good security policy should be the basis for every successful security program, yet over 60-percent of companies do not have policies or have policies that are out of 20011112. Those references that do talk about security policies provide little information on how to actually prepare one. Fewer still help you develop and implement a good policy document that evolves with your evolving security needs. Writing Information Security Polices will help anyone involved in company seurity write a policy that can be both implemented and updated as needed, weather involved in the management or actual technical side of the business. Scott Barman is a systems analyst for a major nonprofit research organization specializing in government information technologies. He has been involved with information security for almost 20 years, dealing with the evolution of systems and their security requirements. Since the explosion of the Internet, he has focused on security and policy development for many organizations in the Washington, D.C. area. Barman has been an instructor for George Washington University in the Client/Server and UNIX/C Certification Programs. Currently, he is a candidate for the Master of Information Systems Management at Carnegie Mellon University with a concentration in Information Security Managemen
650		0	_aComputer security. _910393
650		0	_aComputer security _x Management. _910394
650		0	_aData protection. _910395
596			_a1
999			_c4203 _d4203