> ## Content Index
> Fetch the complete content index at: https://ishangirdhar.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# CDPSE Certified Data Privacy Solutions Engineer All-in-One Exam Guide
- URL: https://ishangirdhar.com/cdpse-certified-data-privacy-solutions-engineer-all-in-one-exam-guide/
- Published: 2021-10-27T04:56:00.000Z
- Updated: 2026-11-17T17:40:06.000Z
- Description: by Peter H. Gregory
- Author: Ishan Girdhar
- Tags: Books, #reading-list, #ebook, #toc, #book

## Highlights

> PART I Privacy Governance

**My note:** .h1

> CHAPTER 1 Governance

**My note:** .h2

> In this chapter, you will learn about • Business alignment • Privacy and security governance activities • Privacy and security strategy development • Resources needed to develop and execute a privacy and security strategy • Obstacles to strategy development and execution • Privacy and security metrics

**My note:** .Questions

> Properly implemented, governance is a process whereby senior management exerts strategic control over business functions through policies, objectives, delegation of authority, and monitoring. Governance is management’s continuous oversight of an organization’s business processes to ensure that they effectively meet the organization’s business vision and objectives.

> Effective governance is enabled through the development and enforcement of documented policies, standards, requirements, and various reporting metrics.

> Introduction to Privacy Governance

**My note:** .h3

> A goal of the privacy program is enabling the fulfillment of the privacy strategy, which itself will continue to align with the business, business objectives, and developing regulations. The processes supporting these principles and outcomes include privacy policy, data governance, compliance, risk management, and cybersecurity.

> Privacy is a business issue, and organizations that are not yet properly managing or adequately protecting personal information have a business problem.

> Think of privacy as having two main components: proper data management and usage, and data protection—commonly referred to as cybersecurity, data security, or information security.

> Privacy and Security: Together or Separate?

**My note:** .h3

> Should privacy and security be managed separately or together? Although there’s no right or wrong answer, know this: privacy cannot succeed without information security. The objectives of a privacy program are the protection and proper handling of personal information. The protection part is done by information security, and the proper handling part is solely the domain of privacy. Privacy needs information security to be successful. Security is a prerequisite to privacy, but privacy adds more: the proper handling of information and its protection. This is why privacy and security are discussed hand-in-hand throughout this chapter and in most of this book. To discuss privacy alone, without security, tells only half of the entire story that needs to be told.

> Privacy Governance Influencers

**My note:** .h3

> The Nature of Personal Data and Information

**My note:** .h3

> The Imperfect Lexicon of Privacy

**My note:** .h3

> As in every profession, privacy and information security professions include some special vocabularies. In the privacy profession are the terms personal information and data subject request. Is there really a distinction and a valid reason why “personal information” uses the term information while “data subject request” uses the term data? Looking at dictionary definitions, data and information have similar definitions. However, if we go deeper and more specific, we find definitions (in this case, from www.diffen.com) along these lines: “Data are simply facts or figures—bits of information, but not information itself. When data are processed, interpreted, organized, structured, or presented so as to make them meaningful or useful, they are called information. Information provides context for data.” Perhaps this is a clue. The remainder of this exercise is left to the reader.

> Privacy Laws

**My note:** .h3

> Covered entities are required to enact business associate agreements (BAAs) with all third parties that store or process ePHI on behalf of covered entities.

> Other Legal Obligations

**My note:** .h3

> Privacy Practices

**My note:** .h3

> Legitimate interest gives organizations a basis for collecting and processing personal information if they benefit from doing so. But it doesn’t end there: the real issue of legitimate interest lies in the fact that organizations must balance their interests with that of the data subject.

> the real issue of legitimate interest lies in the fact that organizations must balance their interests with that of the data subject.

> Data Governance and Data Management

**My note:** .h3

> Cybersecurity Practices

**My note:** .h3

> Information Systems and Their Capabilities

**My note:** .h3

> Reasons for Privacy Governance

**My note:** .h3

> organizations must be transparent about how they obtain, collect, process, and pass on personal information.

> privacy governance is all about keeping organizations out of trouble with regulators, outraged citizens, and the courts.

> Privacy and Security Governance Activities and Results

**My note:** .h3

> Business Alignment

**My note:** .h3

> Goals and Objectives

> Risk Appetite

**My note:** .h3

> Monitoring Privacy Responsibilities

**My note:** .h3

> Privacy Governance Metrics

**My note:** .h3

