Skip to main content

PRI-03.3: Prohibition of Selling, Processing and/or Sharing Personal Data (PD)

PRI 5 — Medium Identify

Mechanisms exist to prevent the sale, processing and/or sharing of Personal Data (PD) when: (1) Instructed by the data subject; or (2) The data subject is a minor, where selling and/or sharing PD is legally prohibited.

Control Question: Does the organization prevent the sale, processing and/or sharing of Personal Data (PD) when: (1) Instructed by the data subject; or (2) The data subject is a minor, where selling and/or sharing PD is legally prohibited?

General (2)
Framework Mapping Values
NIST Privacy Framework 1.0 CT.PO-P1 CT.PO-P3
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) PRI-03.3
US (7)
Framework Mapping Values
US HIPAA Administrative Simplification 2013 (source) 164.502(a)(5)(ii)(A)
US - CO Colorado Privacy Act 6-1-1306(1) 6-1-1306(1)(a)(I)(A) 6-1-1306(1)(a)(I)(B) 6-1-1306(1)(a)(I)(C) 6-1-1306(1)(a)(II) 6-1-1306(1)(a)(III) 6-1-1306(1)(a)(IV)(A) 6-1-1306(1)(a)(IV)(B) 6-1-1306(1)(a)(IV)(C)
US - IL BIPA 15(c)
US - NV SB220 2.3
US - TN TIPA 47-18-3203(a)(2)(E)(i) 47-18-3203(a)(2)(E)(ii) 47-18-3203(a)(2)(E)(iii) 47-18-3204(d)
US - TX CDPA 541.101(b)(4)
US - VA CDPA 2025 59.1-577.1.C 59.1-578.F.1 59.1-578.F.1.a
EMEA (1)
Framework Mapping Values
EMEA Serbia 87/2018 37
APAC (2)

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to prevent the sale, processing and/or sharing of Personal Data (PD) when: (1) Instructed by the data subject; or (2) The data subject is a minor, where selling and/or sharing PD is legally prohibited.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to prevent the sale, processing and/or sharing of Personal Data (PD) when: (1) Instructed by the data subject; or (2) The data subject is a minor, where selling and/or sharing PD is legally prohibited.

Level 2 — Planned & Tracked

Privacy (PRI) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • Privacy management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
  • The data privacy program is developed to work with IT and cybersecurity staff to ensure that applicable statutory, regulatory and contractual data privacy obligations for Personal Data (PD) are properly identified and implemented across the enterprise.
  • IT/cybersecurity personnel identify cybersecurity and data protection controls to address applicable statutory, regulatory and contractual requirements for data privacy management.
  • A qualified individual is formally assigned as the Chief Privacy Officer (CPO), or similar role, to lead the organization's data privacy program. This individual may be assigned to multiple duties, including that as a Data Protection Officer (DPO).
  • The CPO, or similar role, identifies “data privacy principles” that systems, applications, services, processes and third-parties must adhere to, based on leading data privacy practices.
  • Administrative processes and technologies collect, store, processes, transmit share or use PD only for the purposes identified in the data privacy notice.
  • The DPO reviews the management of PD to ensure that controls exist to prohibit the sale of PD when instructed by the data principle.
Level 3 — Well Defined

Privacy (PRI) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • A Chief Privacy Officer (CPO), or similar function with technical competence to address data privacy concerns, analyzes the organization's business strategy to develop and publish authoritative guidance on the organization's data privacy program.
  • A Privacy program, run by a CPO, or similar role, ensures that applicable statutory, regulatory and contractual data privacy obligations are properly identified and implemented to limit and secure Personal Data (PD) that the organization stores, transmits and processes.
  • As part of the organization's data privacy program, the CPO publishes a clear set of “data privacy principles”, based on leading data privacy practices, that systems, applications, services, processes and third-parties must adhere to.
  • A Project Management Office (PMO), or project management function, ensures both cybersecurity and data privacy principles are identified and implemented within ongoing or planned projects.
  • The Chief Information Security Officer (CISO), or similar function with technical competence to address cybersecurity concerns, analyzes the organization's business strategy to determine prioritized and authoritative guidance for cybersecurity-related data privacy practices.
  • The CISO, or similar function, develops a security-focused Concept of Operations (CONOPS) that documents management, operational and technical measures to apply defense-in-depth techniques across the enterprise for cybersecurity-related data privacy practices.
  • A Governance, Risk & Compliance (GRC) function, or similar function, provides governance oversight for the implementation of applicable statutory, regulatory and contractual cybersecurity and data protection controls to protect the confidentiality, integrity, availability and safety of the organization's applications, systems, services and data with regards to data privacy.
  • A steering committee is formally established to provide executive oversight of the cybersecurity and data privacy program.
  • Data/process owners operationalize data privacy controls into the processes they control.
  • Third-party contracts included data protection requirements, including flow-down requirements to subcontractors.
  • Data Protection Officers (DPOs) are assigned to work closely with business units and project teams to ensure data privacy principles are being implemented.
  • CPO and DPO determine and document the legal authority that permits the collection, use, maintenance and sharing of PD, either generally or in support of a specific program or system need.
Level 4 — Quantitatively Controlled

See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to prevent the sale, processing and/or sharing of Personal Data (PD) when: (1) Instructed by the data subject; or (2) The data subject is a minor, where selling and/or sharing PD is legally prohibited.

Level 5 — Continuously Improving

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to prevent the sale, processing and/or sharing of Personal Data (PD) when: (1) Instructed by the data subject; or (2) The data subject is a minor, where selling and/or sharing PD is legally prohibited.

Assessment Objectives

  1. PRI-03.3_A01 Personal Data (PD) identified as "do not sell" by the data subject is identified.
  2. PRI-03.3_A02 the sale of Personal Data (PD) identified as "do not sell" is prevented anywhere the PD is stored and/or processed.

Technology Recommendations

Micro/Small

  • Data classification program
  • Data privacy program
  • Data Protection Impact Assessment (DPIA)
  • Product / project management

Small

  • Data classification program
  • Data privacy program
  • Data Protection Impact Assessment (DPIA)
  • Product / project management

Medium

  • Data classification program
  • Data privacy program
  • Data Protection Impact Assessment (DPIA)
  • Product / project management

Large

  • Data classification program
  • Data privacy program
  • Data Protection Impact Assessment (DPIA)
  • Product / project management

Enterprise

  • Data classification program
  • Data privacy program
  • Data Protection Impact Assessment (DPIA)
  • Product / project management

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.