IEEE P7002 D7-2021 pdf download – Draft Standard for Data Privacy Process.
4.1 Key terminology There is often uncertainty as to the distinction between certain key terms that are often used when discussing privacy risk management, including: a) Data privacy and privacy. Privacy is personal and contextual, experienced by each person in a variety of different ways. Data privacy is a subset of privacy, which relates to privacy considerations that arise from the processing of data that relates to individuals. b) Data privacy and information security. The goals of data privacy and information security are overlapping in some instances and distinct in others. The goals of information security are typically characterized by preventing the loss of confidentiality, integrity, and availability. In contrast, data privacy does not have equivalent, widely agreed upon goals, although it is often related to the fair and legitimate processing of personal data. As data privacy is just a part of the wider set of privacy issues, so information security is just a part of the wider field of security. For more information about data privacy objectives, see 7.2.2. c) Data privacy and data protection. Some jurisdictions avoid the use of the term “privacy” (for instance it doesn’t appear in the General Data Protection Regulation [GDPR]), but rather focus on the protection of data that relates to individuals, and the principles, rights, responsilities, and obligations involved when processing personal data. While data protection laws and regulations often overlap with privacy and security issues, they are distinct’. For example, group privacy, the privacy of groups as opposed to specific individuals, might be considered an issue in data privacy, but is generally not covered in data protection law.
Some organizations may be developing systems for internal use, while others may be developing systems6 that will be used by others, possibly in other jurisdictions or industries. Those developing systems for use by others should consider not just the contextual factors which affect them, but those which may affect the users of their system. The standard is iterative in its nature, meaning that many of the actions may not happen in the order laid out. The choice and order of actions to be applied to a system is contingent on the maturity of the organization’ s privacy framework. At times the user of the standard may need to repeat a process within one of the clauses or subclauses, for example a risk assessment may need to be repeated after changes to the system design. At other times they may find, through monitoring their wider context, organization, or system, that they need to respond to a change which in turn requires further changes that cross from one section to another. For example, a change in the regulatory context, may lead to new privacy requirements that in turn affect both the organizational privacy framework and system level requirements. Managing privacy risk requires active engagement from a diverse set of stakeholders, including those responsible for development, business strategy, regulatory compliance and risk, and senior leadership, designers, producers, suppliers and marketers who design systems. To deliver on the normative requirements in this standard it is critical to continuously engage with these diverse stakeholders.