PRI-21: Data Privacy Notice
Mechanisms exist to: (1) Make data privacy notice(s) available to individuals upon first interacting with an organization and subsequently as necessary; (2) Ensure that data privacy notices are clear and easy-to-understand, expressing relevant information about how Personal Data (PD) is collected, received, processed, stored, transmitted, shared, updated and/or disposed; (3) Contain all necessary notice-related criteria required by applicable statutory, regulatory and contractual obligations; (4) Define the scope of PD processing activities, including the geographic locations and third-party recipients that process the PD within the scope of the data privacy notice; (5) Periodically, review and update the content of the privacy notice, as necessary; and (6) Retain prior versions of the privacy notice, in accordance with data retention requirements.
Renumbered: Formerly PRI-02 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, PRI-21 was Notice of Right To Opt-Out. That control is now PRI-26.
Control Question: Does the organization: (1) Make data privacy notice(s) available to individuals upon first interacting with an organization and subsequently as necessary; (2) Ensure that data privacy notices are clear and easy-to-understand, expressing relevant information about how Personal Data (PD) is collected, received, processed, stored, transmitted, shared, updated and/or disposed; (3) Contain all necessary notice-related criteria required by applicable statutory, regulatory and contractual obligations; (4) Define the scope of PD processing activities, including the geographic locations and third-party recipients that process the PD within the scope of the data privacy notice; (5) Periodically, review and update the content of the privacy notice, as necessary; and (6) Retain prior versions of the privacy notice, in accordance with data retention requirements?
General (16)
| Framework | Mapping Values |
|---|---|
| AICPA Privacy Management Framework (PMF) | M1.0-POF1 N2.1 N2.1-POF2 N2.1-POF3 N2.1-POF4 N2.2 C3.1-POF3 M9.1-POF1 |
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC2.3-POF7 P1.1 P1.1-POF1 P1.1-POF2 P1.1-POF3 P1.1-POF4 P1.1-POF5 P1.1-POF7 |
| APEC Privacy Framework 2015 | 2 2(a) 2(b) 2(c) 2(d) 2(e) |
| CSA CCM 4.1.0 | DSP-14 |
| ISO 27002 2022 | 5.34 |
| ISO 27018 2025 | 5.34 |
| ISO 29100 2024 | 6.3 |
| NIST 800-53 R4 | TR-1 TR-2 |
| NIST 800-53 R5.2 | PM-20(01) PT-05 |
| NIST 800-53B R5 (privacy) (source) | PM-20(01) PT-05 |
| NIST 800-82 R3 | PM-20(01) PT-05 |
| NIST 800-82 R3 LOW OT Overlay | PM-20(01) |
| NIST 800-82 R3 MODERATE OT Overlay | PM-20(01) |
| NIST 800-82 R3 HIGH OT Overlay | PM-20(01) |
| NIST Privacy Framework 1.0 | CM.PO-P1 CM.AW-P1 |
| SCF DPMP 2026 | 4.0 |
US (17)
| Framework | Mapping Values |
|---|---|
| USA Federal CMS MARS-E 2.0 | TR-1 TR-1.a TR-1.a.1 TR-1.a.2 TR-1.a.3 TR-1.a.4 TR-1.b TR-1.b.1 TR-1.b.2 TR-1.b.3 TR-1.b.4 TR-1.b.5 TR-1.b.6 TR-1.c |
| USA Federal Data Privacy Framework 2023 | II.1.a.i II.1.a.ii II.1.a.iii II.1.a.iv II.1.a.v II.1.a.vi II.1.a.vii II.1.a.viii II.1.a.ix II.1.a.x II.1.a.xi II.1.a.xii II.1.a.xiii II.1.b III.11.d.i III.11.d.ii III.14.b.ii |
| USA Federal 45 CFR 155.260 | 155.260(a)(3)(iii) |
| USA Federal COPPA 2024 | Sec. 6502.(b)(1)(A)(i) |
| USA Federal HIPAA Administrative Simplification 2013 | § 164.520(a)(1) § 164.520(a)(2)(i) § 164.520(a)(2)(i)(A) § 164.520(a)(2)(i)(B) § 164.520(a)(2)(ii) § 164.520(a)(2)(ii)(A) § 164.520(a)(2)(ii)(B) § 164.520(a)(2)(iii) § 164.520(b)(1) § 164.520(b)(1)(i) § 164.520(b)(1)(ii) § 164.520(b)(1)(ii)(A) § 164.520(b)(1)(ii)(B) § 164.520(b)(1)(ii)(C) § 164.520(b)(1)(ii)(D) § 164.520(b)(1)(ii)(E) § 164.520(b)(1)(iv) § 164.520(b)(1)(iv)(A) § 164.520(b)(1)(iv)(B) § 164.520(b)(1)(iv)(C) § 164.520(b)(1)(iv)(D) § 164.520(b)(1)(iv)(E) § 164.520(b)(1)(iv)(F) § 164.520(b)(1)(v) § 164.520(b)(1)(v)(A) § 164.520(b)(1)(v)(B) § 164.520(b)(1)(v)(C) § 164.520(b)(1)(vi) § 164.520(b)(1)(vii) § 164.520(b)(1)(viii) § 164.520(b)(2)(i) § 164.520(b)(2)(ii) § 164.520(b)(3) § 164.520(c) § 164.520(c)(1)(i) § 164.520(c)(1)(i)(A) § 164.520(c)(1)(i)(B) § 164.520(c)(1)(ii) § 164.520(c)(1)(iii) § 164.520(c)(1)(iv) § 164.520(c)(1)(v) § 164.520(c)(1)(v)(A) § 164.520(c)(1)(v)(B) § 164.530(i)(4)(i)(C) |
| USA Federal FIPPS 1973 | 7.0 8.0 |
| USA California CCPA 2025 | 7002(b)(5) 7003(a) 7004(a)(1) 7010(a) 7011(a) 7011(b) 7011(c) 7011(d) 7011(e) 7011(e)(1) 7011(e)(1)(A) 7011(e)(1)(B) 7011(e)(1)(C) 7011(e)(1)(D) 7011(e)(1)(E) 7011(e)(1)(F) 7011(e)(1)(G) 7011(e)(1)(H) 7011(e)(1)(I) 7011(e)(1)(J) 7011(e)(2) 7011(e)(2)(A) 7011(e)(2)(B) 7011(e)(2)(C) 7011(e)(2)(D) 7011(e)(2)(E) 7011(e)(2)(F) 7011(e)(2)(G) 7011(e)(2)(H) 7011(e)(3) 7011(e)(3)(A) 7011(e)(3)(B) 7011(e)(3)(C) 7011(e)(3)(D) 7011(e)(3)(E) 7011(e)(3)(F) 7011(e)(3)(G) 7011(e)(3)(H) 7011(e)(3)(I) 7011(e)(3)(J) 7011(e)(4) 7011(e)(5) 7012(f) 7012(g)(1) 7013(c) 7013(e) 7013(e)(1) 7013(e)(2) 7013(e)(3) 7013(g)(2) 7014(b) 7014(c) 7014(d) 7014(e)(1) 7014(e)(2) 7014(e)(3) 7014(g)(1) 7014(g)(2) 7014(h) 7025(g)(2) 7025(g)(2)(A) 7025(g)(2)(B) 7025(g)(2)(C) 7025(g)(2)(D) 7072(a) |
| USA Colorado Colorado Privacy Act 2021 | 6-1-1308(1)(a) 6-1-1308(1)(a)(III) 6-1-1308(1)(a)(IV) 6-1-1308(1)(a)(V) 6-1-1308(1)(b) 6-1-1308(2) |
| USA Illinois BIPA 2008 | 15(a) 15(b)(1) 15(b)(2) |
| USA Illinois IPA 2009 | 35(a)(5) 37(a)(5) |
| USA Montana CDPA 2025 | 30-14-2808(2) 30-14-2812(4) 30-14-2812(5) 30-14-2812(5)(c) 30-14-2812(5)(d) 30-14-2812(5)(e) 30-14-2812(5)(f) 30-14-2812(5)(g) 30-14-2812(8) 30-14-2815(1)(b) |
| USA Nevada Privacy Law 2023 | 603A.340.1 603A.340.1(b) 603A.340.1(c) 603A.340.1(d) 603A.340.1(e) 603A.345.1 603A.346.1 603A.495.1 603A.495.1(a) 603A.495.1(b) 603A.495.1(c) 603A.495.1(d) 603A.495.1(e) 603A.495.1(f) 603A.495.1(g) 603A.495.1(h) 603A.495.1(i) 603A.495.1(j) 603A.495.1(k) 603A.495.2 |
| USA Oregon CPA 2023 | Section 5(1)(a) Section 5(4)(a) Section 5(4)(b) Section 5(4)(c) Section 5(4)(d) Section 5(4)(e) Section 5(4)(f) Section 5(4)(g) Section 5(4)(h) Section 5(4)(i) |
| USA Oregon 646A 2025 | 646A.578(1)(a) 646A.578(4) 646A.578(4)(a) 646A.578(4)(b) 646A.578(4)(c) 646A.578(4)(d) 646A.578(4)(e) 646A.578(4)(f) 646A.578(4)(g) 646A.578(4)(h) 646A.578(4)(i) 646A.578(5)(b) 646A.583(1)(a)(B) |
| USA Tennessee TIPA 2025 | 47-18-3204(a)(1) 47-18-3204(c) 47-18-3204(c)(1) 47-18-3204(c)(2) 47-18-3204(c)(3) 47-18-3204(c)(4) 47-18-3204(c)(5) 47-18-3204(d) 47-18-3204(e)(1) |
| USA Texas CDPA 2025 | 541.053(b) 541.055(c) 541.055(d) 541.102(a)(1) 541.102(a)(2) 541.102(a)(3) 541.102(a)(4) 541.102(a)(5) 541.102(a)(6) 541.102(b) 541.103 541.106(a)(2) |
| USA Virginia CDPA 2023 | 59.1-578.C 59.1-578.C.1 59.1-578.C.2 59.1-578.C.3 59.1-578.C.4 59.1-578.C.5 59.1-578.D 59.1-578.E 59.1-581.A.2 |
EMEA (25)
| Framework | Mapping Values |
|---|---|
| EMEA Austria FAPPD 2000 | § 43(1) § 43(2) § 43(3) § 43(4) |
| EMEA Belgium Act 8 1992 | Title 2, Chapter III, Art. 37(1) Title 2, Chapter III, Art. 37(2) Title 4, Chapter III, Section 1, Art. 193 |
| EMEA Switzerland FADP 2025 | 2.2.15.3 3.19.1 3.19.2 3.19.2.a 3.19.2.b 3.19.2.c 3.19.3 3.19.4 3.19.5 3.21.1 |
| EMEA Germany FDPA 2017 | 3.2.51(4) 3.3.55 3.3.55.1 3.3.55.2 3.3.55.3 3.3.55.4 3.3.55.5 3.3.56(1) 3.3.56(1)1 3.3.56(1)2 3.3.56(1)3 3.3.56(1)4 3.3.56(1)5 3.3.56(2)1 3.3.56(2)2 3.3.56(2)3 3.3.56(3) |
| EMEA Spain CCN-STIC 825 | mp.info.1 |
| EMEA EU GDPR 2016 | Article 12.7 Article 13.1(a) Article 13.1(b) Article 13.1(c) Article 13.1(d) Article 13.1(e) Article 13.2 Article 13.2(a) Article 13.2(b) Article 13.2(c) Article 13.2(d) Article 13.2(e) Article 13.2(f) Article 13.3 Article 14.1(a) Article 14.1(b) Article 14.1(c) Article 14.1(d) Article 14.1(e) Article 14.1(f) Article 14.2 Article 14.2(a) Article 14.2(b) Article 14.2(c) Article 14.2(d) Article 14.2(e) Article 14.2(f) Article 14.2(g) Article 14.3(a) Article 14.3(b) Article 14.3(c) Article 14.4 Article 14.5(a) |
| EMEA UK DEFSTAN 05-138 2024 | 2406 2407 |
| EMEA UK DEFSTAN 05-138 - L1 2024 | 2407 |
| EMEA UK DEFSTAN 05-138 - L2 2024 | 2406 2407 |
| EMEA UK DEFSTAN 05-138 - L3 2024 | 2406 2407 |
| EMEA UK DPA 2018 | Section 44(1) Section 44(1)(a) Section 44(1)(b) Section 44(1)(c) Section 44(1)(d) Section 44(1)(d)(i) Section 44(1)(d)(ii) Section 44(1)(d)(iii) Section 44(1)(e) Section 44(2) Section 44(2)(b) Section 44(2)(c) Section 44(2)(d) Section 44(3) Section 69(4) |
| EMEA Greece PIRPPD 1997 | C.11.1 C.11.1.a C.11.1.b C.11.1.c C.11.1.d C.11.2 C.11.3 |
| EMEA Hungary Act CXII 2011 | II.5.6(4) II.7.8(1)(a) II.14.20(1) II.14.20(2) II.14.20(4)(a) II.14.20(4)(b) II.14.20(4)(d) |
| EMEA Ireland DPA 2018 | s.90 |
| EMEA Israel PPL 2025 | s.11 |
| EMEA Italy PDPC 2018 | Article 2-d(2) Article 77(1)(a) Article 77(1)(b) Article 78(1) Article 78(2) Article 78(3) Article 132-c(1) |
| EMEA Kenya DPA 2019 | IV.25(e) IV.26(a) IV.29 IV.29(a) IV.29(b) IV.29(c) IV.29(d) IV.29(e) IV.29(f) IV.29(g) IV.29(h) |
| EMEA Nigeria DPR 2019 | 2.3(1) 2.5 2.5(a) 2.5(b) 2.5(c) 2.5(d) 2.5(e) 2.5(f) 2.5(g) 2.5(h) 2.5(i) 3.1(1) 3.1(7) 3.1(7)(a) 3.1(7)(b) 3.1(7)(c) 3.1(7)(d) 3.1(7)(e) 3.1(7)(f) 3.1(7)(g) 3.1(7)(h) 3.1(7)(i) 3.1(7)(j) 3.1(7)(k) 3.1(7)(l) 3.1(7)(m) 3.1(7)(n) 3.1(8) |
| EMEA Poland Act 10 2018 | Art. 11 |
| EMEA Qatar PDPPL 2020 | 3.9 3.9.1 3.9.2 3.9.3 3.9.4 4.17.1 |
| EMEA Russia 152-FZ 2025 | Art. 18 |
| EMEA Saudi Arabia PDPL | Article 4.1 Article 12 Article 13.2 Article 13.4 Article 13.5 Article 13.6 |
| EMEA Serbia 87/2018 | III.1.21 III.2.23-1 III.2.23-1(1) III.2.23-1(2) III.2.23-1(3) III.2.23-1(4) III.2.23-1(5) III.2.23-1(6) III.2.23-2 III.2.23-2(1) III.2.23-2(2) III.2.23-2(3) III.2.23-2(4) III.2.23-2(5) III.2.23-2(6) III.2.24-1 III.2.24-1(1) III.2.24-1(2) III.2.24-1(3) III.2.24-1(4) III.2.24-1(5) III.2.24-1(6) III.2.24-2 III.2.24-2(1) III.2.24-2(2) III.2.24-2(3) III.2.24-2(4) III.2.24-2(5) III.2.24-2(6) III.2.24-2(7) III.2.24-3 III.2.24-3(1) III.2.24-3(2) III.2.24-3(3) |
| EMEA Turkey LDDP 2016 | 10(1) 10(1)(a) 10(1)(b) 10(1)(c) 10(1)(ç) 10(1)(d) 11(1) 11(1)(a) 11(1)(b) 11(1)(c) 11(1)(ç) 11(1)(d) 11(1)(e) 11(1)(f) 11(1)(g) 11(1)(ğ) |
| EMEA South Africa POPIA 2013 | 3.A.3.13(1) 3.A.3.13(2) |
APAC (15)
| Framework | Mapping Values |
|---|---|
| APAC Australian Privacy Principles 2026 | 1.1.3 1.1.4 1.1.4.a 1.1.4.b 1.1.4.c 1.1.4.d 1.1.4.e 1.1.4.f 1.1.4.g 1.1.5 1.1.5.a 1.1.5.b 1.1.6 2.5.1 2.5.1.a 2.5.1.b 2.5.2 2.5.2.a 2.5.2.b 2.5.2.b.i 2.5.2.b.ii 2.5.2.c 2.5.2.d 2.5.2.e 2.5.2.f 2.5.2.g 2.5.2.h 2.5.2.i 2.5.2.j |
| APAC China Privacy Law 2021 | Article 17 Article 18 Article 30 Article 39 |
| APAC Hong Kong PDO 2022 | 35C(2) 35C(2)(a) 35C(2)(a)(i) 35C(2)(a)(ii) 35C(2)(b) 35C(2)(b)(i) 35C(2)(b)(ii) 35C(2)(c) 35C(3) 35C(4) 35C(5) 35J(2) 35J(2)(a) 35J(2)(a)(i) 35J(2)(a)(ii) 35J(2)(b) 35J(2)(b)(i) 35J(2)(b)(ii) 35J(2)(b)(iii) 35J(2)(b)(iv) 35J(2)(c) 35J(3) 35J(4) 35J(5) 35J(5)(a) 35J(5)(b) Schedule 1 - 1(3)(a) Schedule 1 - 1(3)(b)(ii)(B) Schedule 1 - 5 Schedule 1 - 5(a) Schedule 1 - 5(b) Schedule 1 - 5(c) |
| APAC India DPDPA 2023 | 5(1)(i) 5(1)(ii) 5(1)(iii) 5(2)(a)(i) 5(2)(a)(ii) 5(2)(a)(iii) 6(3) 6(10) |
| APAC India ITR 2011 | 4.0 4(i) 4(ii) 4(iii) 4(iv) 4(v) 5(3) 5(3)(a) 5(3)(b) 5(3)(c) 5(3)(d) 5(3)(d)(i) 5(3)(d)(ii) |
| APAC India RBI Digital Payments 2021 | 46.0 |
| APAC India RBI PA 2025 | III.8.c |
| APAC Japan APPI 2020 | IV.1.18(1) IV.1.18(2) IV.1.18(3) IV.1.23(2) IV.1.23(2)(i) IV.1.23(2)(ii) IV.1.23(2)(iii) IV.1.23(2)(iv) IV.1.23(2)(v) IV.1.23(2)(vi) IV.1.23(2)(vii) IV.1.23(2)(viii) IV.1.27(1) IV.1.27(1)(i) IV.1.27(1)(ii) IV.1.27(1)(iii) IV.1.27(1)(iv) |
| APAC South Korea PIPA 2011 | III.1.18(3) III.1.18(3)1 III.1.18(3)2 III.1.18(3)3 III.1.18(3)4 III.1.18(3)5 IV.30(1) IV.30(1)1 IV.30(1)2 IV.30(1)3 IV.30(1)4 IV.30(1)5 IV.30(1)6 IV.30(2) IV.30(3) |
| APAC Malaysia RMiT 2025 | 16.2(e) |
| APAC Malaysia PDPA 2010 | 7(1) 7(1)(a) 7(1)(b) 7(1)(c) 7(1)(d) 7(1)(e) 7(1)(f) 7(1)(g) 7(1)(h) 7(2) 7(2)(a) 7(2)(b) 7(2)(c) 7(2)(c)(i) 7(2)(c)(ii) |
| APAC New Zealand Privacy Act of 2020 | 3.1.22.3(1) 3.1.22.3(1)(a) 3.1.22.3(1)(b) 3.1.22.3(1)(c) 3.1.22.3(1)(d) 3.1.22.3(1)(d)(i) 3.1.22.3(1)(d)(ii) 3.1.22.3(1)(e) 3.1.22.3(1)(e)(i) 3.1.22.3(1)(e)(ii) 3.1.22.3(1)(f) 3.1.22.3(1)(g) 4.1.45(1) 4.1.45(1)(a) 4.1.45(1)(b) 4.1.45(1)(c) 4.1.45(2) |
| APAC Singapore MAS TRM 2021 | 14.4.1 |
| APAC Singapore PDPA 2012 | 3.11(5) 3.11(5A) 4.1.14(1)(a) 4.1.15A(4)(b) 4.1.15A(4)(b)(i) 4.1.15A(4)(b)(ii) 4.1.15A(4)(b)(iii) 4.2.20(1)(a) 4.2.20(1)(b) 4.2.20(1)(c) 4.2.20(2) |
| APAC Taiwan PDPA 2025 | I.8-1 I.8.1-1 I.8.2-1 I.8.3-1 I.8.4-1 I.8.5-1 I.8.6-1 I.8-2 I.8.1-2 I.8.2-2 I.8.3-2 I.8.4-2 I.8.5-2 I.8.6-2 I.9 I.9.1 I.9.2 I.9.3 I.9.4 I.9.5 |
Americas (5)
| Framework | Mapping Values |
|---|---|
| Americas Bahamas DPA 2003 | II.8(1) II.8(1)(a) II.8(1)(b) II.8(1)(c) II.8(1)(d) II.8(1)(e) II.8(1)(f) II.8(1)(g) II.8(1)(g)(i) II.8(1)(g)(ii) II.8(1)(g)(iii) II.8(1)(h) II.8(1)(i) II.8(2) II.8(2)(a) II.8(2)(b) IV.24(1)(a) IV.24(1)(b) IV.24(1)(b)(i) IV.24(1)(b)(ii) IV.24(1)(b)(iii) IV.24(1)(b)(iv) IV.24(1)(b)(v) IV.24(1)(c) IV.24(1)(c)(i) IV.24(1)(c)(ii) IV.24(1)(c)(iii) IV.24(1)(d) IV.24(1)(e) IV.24(1)(f) IV.24(1)(g) V.45(8) V.52(3) |
| Americas Brazil LGPD 2018 | II.I.9 II.I.9.I II.I.9.II II.I.9.III II.I.9.IV II.I.9.V II.I.9.VI II.I.9.VII II.I.9.VII.1 |
| Americas Canada PIPEDA 2000 | P2-4.2 P2-4.2.1 P2-4.2.2 P2-4.2.3 P8-4.8 P8-4.8.1 P8-4.8.2 P8-4.8.2(a) P8-4.8.2(b) P8-4.8.2(c) P8-4.8.2(d) P8-4.8.2(e) P8-4.8.3 |
| Americas Colombia Law 1581 2012 | VI.17(c) |
| Americas Mexico FDPA 2010 | II.7 II.12 II.15 II.16 II.16.I II.16.II II.16.III II.16.IV II.16.V II.16.VI II.17 II.17.I II.17.II II.18 V.36 |
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. ▪ The CPO, or similar role, develops and ensures data privacy notices are published that include relevant purpose, notice and data privacy program information.
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: (1) Make data privacy notice(s) available to individuals upon first interacting with an organization and subsequently as necessary; (2) Ensure that data privacy notices are clear and easy-to-understand, expressing relevant information about how Personal Data (PD) is collected, received, processed, stored, transmitted, shared, updated and/or disposed; (3) Contain all necessary notice-related criteria required by applicable statutory, regulatory and contractual obligations; (4) Define the scope of PD processing activities, including the geographic locations and third-party recipients that process the PD within the scope of the data privacy notice; (5) Periodically, review and update the content of the privacy notice, as necessary; and (6) Retain prior versions of the privacy notice, in accordance with data retention 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
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. ▪ Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes. ▪ Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions via Artificial Intelligence (AI) or Machine Learning (ML) technologies.
Assessment Objectives
- PRI-21_A01 privacy notice(s) are developed and posted on all external-facing websites.
- PRI-21_A02 privacy notice(s) are developed and posted on all mobile applications.
- PRI-21_A03 privacy notice(s) are developed and posted on all other digital services.
- PRI-21_A04 the privacy notice(s) are written in plain language.
- PRI-21_A05 the privacy notice(s) are organized in a way that is easy to understand and navigate.
- PRI-21_A06 the privacy notice(s) provide the information needed by the public to make an informed decision about whether to interact with the organization.
- PRI-21_A07 the privacy notice(s) provide the information needed by the public to make an informed decision about how to interact with the organization.
- PRI-21_A08 the privacy notice(s) are updated whenever the organization makes a substantive change to the practices it describes.
- PRI-21_A09 the privacy notice(s) include a time/date stamp to inform the public of the date of the most recent changes.
- PRI-21_A10 the frequency at which a notice is provided to individuals after initial interaction with an organization is defined.
- PRI-21_A11 information to be included with the notice about the processing of Personal Data (PD) is defined.
- PRI-21_A12 a notice to individuals about the processing of Personal Data (PD) is provided such that the notice is available to individuals upon first interacting with an organization.
- PRI-21_A13 a notice to individuals about the processing of Personal Data (PD) is provided such that the notice is subsequently available to individuals frequency.
- PRI-21_A14 a notice to individuals about the processing of Personal Data (PD) is provided that is clear, easy-to-understand and expresses information about Personal Data (PD) processing in plain language.
- PRI-21_A15 a notice to individuals about the processing of Personal Data (PD) that identifies the authority that authorizes the processing of Personal Data (PD) is provided.
- PRI-21_A16 a notice to individuals about the processing of Personal Data (PD) that identifies the purpose for which Personal Data (PD) is to be processed is provided.
- PRI-21_A17 a notice to individuals about the processing of Personal Data (PD) which includes information is provided.
Evidence Requirements
- E-PRI-08 Data Privacy Notice
-
Documented evidence of a publicly-accessible data privacy notice.
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