Blog. Audit evidence.
Audits check process, not data: what a CISO can show the board
Co-founder and CEO · November 6, 2026 · 4 min read

On this page
Passing an audit tells you your process was documented. It doesn’t tell you where your data is. That says nothing against auditors; it describes what an audit is built to do. The trouble starts when a board reads a clean audit report as the answer to a question the audit never asked.
An audit tests the control
NIST SP 800-53A, the US federal guide to assessing security and privacy controls, names three assessment methods. Examine means reviewing documents, mechanisms or activities. Interview means talking to the people involved. Test means exercising a mechanism under set conditions “to compare the actual state of the object to the desired state or expected behavior of the object.”
In an access control audit, examining means reading the policy and a sample of review records. Interviewing means asking the system owner how reviews run. Testing means checking that a control behaves as described. All three methods point at the control, and none is designed to produce an inventory of the sensitive data the control exists to protect.
I know this from the preparation side. At CBRE, I managed three to five applications with a team of over 200 people. Before each access review, I kept manual Excel sheets of who needed to do what. That work showed a process had run. It was never meant to show where our most sensitive data was.
The gap shows when the question changes
“Do you review access?” is a process question. “Which systems hold customer identity numbers, and who can reach them today?” is a data question. Regulators ask the second kind more directly.
GDPR Article 33(5) requires a controller to document personal data breaches, and that documentation “shall enable the supervisory authority to verify compliance.” Ireland’s Data Protection Commission received 6,521 valid breach notifications in 2025, according to its annual report. A regulator who asks to see breach records is asking for evidence of what happened, and a board can ask the same of its own data.
Leadership is accountable for what the process protects
NIST’s Cybersecurity Framework 2.0 states that “organizational leadership is responsible and accountable for cybersecurity risk” (GV.RR-01). The same framework treats an inventory of data as an outcome of its own, separate from inventories of hardware and software (ID.AM-07).
A list of passed audits shows the process. A board that is accountable needs a view of the data the process looks after.
One page gives the board the data side each quarter
Every line links to evidence a director could ask to see. A line that can’t link to evidence says so, and that admission earns more trust than another green status.
| Line | This quarter | Evidence a director can ask for |
|---|---|---|
| Scope | Seven systems assessed; the HR platform not assessed because its owner is not yet named | Coverage record with a state per system |
| Where sensitive data sits | Customer identity numbers in the core database and two exports; payroll data in the HR platform | Findings linked to their source, with scan dates |
| Who can reach it | Widest reach: a schema-wide reporting role on the core database; down from three such roles last quarter | Access view and the review decisions |
| What changed | One new export job; one fix confirmed by a re-scan of the same scope | Re-scan findings beside the first scan |
| Open decisions | Name an HR platform owner by December 4, 2026; decide on the archive schema | Decision log with owner and date |
For the “what changed” line, a closed ticket records that someone acted. A dated re-check of the same scope shows the access gone. Accept the second as the proof.
The first version will look thin
The first time a CISO builds this page, many lines will say “not assessed” or “owner not named.” That is the point. The page shows the board the real size of what is known, and the gaps become next quarter’s plan.
Over a few quarters the scope line grows and the open decisions shrink. That trend tells a board more than a single green status, because each step in it can be checked. Leave off counts with no denominator, green status with no statement of what was checked, coverage figures for an inventory nobody has verified and breach cost estimates used to create urgency.
Each finding carries its scan date and a source link. The scan lists what it couldn’t read, with the reason. A later complete scan of that scope shows if an access remains. IRIS doesn’t change it.
For each control, IRIS shows whether evidence is present, missing or deferred. Whether that evidence is sufficient, or the control met, is your auditor’s call. Capabilities vary by edition.
IRIS for CISOs and the audit evidence page cover this in more depth.
Send the thin first version to the board anyway
Build the page from what you can link to today, mark the rest “not assessed,” and put it in the next board pack. The GDPR page covers the breach duties in more detail, and the auditor question bank shows what follows the first question.
Sources
- NIST: SP 800-53A Rev. 5, Assessing Security and Privacy Controls, section 2.4.2, examine, interview and test (January 2022; opened November 9, 2026)
- European Union: Regulation (EU) 2016/679, the General Data Protection Regulation, Article 33(5) (April 27, 2016; opened November 9, 2026)
- Data Protection Commission, Ireland: Annual Report 2025, summary of the year’s figures (published June 30, 2026; opened November 9, 2026)
- NIST: The NIST Cybersecurity Framework (CSF) 2.0, subcategories GV.RR-01 and ID.AM-07 (February 26, 2024; opened November 9, 2026)
Start with a free assessment of one database you choose.
Get a free assessmentProtect your brand. Start with your data.
Book a demo, or start with a free assessment of one database.


