800-53 · PT PII Processing and Transparency
PT-3
Personally Identifiable Information Processing Purposes
frameworkNIST SP 800-53 Rev 5.2
sectionPT PII Processing and Transparency
csf 2.0—
topics—
frameworks1 0 12
Official texta. 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].NIST SP 800-53 Rev 5.2 control statement (public domain)
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].NIST SP 800-53 Rev 5.2 control statement (public domain)
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | — | No requirement | No mapping in our data | No mapping in our data. |
| ISO 27001 | A.5.34 | Privacy and protection of PII | Crosswalk | NIST SP 800-53 → ISO 27001 mapping |
| CIS v8.1 | — | No requirement | No mapping in our data | No mapping in our data (most CIS links are editorial: CIS's published crosswalk covers 49 of 153 safeguards). |
| SOC 2 | — | No requirement | No mapping in our data | No mapping in our data (SOC 2 links are editorial only). |
| PCI DSS | — | No requirement | No mapping in our data | No mapping in our data. |
| CMMC | — | No requirement | No mapping in our data | No mapping in our data. |
| HIPAA | — | No requirement | No mapping in our data | No mapping in our data. |
| GDPR | — | No requirement | No mapping in our data | No mapping in our data (only GDPR's security articles are mapped, editorially). |
| NIS2 | — | No requirement | No mapping in our data | No mapping in our data. |
| Essential Eight | — | No requirement | No mapping in our data | No mapping in our data (Essential Eight links are editorial only). |
| DORA | — | No requirement | No mapping in our data | No mapping in our data (DORA links are editorial, and its technical standards are not mapped). |
| CPS 234 | — | No requirement | No mapping in our data | No mapping in our data (CPS 234 is principles-based and its links are editorial). |
| Cyber Essentials | — | No requirement | No mapping in our data | No mapping in our data (Cyber Essentials covers five technical controls only). |
Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.