SOC 2
P - Privacy

SOC 2 SOC2-P4.1: P4.1 Limiting use to identified purposes

The privacy objectives name purposes, and personal information is put to no use beyond them. Points of focus: personal information serves only the purposes it was collected for and only with implicit or explicit consent, unless law requires otherwise.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 41 controls across 17 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 · 10 controls

  • 6.11.3 Test data
  • 7.2 Conditions for collection and processing
  • 7.2.1 Identify and document purpose
  • 7.3.10 Automated decision making
  • 7.4.2 Limit processing
  • 8.1 General
  • 8.2 Conditions for collection and processing
  • 8.2.2 Organization’s purposes
  • 8.2.3 Marketing and advertising use
  • 8.4 Privacy by design and privacy by default

APPI · 3 controls

  • APPI-A17 Specification of the Purpose of Use
  • APPI-A18 Restriction on Handling Beyond the Purpose of Use
  • APPI-A19 Prohibition of Improper Use
  • MYHR-CUD-2 Prohibition on unauthorised collection, use and disclosure
  • MYHR-CUD-3 Use limited to My Health Record purposes
  • MYHR-CUD-6 Prohibition on use for a prohibited purpose

CCPA/CPRA · 3 controls

  • CCR §7050 Service Provider and Contractor Obligations
  • §1798.100 General Duties of Businesses that Collect Personal Information
  • §1798.121 Right to Limit Use and Disclosure of Sensitive Personal Information

ISO/IEC 42001:2023 · 3 controls

  • 6.1.4 AI system impact assessment
  • 8.4 AI system impact assessment
  • A.5.4 Assessing AI system impact on individuals or groups of individuals

NIST SP 800-53 Rev 5 · 3 controls

  • NIST800-AC-16 AC-16 Security and Privacy Attributes
  • NIST800-PT-2 PT-2 Authority to Process Personally Identifiable Information
  • NIST800-PT-3 PT-3 Personally Identifiable Information Processing Purposes

GDPR · 2 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
  • AUCDR-PS-6 Privacy Safeguard 6 - Use or disclosure of CDR data

CMMC 2.0 · 1 control

  • CCM-DSP-12 Limitation of Purpose in Personal Data Processing

DORA · 1 control

EU AI Act · 1 control

  • EUAI-Art.59 Further processing of personal data for developing certain AI systems in the public interest in the AI regulatory sandbox

ISO 27001:2022 · 1 control

  • 5.34 Privacy and protection of personal identifiable information (PII)

ISO 27002:2022 · 1 control

  • 5.34 Privacy and protection of PII
  • 161R1-PM-25 Minimization of Personally Identifiable Information Used in Testing, Training, and Research

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 P - Privacy

You are reading one control. How much of SOC 2 have you already done?

SOC 2 SOC2-P4.1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of SOC 2 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 49 of 61 SOC 2 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. 193 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

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