> Effective Metrics

**My note:** .h3

> Risk Management

**My note:** .h3

> Performance Measurement

**My note:** .h3

> Resource Management

**My note:** .h3

> Developing Metrics in Layers for Audience Relevance

**My note:** .h3

> When embarking on the quest for privacy and security metrics development, a common pitfall is the development of a one-dimensional metrics framework that publishes a set of metrics to all audiences. For instance, a metrics program may publish figures on vulnerabilities discovered, vulnerabilities remediated, privacy incidents, security incidents, and internal audits and their exceptions. Publishing this or a similar set of metrics to various stakeholders will add little value to some audiences and no value to others. A better approach is the development of operational metrics, which are usually easily discovered and measured. The next step is to transform those operational metrics into different metrics, stated in business terms, for business audiences. In a given organization, a privacy program may employ two, three, or more layers of metrics, usually related to each other, and stated in relevant technical or business terms for each respective audience. While it may be a good starting point to ask business leaders what kinds of metrics they want to see, in many cases, privacy and security leaders will be asked what metrics they want to see. This can be a challenge at times, but by understanding the business, culture, compliance climate, and individuals involved at the stakeholder level, the privacy and security leader can start with a set of metrics that shows success in investments made or use metrics as a call to action by the leadership team.

> Privacy Strategy Development

**My note:** .h3

> Strategy Objectives

**My note:** .h3

> Control Frameworks

**My note:** .h3

> ISO/IEC 27701

**My note:** .h3

> NIST Privacy Framework

**My note:** .h3

> NIST Cybersecurity Framework

**My note:** .h3

> ISO/IEC 27001

**My note:** .h3

> NIST SP 800-53 and NIST SP 800-53A

**My note:** .h3

> NIST SP 800-122

**My note:** .h3

> Center for Internet Security Critical Security Controls

**My note:** .h3

> PCI DSS

**My note:** .h3

> Risk Objectives

**My note:** .h3

> Strategy Resources

**My note:** .h3

> NOTE A threat assessment is an essential element of strategy development. Without a threat assessment, there is a possibility that strategic objectives may fail to address important threats. This would result in a privacy or security strategy that would not adequately protect the organization.

> NOTE The topic of audits is discussed in considerable detail in the book CISA Certified Information Systems Auditor All-In-One Study Guide.

> NOTE Many organizations align their privacy and security policies with the privacy and security control frameworks they have adopted.

> NOTE The presence of a recent BIA provides a strong indication of the organization’s maturity through its intention to protect its most critical processes from disaster scenarios. Correspondingly, the absence of a BIA suggests that the organization does not consider business continuity and disaster recovery (BCDR) as having strategic importance.

> CAUTION When considering an organization’s culture, the strategist needs to rely more upon the organization’s actual operations, as opposed to its statements of culture and values. The actual organizational culture may not align with the organization’s claims. • Maturity The characteristics of privacy and security management programs discussed in this list all contribute to the overall maturity of the organization’s program. By itself, the maturity level of the program doesn’t tell the strategist anything about the program’s details. The strategist’s observations of the overall program will provide a visceral feeling for its overall maturity. • Risk appetite Undocumented in most organizations, risk appetite can be discerned through the record of risk treatment decisions and observation of an organization’s executive culture. Even then, however, the attitude and culture of risk appetite may differ from an organization’s actual practices.

> Privacy Program Strategy Development

**My note:** .h3

> NOTE The strategist must consider many inputs before developing objectives and strategies to achieve them. These inputs serve a critical purpose: to help the strategist understand the organization’s current state. The journey to developing and achieving a strategy is not possible without understand the journey’s starting point. These are discussed in the previous section, “Strategy Resources.”

> Gap Analysis

**My note:** .h3

> Strengths, Weaknesses, Opportunities, and Threats Analysis

**My note:** .h3

> Capability Maturity Models

**My note:** .h3

> Road Map Development

**My note:** .h3

> Developing a Business Case

**My note:** .h3

> Establishing Communications and Reporting

**My note:** .h3

> Obtaining Management Commitment

**My note:** .h3

> Strategy Constraints

**My note:** .h3

> The Obstacle of Organizational Inertia

**My note:** .h3

