Skip to main content

PRI-05: Documenting Data Processing Activities

PRI 8 — High Identify

Mechanisms exist to document Personal Data (PD) processing activities that covers collection, receiving, processing, storage, transmission, sharing, updating and/or disposal actions with sufficient detail to demonstrate conformity with applicable statutory, regulatory and contractual requirements.

Renumbered: Formerly PRI-14 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, PRI-05 was Personal Data (PD) Retention & Disposal. That control is now PRI-30.

Control Question: Does the organization document Personal Data (PD) processing activities that covers collection, receiving, processing, storage, transmission, sharing, updating and/or disposal actions with sufficient detail to demonstrate conformity with applicable statutory, regulatory and contractual requirements?

General (16)
US (3)
Framework Mapping Values
USA Federal CMS MARS-E 2.0 AR-6 DM-2(1)
USA Nevada Privacy Law 2023 603A.535.3 603A.535.3(a) 603A.535.3(b) 603A.535.3(c) 603A.535.3(d) 603A.535.3(e) 603A.535.3(f) 603A.535.3(g) 603A.535.3(h) 603A.535.3(i) 603A.535.8
USA Texas CDPA 2025 541.052(f)(1)
EMEA (13)
Framework Mapping Values
EMEA Austria FAPPD 2000 § 13(2) § 49(1) § 49(2) § 49(3) § 50(1) § 50(2) § 50(3) § 50(5)
EMEA Belgium Act 8 1992 Title 1, Section III, Art. 14(3) Title 2, Chapter III, Art. 45(5) Title 2, Chapter IV, Section 4, Art. 55(1) Title 2, Chapter IV, Section 4, Art. 55(2) Title 2, Chapter IV, Section 4, Art. 55(3) Title 2, Chapter IV, Section 4, Art. 56(1) Title 2, Chapter IV, Section 4, Art. 56(2) Title 2, Chapter IV, Section 4, Art. 56(3) Title 2, Chapter IV, Section 4, Art. 57 Title 2, Chapter IV, Section 4, Art. 58 Title 4, Chapter II, Art. 191 Title 4, Chapter II, Art. 192
EMEA Switzerland FADP 2025 2.1.12.1 2.1.12.2 2.1.12.2.a 2.1.12.2.b 2.1.12.2.c 2.1.12.2.d 2.1.12.2.e 2.1.12.2.f 2.1.12.2.g 2.1.12.3 2.2.15.1
EMEA Germany FDPA 2017 3.4.70(1) 3.4.70(1)1 3.4.70(1)2 3.4.70(1)3 3.4.70(1)4 3.4.70(1)5 3.4.70(1)6 3.4.70(1)7 3.4.70(1)8 3.4.70(1)9 3.4.70(2)1 3.4.70(2)2 3.4.70(2)3 3.4.70(4) 3.4.76(1) 3.4.76(1)1 3.4.76(1)2 3.4.76(1)3 3.4.76(1)4 3.4.76(1)5 3.4.76(1)6 3.4.76(2) 3.4.76(3) 3.4.76(4) 3.5.79(2)
EMEA EU AI Act Article 10.5(f)
EMEA EU GDPR 2016 Article 30.1 Article 30.1(a) Article 30.1(b) Article 30.1(c) Article 30.1(d) Article 30.1(e) Article 30.1(f) Article 30.1(g) Article 30.2 Article 30.2(a) Article 30.2(b) Article 30.2(c) Article 30.2(d) Article 30.3
EMEA UK DPA 2018 Section 61(1) Section 61(2) Section 61(2)(a) Section 61(2)(b) Section 61(2)(c) Section 61(2)(d) Section 61(2)(e) Section 61(2)(f) Section 61(2)(f)(i) Section 61(2)(f)(ii) Section 61(2)(g) Section 61(2)(h) Section 61(2)(h)(i) Section 61(2)(j) Section 61(2)(k) Section 61(3) Section 61(4) Section 61(4)(a) Section 61(4)(b) Section 61(4)(c) Section 61(4)(d) Section 61(4)(e) Section 61(4)(f) Section 61(5) Section 62(1) Section 62(1)(a) Section 62(1)(b) Section 62(1)(c) Section 62(1)(d) Section 62(1)(e) Section 62(1)(f) Section 62(2) Section 62(2)(a) Section 62(2)(b) Section 62(3) Section 62(3)(a) Section 62(3)(b) Section 62(3)(b)(i) Section 62(3)(b)(ii) Section 62(4) Section 62(4)(a) Section 62(4)(b) Section 62(4)(c) Section 62(4)(d) Section 62(5)
EMEA Hungary Act CXII 2011 II.13.15(2)
EMEA Ireland DPA 2018 s.81 s.82
EMEA Italy PDPC 2018 Article 110(2)
EMEA Nigeria DPR 2019 3.1(8)
EMEA Saudi Arabia PDPL Article 31 Article 31.1 Article 31.2 Article 31.3 Article 31.4 Article 31.5 Article 31.6
EMEA Serbia 87/2018 II.15 IV.1.47-2 IV.1.47-2(1) IV.1.47-2(2) IV.1.47-2(3) IV.1.47-2(4) IV.1.47-2(5) IV.1.47-2(6) IV.1.47-2(7) IV.1.47-2(8) IV.1.47-2(9) IV.1.47-3 IV.1.47-3(1) IV.1.47-3(2) IV.1.47-3(3) IV.1.47-3(4) IV.1.47-4 IV.1.47-4(1) IV.1.47-4(2) IV.1.47-4(3) IV.1.47-4(4)
APAC (3)
Framework Mapping Values
APAC Australian Privacy Principles 2026 3.6.5
APAC Hong Kong PDO 2022 27(1) 27(1)(a) 27(1)(b) 27(1)(c) 27(1)(c)(i) 27(1)(c)(ii) 27(2) 27(2)(a) 27(2)(b) 27(2)(c) 27(2)(d) 27(3) 27(3)(a) 27(3)(b) 27(3)(c) 27(3)(d) 27(4) 27(4)(a) 27(4)(b)
APAC Malaysia PDPA 2010 44(1)
Americas (3)
Framework Mapping Values
Americas Bahamas DPA 2003 V.43(1) V.43(2) V.43(2)(a) V.43(2)(b) V.43(2)(c) V.43(2)(d) V.43(2)(e) V.43(2)(f) V.43(2)(g) V.43(2)(h) V.43(2)(i) V.43(2)(j) V.43(3) V.43(4) V.43(4)(a) V.43(4)(b) V.43(4)(c)
Americas Brazil LGPD 2018 VI.I.37
Americas Canada PIPEDA 2000 P5-4.5.1

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

