A number without its scope
A risk score that doesn’t say which systems were scanned, which failed and which were never connected is one a director can’t weigh.
Data security for CISOs. Board reporting.
Know what was assessed, what was missed, what’s exposed, and what you can defend.
Four paid engagements and three proofs of concept.
A risk score that doesn’t say which systems were scanned, which failed and which were never connected is one a director can’t weigh.
Dipal Panchal treats a source that is connected but has never been scanned as a red flag. He names it in the executive report, so the board can ask why nobody scanned it.
“Data security posture management is an enabler,” Dipal Panchal says. Ownership and accountability for the data stay with the people who run the business.
One quarter set against the last, with the record behind each figure, and in the last row the decision you ask the board for.
| Board question | Q3 2026 | Q2 2026 | Where the figure comes from |
|---|---|---|---|
| What did we check? | 49 of 52 connected systems scanned; 3 connected but never scanned | 45 of 49 scanned; 4 never scanned | IRIS’s connected sources and their scan history, scans dated September 1 to 30, 2026 |
| What didn’t we check? | 7 systems in the asset register not connected, each with an owner and a reason | 9 not connected | Your asset register, set against IRIS’s list of connected sources |
| Where is restricted data stored in plain form? | 12 columns in 5 systems | 19 columns in 6 systems | IRIS findings your reviewers confirmed, from the protection check on sampled values |
| Who can reach it beyond need? | 23 accounts with admin rights; 8 unused past the 90-day default | 31 and 14 | IRIS access findings, from the table and view grants and file sharing its accounts can read |
| What changed since last quarter? | 9 fixes confirmed by a re-scan; 2 new plain-form columns found | Not tracked | Pairs of dated scans of the same scope, before and after each fix |
| What do we need from the board? | Accept the 3 unscanned HR systems as a risk until Q1, or fund the owners’ time to connect them | Not asked | The recommendation of the chief information security officer (CISO), with owners named |
The Govern function of the voluntary National Institute of Standards and Technology (NIST) Cybersecurity Framework (CSF) 2.0 covers risk strategy and its oversight. GV.OV-01 has strategy outcomes reviewed to inform and adjust strategy and direction, and GV.RR-01 makes leadership responsible and accountable for cybersecurity risk.
The board view above is one way to put those outcomes in front of directors. For US-listed companies, Item 106(c)(1) of Regulation S-K asks how the board oversees cybersecurity risk, and in the EU, NIS2 Article 20 has management bodies approve and oversee it.
The view’s first two rows rest on ID.AM-07, an inventory of data and its metadata for the data types you designate. Its fourth rests on PR.AA-05, which has access permissions reviewed with least privilege and separation of duties.
Each scan lists the sources it covered, the tables and files it couldn’t read and why. Sources you never connected sit outside that record, so list them beside it in the board pack.
Whether sensitive values are encrypted, masked or hashed, from a check on sampled values that runs once it is activated on your install.
Accounts with admin rights on sensitive data, and access unused past the 90-day default, or a period you set, where the source records activity.
A re-scan of the same scope after a fix records the new condition on its own date, and the scan history keeps the earlier scan to count against.
What your own security review will ask about the system behind the board view.
IRIS can be deployed in your own infrastructure, on-premises or in any cloud, so your data stays within your environment.
IRIS only reads your sources, through accounts your team creates; use a read-only account wherever the source offers one.
IRIS reads a sample of each table, and small tables in full. A value held in a few rows of a very large table can be missed in one run.
Scans run on demand or on a schedule you set, and each one is dated. A quarter’s view rests on the scans dated inside it, plus the activity each source itself recorded.
Findings, coverage records and samples stay in the IRIS database on your host unless emailed reports are on. Stored samples are masked by default in personal-data columns; storage can be turned off.
The license service at activation and when an admin validates, the cloud and SaaS sources you scan, a time source that can be your own, and emailed reports if you turn them on.
Capabilities vary by edition.
Each figure is a reading on its scan date for the sources you connected. A scan shows the state on its date, not what changed between scans. Access history comes from the source audit logs, where a source keeps one. IRIS doesn’t fix what it finds: your teams change the source systems.
On PostgreSQL, activity is tracked per database account unless audit logging is turned on. IRIS also can’t tell you whether a system should hold the data. That call belongs to the data owner, which is why the last row asks the board for a decision.
What each framework or law asks of your data, and the evidence IRIS produces for it.
For SOC 2, ISO/IEC 27001, PCI DSS, UK GDPR and UAE PDPL, IRIS maps its evidence to their controls. A scored readiness view for the CISO’s frameworks isn’t in v1; ask us if you need one.
Start with the system your board asks about most, and scan it; access mapping runs after the scan. The how-it-works page follows that scan to the records in each row, and the architecture page answers your own security team’s questions first.
Each quarter, by our rule, from scans dated inside that quarter. A view built from a single scan shows one date, so say that on the slide.
Yes, for questions about where sensitive data sits, who can reach it and how it is stored, with the scan date. Questions about your own controls, such as incident response, need other evidence.
A host to run it on, and an account for each source that can read the data in scope and its grants. The security pack lists the grant for each source type. Explore deployment
Yes. It scores risk from how sensitive the data is, whether it is protected and who can reach it, so your team can start with the worst.
Name the system your board asks about most. We’ll build the first rows of the view from it.