Cookie settings

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

Skip to content
Skip to content

Blog. Audit evidence.

How to scope an evidence-readiness evaluation of three to five systems

Dipal Panchal

Co-founder and CEO · November 6, 2026 · 3 min read

On this page

Two questions can start an evaluation of a data security posture management (DSPM) tool. One asks whether the platform has many features. The other asks whether your named owners can inspect the evidence you need for this assurance problem. The first produces a demo and the second produces a decision, so scope the evaluation around the second, on three to five systems.

One sentence about the trigger sets the whole scope

Something made the evaluation necessary: an audit, a customer security review, a regulator’s question or a board request. Write it in one sentence, with the date it has to be answered by. In a constructed example: “Our largest customer’s next security review asks where their records are stored and who can reach them, and we answer from a spreadsheet today.”

If a system, an output or a test doesn’t help answer that sentence, leave it out.

Choose the systems the decision depends on

Pick the systems the decision rests on. A useful set mixes a primary database, an analytics copy such as a warehouse and a file location where exports land. For each system, confirm three things before the evaluation starts.

  • An owner who approves its inclusion in writing.
  • A read-only account that your team creates and controls.
  • A confirmed answer on what the tool can read in that system.

A few systems read properly tell you more than many read in name only. NIST’s Cybersecurity Framework 2.0 accepts a narrow scope too: an Organizational Profile can address a whole organization or be scoped to its financial systems.

NIST SP 800-53A goes further for assessments. Depth and coverage are “assigned by the organization and specified within the assessment plan,” so scope is decided and written down before the work starts.

The charter fits on one page

Records
ItemEntry
ProblemAnswer the customer’s storage and access question from system evidence
SystemsCustomer database, data warehouse, export share, support platform
PermissionsRead-only accounts created by the platform team, switched off by the same team on the readout date
OutputsA coverage record per system, findings linked to their source, an access view, a one-page readout
ReviewersSystem owner for coverage, data owner for findings, security lead for the access view
SuccessApproved systems have coverage states; findings have sources; the owner agrees it answers the trigger or lists gaps
ExcludedEmail, held back until the privacy lead approves it

Exceptions belong in the same document. A system that could not be connected is an exception with a reason, and hiding one is the failure. Agree too where the tool will run, what it stores and what, if anything, leaves your network, and have your security team sign that off before the first connection.

Four drifts to design out of the charter

  • The cleanest system gets chosen, so the evaluation proves little about the messy ones.
  • The vendor picks the systems, so the evaluation tests the demo and skips your estate.
  • Exclusions are agreed in a meeting and never written down, so they vanish from the readout.
  • Success reads “the tool works,” a statement nobody can disagree with or act on.

Each is cheap to prevent when the charter exists before the first connection. Once results exist and people have started to like them, the same fixes cost an argument.

With IRIS

IRIS reads sources with read-only access, agentless where supported, using accounts you create. A source it can’t read is listed with the reason, so each charter exclusion has a line in the record.

Check the supported sources and the deployment options against your charter. A free assessment of one database is a smaller first step.

Hold a dated decision review

End the evaluation with a dated meeting of the sponsor, the system owners and the evaluator. Go through each output against the success line, then decide to proceed, extend the scope or stop. Keep commercial terms in a separate agreement, so the charter is judged on evidence alone.

Draft the charter this week, with the review date already in it. The guide on the evidence readiness checklist lists the evidence to ask each system for.

Sources

Share this article

Protect your brand. Start with your data.

Book a demo, or start with a free assessment of one database.