NIST SP 800-53 Rev 5
PT - PII Processing and Transparency

NIST SP 800-53 Rev 5 NIST800-PT-1: PT-1 Policy and Procedures

a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (one or more): organization-level; mission/business process-level; system-level] personally identifiable information processing and transparency policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the personally identifiable information processing and transparency policy and the associated personally identifiable information processing and transparency controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the personally identifiable information processing and transparency policy and procedures; and c. Review and update the current personally identifiable information processing and transparency: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 49 controls across 15 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

ISO 27701:2019 · 12 controls

  • 5.3.2 Policy
  • 5.3.3 Organizational roles, responsibilities and authorities
  • 5.5.4 Communication
  • 5.5.5 Documented information
  • 6.2.1 Management direction for information security
  • 7.2.6 Contracts with PII processors
  • 7.2.7 Joint PII controller
  • 7.3.1 Determining and fulfilling obligations to PII principals
  • 7.3.7 PII controllers' obligations to inform third parties
  • 7.4.2 Limit processing
  • 8.5.6 Disclosure of subcontractors used to process PII
  • 8.5.8 Change of subcontractor to process PII

ISO 27002:2022 · 5 controls

  • 5.1 Policies for information security
  • 5.2 Information security roles and responsibilities
  • 5.31 Legal, statutory, regulatory and contractual requirements
  • 5.34 Privacy and protection of PII
  • 5.36 Compliance with policies, rules and standards for information security

ISO 22301:2019 · 4 controls

  • 5.2.1 Establishing the business continuity policy
  • 5.2.2 Communicating the business continuity policy
  • 5.3 Roles, responsibilities and authorities
  • 7.5.1 General

ISO 27001:2022 · 4 controls

  • 5.1 Policies for information security
  • 5.2 Information security roles and responsibilities
  • 5.34 Privacy and protection of personal identifiable information (PII)
  • 5.36 Compliance with policies, rules and standards for information security

ISO/IEC 42001:2023 · 4 controls

  • 5.2 AI policy
  • 5.3 Roles, responsibilities and authorities
  • 7.5.1 General
  • A.8 Information for interested parties of AI systems

NIST Cybersecurity Framework 2.0 · 4 controls

  • NIST-CSF-GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission
  • NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced

SOC 2 · 4 controls

  • SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • SOC2-P1.1 P1.1 Privacy notice to data subjects
  • SOC2-P6.4 P6.4 Privacy commitments from vendors and third parties

APEC Cross-Border Privacy Rules (CBPR) System · 3 controls

APPI · 2 controls

  • APPI-A17 Specification of the Purpose of Use
  • APPI-A32 Matters Concerning Retained Personal Data to Be Made Accessible

Australia My Health Records Act 2012 · 2 controls

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-PS-1 Privacy Safeguard 1 - Open and transparent management of CDR data

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

  • CCM-DSP-01 Security and Privacy Policy and Procedures

GDPR · 1 control

NIST SP 800-161 Rev 1 · 1 control

PCI DSS 4.0 · 1 control

  • 12.1.1 12.1.1 Overall information security policy established and disseminated

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in PT - PII Processing and Transparency

You are reading one control. How much of NIST SP 800-53 Rev 5 have you already done?

NIST SP 800-53 Rev 5 NIST800-PT-1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-53 Rev 5 your existing evidence covers. Hold ISO 27001:2022 and 163 of 1014 NIST SP 800-53 Rev 5 controls already carry evidence.

If you hold ISO 27001:202216.1% covered · 851 gapsIf you hold ISO 27002:202210.8% covered · 904 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.110.2% covered · 911 gapsIf you hold CIS Controls v810.1% covered · 912 gapsIf you hold NIST SP 800-171 Rev 310.1% covered · 912 gapsIf you hold C5 (Germany)9.6% covered · 917 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 342 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 49 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll NIST SP 800-53 Rev 5 controls