Cookie settings

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

Skip to content
Skip to content

Guide. Audit evidence. Exclusions.

How to document exclusions when a source can’t be scanned

Record each excluded source with its reason, the owner who accepts the risk, the evidence you hold instead and the date the exclusion ends.

Dipal Panchal

Co-founder and CEO · Updated November 8, 2026

On this page

When a gap counts as an exclusion

Applies to any data scan that leaves a source out, on any platform. The export command below is for a Windows file share, comes from Microsoft documentation and has not yet been run by Sylox.

Rule: a source is excluded only when a named owner has decided, in writing, to leave it out. A source nobody decided on is failed or not connected. It stays open on the register until someone scans it or decides.

The scan owner drafts the record and the data or system owner signs it. A reviewer outside the scan team checks it each cycle. Allow about an hour per exclusion, evidence included.

  • Name the part of the source that is out of scope
  • Write the reason in one plain sentence
  • Label what the source likely holds as declared
  • Attach the evidence you hold instead, dated
  • Get the owner’s acceptance, and set the end date

The exclusion record, field by field

One record per exclusion. The example column shows a file share and roles.

The exclusion record, field by field
FieldWhat to writeExample
Source and partSystem, environment and the part that is outHR file share, production, all folders
ReasonOne sentence a stranger followsMid-migration; folders are moving daily
Decided byName, role and date of the decisionHR director, October 28, 2026
Likely contentsWhat the owner says it holds, marked declaredDeclared: employee records, payroll exports, identity documents
Evidence held insteadEarlier scans or exports, each with date and typeFolder listing and access list, exported October 27, 2026
Risk accepted byThe data or system owner, with the dateHR director, October 28, 2026
Review dateWhen the exclusion ends or needs a fresh signatureJanuary 15, 2027, after the migration

Choose the right word and the right reason

Excluded is a decision, failed is an attempt that did not finish, and not connected is work not started. If a team never connects a source, the report says so, and its results come only from the sources that were scanned.

Reasons that stand up: no read-only account is approved yet, no network path exists, the system is being retired, vendor terms bar a scan, or no change window is agreed. Scope can also be set by the account itself. When a client wanted only one subsidiary’s records reviewed, the access it granted showed only those records, and the rest of the shared system was out of scope by design.

A reason like “out of scope” with nothing attached is a gap with a label on it. A reason with a migration ticket, a contract clause or an access request is something an auditor can retest.

Export the evidence you hold instead

For an excluded file share, a read-only export of file counts, dates and permissions is compensating evidence. Run it as an account that can list the share.

PowerShellFrom Microsoft Learn documentation, page updated August 10, 2026; not yet tested by Sylox.
# Read-only. Lists names, sizes, dates and permissions; it never opens file contents.
$root = '\\fileserver01.example.com\hr'
$stamp = '20261108'

$files = Get-ChildItem -Path $root -Recurse -File -ErrorAction SilentlyContinue -ErrorVariable listErrors
"Files listed: $($files.Count); folders that refused listing: $($listErrors.Count)"

# Types and age: what the share probably holds, as evidence of the declared contents.
$files | Group-Object Extension | Sort-Object Count -Descending |
  Select-Object -First 10 Name, Count | Export-Csv "hr-share-types-$stamp.csv" -NoTypeInformation
$files | Measure-Object LastWriteTime -Minimum -Maximum |
  Select-Object Minimum, Maximum | Export-Csv "hr-share-dates-$stamp.csv" -NoTypeInformation

# Who can reach the share root.
(Get-Acl -Path $root).Access |
  Select-Object IdentityReference, FileSystemRights, AccessControlType |
  Export-Csv "hr-share-acl-$stamp.csv" -NoTypeInformation

Prove the export is complete, then label it

Folders the account cannot list are counted in listErrors, so the file count is a floor. Write the number of refused folders into the record, and compare the file count with the share’s own report if the file server keeps one.

