Skip to main content

PRI-39.5: Appeal Adverse Decision

PRI 4 — Medium Respond

Mechanisms exist to maintain a process for data subjects to appeal an adverse decision.

Renumbered: Formerly PRI-06.3 in SCF 2025.4.

Control Question: Does the organization maintain a process for data subjects to appeal an adverse decision?

General (11)
US (11)
Framework Mapping Values
USA Federal 45 CFR 155.260 155.260(a)(3)(ii)
USA Federal HIPAA Administrative Simplification 2013 § 164.524(d)(4)
USA California CCPA 2025 7023(d)(1) 7023(f)(3)
USA Colorado Colorado Privacy Act 2021 6-1-1306(3)(a)
USA Montana CDPA 2025 30-14-2808(4)(b) 30-14-2808(5)
USA Nevada Privacy Law 2023 603A.520.1 603A.520.1(a) 603A.520.1(b) 603A.520.2 603A.520.2(a) 603A.520.2(b) 603A.520.2(c)
USA Oregon CPA 2023 Section 4(6)(a)
USA Oregon 646A 2025 646A.576(6) 646A.576(6)(a) 646A.576(6)(b) 646A.576(6)(c) 646A.576(6)(d)
USA Tennessee TIPA 2025 47-18-3203(c)
USA Texas CDPA 2025 541.053(a)
USA Virginia CDPA 2023 59.1-577.C
EMEA (1)
Framework Mapping Values
EMEA Russia 152-FZ 2025 Art. 17

Capability Maturity Model

Level 0 — Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 — Performed Informally

SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.

Level 2 — Planned & Tracked

SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts).

Level 3 — Well Defined

Privacy (PRI) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with PRI domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with PRI domain capabilities are well-documented and kept current by process owners. ▪ A data privacy team, or similar function, is appropriately staffed and supported to implement and maintain PRI domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of data privacy operations (e.g., privacy notice management software and customer management solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with PRI domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to maintain a process for data subjects to appeal an adverse decision.

Level 4 — Quantitatively Controlled

Privacy (PRI) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

Level 5 — Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

Assessment Objectives

  1. PRI-39.5_A01 a process for receiving & acknowledging complaints, concerns or questions from individuals about organizational cybersecurity / data privacy practices is implemented.
  2. PRI-39.5_A02 a process for responding to complaints, concerns or questions from individuals about organizational cybersecurity / data privacy practices is implemented.
  3. PRI-39.5_A03 the time period in which complaints (including concerns or questions) from individuals are to be reviewed and acknowledging is defined.
  4. PRI-39.5_A04 the time period in which complaints (including concerns or questions) from individuals are to be addressed is defined.
  5. PRI-39.5_A05 the complaint management process includes mechanisms that are easy to use by the public.
  6. PRI-39.5_A06 the complaint management process includes mechanisms that are readily accessible by the public.
  7. PRI-39.5_A07 the complaint management process includes all information necessary for successfully filing complaints.
  8. PRI-39.5_A08 the complaint management process includes tracking mechanisms to ensure that all complaints are reviewed within an organization-defined time period.
  9. PRI-39.5_A09 the complaint management process includes tracking mechanisms to ensure that all complaints are addressed within an organization-defined time period.
  10. PRI-39.5_A10 the complaint management process includes acknowledging the receipt of complaints, concerns or questions from individuals within an organization-defined time period.
  11. PRI-39.5_A11 the complaint management process includes responding to complaints, concerns or questions from individuals within an organization-defined time period.

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.