book

The Privacy Engineer's Manifesto: Getting from Policy to Code to QA to Value

by Michelle Finneran Dennedy, Jonathan Fox, Thomas R. Finneran

January 2014

Intermediate to advanced

400 pages

11h 8m

English

Apress

Read now

Unlock full access

The Relationship Between Information Technology Innovation and Privacy The Information Age The Dawning of the Personal Information Service EconomyConclusion
What Is Privacy?Privacy Engineering Personal Information PrivacyFair Information Processing Principles and the OECD GuidelinesOther Governance Standards of which to be aware Privacy Is Not Confidentiality and Security Is Not PrivacyConclusion
Data Management: The Management of “Stuff”Data GovernanceData Privacy Governance Frameworks Generally Accepted Privacy Principles (GAPP)Privacy by Design Conclusion
Elements of Privacy Engineering DevelopmentPrivacy Policy DevelopmentDesigning a Privacy PolicyEnterprise-Specific Privacy DevelopmentInternal vs. External PoliciesPolicies, Present, and FutureConclusion
Three Example ScenariosPrivacy Requirements EngineeringPrivacy Requirements EngineeringDetermining Data RequirementsConclusion
Enterprise ArchitectureMethodologyStage 1: Project Initiation and Scoping WorkshopStage 2: Develop Use Cases and Class or Data ModelsStage 3: Design an Engineered SolutionStage 4: Complete System DevelopmentStages 5 and 6: Quality Assurance and RolloutConclusion
Privacy Component Context DiagramThe Privacy Component Class ModelPrivacy Component User Interface RequirementsDesign the Privacy Component SolutionDevelop the Privacy Component DesignUsing the System Development Methodology for the Privacy ComponentConclusion
The Runner’s Mobile App Use CaseThe Runner’s App Class or Data ModelThe Runner’s App User Experience RequirementsDesign the App StructureThe Runner’s App System Activity DiagramPrivacy Assessment Using a System Activity DiagramDevelop the Runner’s App Component DesignUsing the System Development MethodologyConclusion
Requirements DefinitionPrivacy Component Class and Data ModelVacation Planner User Interface RequirementsDesign the Vacation Planner SolutionUsing the System Development MethodologyConclusion
Quality AssuranceUsing Frameworks to Create a Privacy Quality Assurance ChecklistPrivacy Concerns During Quality AssuranceResources for Conducting Privacy Impact AssessmentsConclusion
Privacy Responsibilities in Different Parts of the OrganizationPrivacy Awareness and Readiness AssessmentsBuilding the Operational Plan for Privacy Awareness and ReadinessBuilding a Communication and Training Plan for Privacy Awareness and ReadinessConclusion
Organizational Placement and StructureCommon Privacy Engineering RolesChallenges of Bringing Privacy Engineering to the ForefrontBest Practices for Organizational AlignmentBenefits of Data GovernanceBusiness Benefits of AlignmentConclusion
Finding Values for DataValuation ModelsBuilding the Business CaseTurning Talk into ActionConclusion
Where the Future Doesn’t Need UsEven Social Networks (and Their Leaders) Get Cranky When Their Privacy Is CompromisedLet’s Remember How We Got HerePrivacy Is Not a One-Size-Fits-All FormulaInnovation and PrivacySocietal Pressures and PrivacyIt Still Comes Down to Trust and ValueA New Building Code for PrivacyGetting StartedA Privacy Engineer’s ManifestoConclusion
Example Use-Case Format

Content preview from The Privacy Engineer's Manifesto: Getting from Policy to Code to QA to Value

Foreword, with the Zeal of a Convert

It’s a call I get every 6 to 12 months. My credit card has been “compromised” and needs to be replaced with a new one. Once a major annoyance, this has become a well-oiled, mildly inconvenient ritual for updating useful accounts and dropping the ones I no longer need or want—an effective method for canceling sticky subscriptions. It is a tribute to the resilience of human beings that we can adapt so easily to a bad state of affairs. And so it is for me, and many others I suspect, the way that I am reminded about privacy and its protection, by accident, every 6 to 12 months, for just a few days. It’s not that I don’t like privacy; it’s just that I really didn’t care all that much.

The book you are holding ...