> Every organization has a finite capacity to undergo change. This is a fact that is often overlooked by overly ambitious strategists who want to accomplish a great deal in too short a time. I have coined the term organizational inertia to represent an analogy to Newton’s laws of motion: an object either remains at rest or continues to move at a constant velocity, unless acted upon by a force. In an organization, this means that things will be done in the same way until some force requires the organization to change what is done or how things are done. The greater amount of change that is needed, the greater the outside force is required to implement the change. The nature of organizational inertia, or its resistance to change, is threefold: • Operational people changing their processes and procedures • Learning curve • Human resistance to change

> Chapter Review

**My note:** .h3

> Quick Review

**My note:** .h3

> The addition of privacy and information security as part of fiduciary duty by board members and executives is an important and growing trend in business today.

> Privacy and security executives and the board of directors are responsible for implementing a privacy and security governance model encompassing privacy strategy, security strategy, and other mandates. As a result, the industry is seeing a shift from a passive to a…

> Privacy and security programs should be in alignment with the organization’s overall mission, goals, and objectives. This means that the chief privacy officer, chief information security officer, and others should be aware of, and involved in, strategic…

> Risk appetite is generally expressed in qualitative terms such as “very low tolerance for risk” and “no tolerance for risk.” Different activities in an…

> An organization’s definitions of roles and responsibilities may or may not be in sync with its culture of accountability. For instance, an organization may have clear definitions of responsibilities documented in policy and process documents and yet may rarely…

> • Ideally, an organization’s board of directors will be aware of privacy and security risks and may direct that the organization enact safeguards to protect the organization. However, in many organizations, the board of directors is still uninvolved in privacy and security matters; in these cases, it is still possible to have successful…

> Privacy and information security is the responsibility of every person in an organization; however, the means for assigning and monitoring privacy and security…

> The NIST Cybersecurity Framework and Privacy Framework are emerging as foundations for the development of high-level metrics. Still, it is up to every privacy and security leader to develop metrics that are meaningful and…

> The methodology for calculating return on security investment is widely discussed but not widely practiced, mainly because it is difficult to calculate the benefit of security controls designed to…

> Privacy and security managers developing strategies in an organization without a program will need to rely on their past experiences, anecdotal accounts of…

> Privacy and security strategists should be mindful of each organization’s tolerance for change within a given period of time. While much progress may be warranted, the amount of change that can be reasonably…

> • Many organizations ruminate over the selection of a control framework. Instead, the organization should select a framework and then make adjustments to its controls to suit the business. A control framework should generally be considered a starting point, not a rigid and unchanging list of…

> While it is important for privacy and security strategists to understand the present state of the organization when developing a strategic road map, the strategist must proceed knowing that there can never be a sufficient level of understanding. Besides, if even the most thorough snapshot has been taken, the organization is slowly (or perhaps quickly) changing anyway. Execution of a strategic plan…

> Capability maturity models are useful tools for understanding the maturity level of a process and developing desired future states. The maturity of processes in the organization will vary, as it is appropriate for some processes to have high maturity while it is acceptable for others to have lower maturity. The right question to ask about…

> Each organization has its own practice for the development of business cases for the presentation, discussion, and…

> Privacy and security strategists must anticipate obstacles and constraints affecting the achievement of strategic objectives and consider refining those…

> CHAPTER 2 Management

**My note:** .h2

> In this chapter, you will learn about • Privacy-related roles and responsibilities • Privacy training and awareness • Third-party risk management • Auditing privacy processes and systems • Privacy and security incident response

**My note:** .Questions

> Privacy Roles and Responsibilities

**My note:** .h2

> Board of Directors

> Executive Management

**My note:** .h2

> Privacy and Security Steering Committees

**My note:** .h2

> Business Process and Business System Owners

**My note:** .h2

> Custodial Responsibilities

**My note:** .h2

> Chief Privacy Officer

**My note:** .h2

> Chief Information Security Officer

**My note:** .h2

> Software Development

**My note:** .h2

> Data Management

**My note:** .h2

> Network Management

**My note:** .h2

> Systems Management

**My note:** .h2

> Privacy Operations

**My note:** .h2

> Security Operations

**My note:** .h2

> Privacy Audit

**My note:** .h2

> Security Audit

**My note:** .h2

> Service Desk

**My note:** .h2

> Quality Assurance

**My note:** .h2

> Building a Privacy Operation

**My note:** .h2

> Identifying Privacy Requirements

**My note:** .h2

> Culture and Values

**My note:** .h2

> Applicable Regulations

**My note:** .h2

> Legal Interpretation

**My note:** .h2

> Cybersecurity Policies, Requirements, and Regulations

**My note:** .h2

