Cookie settings

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

Skip to content
Skip to content

Category comparison. Scan timing.

Scheduled vs event-driven scans: what each can evidence

Three ways to time a data scan, and what each lets you show an auditor over a 12-month period.

By Dipal Panchal, co-founder and CEO · Updated November 8, 2026

Overview

A scan shows only the moment it ran

A point-in-time scan records what was in a source on the date it ran. A scheduled scan repeats that on a fixed rhythm, so you build a dated series. An event-driven scan runs when the source reports a change, such as a new file or a changed permission.

Each one shows only what it observed. NIST’s guide to assessing controls leaves the frequency of assessments to the organization, so the rhythm is a choice you make and defend. Match it to how fast the data can change.

Explore scan coverage
Compare

Three timing models side by side

Cells describe the typical tool for each scan-timing model.

Three timing models side by side
AspectPoint-in-timeScheduledEvent-driven
Acts onEach source in scope, onceEach source in scope, on every runThe changes a source reports
Main strengthA baseline, or a dated answer for one reviewA dated series an auditor can sampleFast notice of a high-risk change
What it cannot doShow anything that changed after the scan dateShow what happened between two scansShow the full state, or changes the source never reported
Best fitA first assessment, or a check before an audit or customer reviewShowing that the same check repeats on a known rhythmA file shared outside the company, or a changed permission
A typical scenarioA pre-audit scan of the billing databaseA weekly scan of the same database through the audit periodAn alert when a folder is shared with anyone who has the link
Where it runsWherever the scanner runs, started by a personOn a scheduler that starts the scannerA service that receives notices from each source
What it needsRead access at scan timeRead access, plus a scheduler and capacity for each runA source that emits events, a live subscription and a service ready to receive them
Load on the sourceOne read of each source in scopeA read of each source on every runSmall reads per event, plus a first scan to set the starting point
Gaps to plan forIt ages from the day after the scanThe interval between runs is the gapNotices can arrive late or more than once, and subscriptions can expire
Use cases

One audit period, three timing models

Take an audit period of January to December 2026, covering one database that holds personal data. The auditor sets the questions.

One audit period, three timing models
Audit questionPoint-in-time (Dec 1)Scheduled (monthly)Event-driven
Where was personal data in March?Cannot say; the record starts December 1Answered by the March scan, with its dateAnswered only if a baseline scan came first
A permission added in June and removed in JulyInvisibleSeen only if a scan ran between the two datesSeen if the source reported both changes
A source unreachable for two weeks in AugustNot in the recordA failed run on record, with the reasonA silent gap if the subscription lapsed
Does the rhythm match the policy?No rhythm to showTwelve dated runs against the policyDepends on what the source emits
What the auditor can retestOne dated stateAny of the dated states, by reading the source againThe reported changes, not the full state
Who it’s for

When each model is enough

Point-in-time is enough when

You need a baseline, or a dated answer for one audit or customer review, and the sources in scope change slowly.

A schedule is enough when

An auditor wants the same check to repeat on a known rhythm, and the gap between runs is acceptable for the data in scope.

Event-driven helps when

A single change matters fast, such as a file shared with anyone who has the link. Events show change, not the full state, so pair them with scans.

You combine them when

You need a baseline and a dated series for audits, plus fast notice of the few changes that can’t wait for the next run.

Requirements

What to test in a proof of concept

Change something on a test source, then check what each model recorded.

  • Add and remove a test permission between two scheduled runs, and see whether either run shows it.
  • Let a test connection fail for a week and check what the record says about that week.
  • Ask for the dated output of the last three runs, and check that each states its scope.
  • For events, expire the subscription and check that the tool tells you.
Capabilities

How IRIS fits

IRIS runs point-in-time scans that you schedule or run on demand.

Scheduled and on-demand scans

Scans run on a daily or weekly schedule, or on demand before an audit. Every scan is dated, and a re-scan changes only what it covered.

Scope and coverage record

For every scan, IRIS records what was in scope, scanned, failed or excluded. Any file it couldn’t read appears with a reason, and unknowns show as unknown, never zero.

Evidence register

Evidence is generated from scan data and collected in a register. You can review it and export it as CSV or XLSX.

Re-scan after a fix

After your team fixes a finding in the source, a re-scan records the new condition with its own date.

Capabilities vary by edition.

Official sources

  1. NIST SP 800-53A Rev. 5, Assessing Security and Privacy Controls, NIST. Opened November 8, 2026.
FAQ

Scan timing questions

Protect your brand. Start with your data.

Change a test permission between two runs, then book a demo to see a dated re-scan.