Menu
Home
Log in / Register
 
Home arrow Computer Science arrow The Privacy Engineer’s Manifesto
Next >
The Privacy Engineer’s Manifesto - Michelle Finneran Dennedy




Part 1 Getting Your Head Around PrivacyChapter 1 Technology Evolution, People, and PrivacyThe Relationship Between Information Technology Innovation and PrivacyThe Information AgeThe Firewall StageThe Net StageThe Extranet StageAccess StageThe Intelligence StageThe Dawning of the Personal Information Service EconomyData-Centric and Person-Centric ProcessingConclusionChapter 2 Foundational Concepts and FrameworksWhat Is Privacy?Privacy EngineeringPersonal InformationPrivacyAn Operational Definition of PrivacyFair Information Processing Principles and the OECD GuidelinesCollection Limitation PrincipleData Quality PrinciplePurpose Specification PrincipleUse Limitation PrincipleSecurity Safeguards PrincipleOpenness PrincipleIndividual Participation PrincipleAccountability PrincipleOther Governance Standards of which to be awarePrivacy Is Not Confidentiality and Security Is Not PrivacyConfidentiality ≠ PrivacySecurity ≠ PrivacyThe OverlapsThe DisconnectsConclusionChapter 3 Data and Privacy Governance ConceptsData Management: The Management of “Stuff”Data GovernanceBenefits of Data GovernanceThe Privacy and Data Governance/Stewardship ConnectionData Privacy Governance FrameworksGenerally Accepted Privacy Principles (GAPP)Impact of Frameworks on the Privacy EngineerFrameworks Are Not the Same as LawsPrivacy by DesignHow Privacy Engineering and Privacy by Design work TogetherConclusionPart 2 The Privacy Engineering ProcessChapter 4 Developing Privacy PoliciesElements of Privacy Engineering DevelopmentPrivacy Policy DevelopmentWhat Is a Good Policy?Designing a Privacy PolicyWhat Should Be Included in a Privacy Policy?General-Level Privacy Policy DevelopmentEnterprise-Specific Privacy DevelopmentInternal vs. External PoliciesPolicies, Present, and FutureConclusionChapter 5 Developing Privacy Engineering RequirementsThree Example ScenariosExample Scenario 1: The Privacy ComponentExample Scenario 2: A Runner's AppExample Scenario 3: Hospitality Vacation PlannerPrivacy Requirements EngineeringPrivacy Requirements EngineeringUse Cases: A Tool for Requirements GatheringUse Cases within Privacy EngineeringPrivacy Requirements Derived from Privacy FrameworksDevelop Privacy Requirement Use CasesThe Privacy Engineer's Use of Use Case MetadataDetermining Data RequirementsHow Does the Distribution Channel Impact Privacy Engineering Requirements?ConclusionChapter 6 A Privacy Engineering Lifecycle MethodologyEnterprise ArchitectureArchitectural ViewsSolution ArchitectureDevelop Procedures, Processes, and MechanismsMethodologySystem Engineering LifecycleThe Use of Models within the MethodologyStage 1: Project Initiation and Scoping WorkshopProject Initiation Defines Project ProcessesRequirements Definition Within the Scoping WorkshopStage 2: Develop Use Cases and Class or Data ModelsDevelop Business Activity DiagramsDefining Business and Privacy Data ClassesUsing the Unified Modeling Language Class Model as a Data ModelExample: Privacy Component Class ModelData Modeling StepsStage 3: Design an Engineered SolutionUser Interface DesignUser Interface PrototypeComponent DesignExample: Privacy ComponentPrivacy RulesDevelop a System Activity DiagramDynamic ModelingDefine Service Components and Supporting MetadataStage 4: Complete System DevelopmentStages 5 and 6: Quality Assurance and Roll outDevelop and Execute Test CasesConclusionChapter 7 The Privacy Component AppPrivacy Component Context DiagramUse Case Requirements to Build a “Privacy Component”The Privacy Component Class ModelDeveloping the Unified Modeling Language Class ModelPrivacy Component User Interface RequirementsDesign the Privacy Component SolutionThe Privacy Component Solution ArchitectureThe Privacy Component Class StructurePrivacy Component System Activity DiagramPrivacy Assessment Using the System Activity DiagramDevelop the Privacy Component DesignUsing the System Development Methodology for the Privacy ComponentConclusionChapter 8 A Runner's Mobile AppThe 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 MethodologyConclusionChapter 9 Vacation Planner ApplicationRequirements DefinitionUse Case Metadata for Hospitality Vacation Planner Enterprise ApplicationDevelop Business Activity DiagramsPrivacy Component Class and Data ModelVacation Planner User Interface RequirementsDesign the Vacation Planner SolutionThe Vacation Planner Solution ArchitectureThe Vacation Planner Component Architecture StructureDevelop System Activity DiagramsDynamic ModelingDefine Service Components and Supporting MetadataUsing the System Development MethodologyConclusionChapter 10 Privacy Engineering and Quality AssuranceQuality AssuranceUsing Frameworks to Create a Privacy Quality Assurance ChecklistPurposeNoticeChoice or ConsentTransferAccess, Correction, or DeletionSecurityMinimizationProportionalityRetentionAct ResponsiblyPrivacy Concerns During Quality AssuranceVector 1: Managing Privacy During Quality AssuranceVector 2: Privacy Impact Assessment: A Validation ToolWho Is Usually Involved in a PIA?What Should a Privacy Impact Assessment Document Contain?Vector 3: The Importance and Value of Privacy Impact Assessment to Key StakeholdersResources for Conducting Privacy Impact AssessmentsConclusionPart 3 Organizing for the Privacy Information AgeChapter 11 Engineering Your Organization to Be Privacy ReadyPrivacy Responsibilities in Different Parts of the OrganizationPrivacy Awareness and Readiness AssessmentsDefine Existing Systems and ProcessesConsider the ContextSkills AssessmentBuilding the Operational Plan for Privacy Awareness and ReadinessBuilding a Communication and Training Plan for Privacy Awareness and ReadinessCommunicatingInternal CommunicationsExternal CommunicationA Word About What Are Usually Important, but Boring WordsMonitoring and Adapting the StrategyConclusionChapter 12 Organizational Design and AlignmentOrganizational Placement and StructureHorizontal Privacy Team: ProsHorizontal Privacy Teams: ConsCommon Privacy Engineering RolesChallenges of Bringing Privacy Engineering to the ForefrontExpanding Executive Management SupportSpreading Awareness and Gaining Cultural AcceptanceExtending Your Reach with Limited ResourcesCreating AlliancesExpanding the Scope of Data GovernanceRemaining Productive Amid Competing Priorities and DemandsBest Practices for Organizational AlignmentAligning with Information Technology and Information SecurityAligning with Data Governance FunctionsBenefits of Data GovernanceBusiness Benefits of AlignmentOther BenefitsConclusionPart 4 Where Do We Go from Here?Chapter 13 Value and Metrics for Data AssetsFinding Values for DataValuation ModelsModel 1Model 2Model 3Model 4Model 5Building the Business CaseTurning Talk into ActionConclusionChapter 14 A Vision of the Future: The Privacy Engineer's ManifestoWhere 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
 
Found a mistake? Please highlight the word and press Shift + Enter  
Next >
 
Subjects
Accounting
Business & Finance
Communication
Computer Science
Economics
Education
Engineering
Environment
Geography
Health
History
Language & Literature
Law
Management
Marketing
Philosophy
Political science
Psychology
Religion
Sociology
Travel