> Developing Privacy Policies

**My note:** .h2

> Internal Privacy Policy

**My note:** .h2

> External Privacy Policy

> Developing and Running Data Protection Operations

**My note:** .h2

> Developing and Running Data Monitoring Operations

**My note:** .h2

> Data Discovery Scanning

**My note:** .h2

> Data Movement Monitoring

**My note:** .h2

> Working with Data Subjects

**My note:** .h2

> Inquiries for Data Usage

**My note:** .h2

> Requests for Corrections

**My note:** .h2

> Requests for Removal

**My note:** .h2

> Working with Authorities

**My note:** .h2

> Privacy Training and Awareness

**My note:** .h2

> Training Objectives

**My note:** .h2

> Creating or Selecting Content

**My note:** .h2

> Information Workers

**My note:** .h2

> Technical Workers

**My note:** .h2

> Software Developers

**My note:** .h2

> Third Parties

**My note:** .h2

> New Hires

**My note:** .h2

> Annual Training

**My note:** .h2

> Communication Techniques

**My note:** .h2

> Third-Party Risk Management

**My note:** .h2

> Cloud Service Providers

**My note:** .h2

> Privacy Regulation Requirements

**My note:** .h2

> TPRM Life Cycle

**My note:** .h2

> Initial Assessment

**My note:** .h2

> Legal Agreement

**My note:** .h2

> Classifying Third Parties

**My note:** .h2

> Questionnaires and Artifacts

**My note:** .h2

> Assessing Third Parties

**My note:** .h2

> Risk Mitigation

**My note:** .h2

> Auditing Privacy Operations

**My note:** .h2

> Privacy Audit Scope

**My note:** .h2

> Privacy Audit Objectives

**My note:** .h2

> Types of Privacy Audits

**My note:** .h2

> Privacy Audit Planning

**My note:** .h2

> Audit Statement of Work

**My note:** .h2

> Communication Plan

**My note:** .h2

> Report Preparation

**My note:** .h2

> Wrap-up

**My note:** .h2

> Post-audit Follow-up

**My note:** .h2

> Privacy Audit Evidence

**My note:** .h2

> Gathering Evidence

**My note:** .h2

> Relying on the Work of Other Auditors

**My note:** .h2

> Reporting Privacy Audit Results

**My note:** .h2

> Auditing Specific Privacy Practices

**My note:** .h2

> Auditing Privacy Policy

**My note:** .h2

> Auditing Data Management

**My note:** .h2

> Auditing Data Collection

**My note:** .h2

> Auditing Data Subject Requests

**My note:** .h2

> Auditing Data Minimization

> Auditing Anonymization and Pseudonymization

**My note:** .h2

> Auditing Privacy Incident Management

**My note:** .h2

> Audit Standards

**My note:** .h2

> Privacy Incident Management

**My note:** .h2

> Phases of Incident Response

**My note:** .h2

> Privacy Incident Response Plan Development

**My note:** .h2

> Privacy Continuous Improvement

**My note:** .h2

> Chapter Review

**My note:** .h2

> The management of a privacy program in an organization begins with an understanding of all of the IT, security, and privacy-related roles and responsibilities. A role is a description of expected activities that each employee is obliged to perform as part of his or her employment. A responsibility is a statement of outcomes that a person is expected to support.

