SOC 2
PI - Processing Integrity

SOC 2 SOC2-PI1.1: PI1.1 Quality information about processing objectives, data definitions and specifications

Relevant, good-quality information about processing objectives, including what the processed data means and what products and services are specified to do, is obtained or generated, used and communicated to support use of the products and services. Points of focus: the information specifications needed to use products and services are identified; where data is supplied as part of a service or a reporting obligation, its definition is available to users and covers the population included, the nature of each element, sources, units of measure, accuracy and precision, uncertainty, the date or period observed and the inclusion and exclusion factors, is complete and accurate, and any metadata needed to understand it is described; and for goods, the information users need is available, clearly identifiable and validated.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 46 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.

NIST SP 800-53 Rev 5 · 6 controls

ISO 27002:2022 · 5 controls

  • 5.12 Classification of information
  • 5.13 Labelling of information
  • 5.14 Information transfer
  • 8.26 Application security requirements
  • 8.33 Test information

ISO/IEC 42001:2023 · 5 controls

  • A.7.2 Data for development and enhancement of AI system
  • A.7.3 Acquisition of data
  • A.7.4 Quality of data for AI systems
  • A.7.5 Data provenance
  • A.8.2 System documentation and information for users

HIPAA Security Rule · 4 controls

ISO 27001:2022 · 4 controls

  • 5.12 Classification of information
  • 5.14 Information transfer
  • 8.13 Information backup
  • 8.33 Test information
  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • NIST-CSF-GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated
  • NIST-CSF-ID.AM-07 Inventories of data and corresponding metadata for designated data types are maintained
  • NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

NIST SP 800-66 Rev 2 · 4 controls

PCI DSS 4.0 · 4 controls

  • 10.2.1 10.2.1 Audit logging enabled on all system components
  • 10.5.1 10.5.1 Keep logs 12 months, latest three months online
  • 3.2.1 3.2.1 Data retention and disposal minimise stored account data
  • 7.2.4 7.2.4 User accounts and privileges reviewed every six months

EU AI Act · 3 controls

NIST SP 800-218 · 2 controls

AICPA SOC 3 · 1 control

  • SOC3-PROC-INTEG Processing Integrity

C5 (Germany) · 1 control

  • C5-PI-01 Documentation and safety of input and output interfaces

FedRAMP High · 1 control

  • AU-6 Audit Record Review, Analysis, and Reporting

FedRAMP Moderate · 1 control

  • AU-6 Audit Record Review, Analysis, and Reporting

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 PI - Processing Integrity

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

SOC 2 SOC2-PI1.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 46 it maps to, and the evidence behind each claim, over MCP and REST.