PROGRAM GUIDE, read 10 Nov 2026
Treat the spreadsheet as a data source first, then retire it only after one clean cycle
Inventory what the spreadsheet actually does
Before choosing a platform, list every column and every formula in the workbook, and every person who edits it. In most programs the workbook does five jobs: it lists findings, assigns owners, records due dates, records exceptions and produces a count for a monthly report. Each job needs a home in the new platform, and the owner and exception columns are the ones most often lost.
Write the ranking rule down in one sentence per tab. If the rule is a person's judgment, say so. The new platform will ask you to express it as weights or conditions, and a rule that was never written down cannot be rebuilt.
Use the file connector route
Platforms that take file input let you load the workbook as a source instead of retyping it. Brinqa's documentation describes a connector framework that covers APIs, database extracts and CSV, JSON and XML files, and a CSV connector with a flexible schema. Tenable's connector page says the Tenable One Open Connector ingests data from tools, internal systems, spreadsheets or files. Nucleus states that its FlexConnect ingests data from any source in any format; that is a vendor claim, and Nucleus publishes no public technical documentation to check it against.
Export each tab to CSV with a header row, one finding or asset per row, an ISO date format (2026-11-10) and a stable identifier column. Remove merged cells, color coding that carries meaning and free-text notes inside the key columns. Put the meaning of any color into its own column first.
Reconcile before you retire
Run the spreadsheet and the platform side by side for one full remediation cycle. Pick a fixed date, count open findings by owner in both, and explain every difference in a short log. Differences usually come from three places: duplicates the spreadsheet carried, findings the scanner closed that nobody updated, and assets the scanner no longer sees.
Do not delete the workbook at cutover. Save a read-only copy with the date in its name and a hash, so you can answer a question from an auditor about how a past decision was made.
- Count open findings by owner on a fixed date in both systems.
- Log every difference with a cause.
- Move exceptions with their approver and expiry date, not only a yes or no.
- Freeze the workbook read-only and store it with a hash.
What the platform will change
The first change is that the same finding can appear from several scanners, and the platform will group or deduplicate it. Your counts will drop, and that is expected. Tell stakeholders before the first report, with the old and the new count for the same date.
The second change is scoring. A workbook usually sorts by CVSS plus a manual flag. The platform will offer other inputs. The scoring guide covers how to recreate a sort order you trust before you adopt a new one.
When a spreadsheet is still the right answer
A spreadsheet works for a program with one scanner, a few hundred assets and one or two people who both own and fix. The cost appears when a second scanner arrives, when findings multiply, or when the person who built the workbook leaves. The signs that it is time are plain: two people cannot edit it at once, the count in last month's report cannot be reproduced, exceptions are tracked in email, and the audit evidence is a screenshot.
Be honest about the size of the problem. If the program has fewer than a few hundred open findings and a single source, a smaller step may be enough: move the data to a shared database table with the same columns, add an owner and due date field with data validation, and automate the scanner import. That is a smaller project than a platform migration and it keeps your options open.
If you do choose a platform, the spreadsheet gives you something useful: a written record of how your team decides. Platform vendors will show you a score. You already have a ranking that works well enough for your program, however crude, and the first test of any platform is whether it reproduces that ranking and then improves on it.
Plan the people side as carefully as the data. The person who built the workbook knows which rows are wrong, and which colors mean what. Give that person two hours with the import file before the trial starts, and let them mark the rows that should not be loaded. Then ask them to sit in the first weekly comparison. Their corrections in the first week are worth more than any automated check, and they are also the people who will be most worried that the platform replaces their judgment. Show them where their rules are written down in the new system. Ask them to sign off the first report.
Budget one working day per tab for cleanup, and a second day for the owner mapping. Teams that skip the owner mapping end up with a platform that is full of findings assigned to nobody.
Sources
- Brinqa connectors, read 10 Nov 2026
- Brinqa CSV connector, read 10 Nov 2026
- Tenable One connectors, read 10 Nov 2026
- Nucleus integrations (vendor page), read 10 Nov 2026
Last reviewed 10 Nov 2026.