Date and type the export. NIST SP 800-53A asks that when earlier assessment results are reused, the date and type of the original assessment are documented. An export from October 27 is evidence about October 27, and the record should say so.

Five gaps, and which are exclusions

Register rows from one scan cycle. The first two stand as exclusions, the last is rejected as written, and the middle two stay open.

Records
SourceStatusReasonOwner
HR file share, productionExcludedMid-migration; HR director accepted the risk on October 28, 2026; review January 15, 2027HR director
Legacy billing (Oracle)ExcludedDecommissioned June 30, 2026; purge record attached; approved by the CISO on July 2, 2026Payments engineering
Analytics warehouseFailedNot an exclusion: the scan host could not reach the warehouse; re-run due November 13, 2026Data platform lead
Support desk (SaaS)Not connectedNot an exclusion: no connection set up and nobody has decided; decision due November 30, 2026Support lead
Contractor laptop folderExcludedRejected as written: “out of scope” with no owner, no evidence and no dateScan owner

How an auditor tests one exclusion

Expect the auditor to sample exclusions as they sample findings. Each row is a test they can run on your record.

How an auditor tests one exclusion
TestThe auditor checksThe record passes when
Reason still trueWhether the stated reason holds todayThe migration ticket is open or the system is still retired
AuthorityWhether the signer owns the data or the systemThe signer’s role matches the owner list, and the signer did not run the scan
Review dateWhether the date has passed without a decisionThe date is in the future, or a fresh signature is on file
EvidenceWhether the held-instead evidence is dated and fits the sourceThe export date, type and refused-folder count are written down
Declared contentsWhether owner statements are labeled as statementsThe word declared sits beside the contents, not evidenced

Who accepts the risk, and for how long

NIST SP 800-53A treats risk acceptance as the organization’s decision, made after the assessment. Where an assessor cannot obtain enough information, the finding is other than satisfied, with the reason in the report. Your record puts the reason there before the assessor writes it.

The owner who accepts the risk is never the person who ran the scan. If no one will sign, the exclusion is not agreed: mark the source not connected and escalate. An exclusion runs until its reason ends and no longer than your next scan cycle without a fresh signature. Our recommendation is a review date no more than twelve months out.

What this method misses

The export shows names, sizes, dates and permissions. It does not show what the files contain, so declared contents stay declared. A listing also misses files created after it ran, which is why the record carries the export date.

An exclusion covers one instance. Copies of the excluded source in other places are separate rows. If the source probably holds sensitive data, say so in the record; an exclusion that admits the risk is more credible than one that plays it down.

With IRIS

IRIS records each scan’s coverage for the sources you connect, with the reason for anything it could not read. Capabilities vary by edition.

A scan status for each connected source, with a reason: IRIS produces this.

Unknown outcomes shown as unknown, never as clean: IRIS produces part of this, for the sources and tables in a scan.

Sources nobody connected, such as SaaS apps: Not produced by IRIS.

The owner’s acceptance, review date and reminders: Not produced by IRIS.

Explore audit evidence

Test your own oldest exclusion today

Take the oldest exclusion on your register and run the five tests above as if you were the auditor. If any fails, fix the record or scan the source. Re-check on the review date and file the result with the record.

The next guide, questions auditors ask about sensitive data, shows where an exclusion record answers an auditor’s question about what you could not check.

Official sources

  1. NIST SP 800-53A Rev. 5: findings, reuse of results and risk acceptance, NIST. Opened November 8, 2026.
  2. Get-ChildItem (Microsoft.PowerShell.Management), Microsoft Learn. Opened November 8, 2026.
  3. Get-Acl (Microsoft.PowerShell.Security), Microsoft Learn. Opened November 8, 2026.
Share this guide
FAQ

Exclusion questions

Protect your brand. Start with your data.

See how a coverage record lists what was scanned, what failed and what was excluded, in our sample report.