David Zetoony, co-chair of the firm’s U.S. Data, Privacy and Cybersecurity Practice, co-authored an IAPP article titled “Data Privacy Requests Metrics: Lessons for Your Privacy Program.” Read the full article here.

Updates on the Evolving Data Protection Landscape
David Zetoony, co-chair of the firm’s U.S. Data, Privacy and Cybersecurity Practice, co-authored an IAPP article titled “Data Privacy Requests Metrics: Lessons for Your Privacy Program.” Read the full article here.
The ISO 29100 privacy framework sets forth the following eleven core principles:
The ISO 27701 privacy framework is not explicitly organized using the…
While theoretically an organization could adopt ISO 27701 as a separate standalone framework to apply to an organization’s privacy program, the framework was conceptualized as an extension of the ISO data security standards. As a result, it is organized based upon the assumption that an organization already has a security program that is built off…
In 2019, the International Organization for Standards joint technical committee ISO/IEC JTC1, Information technology subcommittee SC27, developed a privacy framework that was intended to build off of the existing ISO data security standards – i.e., ISO/IEC 27001:2013 (Information security management systems) and ISO/IEC 27002:2013 (Code of practice for information security controls) – by integrating into…
No. The NIST privacy framework recommends that companies summarize their maturity with respect to each category by using four “Tiers.” The Tiers are intended to describe whether the current practices of the company with respect to the domain are partially in place (Tier 1), risk informed (Tier 2), repeatable (Tier 3), or adaptive (Tier 4).…
The NIST privacy framework refers to the term “current profile” to describe the current state of a company’s privacy program in relation to a specific Subcategory. So, for example, a company might include the following description in its current profile for the following subcategory:
Subcategory | Current Profile |
ID.IM-P1: Systems/products/services that process data are inventoried. | The |
…
The NIST privacy framework refers to the term “core” to describe a set of privacy activities and outcomes. The core is composed of three nested levels: Function, Category, and Subcategory. Subcategory is the most granular, and tangible, aspect of the core. In total, the NIST privacy framework proposes 100 Subcategories. It should be noted, however,…
The NIST privacy framework refers to the term “core” to describe a set of privacy activities and outcomes. The core is composed of three nested levels: Function, Category, and Subcategory. Categories are intended to be subdivisions of the Functions, and groupings of the Subcategories. In total, the NIST privacy framework contains 18 Categories.
No. ISO 27701 utilizes the same terms, definitions, and abbreviations as ISO 29100.
The NIST privacy framework refers to the term “core” to describe a set of privacy activities and outcomes. The core is composed of three nested levels: Function, Category, and Subcategory. The core “Function” is the broadest category level and consists of five recommended Functions: Identify, Govern, Control, Communicate, and Protect.