Your Data Is in the Cloud. Is It Protected?

By VaultTek | November 20, 2026

“Our data is in the cloud, so we’re protected.”

It’s an understandable assumption.

Cloud technology has transformed how organizations store, access, and manage information. Files are available from multiple locations. Employees can collaborate without being in the same building. Organizations can expand their storage capacity without purchasing additional equipment or maintaining extensive on-site infrastructure.

For courts, municipalities, and other organizations responsible for essential records, these advantages can be significant.

But there is an important distinction that is sometimes overlooked.

Storing data in the cloud is not the same as having a comprehensive data-protection strategy.

The cloud is not an invisible, indestructible place where information is automatically immune to loss.

It is a physical environment, operated by people, dependent on hardware, software, power, networks, and security controls. And like any physical environment, it can experience hardware failures, disruptions, human error, and cyberattacks.

That doesn’t make cloud technology inherently unsafe.

It means organizations need to understand what the cloud protects, what it doesn’t, and why having additional, independent copies of essential data remains so important.

What Is the Cloud, Really?

When someone says their data is stored “in the cloud,” what they generally mean is that the information resides on computers and storage systems located somewhere other than their own office.

Those systems are housed in physical data centers containing servers, networking equipment, storage devices, cooling systems, and power infrastructure.

A cloud provider manages much of that technology so customers can access applications, documents, and other resources over the internet.

The arrangement offers important advantages:

    • Accessibility: Authorized users can retrieve information from different locations and devices.
    • Scalability: Storage and computing resources can expand as organizational needs change.
    • Reduced infrastructure demands: Organizations may not need to purchase, house, and maintain as much local equipment.
    • Geographic redundancy: Some providers distribute data and services across multiple facilities or locations to reduce the impact of individual failures.
    • Managed infrastructure: Providers can handle many underlying maintenance, availability, and security responsibilities.

 

These are legitimate benefits, and for many organizations, cloud services have become essential to everyday operations.

But moving information into a professionally managed data center does not eliminate every risk associated with that information.

It changes where some of those risks reside and who is responsible for managing them.

The Cloud Is Still Vulnerable to Data Loss

Cloud providers invest heavily in infrastructure reliability, security, and redundancy. In many cases, their facilities offer protections that would be difficult or costly for an individual organization to reproduce.

Even so, cloud environments are not immune to problems.

Consider what can happen when:

    • Hardware or storage systems fail.
    • Power or network disruptions make services unavailable.
    • Software errors corrupt or delete information.
    • An employee accidentally removes important records.
    • Compromised credentials allow unauthorized access.
    • Ransomware or malicious activity affects cloud-connected data.
    • A cloud provider experiences a configuration error or service failure.

 

Some of these incidents result in temporary interruptions. Others can affect the integrity, availability, or recoverability of stored information.

And while cloud providers may maintain multiple copies of data within their infrastructure, those copies do not necessarily provide the same protection as an independent backup.

Consider three related but different concepts:

Cloud Availability: Is the platform operational, and can users access it when needed?

Cloud Redundancy: Does the provider maintain additional copies or infrastructure to withstand certain equipment or service failures?

Independent Backup and Recovery: If the original cloud environment or its data becomes unavailable, corrupted, or deleted, does the organization have a protected copy that can be restored independently?

These protections may work together, but they are not interchangeable.

An organization may have an excellent cloud platform with redundant infrastructure and still discover that a problem affecting its account, configuration, or stored records has consequences beyond what it anticipated.

Redundancy within a system is not always the same as having independent recovery options outside that system.

Real-World Example: When Google Cloud Deleted a Customer’s Environment

In May 2024, Australian retirement fund UniSuper experienced a major service disruption after an error within Google Cloud resulted in the unintended deletion of one of its private cloud environments.[i]

According to a joint statement from UniSuper and Google Cloud, the organization had duplicated infrastructure across two geographic zones to protect against outages and data loss.

However, the deletion affected the private cloud environment across both zones.

It was not a cyberattack. Google Cloud later explained that an inadvertent configuration error during the original setup of the environment had triggered an unexpected automatic deletion.

The incident disrupted UniSuper’s systems and required extensive work to restore hundreds of virtual machines, databases, applications, and supporting infrastructure.

How did UniSuper recover?

Importantly, UniSuper had maintained additional backup arrangements beyond the affected private cloud environment, including resources from another service provider.

Those backups, together with other unaffected backup resources, helped UniSuper and Google Cloud restore the environment and bring critical systems back online.

In a February 2025 follow-up report, UniSuper confirmed that no member data had been lost or exposed. The organization credited its multi-cloud strategy and recovery practices with helping it navigate the disruption, although restoring its systems took approximately two weeks.

