- Amazon Student members save an additional 10% on Textbooks with promo code TEXTBOOK10. Enter code TEXTBOOK10 at checkout. Here's how (restrictions apply)
Privacy: What Developers and IT Professionals Should Know Paperback – Sep 21 2004
Special Offers and Product Promotions
No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
To get the free app, enter your e-mail address or mobile phone number.
From the Inside Flap
"Is it secret? Is it safe?"
Gandalf to Frodo Lord of the Rings, The Fellowship of the Ring
The movie Marathon Man contains a scene in which the protagonist is tied to a chair and being asked over and over again "Is it safe?" He doesn't know how to answer the question and starts to squirm when the interrogator takes out a set of dental tools and walks toward him. This is the discomfort that many consumers feel when considering whether to complete an online form or download software from the Internet. Not knowing whether it is safe to share your information or use technology can be frustrating. There should be no ambiguity when it comes to a person's safety. It should be clear what will happen to a person's data when clicking the Submit button on a form or dialog. You should be able to trust that the new software you installed on your computer won't take data from your computer and send it across the Internet.
When a dentist is looking in your mouth or a mechanic is looking under the hood of your car, do you wonder whether they are looking for their next Porsche payment or trip to Hawaii? Do you wish there were an easy way to trust their intentions? In the same manner, you probably wish there were an easy way to trust the privacy statement that is obtained from a Web site or the end-user license agreement from an application before you used them. You should not have to feel obliged to perform a Google search before trusting a company.
The term solutions, as used throughout this book, refers to applications, tools, software services, interactive Web pages, and any other products created with a programming or script language. I don't want anyone to think that I am focusing on only a specific type of technology or platform to provide answers to today's privacy issues.
This book will help you learn to use technologies that will help you protect your privacy and to build solutions that can help protect the privacy of others. More than that, you will learn to build your own privacy infrastructure to permit the creation of trustworthy software and services and help you respond effectively to privacy incidents.Disclaimer
I currently work at Microsoft in their Corporate Privacy Group. Most of what I know about privacy and much of the technology discussed in this book I learned while working there and with other groups at Microsoft during my six-year tenure. However, the opinions expressed in this book are entirely mine and the other contributors to this book, not those of Microsoft. Although many of the practices described in this book come from Microsoft practices, there are subtle differences between some of the practices described here and the ones followed at Microsoft. I even included descriptions of technology from companies other than Microsoft to give you a broader view of the privacy technologies that exist today.
My focus on Microsoft technologies in this book is not a statement that they are the only means or best means for developing privacy solutions; it is only indicative of the fact that I spent more than 15 years working on those technologies.
The information provided in this book should not be considered legal advice. Any practices that might affect the image of your company or that could expose you to litigation should not be implemented without consultation from your company's executive and legal departments.Organization of the Book
The book consists of three parts, each with its own specific focus. Although all readers will benefit from reading the entire book, some readers may want to concentrate on areas that are of greatest interest to them.
Part II is Privacy and the Organization. It gives instruction on how to build a privacy organization, which looks at selecting personnel, getting training, and evangelizing privacy throughout the company. This part also looks at building a privacy response center to respond to privacy issues that might arise in a company.
Chapters 4 through 9 discuss issues that are important to consumers in protecting their privacy online. Consumers will learn about ways to protect themselves from spam, how to use P3P, and about privacy-invasive technologies.
Part III is Privacy and the Developer. This part goes into more technical topics that will be of interest to developers building privacy-enhancing technologies and companies looking to include privacy awareness into the way products are built. The Platform for Privacy Preferences Project is discussed along with protecting database data. This part includes a couple of sample applications that provide instruction on how to use role-based access control to protect access to data based on the category of the data and the role of the user wanting to access the data.© Copyright Pearson Education. All rights reserved.
From the Back Cover
Praise for J.C. Cannon's Privacy
"A wonderful exploration of the multifaceted work being done to protect the privacy of users, clients, companies, customers, and everyone in between."
Peter Wayner, author of Translucent Databases
"Cannon provides an invaluable map to guide developers through the dark forest created by the collision of cutting-edge software development and personal privacy."
Eric Fredericksen, Sr. Software Engineer, PhD., Foundstone, Inc.
"Cannon's book is the most comprehensive work today on privacy for managers and developers. I cannot name any technical areas not covered. No practitioners should miss it."
Ray Lai, Principal Engineer, Sun Microsystems, Inc., co-author of Core Security Patterns and author of J2EE Platform Web Services
"Every developer should care deeply about privacy and this is the best book I've read on the subject. Get it, read it, and live it."
Keith Ballinger, Program Manager, Advanced Web Services, Microsoft
"J.C. Cannon's book demonstrates that information and communication technology can contribute in a significant way to restoring individual privacy and raises more awareness of the complexity and importance of this societal problem."
Dr. John J. Borking, Former Commissioner and Vice-President of the Dutch Data Protection Authority
"If you are planning, implementing, coding, or managing a Privacy campaign in your company or your personal computing, there is no more relevant reference. J.C. Cannon nails the issues."
Rick Kingslan, CISSP, Microsoft MVP-Windows Server: Directory Services and Right Management, West Corporation
"It's often been said that security is a process, not a product. Privacy is no different! Unlike other privacy books, J.C. Cannon's book has something valuable to convey to everyone involved in the privacy process, from executives to designers and developers, many of whom aren't thinking about privacy but should be."
Keith Brown, Co-founder of Pluralsight and author of The .NET Developer's Guide to Windows Security and Programming Windows Security
"J.C. Cannon's new book on electronic privacy is an important addition to the available works in this emerging field of study and practice. Through many humorous (and occasionally frightening) examples of privacy gone wrong, J.C. helps you better understand how to protect your privacy and how to build privacy awareness into your organization and its development process. Keenly illustrating both the pros and cons of various privacy-enhancing and potentially privacy-invading technologies, J.C.'s analysis is thorough and well-balanced. J.C. also explains many of the legal implications of electronic privacy policies and technologies, providing an invaluable domestic and international view."
Steve Riley, Product Manager, Security Business and Technology Unit, Windows Division, Microsoft
"Privacy concerns are pervasive in today's high-tech existence. The issues covered by this book should be among the foremost concerns of developers and technology management alike."
Len Sassaman, Security Architect, Anonymizer, Inc.
You're responsible for your customers' private information. If you betray their trust, it can destroy your business. Privacy policies are no longer enough. You must make sure your systems truly protect privacyand it isn't easy. That's where this book comes in.
J.C. Cannon, Microsoft's top privacy technology strategist, covers every facet of protecting customer privacy, both technical and organizational. You'll learn how to systematically build privacy safeguards into any application, Web site, or enterprise system, in any environment, on any platform. You'll discover the best practices for building business infrastructure and processes that protect customer privacy. You'll even learn how to help your customers work with you in protecting their own privacy. Coverage includes
- How privacy and security relateand why security isn't enough
- Understanding your legal obligations to protect privacy
- Contemporary privacy policies, privacy-invasive technologies, and privacy-enhancing solutions
- Auditing existing systems to identify privacy problem areas
- Protecting your organization against privacy intrusions
- Integrating privacy throughout the development process
- Developing privacy-aware applications: a complete sample application
- Building a team to promote customer privacy: staffing, training, evangelization, and quick-response
- Protecting data and databases via role-based access control
- Using Digital Rights Management to restrict customer information
- Privacy from the customer's standpoint: spam avoidance, P3P, and other tools and resources
Whether you're a manager, IT professional, developer, or security specialist, this book delivers all the information you need to protect your customersand your organization.
The accompanying CD-ROM provides sample privacy-enabling source code and additional privacy resources for developers and managers.
J. C. CANNON, privacy strategist at Microsoft's Corporate Privacy Group, specializes in implementing application technologies that maximize consumer control over privacy and enable developers to create privacy-aware applications. He works closely with Microsoft product groups and external developers to help them build privacy into applications. He also contributed the chapter on privacy to Michael Howard's Writing Secure Code (Microsoft Press 2003). Cannon has spent nearly twenty-five years in software development.
© Copyright Pearson Education. All rights reserved.See all Product Description
Top Customer Reviews
FYI: CD is referred to as "accompanying CD-ROM" but it does not inform you as to how / where to obtain it, that I could find. PLS see the following URL to download it via the Downloads tab;
To the author, PLS provide ebook or some digital book version option for sale, instead of paper only copy.
This is a supplemental read item for the CIPP/IT, so it could use an update. However note, references are still mostly relevant with current versions...unfortunately. An overall updated of the book (to current events, since publication of 2004...approximately 10 years since written) would be very appreciated.
Most Helpful Customer Reviews on Amazon.com (beta)
Chapter list: An Overview Of Privacy; The Importance of Privacy-Enhancing and Privacy-Aware Technologies; Privacy Legislation; Managing Windows Privacy; Managing Spam; Privacy-Invasive Devices; Building a Privacy Organizational Infrastructure; The Privacy Response Center; Platform for Privacy Preferences Project (P3P); Integrating Privacy in the Development Process; Performing a Privacy Analysis; A Sample Privacy-Aware Application; Protecting Database Data; Managing Access to Data: A Coding Example; Digital Rights Management; Privacy Section for a Feature Specification; Privacy Review Template; Data Analysis Template; List of Privacy Content; Privacy Checklist; Privacy Standard; References; Index
In today's environment, nearly every aspect of your daily existence touches data processing systems in some way. And if you surf the web, you know you are constantly being asked for personal and demographic information. But all too often, privacy issues related to all this information are not addressed in a secure, consistent methodology. Because of that, you stand a good chance of having far more personal information released to 3rd parties than you may be comfortable with. This book will help you become aware of the issues and build solid systems and processes that protect that privacy.
The first part of the book shows you how to secure your own privacy when you're working with computers. With the use of features such as pop-up blockers, cookie blockers, anonymous email services, and other related tools, you can effectively control the amount of information about your person and your activities while online. This information is really useful to anyone reading the book regardless of whether they are in IT or not. The second part of the book concentrates more on building software and processes that recognizes this right to privacy and gives the consumer choices on how to disclose and manage their personal information. The information is very practical and readable, and organizations would do well to consider the information presented here.
If you happen to be working in an industry affected by legislation such as HIPAA, this book becomes critical. If you're dealing with personal health information, you have no choices when it comes to privacy. The laws are spelled out, and the legal consequences for violating these laws are severe. Companies such as these should definitely get a copy.
This information has even affected one of the application changes I am currently working on. The user wanted to track the number of hits that a document got for reading. I started to build the change to track *who* read it, but then remembered that "less is more". There's no reason to track that information, so I shouldn't. As a result, I've got a more privacy-friendly application that delivers the desired results without violating the reader's privacy.
Good book, and worth the time for reading...
There are two questions an organization should ask about privacy: What is the cost of implementing a privacy program and what is the potential cost of not implementing a privacy program. Cannon's book will appeal as much to managers and executives responsible for knowing the answers to those questions.
The first third of the book provides an overview of privacy legislation and of technologies that are either privacy-enhancing or privacy-invasive, with suggestions for how to protect oneself from privacy intrusion. Chapter 4 is devoted to the subject of managing privacy for Windows products which can be helpful to administrators and consumers. It covers the privacy settings for XP, Windows Server 2003, Windows Office 2003, and Windows Media Player 9. Consumers and privacy advocates alike will find a wealth of information here about what privacy technologies exist and how to use them.
In the next fifty pages, Cannon discusses how to build a privacy organizational infrastructure and a privacy response center; and the reminder of the 350-page book is devoted to walking developers through the steps necessary to actually build privacy functionalities into their solutions. It is here that Cannon delves into more technical topics of interest to developers building privacy-enhancing technologies and to companies looking to include privacy awareness into the way products are built.
P3P is something I have struggled with on the SANS Institute's own web page. At present, it seems like an organization is safer not implementing it and the book was very helpful for me to better grasp the issues surround electronic enforcement of privacy.
With all this background information in mind he then discusses how to integrate consideration of these privacy issues into your program and way of thinking in general. This is not an expose of particular privacy problems but a theoretical framework for privacy that uses real-world examples to illustrate the issues. One of the really good points the author makes is that there is a difference between privacy and security. There are a lot of good books on security available today but privacy is rarely discussed. The author provides a thoroughly convincing argument as to why security is not enough and privacy issues must be considered at all times and in all environments.
Privacy: What Developers and IT Professionals Should Know is highly recommended for everyone even remotely connected to the computer technology environment, no exceptions.
One of the issues covered is spam. He gives a summary of the main antispam methods currently in vogue. The reader needs to be aware that the discussion is very limited. Extensions are ignored that improve the effectiveness of several methods. Consider for example the hashing method. He restricts this to making a single hash from a message. But making several hashes is far more robust to spammer countermeasures.
Likewise, block lists are described. (More commonly known as black lists.) He says the drawback is that spammers usually use fake email addresses and domain names. Well, for one thing, not all spammers fake these. So the black list can still be applied against the purported sender, to detect the latter. But suppose that a spammer does forge her address in the header. The black list can also be applied against the message body. Typically with devastating effect.
Look for similar items by category
- Books > Computers & Technology > History & Culture > Privacy
- Books > Computers & Technology > Microsoft > Operating Systems
- Books > Computers & Technology > Operating Systems
- Books > Computers & Technology > Web Development > Security & Encryption > Encryption
- Books > Qualifying Textbooks - Fall 2007 > Computers & Internet
- Books > Textbooks > Computer Science & Information Systems > Operating Systems