Book details of 'Privacy : What Developers and IT Professionals Should Know'

Title	Privacy : What Developers and IT Professionals Should Know
Author(s)	J. C. Cannon
ISBN	0321224094
Language	English
Published	September 2004
Publisher	Addison-Wesley Professional

---

Back to shelf Computer security
Back to shelf Privacy
Amazon.com info for Privacy : What Developers and IT Professionals Should Know

Score:

Vote for this book

The Virtual Bookcase Reviews of 'Privacy : What Developers and IT Professionals Should Know':

Reviewer Rob Slade wrote:
The preface states that this book should help people learn about privacy technologies. (The cover refines this: it contains what developers and information technology professionals should know.) Part one examines privacy for everyone. Chapter one is a vague review of privacy. A list of privacy related technologies is in chapter two. There is a brief look, in chapter three, at privacy lawsuits and legislation. Chapter four discusses privacy settings in Windows, including the metadata in Word files. Spam, and anti-spam technologies, are surveyed in chapter five. Privacy invasive technologies are examined in chapter six, concentrating on radio- frequency identity chips. Part two looks at privacy and the organization. Chapter seven suggests some corporate structures to do with security, such as having a chief privacy officer and a privacy council. A "Privacy Response Center" is recommended in chapter eight. (I thought they used to call this an "ombudsman" or something.) Part three concerns privacy factors for the developer. Chapter nine outlines the Platform for Privacy Preferences Project (P3P). Advice on developing "privacy aware" software programs is given in chapter ten, although most of it seems to be fairly standard system development methodology. A not-terribly-clear-or-helpful system of diagramming information flow to analyze privacy distribution is suggested in chapter eleven. (An effort to demonstrate a data flow diagrammatic approach to privacy chooses to put error data, administrative activities, and system settings inside the privacy boundary.) Chapter twelve attempts to give an example of how the foregoing three chapters would work in building an application. Some considerations for databases are discussed in chapter thirteen. Another attempt to present a privacy aware program is given in chapter fourteen. Rather oddly, chapter fifteen talks about technologies that protect intellectual property. It is very hard to say what this book is about. Some of part one is not bad, although hardly inspired. The corporate material, in part two, is turgid, and seemingly applicable only to the most massive of corporations. Part three's suggestions about privacy aware applications seem not only unhelpful but pointless, at least in terms of real privacy issues. copyright Robert M. Slade, 2005
Add my review for Privacy : What Developers and IT Professionals Should Know