Skip to main content

PRI-07.4: Reject Unauthenticated or Untrustworthy Disclosure Requests

PRI 5 — Medium Identify

Mechanisms exist to reject unauthenticated, or untrustworthy, disclosure requests.

Control Question: Does the organization reject unauthenticated, or untrustworthy, disclosure requests?

General (3)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) P5.1-POF4 P5.2-POF1 P5.2-POF3
CSA CCM 4 DSP-11 DSP-18
NIST Privacy Framework 1.0 CT.DM-P1
US (6)
Framework Mapping Values
US HIPAA Administrative Simplification 2013 (source) 164.524(d)(2)(i) 164.524(d)(2)(ii) 164.524(d)(2)(iii) 164.524(d)(3)
US - CA CCPA 2025 7022(a) 7023(b) 7024(a) 7024(b) 7026(e)
US - CO Colorado Privacy Act 6-1-1306(1)
US - OR CPA 4(5)(e)(B)
US - TN TIPA 47-18-3203(b)(4)
US - TX CDPA 541.052(e)
EMEA (1)
Framework Mapping Values
EMEA Serbia 87/2018 21.2 22.2
APAC (1)
Framework Mapping Values
APAC China Privacy Law 45 46 49

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to reject unauthenticated, or untrustworthy, disclosure requests.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to reject unauthenticated, or untrustworthy, disclosure requests.

Level 2 — Planned & Tracked

C|P-CMM2 is N/A, since a well-defined process is required to reject unauthenticated, or untrustworthy, disclosure requests.

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 reject unauthenticated, or untrustworthy, disclosure requests.

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 reject unauthenticated, or untrustworthy, disclosure requests.

Assessment Objectives

  1. PRI-07.4_A01 reject unauthorized disclosure requests.

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.