> Models such as RACI charts are used to determine and illustrate levels and types of responsibilities in selected business processes. RACI charts show who performs tasks, who helps, and who is to be told of them. Alternatives to RACI include PARIS (Participant, Accountable, Review Required, Input Required,…

> The formation of a privacy steering committee helps to ensure that an organization’s privacy plan will align with the organization’s core business operations while fulfilling business…

> Privacy operations include many activities already present in many organizations, including identity and access management, incident monitoring and response,…

> Through the concept of privacy by design and by default, privacy affects the processes, procedures, and activities of many (if not…

> Building a privacy operation requires detailed knowledge of privacy requirements—that is, the activities and outcomes the organization is required to undertake at present and in the foreseeable future. Those requirements generally stem from applicable regulations; implicit and explicit…

> External privacy policies are the official statements describing the organization’s practices for the collection, use, and ultimate disposal of personal information. Privacy policies also describe how data subjects may make…

> Internal privacy policies describe the roles, responsibilities, practices, standards, and…

> Data management is a key activity for an organization’s privacy program, as this includes the protection of personal…

> Modern privacy laws require that organizations establish means for accepting incoming inquiries and requests from internal and external data subjects. Effective procedures and controls are required to ensure…

> Subject requests for data removal require that an organization understand whether applicable laws require the retention of such data, and whether anonymization or pseudonymization may…

> Supervisory authorities are government or quasi-government agencies that investigate potential wrongdoing by organizations and their management of personal information. Organizations need to be prepared to respond to their…

> Like security awareness training to inform the workforce of expectations in behavior and safe Internet usage, privacy awareness training informs the workforce of expectations for the…

> Third-party risk management (TPRM) refers to activities used to discover and manage risks associated with external organizations performing operational functions for an organization. TPRM industry practices are well developed and…

> The best practice in TPRM is the practice of establishing risk tiers of an organization’s service provider population and applying varying levels of rigor to each tier. This ensures a risk-based allocation of resources in…

> Like other important business processes, many organizations undergo audits of some or all aspects of their privacy and data management operations. The principles of information systems auditing are no different in privacy audits: the goal is to determine the effective design and operations of key…

> Audits of privacy programs may target data protection (information security) and the proper use of personal information. Audits will also frequently cover…

> A privacy incident is an event in which one or more data subjects’ personal information has been inappropriately used or disclosed, contrary to applicable laws or regulations. A privacy incident can also be thought of as an event representing a…

> The overall techniques used for privacy incident response are similar to those for security incident response. Incidents are detected, analyzed, contained, and eradicated. Systems are recovered, and remediation steps are carried out to prevent…

> Privacy incident response plans need to be periodically tested, and all incident…

> It is vital that an organization’s culture not be satisfied with its current state of policies, practices, and operations. Instead, a spirit of continuous improvement…

> Quick…

**My note:** .h2

> An employee’s title and rank together connote the employee’s role in the organization, along with his or her sphere of responsibility. Industries do not…

> • The placement and structure of an organization’s staff hierarchies (the org chart) is less important than the…

> The involvement of an organization’s board of directors ranges from high involvement in the organization throughout the year, to merely attending a quarterly meeting, to listening to…

> In a smaller, younger organization, board members are often the organization’…

> An organization can combine its privacy, security, and even IT steering committees if the participants are…

> • Through the concept of privacy by design and by default, privacy affects the processes, procedures, and activities of many (if not…

> Because of the high velocity of change of applicable privacy and data protection laws, organizations are compelled to establish reliable means…

> • The presence and use of unstructured data is often the greatest concern for a privacy officer. The power and flexibility of endpoint operating systems and their connectivity mean that employees can do nearly anything they want with personal information, subject to…

> The advent of data privacy laws has compelled organizations to “discover” the presence and usage of personal information in their information systems. Lax or nonexistent data governance in many…

> • The greater the extent of outsourcing of IT services, the greater the need for an…

> • For a privacy program to be effective, close partnerships are required with IT, IT security, human resources, legal, and business units or departments. Privacy cannot work in a vacuum, because all of these other entities manage key business processes and information systems manage personal information.

> • Audits of a privacy program that attempt to establish that only sanctioned uses of personal information exist is tantamount to proving the absence of unsanctioned activities—a difficult undertaking.

> With relatively minor additions, an organization’s security incident response plan can be augmented to serve effectively as a privacy incident response plan as well.

> It is up to management to determine where improvements in processes, procedures, and controls should be implemented.

> CHAPTER 3 Risk Management

**My note:** .h3

> A threat is defined as an event that, if realized, would bring harm to an asset and, thus, to the organization.

> Two excellent resources for PIAs and how PIAs achieve these objectives are • https://www.gsa.gov/reference/gsa-privacy-program/privacy-impact-assessments-pia • https://www.ftc.gov/site-information/privacy-policy/privacy-impact-assessments

> NOTE A PIA is nothing more than a risk assessment whose focus is the privacy and security of subject data in some specific context.

> The Necessity of a PIA

> Integrating into Existing Processes

> Recordkeeping and Reporting

> PART II Privacy Architecture

**My note:** .h1

> CHAPTER 4 Infrastructure

**My note:** .h2

> CHAPTER 5 Applications and Software

**My note:** .h2

> CHAPTER 6 Technical Privacy Controls

**My note:** .h2

> PART III Data Cycle

**My note:** .h1

> CHAPTER 7 Data Purpose

**My note:** .h2

> CHAPTER 8 Data Persistence

**My note:** .h2

223 highlights, exported from my Kindle via Readwise.