Cookie settings

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

Skip to content
Skip to content

Guide. Audit evidence. Checklist.

Evidence-readiness checklist: what to have before a data audit

Ten records to file before fieldwork, each with a filled example row, the control it supports and a check that someone else can repeat it.

Dipal Panchal

Co-founder and CEO · Updated November 8, 2026

On this page

The rule that makes a record ready

A record is ready when a person outside your team can re-run it from your written steps and reach the same row count and the same SHA-256 value. If they can’t, file it as not ready, with an owner and a date, and fix it before fieldwork.

Applies to audits of sensitive data under any framework. The control column below cites ISO/IEC 27001:2022, SOC 2, PCI DSS v4.0.1, the HIPAA Security Rule and the GDPR, and your auditor chooses which apply. Roles: an evidence owner, usually in security or privacy, files the records. System owners confirm their rows, and a reviewer outside the team re-performs them.

Time: the exports take minutes. The slow part is naming an owner for each system and agreeing the review dates, so book the owner conversations first.

  • File the ten records in the table, one folder each
  • Give every record the same six fields
  • Run the five steps below in order
  • Have the reviewer re-perform and sign each record
  • Re-run the failed ones, and keep the failure on file

The ten-record checklist

The example column holds sample rows. Replace them with your own.

The ten-record checklist
RecordFile thisFilled exampleSupports
1. ScopeA dated list of systems in scope, each with an ownerSRC-02 Billing database, PostgreSQL; owner: Payments engineering; listed October 28, 2026ISO/IEC 27001 clause 4.3; PCI DSS 12.5.2
2. ExclusionsEach excluded system with the reason, the approver and a review dateSRC-06 Partner export bucket, excluded: contract bars scanning; DPO approved October 21, 2026; review April 21, 2027ISO/IEC 27001 clause 4.3; HIPAA 164.308(a)(1)(ii)(A)
3. InventoryFindings by source and location, with the method and the scan dateSRC-02, billing.payment_card.card_number, card number, scan October 28, 2026ISO/IEC 27001 A.5.9; GDPR Art. 30(1)
4. CoverageOne status per source: scanned, partial, failed, excluded or not connectedSRC-04 Support desk, not connected; the support lead decides by November 30, 2026ISO/IEC 27001 clause 9.1; PCI DSS 12.5.2
5. Access exportWho can reach each sensitive location, the query and the row countaccess-export-2026-10-28.csv, 41 rows, query text filed beside itISO/IEC 27001 A.5.15; SOC 2 CC6.1
6. Access reviewA decision, a reason, a date and a removal deadline per identitysvc_report: revoke SELECT on billing.payment_card; decided November 2, 2026; remove by November 9, 2026ISO/IEC 27001 A.5.18; PCI DSS 7.2.4; SOC 2 CC6.2
7. Stored-form checkResult of a check on stored values, by locationbilling.payment_card.card_number: plain form; scan October 28, 2026; owner’s decision due November 13, 2026ISO/IEC 27001 A.8.24; PCI DSS 3.5.1; GDPR Art. 32(1)(a)
8. FixesFinding, change record and a dated re-test with the same scopeFND-0142, then CHG-3377 (grant revoked November 3), then re-test November 4 with the same queryISO/IEC 27001 clause 10.2; HIPAA 164.308(a)(1)(ii)(B)
9. IntegrityExports in a read-only folder, each with a line in a manifest of SHA-256 valuesevidence-manifest.csv, line 12: file, row count, SHA-256, UTC time, account that ran itISO/IEC 27001 clause 7.5; HIPAA 164.316(b)(1)
10. Sign-offA named owner signs each record, and a reviewer signs the re-performanceAccess export signed by the Payments engineering lead November 5, 2026; re-performed by internal audit November 6ISO/IEC 27001 clause 9.2; SOC 2 CC6.3

Six fields on every record

NIST SP 800-53A, the US federal guide to assessing controls, names three assessment methods: examine, interview and test. A document supports an examination or an interview. A query run against the system supports a test, and an assessor can repeat it. Aim your records at the test.

Give each record the same six fields so any of them can be re-run. Put them in the header of the file or in the manifest line.

  • Who ran it, and who reviewed it
  • What ran: the query, report or scan settings, word for word
  • When it ran, and the period or state it describes
  • The scope, with each exclusion and its reason
  • Where the output is kept, with its row count and SHA-256 value
  • The control or question the record answers

Five steps to a file an auditor can test

Run the steps in order for each source in scope. Step 4 has a command; the others use your catalog, scan and review tools.

1. Write down scope, owners and exclusions

Owner
Evidence owner, with each system owner
Tool or path
Your register: a spreadsheet or GRC tool
Expected output
A dated list of systems with one owner each, and a list of exclusions with reasons.
How to verify
Every system in your asset register is in the scope list or in the exclusions.

