Cookie settings

Necessary, always on: they keep the site working and remember your cookie choice.

Skip to content
Skip to content

SOC 2. Audit evidence.

SOC 2: data inventory and access evidence for your examination

A SOC 2 examination tests controls over security and, where included, confidentiality. IRIS produces evidence that supports your audit.

By Dipal Panchal, co-founder and CEO · Last reviewed: November 9, 2026

Overview

What a SOC 2 examination covers

A SOC 2 examination reports on controls at a service organization relevant to security, availability, processing integrity, confidentiality or privacy. Certified public accountants (CPAs) in public practice perform it, against the Trust Services Criteria of the American Institute of CPAs (AICPA).

The current criteria are the 2017 Trust Services Criteria, with points of focus revised in 2022. On October 26, 2026, the AICPA published exposure drafts of proposed 2027 criteria. Ask your auditor which version your report will use.

This page covers security and confidentiality, where data and access evidence help most. The criteria text sits behind an AICPA account, so the page describes categories and cites no criterion numbers. The content here is general information, not professional advice.

  • CPAs in public practice perform the examination
  • It reports on controls at a service organization
  • Your auditor decides which categories are in scope
  • NCA ECC and SAMA CSF, the Gulf frameworks, are out of scope here
  • For SaaS providers, see [technology and SaaS](/industries/technology-saas)
Requirements

What the examiner tests, and the evidence

Your auditor decides which criteria apply. The first two columns describe each category; the third is what IRIS produces. Capabilities vary by edition.

What the examiner tests, and the evidence
CategoryWhat the examiner testsEvidence IRIS producesWhat it also needs
SecurityControls cover the systems that hold sensitive data.Supports it: an inventory of sensitive data by source, table, column or file, each finding with its scan date.Hardware and software inventories from your other tools.
SecurityAccess to sensitive data is limited to authorized users.Access mapping shows who can reach each sensitive dataset, where the source exposes permission data.Your access rules. IRIS doesn’t grant, block or revoke access.
SecurityAccess is granted, changed and removed as people and roles change.Flags excessive, stale access (90-day default or a period you set) where activity is recorded; reviewers log decisions.The removal, in the source. On PostgreSQL, activity is tracked per database account unless audit logging is turned on.
SecuritySensitive data is protected where it is stored.Checks sampled sensitive-column values for encryption, masking, hashing or plain form, once activated on your install.Applying the protection. IRIS detects protection and doesn’t apply it.
ConfidentialityYou know where confidential information sits and keep it protected.Supports it: findings by data type and location, including data found outside the systems you expected.Your definition of confidential under your commitments.
ConfidentialityConfidential information is disposed of when it is due.A later complete scan of the same scope records whether the data is still there, with both scan dates.The disposal, in your systems, and the rule that says when.
Either categoryThe evidence covers the systems in the report’s scope.A coverage record for each scan, and an evidence register you can review and export as CSV or XLSX. See audit evidence.The system description. Your auditor decides whether a criterion is met.
Availability, processing integrity and privacyUptime, complete processing, and the handling of personal information.IRIS doesn’t do this.Evidence from your operations, change and privacy tools.

Five findings, sorted for an examination

How a reviewer reads what a scan finds in one service organization’s systems. The labels are examples of a scheme you would set yourself.

Records
SourceLocationDetected typeWhySensitivityDecision
Production databasecustomers.contact_emailEmail addressCustomer data in scope for confidentiality commitmentsConfidentialKept
Support file share/exports/tickets_2024.csvName and phone numberA customer export outside the system you expectedConfidentialKept
Analytics warehousedw.events.user_refEmail addressStored in plain form; check against your protection ruleConfidentialKept
Reporting databasearchive_2021.accountsName and postal addressPast your disposal rule; delete, then re-scanConfidentialKept
Staging databaseseed.demo_usersEmail addressOnly example.com addresses; generated demo dataNoneRejected
Questions

