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.
SOC 2. Audit evidence.
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
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.
Your auditor decides which criteria apply. The first two columns describe each category; the third is what IRIS produces. Capabilities vary by edition.
| Category | What the examiner tests | Evidence IRIS produces | What it also needs |
|---|---|---|---|
| Security | Controls 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. |
| Security | Access 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. |
| Security | Access 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. |
| Security | Sensitive 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. |
| Confidentiality | You 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. |
| Confidentiality | Confidential 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 category | The 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 privacy | Uptime, complete processing, and the handling of personal information. | IRIS doesn’t do this. | Evidence from your operations, change and privacy tools. |
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.
| Source | Location | Detected type | Why | Sensitivity | Decision |
|---|---|---|---|---|---|
| Production database | customers.contact_email | Email address | Customer data in scope for confidentiality commitments | Confidential | Kept |
| Support file share | /exports/tickets_2024.csv | Name and phone number | A customer export outside the system you expected | Confidential | Kept |
| Analytics warehouse | dw.events.user_ref | Email address | Stored in plain form; check against your protection rule | Confidential | Kept |
| Reporting database | archive_2021.accounts | Name and postal address | Past your disposal rule; delete, then re-scan | Confidential | Kept |
| Staging database | seed.demo_users | Email address | Only example.com addresses; generated demo data | None | Rejected |
Evidence from IRIS: an inventory by source, table, column or file, each finding linked to its source and scan date.
Evidence from IRIS: who can access each sensitive dataset, where the source exposes permission data, with each review decision recorded.
Evidence from IRIS: whether sampled values in sensitive columns sit in plain form, by column and scan date.
Evidence from IRIS: a later scan of the same scope, showing whether the data is still there, with both dates.
Checked on aicpa-cima.com on November 9, 2026. The next check is on December 7, 2026.
| Item | Status | Source |
|---|---|---|
| 2017 Trust Services Criteria | Current, with points of focus revised in 2022 | AICPA, 2017 Trust Services Criteria |
| Proposed 2027 criteria | Exposure drafts published October 26, 2026; comments open through January 15, 2027 | AICPA exposure drafts page; comment deadline from the news release, October 28, 2026 |
| Proposed effective date | If approved in 2027: engagements beginning on or after December 31, 2027, with early adoption permitted | AICPA news release, October 28, 2026 |
| Sylox’s own SOC 2 report | Not held; see the trust page | Sylox trust page |
| Review | Editorial review by Sylox; not reviewed by a CPA | Last reviewed November 9, 2026 |
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 evidenceAn order of work we recommend; the AICPA sets none. Afterwards, the ISO/IEC 27001 page shows the same evidence read against another framework.
Which Annex A controls a sensitive-data inventory and access evidence support.
The questions auditors ask across frameworks, with the evidence that answers them.
Repeatable data audit evidence, with scope and gaps on the record.
IRIS maps its evidence to SOC 2 controls through its unified compliance framework. A scored SOC 2 readiness view isn’t in v1; ask us if you need one. Your examiner decides what it proves.
No, not yet. Our trust page sets out our security program, and we answer your security questionnaire during scoping. Read the trust page
Mainly security and confidentiality: where sensitive data sits, who can reach it, how it is stored and whether it was disposed of. Availability and processing integrity need evidence from other tools.
No. IRIS produces evidence; your auditor decides whether a criterion is met.
No, not yet. They are exposure drafts, open for comment through January 15, 2027. Ask your auditor which criteria your report will use.
Pick the database your customers ask about most. A free assessment shows what it holds and who can reach it.