Blog. Sylox perspective.
A data-copy register is useful only when someone owns the next decision
Co-founder and CEO · November 6, 2026 · 4 min read

On this page
A list of data copies is a map. A register is a set of decisions, and the difference is whether each line has a person who will decide what happens to that copy next. Copies are made for good reasons: a report, a migration, a new colleague who needs some history. The trouble starts when the reason ends and the copy doesn’t.
One weekly export became four copies
The example is constructed. Every Monday a scheduled job exports active customer records from the customer system to a CSV file in a shared folder. An analyst loads the file into a spreadsheet model, and a dashboard reads the model. Last quarter someone copied the shared folder to a team drive so a new hire could see past exports.
The customer system has a clear owner. Its four copies are another matter, and the register below shows where.
| Copy | Purpose owner | System owner | Who can open it | Retention decision and basis |
|---|---|---|---|---|
| Weekly CSV export | Head of customer analytics | Platform team | Folder group, inherited from the parent folder | Delete when the next export lands; basis: internal policy |
| Spreadsheet model | Head of customer analytics | Analyst who owns the file | Three named analysts | Retention basis to confirm with counsel |
| Dashboard cache | Head of customer analytics | Reporting team | Everyone with dashboard access | Clears on refresh; basis: product setting |
| Team drive copy | No owner found | IT operations | The whole team drive group, inherited | Close: name an owner by November 16, 2026, then delete and verify |
| Nightly backup of the customer system | Out of scope | Platform team | Backup administrators | Covered by the backup policy, not by this register |
A copy shared through an over-broad link has no owner to ask
In 2023 Wiz Research found that Microsoft’s AI research team, while publishing open-source training data, had shared it through an Azure storage link configured to grant access to the entire storage account. The account held 38TB of other private files, including backups of two employees’ workstations. The researchers who found it also report that the token allowed full control, so files could be overwritten.
A register with a permission column asks the question that link answered wrongly: who can open this copy, and from where.
Write down the journey you can confirm
For each hop, record the source, the destination, the trigger and who set it up.
- Customer system to CSV export: a weekly job, set up by the platform team.
- Export to spreadsheet model: loaded by hand by the analyst.
- Spreadsheet model to dashboard: a refresh set up by the reporting team.
- Shared folder to team drive: a one-off copy, origin unknown.
Where an origin or a destination is unknown, say so and give someone the job of finding out. An open line in the register is more useful than a silent gap.
Every copy needs a system owner and a purpose owner
The system owner keeps a system running and controls who can sign in. The purpose owner needs the copy for a business reason, and in the example that is the head of the team that uses the dashboard.
The system owner can tell you where the copy is and who can open it. Only the purpose owner can say whether it should still exist. If a copy exists because your team needs it, the decision about it sits with your team.
The permission column holds the surprise. A shared folder can inherit access from a parent folder with a much wider audience, so record where the permission is set and don’t assume it.
Retention is a decision with a basis
Privacy laws tie retention to purpose. GDPR Article 5(1)(e) says personal data should be kept in identifiable form “for no longer than is necessary for the purposes for which the personal data are processed.”
India’s Digital Personal Data Protection Act, 2023 takes the same approach in section 8(7). A Data Fiduciary must erase personal data when consent is withdrawn, or as soon as it is reasonable to assume the specified purpose is no longer served, whichever is earlier. The exception is where a law requires retention. It must also cause its Data Processor to erase what it was given.
Some data must be kept. Under Rule 8(3) of India’s Digital Personal Data Protection Rules, 2025, certain personal data and processing logs are retained for a minimum of one year, for the purposes in the Seventh Schedule. Rule 8 comes into force eighteen months after the Rules were published in November 2025. Keeping and erasing can apply to one system at once.
So each register line records a decision and its basis: the law, contract or policy relied on. Where the basis is unclear, the line reads “retention basis to confirm with counsel,” which beats a deadline someone invented.
A copy is closed when someone has checked it is gone
Deleting a file ends the task only if someone looks. NIST’s guideline on media sanitization, SP 800-88 Rev. 2, treats verification as a step of its own: the sanitization results “should be inspected to verify that the sanitization technique was completed successfully.” A deleted export deserves the same habit, even with simpler tools.
In the example, the team drive copy is the line a register is most likely to miss. It has no job, no schedule and no owner. It is also the easiest line to close.
IRIS records where sensitive and personal data sits, by source, table and column, or file, with the scan date on each finding. That covers the sources you connect and the data types IRIS detects.
Scans run daily, weekly or on demand. IRIS doesn’t change source systems: it doesn’t delete, move, mask, revoke or block, or make the owner’s decision. The change happens in the source system.
See discovery and classification, and the glossary entry on shadow data.
Close the copy nobody owns first
Find the copy in your estate with no job, no schedule and no named owner. Give it a purpose owner this week, or delete it and record who checked. The guide on personal data in test databases covers the copies engineers make for testing.
Sources
- European Union: Regulation (EU) 2016/679, the General Data Protection Regulation, Article 5(1)(e) (April 27, 2016; opened November 9, 2026)
- Government of India: The Digital Personal Data Protection Act, 2023, section 8(7) (August 11, 2023; opened November 9, 2026)
- Government of India, MeitY: Digital Personal Data Protection Rules, 2025, Rule 8 on retention, Rules 1 and 8(3) (November 2025; opened November 9, 2026)
- NIST: SP 800-88 Rev. 2, Guidelines for Media Sanitization, section 4.5.1 (September 2025; opened November 9, 2026)
- Wiz Research: 38TB of data accidentally exposed by Microsoft AI researchers (September 18, 2023; opened November 9, 2026)
Start with a free assessment of one database you choose.
Get a free assessmentRelated resources
Protect your brand. Start with your data.
Book a demo, or start with a free assessment of one database.