Questions SOC 2 auditors ask about data

Where does confidential data sit?

Evidence from IRIS: an inventory by source, table, column or file, each finding linked to its source and scan date.

Who can reach it, and who approved it?

Evidence from IRIS: who can access each sensitive dataset, where the source exposes permission data, with each review decision recorded.

Is stored data protected as described?

Evidence from IRIS: whether sampled values in sensitive columns sit in plain form, by column and scan date.

Was it disposed of when it was due?

Evidence from IRIS: a later scan of the same scope, showing whether the data is still there, with both dates.

Timeline

Status on November 9, 2026

Checked on aicpa-cima.com on November 9, 2026. The next check is on December 7, 2026.

Status on November 9, 2026
ItemStatusSource
2017 Trust Services CriteriaCurrent, with points of focus revised in 2022AICPA, 2017 Trust Services Criteria
Proposed 2027 criteriaExposure drafts published October 26, 2026; comments open through January 15, 2027AICPA exposure drafts page; comment deadline from the news release, October 28, 2026
Proposed effective dateIf approved in 2027: engagements beginning on or after December 31, 2027, with early adoption permittedAICPA news release, October 28, 2026
Sylox’s own SOC 2 reportNot held; see the trust pageSylox trust page
ReviewEditorial review by Sylox; not reviewed by a CPALast reviewed November 9, 2026
With IRIS

IRIS produces evidence for these rows and maps it to SOC 2 controls; it doesn’t certify compliance. Mapping shows relevance; your auditors judge whether a control is met.

Security and confidentiality: where sensitive data sits: IRIS produces part of this, for the sources you connect; the data types IRIS detects.

Security: who can reach each dataset: IRIS produces part of this, where the source exposes permission data.

Security: how stored values are protected: IRIS produces part of this, on sampled values, once the check is activated on your install.

Scope: what each scan covered and couldn’t read: IRIS produces this.

Scope: the evidence register, with source and scan date: IRIS produces this.

Whether a criterion is met: Not produced by IRIS.

Explore evidence

Check the system description against the data

An order of work we recommend; the AICPA sets none. Afterwards, the ISO/IEC 27001 page shows the same evidence read against another framework.

1. List the systems in the report’s scope

Owner
Compliance lead
Tool or path
Your system description
Expected output
Each system that holds customer or confidential data, with an owner.
How to verify
Every system the product uses to serve customers is on the list.

2. Scan those systems and the ones beside them

Owner
Data platform lead
Tool or path
A discovery scan, or each system administrator’s own queries
Expected output
The sensitive data each system holds and the people who can reach it, by scan date.
How to verify
Each source is listed as scanned, failed or excluded, with the reason.

3. Add what the scan found to the description

Owner
Compliance lead
Tool or path
The findings, read against the system description
Expected output
Confidential data held in systems the description doesn’t name.
How to verify
Each find is added to scope, removed or has a recorded decision.

4. Scan again before fieldwork

Owner
Data platform lead
Tool or path
A scan of the same scope after the changes
Expected output
Both scans side by side, with their dates.
How to verify
Closed items are gone from the later scan; anything left has a decision.

The official texts behind each cell

  1. 2017 Trust Services Criteria, with revised points of focus (2022), AICPA and CIMA. Opened November 9, 2026.
  2. AICPA Exposure Drafts: Proposed 2027 SOC 2 Trust Services Criteria and Description Criteria (October 26, 2026), AICPA and CIMA. Opened November 9, 2026.
  3. AICPA proposes update of SOC 2 Trust Services Criteria (October 28, 2026), AICPA and CIMA. Opened November 9, 2026.
  4. System and Organization Controls: SOC suite of services, AICPA and CIMA. Opened November 9, 2026.
FAQ

SOC 2 questions

Protect your brand. Start with your data.

Pick the database your customers ask about most. A free assessment shows what it holds and who can reach it.