Privacy (PRI) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). 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. ▪ Standardized Operating Procedures (SOP) associated with PRI domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with PRI domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Data privacy management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Data privacy management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ The data privacy program is developed to work with IT and cybersecurity staff to ensure that applicable statutory, regulatory and/or contractual data privacy obligations for Personal Data (PD) are properly identified and implemented.

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 document Personal Data (PD) processing activities that covers collection, receiving, processing, storage, transmission, sharing, updating and/or disposal actions with sufficient detail to demonstrate conformity with applicable statutory, regulatory and contractual requirements.

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-05_A01 privacy reports are defined.
  2. PRI-05_A02 privacy oversight bodies are defined.
  3. PRI-05_A03 officials responsible for monitoring privacy program compliance are defined.
  4. PRI-05_A04 the frequency for reviewing and updating privacy reports is defined.
  5. PRI-05_A05 privacy reports are developed.
  6. PRI-05_A06 privacy reports are disseminated to oversight bodies to demonstrate accountability with statutory, regulatory and policy privacy mandates.
  7. PRI-05_A07 privacy reports are disseminated to officials.
  8. PRI-05_A08 privacy reports are disseminated to other personnel responsible for monitoring privacy program compliance.
  9. PRI-05_A09 privacy reports are reviewed / updated frequently.

Evidence Requirements

E-PRI-09 Record of Processing Activities (RoPA)

Documented evidence of Personal Data (PD) processing activities (e.g., Record of Processing Activities (RoPA)) including data lineage.

Privacy

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.