2. Run the inventory and record coverage

Owner
Security engineer, or the system owner’s delegate
Tool or path
Catalog queries and your scanning tool
Expected output
Findings by source and location with the scan date, plus one status per source.
How to verify
The number of sources with a status equals the number in scope.

3. Export access and record the review

Owner
Database administrator, then the data owner
Tool or path
Each source’s catalog; the review sheet
Expected output
An export with its query and row count, and a sheet with one decision per identity.
How to verify
Every distinct identity in the export has a decision, and nobody decided on their own access.

4. Check each export against its manifest line

Owner
Evidence owner
Tool or path
PowerShell 7 on a read-only copy
Command
PowerShellFrom Microsoft Learn documentation, page updated March 24, 2025; not yet tested by Sylox.
# Read-only. Compares an export with its line in the manifest.
$file  = '.\access-export-2026-10-28.csv'
$line  = Import-Csv .\evidence-manifest.csv |
           Where-Object File -eq (Split-Path $file -Leaf) |
           Select-Object -Last 1

$rows  = (Import-Csv -Path $file).Count
$hash  = (Get-FileHash -Path $file -Algorithm SHA256).Hash

[pscustomobject]@{
  RowsMatch   = ($rows -eq [int]$line.Rows)
  SHA256Match = ($hash -eq $line.SHA256)
}

# Expected for an unchanged file:
#   RowsMatch SHA256Match
#   --------- -----------
#        True        True
Expected output
Two True values for an unchanged file.
How to verify
A False means the file changed or the manifest line is wrong. File that as an exception, with the date.

5. Re-perform and sign

Owner
Reviewer outside the team
Tool or path
Your written steps
Expected output
The same row count and SHA-256 value, and a signed record.
How to verify
The signature carries a name, a role and a date, and the signer didn’t produce the record.

Who signs what

Name three people for each record: the person who ran it, the data owner who reviewed the result and the person who approved any exclusion. Where you can, keep those roles apart.

The data owner decides whether an access is still needed. A security team can show where data sits and who can reach it, and only the business owner can say the access serves a purpose. Store sign-offs with the records they approve, so a question about who accepted a gap is one lookup.

What this checklist misses

It lists records about sensitive data only. It leaves out policies, training records, supplier assurance, physical controls and the management review. It also assumes each source lets you export a grants list, and some SaaS sources limit what an export shows.

A matching SHA-256 value shows that a file is unchanged. It can’t show the export was complete, so the row-count check and the register reconciliation in step 1 matter as much. Your auditor decides what is sufficient, and this page is general information, not audit advice.

With IRIS

IRIS produces several of these records from the sources you connect, each linked to its source and scan date. Capabilities vary by edition.

Record 3, inventory: findings by source and location with the scan date: IRIS produces part of this, in the sources you connect.

Record 4, coverage: the tables and files a scan couldn’t read, and why: IRIS produces part of this, for the tables and files the scan account can list.

Records 5 and 6, access: who can reach sensitive data, with a reviewer’s decision: IRIS produces part of this, where the source exposes permission data.

Record 7, stored-form check: IRIS produces part of this, on sampled values, once activated on your install.

Evidence items from scan data, in a register you can export: IRIS produces this.

Reminders and due dates for open items: Not produced by IRIS.

A scored readiness view for ISO/IEC 27001, SOC 2 or PCI DSS: not in v1; ask us if you need one: Not produced by IRIS.

Explore audit evidence

File record 5 for one database this week

Choose one database that holds sensitive data. Export its grants, record the row count, fingerprint the file in step 4 and ask a colleague to repeat the export from your steps. Matching counts and a matching SHA-256 value mean record 5 is ready.

Next, work out which question each record answers. The auditor question bank lists eight, with the controls behind them.

Official sources

  1. NIST SP 800-53A Rev. 5: examine, interview and test, NIST. Opened November 8, 2026.
  2. ISO/IEC 27001:2022: clauses 4.3, 7.5, 9.1, 9.2 and 10.2; Annex A 5.9 to 8.24, ISO. Opened November 8, 2026.
  3. PCI DSS v4.0.1: requirements 3.5.1, 7.2.4 and 12.5.2, PCI Security Standards Council. Opened November 8, 2026.
  4. 45 CFR 164.316(b)(1): documentation of policies, actions and assessments, eCFR, US Government. Opened November 8, 2026.
  5. GDPR Article 30: the record of processing, EUR-Lex. Opened November 8, 2026.
Share this guide
FAQ

Evidence-readiness questions

Protect your brand. Start with your data.

Start with one database: a free, read-only assessment and a report in the format of our sample report.