NIST SP 800-53 Rev 5
RA - Risk Assessment

NIST SP 800-53 Rev 5 NIST800-RA-8: RA-8 Privacy Impact Assessments

Conduct privacy impact assessments for systems, programs, or other activities before: a. Developing or procuring information technology that processes personally identifiable information; and b. Initiating a new collection of personally identifiable information that: 1. Will be processed using information technology; and 2. Includes personally identifiable information permitting the physical or virtual (online) contacting of a specific individual, if identical questions have been posed to, or identical reporting requirements imposed on, ten or more individuals, other than agencies, instrumentalities, or employees of the federal government.

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

What else in your programme already covers this

This control maps to 48 controls across 13 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/IEC 42001:2023 · 13 controls

  • 6.1.4 AI system impact assessment
  • 8.2 AI risk assessment
  • 8.4 AI system impact assessment
  • A.2.2 AI policy
  • A.5 Assessing impacts of AI systems
  • A.5.2 AI system impact assessment process
  • A.5.3 Documentation of AI system impact assessments
  • A.5.4 Assessing AI system impact on individuals or groups of individuals
  • A.5.5 Assessing societal impacts of AI systems
  • A.7.4 Quality of data for AI systems
  • A.8 Information for interested parties of AI systems
  • A.9 Use of AI systems
  • A.9.3 Objectives for responsible use of AI system

ISO 27701:2019 · 12 controls

  • 5.4 Planning
  • 6.2.1 Management direction for information security
  • 7.2 Conditions for collection and processing
  • 7.2.5 Privacy impact assessment
  • 7.2.8 Records related to processing PII
  • 7.3.7 PII controllers' obligations to inform third parties
  • 7.4 Privacy by design and privacy by default
  • 7.4.1 Limit collection
  • 7.5.1 Identify basis for PII transfer between jurisdictions
  • 7.5.2 Countries and international organizations to which PII can be transferred
  • 8.4 Privacy by design and privacy by default
  • 8.5.1 Basis for PII transfer between jurisdictions

SOC 2 · 6 controls

  • SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)
  • SOC2-P1.1 P1.1 Privacy notice to data subjects
  • SOC2-P2.1 P2.1 Choice and consent
  • SOC2-P3.1 P3.1 Collecting personal information consistent with objectives
  • SOC2-P6.4 P6.4 Privacy commitments from vendors and third parties
  • SOC2-P7.1 P7.1 Quality of personal information

ISO 27001:2022 · 3 controls

  • 5.31 Legal, statutory, regulatory and contractual requirements
  • 5.34 Privacy and protection of personal identifiable information (PII)
  • 8.26 Application security requirements

ISO 27002:2022 · 3 controls

  • 5.31 Legal, statutory, regulatory and contractual requirements
  • 5.34 Privacy and protection of PII
  • 5.8 Information security in project management

EU AI Act · 2 controls

  • EUAI-Art.26 Obligations of deployers of high-risk AI systems
  • EUAI-Art.27 Fundamental rights impact assessment for high-risk AI systems

GDPR · 2 controls

CIS Controls v8 · 1 control

  • CIS-3.2 Establish and Maintain a Data Inventory

HIPAA Security Rule · 1 control

  • NIST-CSF-GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed

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 RA - Risk Assessment

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-RA-8 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.

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.

Query this from an agent

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