Protecting company data starts with knowing where it lives

A useful data-protection conversation starts with four questions: where is the information, who needs access, what happens if it is unavailable and who is responsible for it?

Illustration of scattered data nodes connected by dashed lines to a central gradient vault with a padlock

A useful data-protection conversation starts with four questions: where is the information, who needs access, what happens if it is unavailable and who is responsible for it? Answer them for the places your business actually works, including cloud applications and files stored on employee devices.

You do not need a complicated diagram to begin. A working list can reveal decisions that are currently spread across several people and providers.

Map information to the work it supports

Start with important activities such as preparing customer work, processing invoices and managing employees. For each activity, list the systems and documents it depends on.

Record the business owner, administrator, storage location and any outside provider involved. Ask employees where they keep working copies and how they share files. The answer may differ from the place management expects the final version to live.

Keep the list understandable to someone outside IT. “Customer project files used by the delivery team” explains more than an unexplained server name.

Decide who should be able to use it

Separate information intended for public use from information meant for a particular team, customer or business purpose. Have the responsible business owner decide who needs access and bring uncertain restrictions to the appropriate adviser.

Then compare that decision with current access. Include external sharing, former staff and connections to other applications. Make changes through a planned process so the business understands any effect on current work.

Account administration and business account security are part of the same conversation: the file location and the permission to reach it both matter.

Ask what recovery would involve

For each important system, ask what is protected, where recovery responsibility sits and what evidence exists that the relevant information can be restored. Discuss the order in which business activities would need to resume.

NIST's small-business guidance includes understanding recovery responsibilities and checking the integrity of backed-up data before restoration. Read the NIST Small Business Quick-Start Guide.

Use that discussion to identify unanswered questions. A cloud subscription, synchronization setting or backup label should not substitute for understanding the actual recovery arrangement. The Backup & Recovery page explains the business questions to bring to that conversation.

Review new destinations before information moves

A newly connected application or AI tool can add another place where business information is used. Before approving it, ask what information it needs, who can access the result and what the vendor's terms and settings allow.

Keep approvals tied to a defined purpose. Permission to summarize a public document does not automatically cover confidential project files. Give staff a clear route for asking about new uses rather than expecting them to interpret every vendor setting themselves.

Frequently asked questions

Do we need to inventory every file first?

Begin with important business activities and the systems supporting them. Expand the picture as you find dependencies and gaps.

Does keeping information in the cloud answer the backup question?

No. Confirm the particular service, configuration, retention and recovery responsibilities rather than assuming the location tells you everything.

Is data protection separate from managed IT?

For ProIncident, protecting people, accounts, devices, email and data is part of the ongoing technology relationship. Cybersecurity is included in the standard managed service.

Put responsibility around the information that matters

Bring the places your team stores and shares important work. We can discuss access, protection and responsibility across that environment.

Talk to ProIncident · See Pricing