# PT-03 Personally Identifiable Information Processing Purposes

NIST SP 800-53 control. Family: PT Personally Identifiable Information Processing and Transparency. Function: preventative. Baselines: privacy. Mapping licence: CC BY-SA 4.0.

Statement: a. Identify and document the [Assignment: organization-defined purpose(s)] for processing personally identifiable information; b. Describe the purpose(s) in the public privacy notices and policies of the organization; c. Restrict the [Assignment: organization-defined processing] of personally identifiable information to only that which is compatible with the identified purpose(s); and d. Monitor changes in processing personally identifiable information and implement [Assignment: organization-defined mechanisms] to ensure that any changes are made in accordance with [Assignment: organization-defined requirements].
Guidance: Identifying and documenting the purpose for processing provides organizations with a basis for understanding why personally identifiable information may be processed. The term "process" includes every step of the information life cycle, including creation, collection, use, processing, storage, maintenance, dissemination, disclosure, and disposal. Identifying and documenting the purpose of processing is a prerequisite to enabling owners and operators of the system and individuals whose information is processed by the system to understand how the information will be processed. This enables individuals to make informed decisions about their engagement with information systems and organizations and to manage their privacy interests. Once the specific processing purpose has been identified, the purpose is described in the organization’s privacy notices, policies, and any related privacy compliance documentation, including privacy impact assessments, system of records notices, [PRIVACT] statements, computer matching notices, and other applicable Federal Register notices. Organizations take steps to help ensure that personally identifiable information is processed only for identified purposes, including training organizational personnel and monitoring and auditing organizational processing of personally identifiable information. Organizations monitor for changes in personally identifiable information processing. Organizational personnel consult with the senior agency official for privacy and legal counsel to ensure that any new purposes that arise from changes in processing are compatible with the purpose for which the information was collected, or if the new purpose is not compatible, implement mechanisms in accordance with defined requirements to allow for the new processing, if appropriate. Mechanisms may include obtaining consent from individuals, revising privacy policies, or other measures to manage privacy risks that arise from changes in personally identifiable information processing purposes.

## Enhancements (2)
- PT-03(01) Data Tagging
- PT-03(02) Automation
Each enhancement's statement: /api/v1/controls/PT-03?fields=enhancements

## Patterns that use it (5)
- Critical (2): SP-052 Decentralised Identity & Verifiable Credentials (draft); SP-054 CBDC and Digital Currency Infrastructure (draft)
- Important (3): SP-027 Secure LLM Usage; SP-039 Client-Side Encryption and Data Privacy; SP-045 AI Governance and Responsible AI

## Clauses by framework (44 frameworks)
- iso_27001_2022: A.5.34
- iso_27002_2022: 5.34
- cobit_2019: APO14
- cis_controls_v8: CIS 3
- soc2_tsc: P1.1-POF1
- iso_42001_2023: A.5.4, A.9.4
- bsi_grundschutz: CON.2
- anssi: Hygiene.8, SecNumCloud.19.3
- osfi_b13: B-13.1.3
- finma_circular: IV.D(78), IV.D(79), IV.D(80)
- gdpr: Art.5(1)(b), Art.6(4), Art.9(1), Art.9(2)
- bio2: 5.34
- rbi_csf: Annex1.15
- mlps_2: 8.1.4.11
- cra: CRA.I.2g
- cbb_tm: TM-9
- cbuae: CR-5
- nca_ecc: 2-7
- bom_ctrm: 3.10
- cbe_csf: CTO-2
- cbn_csf: Part3.4, Part7.1
- popia: s13, s15, s26-27
- sa_js2: JS2-8.2
- bcbs_239: Principle 4
- bot_cyber: Ch2.3, Ch9.2
- ecb_croe: CROE.2.3.3
- ffiec_is: II.C.16
- iosco_cyber: PROT-3
- nydfs_500: 500.13, 500.18
- sebi_cscrf: PR.DS
- tiber_eu: TIBER.CONF
- common_criteria: CC Part 2 — FPR
- hitrust_csf: 06.a, 13.a, 13.c
- iso_27799: 5.3, 8.2, 18.2
- lloyds_ms: MS7.1, MS8.7
- naic_ds: 3, 4-asset, 8
- nhs_dspt: NDG-1.1, NDG-5.4
- solvency_ii: Art.49(3)
- owasp_masvs_v2: MASVS-PRIVACY-1, MASVS-PRIVACY-3, MASVS-PRIVACY-4
- csa_ccm_v4: DSP-03, DSP-08, DSP-12, DSP-15
- csa_aicm: DSP-03, DSP-08, DSP-12, DSP-15, DSP-20, DSP-24, MDS-09
- mica: Art.62(9), Art.98(1)
- bssc: GSP-09
- dpdpa: Act.4, Act.5(1), Act.5(2), Act.6(1), Act.7, Rules.3, Rules.Sch2
OSA's mapping for iso_27001_2022 takes NIST's published crosswalk as its base. A clause not marked as OSA's own is in that crosswalk.

## More
- This control as JSON, with guidance and ATT&CK techniques: /api/v1/controls/PT-03
- Clauses only: /api/v1/controls/PT-03?fields=mappings
- Page for people: /controls/pt-03/
- Found an error? Open an issue at https://github.com/opensecurityarchitecture/osa-data/issues with the id, what OSA says and what the source says.