{"data":{"id":"PT-04","name":"Consent","family":"PT","family_name":"Personally Identifiable Information Processing and Transparency","withdrawn":false,"description":"Implement [Assignment: organization-defined tools or mechanisms] for individuals to consent to the processing of their personally identifiable information prior to its collection that facilitate individuals’ informed decision-making.","supplemental_guidance":"Consent allows individuals to participate in making decisions about the processing of their information and transfers some of the risk that arises from the processing of personally identifiable information from the organization to an individual. Consent may be required by applicable laws, executive orders, directives, regulations, policies, standards, or guidelines. Otherwise, when selecting consent as a control, organizations consider whether individuals can be reasonably expected to understand and accept the privacy risks that arise from their authorization. Organizations consider whether other controls may more effectively mitigate privacy risk either alone or in conjunction with consent. Organizations also consider any demographic or contextual factors that may influence the understanding or behavior of individuals with respect to the processing carried out by the system or organization. When soliciting consent from individuals, organizations consider the appropriate mechanism for obtaining consent, including the type of consent (e.g., opt-in, opt-out), how to properly authenticate and identity proof individuals and how to obtain consent through electronic means. In addition, organizations consider providing a mechanism for individuals to revoke consent once it has been provided, as appropriate. Finally, organizations consider usability factors to help individuals understand the risks being accepted when providing consent, including the use of plain language and avoiding technical jargon.","enhancements":[{"id":"PT-04(01)","name":"Tailored Consent","statement":"Provide [Assignment: organization-defined mechanisms] to allow individuals to tailor processing permissions to selected elements of personally identifiable information.","baselines":[]},{"id":"PT-04(02)","name":"Just-in-time Consent","statement":"Present [Assignment: organization-defined consent mechanisms] to individuals at [Assignment: organization-defined frequency] and in conjunction with [Assignment: organization-defined personally identifiable information processing].","baselines":[]},{"id":"PT-04(03)","name":"Revocation","statement":"Implement [Assignment: organization-defined tools or mechanisms] for individuals to revoke consent to the processing of their personally identifiable information.","baselines":[]}],"baseline_low":false,"baseline_moderate":false,"baseline_high":false,"nist_800_53":{"rev5":{"id":"PT-04","name":"Consent","description":"Implement [Assignment: organization-defined tools or mechanisms] for individuals to consent to the processing of their personally identifiable information prior to its collection that facilitate individuals’ informed decision-making.","discussion":"Consent allows individuals to participate in making decisions about the processing of their information and transfers some of the risk that arises from the processing of personally identifiable information from the organization to an individual. Consent may be required by applicable laws, executive orders, directives, regulations, policies, standards, or guidelines. Otherwise, when selecting consent as a control, organizations consider whether individuals can be reasonably expected to understand and accept the privacy risks that arise from their authorization. Organizations consider whether other controls may more effectively mitigate privacy risk either alone or in conjunction with consent. Organizations also consider any demographic or contextual factors that may influence the understanding or behavior of individuals with respect to the processing carried out by the system or organization. When soliciting consent from individuals, organizations consider the appropriate mechanism for obtaining consent, including the type of consent (e.g., opt-in, opt-out), how to properly authenticate and identity proof individuals and how to obtain consent through electronic means. In addition, organizations consider providing a mechanism for individuals to revoke consent once it has been provided, as appropriate. Finally, organizations consider usability factors to help individuals understand the risks being accepted when providing consent, including the use of plain language and avoiding technical jargon.","related_controls":["AC-16","PT-02","PT-05"],"baseline_low":false,"baseline_moderate":false,"baseline_high":false,"baseline_privacy":true,"new_in_rev5":true,"changes_from_rev4":"New control family introduced in Rev 5"}},"compliance_mappings":{"iso_27001_2022":["A.5.34"],"iso_27002_2022":["5.34"],"cobit_2019":["APO14"],"pci_dss_v4":[],"nist_csf_2":[],"cis_controls_v8":["CIS 3"],"soc2_tsc":[],"finos_ccc":[],"iso_42001_2023":["A.7.3"],"iec_62443":[],"asd_e8":[],"nis2":[],"apra_cps_234":[],"mas_trm":[],"pra_op_resilience":[],"bsi_grundschutz":["CON.2"],"anssi":["SecNumCloud.19.3"],"osfi_b13":[],"finma_circular":["IV.D(78)"],"gdpr":["Art.5(1)(a)","Art.6(1)(a)","Art.7(1)","Art.7(2)","Art.7(3)","Art.8(1)"],"dora":[],"bio2":["5.34"],"rbi_csf":["Annex1.15"],"fisc":[],"lgpd_bcb":[],"hkma_tme1":[],"mlps_2":[],"dnb_good_practice":[],"cra":[],"swift_cscf":[],"cbuae":["CR-5"],"cbe_csf":["CTO-2"],"popia":["s5","s11","s34-35","s69"],"sa_js2":["JS2-8.2"],"bot_cyber":["Ch2.3","Ch9.2"],"nydfs_500":["500.18"],"sebi_cscrf":["DATALOC"],"nerc_cip":[],"nrc_73_54":[],"tsa_psd":[],"ieee_1686":[],"ferc_cip":[],"doe_c2m2":[],"api_1164":[],"awia":[],"iaea_nss":[],"pci_pts":[],"fips_140":[],"cbest":[],"tiber_eu":[],"pci_hsm":[],"common_criteria":["CC Part 2 — FPR"],"isae_3402":[],"fca_sysc_13":[],"fda_21_cfr_11":[],"fda_cyber":[],"hitrust_csf":["06.b","13.b","13.e"],"iso_27799":["16.3","18.1","18.2","H.4"],"lloyds_ms":["MS7.1","MS8.7"],"naic_ds":["3","6-b","8"],"nhs_dspt":["NDG-1.3"],"pra_ss1_23":[],"solvency_ii":["Art.49(3)","EIOPA-Cloud-GL9"],"owasp_masvs_v2":["MASVS-PRIVACY-3","MASVS-PRIVACY-4"],"csa_ccm_v4":["DSP-11"],"csa_aicm":["DSP-11","DSP-23"],"ccss_v9":[],"mica":["Art.62(9)","Art.98(1)"],"basel_sco60":[],"bssc":[],"sec_custody_digital":[],"dpdpa":["Act.4","Act.5(1)","Act.6(1)","Act.6(3)","Act.6(4)","Act.6(6)","Act.6(7)-(9)","Act.9(1)","Rules.3","Rules.4","Rules.10","Rules.11"]},"attack_techniques":[],"metadata":{"last_reviewed":"2026-10-03","review_notes":"2026-10-03: statement, discussion and related controls taken from NIST SP 800-53 Release 5.2.0, which this file lacked.","mapping_status":"complete"},"function":"preventative","used_by_patterns":["SP-039","SP-045","SP-050"]}}