
The dangers of centralized data storage
8 min readUpdated
Data can reside in several data centers while depending on one operator and one account. Check access management, the location of copies, and the ability to retrieve data outside the service separately.
Start with one storage service: identify who manages the account, which connections have access, and how to export the files you need. The word “centralized” or “decentralized” does not establish the security of a particular service.
What is centralized data storage
In this article, centralization means that one operator or a limited group of organizations manages the storage. The number of users and servers does not determine this on its own.
Distinguish between:
- Management: Who sets access rules and can change them.
- Location: Where live data and copies reside.
- Dependencies: Which accounts, keys, and services are needed to retrieve data.
In the informational RFC 9518, the author distinguishes the technical distribution of components from the concentration of control. The document represents the author's views rather than IETF community consensus.
| Metric | Result | max | avg | min |
|---|---|---|---|---|
| Ping | —ms | — | — | — |
| Download | —Mbps | — | — | — |
| Upload | —Mbps | — | — | — |
Single point of failure
One operator does not necessarily mean one server. For example, AWS describes S3 Standard storage across at least three Availability Zones within one region. S3 One Zone-IA has different conditions: it uses one zone.
Component redundancy and independence from an operator are different properties. Several copies do not provide access if all of them require an unavailable account.
Check what retrieving a file depends on: account sign-in, a key, an application, and the network. Find out whether you have an accessible copy outside that chain. Do not use the number of servers as a complete assessment of failures.
Mass data breaches and their irreversibility
In July 2019, the FTC announced a settlement with Equifax following the 2017 breach affecting approximately 147 million people. The commission linked the case to inadequate security measures at the company.
This illustrates the scale of a particular incident; it does not prove that every centralized storage service will be breached. The number of people affected is not a comparative test of architectures either.
Check which information the selected service stores and whether your task requires it. Changing a password does not remove records about a person that have already been exposed. Whether data can be replaced or revoked depends on its category; biometric information and historical records need separate consideration.
Loss of control over personal information
Find answers for your service:
- Who the operator is and where to send questions about data.
- Who can gain access: The account owner, people with shared access, connected applications, and staff under the service's terms.
- Which retention periods and deletion procedures are described.
- Which data can be exported and in what format.
- Who manages encryption keys, if that feature is used.
Mark a missing answer as unknown. A policy and a permissions screen describe different aspects of processing; neither is a complete log of activity involving server data.
How to review devices with Google Account access
- Open the official Google Account page and check the selected account.
- Open Security & sign-in.
- Under Your devices, select Manage all devices.
- Select a device or session and compare the available details with your activity.
- If you do not recognize a session, follow Google's instructions for unfamiliar activity.
Several sessions can belong to one device. This list does not show every employee of the operator or every access to data on the server. An unfamiliar entry needs investigation rather than an automatic conclusion that a breach occurred.
Abuse and secondary use of data
On January 18, 2024, the FTC announced its InMarket case. According to the commission, the company obtained location data from its own applications and third-party applications containing its SDK, a set of its software components.
The FTC described matching visits to places and creating advertising segments. It alleged that users had not been adequately informed about this use of data.
This describes a particular case, rather than proving that all storage services operate the same way. Check the stated processing purposes, combination with other sources, and recipients. An advertising segment's label is not an established fact about a person.
How account rules affect access
Access can depend on account status as well as technical failures. Google states that a disabled account cannot be used to sign in to Google services or with Sign in with Google.
The owner can use an appeal procedure. Its existence does not guarantee reinstatement. Check the service's own notice for the reason and available actions.
Do not infer a political reason for a restriction solely from the storage architecture. Check sign-in recovery and data retrieval options in advance. A copy in a service that depends on the same account retains that dependency.
Centralization vs decentralization
Compare specific implementations. The architecture's name does not answer the following questions.
| Criterion | One operator | Several independent participants |
|---|---|---|
| Management | Who changes access rules? | Who makes shared decisions? |
| Failure | Which dependencies have redundancy? | Which dependencies remain shared? |
| Content access | Who has permissions and keys? | Who receives copies and keys? |
| Deletion | How are live data and copies deleted? | Can participants' copies be deleted? |
| Transfer | How can data be exported and read? | How can a node or participant be replaced? |
| Recovery | How can data be retrieved if the operator fails? | How can data and the required keys be recovered? |
Error amplification
Shared software, a setting, or a rule can spread one error across several components. The scope depends on where a change is applied and what isolation measures exist. The author of RFC 9518 discusses the risk of shared software dependencies.
If access fails, record the exact message, time, and action that failed. Check the service's official notice. An unavailable file does not by itself prove a breach or irreversible deletion.
For an important file, separately check whether you can open a saved copy without the unavailable service.
What to check in distributed storage
Distributing copies does not establish confidentiality. For example, the IPFS documentation describes a public network: information about peer and content identifiers can be available in a distributed table.
Connections between peers are encrypted, but that does not mean file contents are encrypted. The documentation addresses content protection separately.
Before choosing a system, find out who can obtain a copy, who manages keys, how availability is maintained, and what deletion means. Do not publish personal data on a public network simply because it is distributed. These IPFS conditions do not describe every decentralized product.
How to check portability and a backup copy
Before transferring important data:
- Select a small set of files you need.
- Check the available export formats and applications that can read them.
- Save a copy in a protected location of your choice. Check which accounts and keys are required to access it.
- Open the saved files with a suitable application and check the content you need.
- If you plan to restore data in another service, check its supported import separately.
A readable export and a backup ready for restoration are different results. Do not delete the originals before checking the files you need. For work data, follow your organization's rules and agree on the transfer with an administrator.
How to export selected Google data
- Open the official Google Takeout page and check the selected account.
- Deselect products you do not need. Review the available export contents for the selected product.
- Select Next step and choose archive settings and a one-time export.
- Choose delivery by link and select Create export.
- When the export is ready, use Google's message or the export page to download it.
- Check the archive contents and whether the required files open. Store the export with regard to the personal data it contains.
According to Google's export help, exporting does not delete the original data. It does not guarantee restoration of all account functions. Contents depend on the selected product; obtaining an archive is not a check that every record is included.
What to check before choosing storage
Keep the results of your checks: operator, sign-in methods, permissions, retention terms, available export, and a verified copy. Look up unknown properties in the documentation or ask support.
After changing access, check the setting again. After exporting, check the required files. These actions do not confirm the absence of every breach, deletion of server copies, or future service availability.
Further checks are covered in the smartphone security guide and the article on browser identification without cookies.
Author: Adam Jensen — Cybersecurity specialist, VPNON