What changed afterward?

Google Cloud reported that it had corrected the system behavior responsible for the unintended deletion, reviewed other private cloud environments for similar vulnerabilities, and eliminated the need for the internal provisioning process that had contributed to the problem.

UniSuper also conducted an independent review of the incident.

The organization subsequently introduced additional vendor-management and risk-control measures, including new governance procedures for technology providers and improvements to monitoring, reporting, and operational resilience.

The lesson is not that Google Cloud, or cloud technology generally, cannot be trusted.

It is that even sophisticated cloud environments with geographic redundancy can experience unexpected failures.

UniSuper’s recovery was supported by backup arrangements and recovery resources that were not affected by the original incident.

Its experience reinforces an important distinction: Having redundant cloud infrastructure may help prevent some disruptions, but independent backups and a tested recovery strategy provide additional protection when something unexpected occurs.

Cloud Storage, Synchronization, and Backup Are Not the Same Thing

Another common misconception involves cloud-based file-sharing and synchronization services.

Consider a familiar situation: An employee saves an important document to a cloud-connected folder. The file automatically synchronizes across devices, making the latest version available wherever the employee works. Everything appears protected.

But what happens if that document is accidentally deleted?

Or if ransomware encrypts the files and those changes synchronize to other connected locations?

Cloud platforms may offer version histories, recycle bins, retention policies, and recovery capabilities. Those features can be extremely valuable.

However, their availability and limitations depend on the particular service, subscription, configuration, and retention settings.

They are not necessarily substitutes for a separately managed backup that preserves recoverable versions of essential records.

This connects to a distinction discussed in our previous VaultTek article, Saving Data Isn’t Backing Them Up: Understanding True Backup vs. Storage.

The principle applies equally to the cloud.

    • Saving information makes it available.
    • Synchronizing information helps keep it consistent across connected systems.
    • Backing up information creates additional copies that can be restored when the original data is lost, damaged, corrupted, or otherwise unavailable.

Those are different functions.

Organizations should understand which capabilities they actually have rather than assuming their cloud subscription provides all three.

Who Is Protecting Your Vendor-Hosted Records?

As more organizations move essential applications into the cloud, another important consideration emerges.

Where are the records generated and maintained by those applications, and who is responsible for protecting them?

Many courts, municipalities, and professional organizations rely on third-party vendors to host important systems. These might include case-management platforms, document-management applications, financial systems, or other specialized software.

In these arrangements, organizational records may reside entirely within the vendor’s infrastructure rather than on local servers.

That can create a protection gap if those records are not included in the organization’s established backup processes.

For example, an organization may have reliable backups for its on-site network while assuming that records maintained by an outside software provider are automatically protected.

The vendor may indeed maintain backups and offer recovery services.

But what do those protections actually include?

How frequently is information backed up? How long are previous versions retained? Can individual records be restored? What happens if the vendor experiences a prolonged outage, a configuration error, or an incident affecting its own backup environment?

And perhaps most importantly, does the organization have an independent recovery option if the vendor cannot restore its records when needed?

These are questions worth addressing before essential information is entrusted to a third-party system.

The goal is not to avoid vendor-hosted applications.

It is to ensure that the organization’s data-protection strategy evolves as the locations and methods of storing its records change. As we shared in a previous article, Having IT Support isn’t the Same as Having a Data Protection Strategy.

When Cloud Convenience Creates Additional Security Risks

The flexibility that makes cloud technology useful can also create challenges when employees adopt services outside established organizational practices.

Two related concerns are Shadow IT and App Sprawl.

Shadow IT refers to software, applications, or technology services used without the approval or oversight of an organization’s IT department.

An employee may use an unapproved file-sharing platform to exchange documents. A department may subscribe to an online application because it simplifies a recurring task.

The tools may work perfectly well, but important organizational information could now reside in systems that IT cannot monitor, properly secure, or include in established backup procedures.

Over time, these individual decisions can lead to App Sprawl – the proliferation of applications and services that becomes increasingly difficult to manage.

More applications can mean more accounts, permissions, vendors, security settings, and places where critical information may reside.

As discussed in our September article on daily operational risks, the technology environment an organization believes it has may not be the same environment employees actually use.

That matters because organizations cannot reliably protect or recover information they do not know exists or cannot locate.

The answer is not to discourage employees from using helpful technology. It is to establish visibility, reasonable controls, and approved processes that make secure cloud use practical.

On-Site or Cloud Backup? The Stronger Answer Is Both.

In our April 2023 article, Is On-site or Cloud Backup Best for Data Protection? Actually, it’s Both, we explored the strengths and limitations of each approach.

That conclusion remains relevant today.

On-site backups generally offer faster access to information and greater direct control over local recovery resources. They can be particularly valuable when essential records must be restored quickly to keep operations moving.

However, on-site equipment can be affected by hardware failure, theft, fire, flooding, severe weather, or a security incident that compromises the local network.

Cloud-based backups offer geographic separation, scalability, and protection when an organization’s physical location becomes unavailable.

But recovering large volumes of data from a remote environment may take time, and cloud services introduce dependencies on internet connectivity, provider availability, access controls, and vendor recovery procedures.

Neither approach eliminates every risk. Combining them creates additional options.

If local systems fail, protected off-site backups may provide a recovery path.

If a cloud environment experiences an outage or other failure, an independently maintained local or alternative off-site backup may help reduce disruption.

This approach is commonly called a hybrid backup and recovery strategy.

Its strength lies not simply in keeping more copies of information, but in reducing dependence on any single location, system, technology, or provider.

Where Should an Organization Start?

A hybrid solution does not necessarily mean purchasing every available technology or storing every file in every possible location.

For organizations managing limited budgets and extensive records, prioritization is essential.

Not all information has the same operational value or requires the same speed of recovery.

As discussed in our three-part Risk Management series, effective planning begins with identifying potential threats, analyzing their impact on essential business assets, and developing strategies to mitigate those risks. This framework can help organizations prioritize their data-protection investments based on actual vulnerabilities and operational needs, rather than assumptions.

A useful starting point is to ask:

  1. Which records are most critical to daily operations?

Identify the applications, documents, databases, and essential records needed to continue providing services. These may warrant more frequent backups and faster recovery capabilities.

  1. Where does the information actually reside?

Review local servers, employee devices, approved cloud platforms, and other storage locations. Include records maintained by third-party software providers and look for information that may exist outside established backup procedures.

  1. What protections do our cloud and software vendors actually provide?

Determine who is responsible for backups, how frequently they occur, how long information is retained, and what recovery options are available. Do not assume that vendor-hosted records are automatically included in the organization’s own backup strategy.

  1. Are backup copies truly independent?

Multiple copies offer limited protection if a single compromised account, configuration error, or system failure can affect all of them.

Consider separation across locations, storage environments, and access controls.

  1. How quickly must essential records be restored, and have we tested that capability?

Some information may be needed within hours, while other records can tolerate longer recovery periods. Understanding these differences helps organizations prioritize resources.

And a successful backup notification does not automatically establish that an organization can restore the records and applications it needs.

Recovery should be verified before an emergency.

Having your group perform tabletop exercises will help them walk through realistic disruption scenarios can reveal gaps in responsibilities, procedures, and recovery assumptions before an actual incident occurs.

These questions help leadership and IT make informed decisions about where to invest, what to protect first, and how to balance cost with operational risk.

Building on the 3-2-1 Backup Rule

A practical foundation for a hybrid approach is the established 3-2-1 backup methodology:

    • 3 copies of essential data
    • 2 different types of storage media
    • 1 copy stored off-site

The objective is straightforward: reduce the likelihood that one incident can compromise every available copy of important information.

As outlined in our earlier article, 3-2-1 Backup Rule Is Best Baseline for Your Data Protection Plan, this methodology is a starting point rather than a one-size-fits-all solution.

Organizations may need additional geographic separation, offline or otherwise isolated backup copies, stronger access protections, and more frequent recovery testing based on the importance of their records.

The key is to build protection around the organization’s actual recovery needs.

Because having three copies of information is only valuable if those copies remain accessible and recoverable when they are needed.

From Cloud Confidence to Vault-Tight Protection

Cloud technology has earned an important place in modern operations.

It provides accessibility, flexibility, and capabilities that can help organizations work more efficiently and securely.

But confidence in a cloud provider should not be confused with a complete data-protection strategy.

For courts, local governments, and other organizations responsible for essential information, the objective is not simply to store records somewhere “safe” and think, “That Won’t Happen to Us”.

It is to ensure those records remain protected and recoverable when systems, devices, infrastructure, or service providers experience a problem.

At VaultTek, our vault-tight approach is grounded in the proven 3-2-1 backup methodology. We provide triple-redundant protection through secure on-site backup and two geographically separate, U.S.-based off-site backups, supported by proactive monitoring and personalized service.

Our approach recognizes that essential information may reside in different environments, including on-site systems and vendor-hosted platforms. Protecting that information requires solutions appropriate to where the records are maintained and how they can be securely included in a broader recovery strategy.

Because the cloud is a valuable place to store and protect data.

It just shouldn’t be the only place an organization depends on when that data needs to be recovered.