Protecting ePHI in the Cloud: HIPAA-Compliant Cloud Backup Strategies for US Healthcare

Managing electronic protected health information (ePHI) in the cloud has become necessary as healthcare organizations progressively choose cloud technologies. This method raises data remote access, cost-effectiveness, and accessibility.

However, it also comes with compliance and security issues. Failing to protect ePHI, even in backups, for covered entities under the Health Insurance Portability and Accountability Act (HIPAA) runs a risk of significant fines, legal action, mistrust development, and damage to patient relationships.

Thus, providers must ensure that their backup plans are safe, tested, and monitored closely against government rules. This post explores the most practical approaches and insights relevant to U.S. healthcare institutions.

HIPAA Requirements for Backing Up ePHI

ePHI protection is governed by the Health Insurance Portability and Accountability Act (HIPAA). This act also specifies how ePHI must be backed up and recovered should a disaster or failure strike. HIPAA outlines critical backup-related criteria but does not specify certain technologies:

• Procedures must be in place for data backup to generate and preserve exact, retrievable copies of ePHI.
• In data recovery plans, organizations must specify how ePHI would be rebuilt following a cybercrime, system outage, or natural disaster.
• Critical systems must be able to operate in emergency conditions to protect data integrity in emergency mode plans.
• Backup and recovery strategies must be routinely tested and changed depending on changing risk.
• Only authorized staff members should access ePHI; audit trails are in place to track interactions.

Meeting these criteria in a traditional on-premise solution is tough enough. In a cloud-based setting, the stakes are even higher, and the strategies more complex.

On-Prem vs. Cloud Backup for HIPAA

Cloud backup offers greater flexibility and cost efficiency. However, it shifts part of the security responsibility to your provider. Vetting and partnering with the right cloud service provider (CSP) is critical.

Why Cloud Backup Requires Special Attention

Cloud backup offers agility and cost savings, but it also brings new levels of complexity, especially around shared accountability. Many healthcare businesses wrongly assume their cloud provider manages HIPAA compliance by default. In truth, compliance is a joint effort.

Cloud-specific risks include:

• Multi-tenancy: Data hosted on shared infrastructure increases exposure.
• Remote Access: Greater accessibility can lead to increased attack surfaces.
• Data Sovereignty: The physical location of your data may affect compliance with US regulations.

Understanding your and the provider’s roles is crucial for protecting ePHI.

How to Build a HIPAA-Compliant Cloud Backup Strategy

An effective cloud backup plan has to be proactive, tested several times, and compliant with HIPAA. Here’s how you approach it:

Choose the Right Cloud Provider

Not every cloud vendor is prepared to meet HIPAA’s requirements. You’ll need a provider that:

• Offers a signed Business Associate Agreement (BAA)
• Demonstrates a proven track record with healthcare clients
• Provides transparent security practices and compliance certifications

Seek vendors with industry-standard certifications, including HIPAA, HITECH, and SOC 2 Type II.

Encrypt Data at All Times

HIPAA necessitates the safeguarding of ePHI both at rest and in transit. This means

• Enabling AES-256 encryption for stored backups
• Using TLS or SSL protocols for data transfer
• Implementing secure key management systems

This ensures that the data remains unreadable even if unauthorized actors access backups.

Ensure Data Redundancy and Availability

Cloud backups must be:

• Geo-redundant in order to withstand regional outages.
• Supported by Recovery Point Objectives (RPOs) and Acceptable Recovery Time Objectives (SLAs) specifications.
• Capability of automatic and frequent backups with choices for long-term storage.

Redundancy isn’t just a performance booster; it’s a compliance measure.

Implement Strong Access Controls

Unauthorized access is one of the most common causes of HIPAA breaches. Limit exposure by:

• Using Role-Based Access Controls (RBAC) to grant access based on job roles
• Enforcing the principle of least privilege
• Deploying Multi-Factor Authentication (MFA) for cloud portal access
• Logging and auditing all interactions with backup systems

This creates a controlled, traceable environment around your sensitive cloud data.

Conduct Regular Testing and Validation

A backup that doesn’t work is a liability. HIPAA requires regular testing and revision of all backup and disaster recovery procedures. Best practices include:

• Simulating disaster scenarios to test recovery speed and integrity
• Documenting results and updating policies accordingly
• Involving IT and compliance teams in every phase of the testing process

Testing ensures that your cloud-based recovery plan isn’t just theoretical—it’s reliable when needed.

Common Pitfalls to Avoid

Even well-intentioned organizations can fall into traps that undermine their HIPAA backup strategy. Watch out for these frequent mistakes:

• Assuming all cloud storage is HIPAA-compliant. A vendor’s offering of encryption or redundancy does not automatically satisfy all compliance criteria.
• Failing to sign a business associate agreement (BAA) means your cloud provider is not legally obligated to follow HIPAA.
• Using consumer-grade backup tools. For instance, the Standard edition of Dropbox or Google Drive lacks the restrictions required for healthcare data and isn’t built for HIPAA compliance.
• Ignoring backup monitoring calls for regular validation of completion, integrity, and accessibility.

Steering clear of these traps calls for diligence, teamwork, and vendor responsibility.

The Role of Immutable Backups and Air-Gapping

Healthcare organizations should consider including immutable backups (copies of data that cannot be changed or deleted for a designated period) for extra security. These backups can stop ransomware attackers from either encrypting or destroying recovery information.

In tandem, air-gapping techniques (storing backups in physically or logically separated environments) offer another layer of protection. Appropriately utilized techniques enable you to keep HIPAA compliance even in worst-case situations.

To Sum Up: Compliance is a Continuous Process

Adoption of cloud backup systems only modifies your HIPAA responsibilities rather than absolving them. Protecting ePHI in the cloud calls for a well-crafted backup plan that strikes a compromise between security, performance, and compliance.

To recap, a HIPAA-compliant cloud backup strategy should:

• Built with a vetted provider that offers a BAA
• Include encryption, access controls, and redundancy.
• Be tested and monitored regularly.
• Align with HIPAA’s administrative, physical, and technical safeguards

Cloud backup compliance reflects your company’s dedication to data protection, patient safety, and regulatory responsibility, more than just a checkbox. Your patients and operations will be less vulnerable in the face of growing risks, the more solid your plan is.

European data protection is undergoing a quiet but radical shift. Once centered on legal compliance and checkbox auditing, it is now a high-stakes game of cybersecurity resilience. The rise of sophisticated ransomware, targeted attacks on backup systems, and the rapid expansion of cloud and IoT infrastructure have left organizations vulnerable, even those that believe they are prepared.

Regulatory evolution, like the GDPR and the new Data Act, reflects this new reality: data must be protected, recoverable, reliable, and continuously available.

This post explores two critical technologies that have emerged as strategic defenses in this environment: immutability and air-gapping. For European businesses facing a growing cyber threat landscape, they are increasingly essential to both compliance and continuity.

The Expanding Web of European Data Regulations

The EU’s data protection framework continues to evolve in scope and complexity:

• GDPR emphasizes privacy and security. Article 32 mandates the ability to promptly restore availability and access to personal data in the event of a technical or physical incident.
• ISO/IEC 27001 now includes enhanced cloud and SaaS protection measures, targeting resiliency in modern infrastructure.
• The Data Act, applicable from September 2025, shifts the conversation toward accessibility, fairness, and transparency in data usage. It mandates secure and user-controlled access to data from connected devices, raising the bar for secure data handling.

These regulations are not mutually exclusive. Together, they push organizations toward architectures that can retain data securely, enable user access and deletion, and maintain business continuity even in a crisis.

Why Backups Alone No Longer Cut It

Backups have traditionally been a fallback option, essential but passive. Unfortunately, attackers have caught up. A 2024 report on cyberattacks and ransomware shows that over 2 million cases of breaches were recorded from 556 publicly disclosed breaches in the EU.

Modern ransomware now encrypts production data and actively seeks out and destroys backup files and infrastructure. For example, some ransomware strains include scripts designed to locate Veeam or Hyper-V backups and corrupt or delete them. Others exploit admin credentials to access and erase snapshots or backup volumes. Once this happens, even the most comprehensive backup strategy is rendered useless.

This is where immutability and air-gapping enter the equation.

What Is Immutability?

Immutability is the ability to store data in a way that cannot be altered, deleted, or overwritten for a defined retention period. Data kept on immutable storage stays exactly as it is—tamper-proof and time-locked once written.

Key Benefits:

• Ransomware protection: Attackers cannot modify or delete immutable backup files.
• Compliance-ready: Meets retention requirements under GDPR, financial, and healthcare regulations.
• Audit integrity: Immutability ensures logs and data are preserved without risk of tampering.

How It Works:

• On-premises: WORM-enabled NAS or object storage.
• Cloud: Amazon S3 Object Lock, Microsoft Azure Immutable Blob Storage.
• Backup software: Veeam, Commvault, and others now support immutable backup repositories.

What Is Air-Gapping?

Air-gapping, particularly with relation to the internet, is the process of separating a system or network from unprotected networks. In data security, it refers to either physically (offline) or logically (network-segmented with rigorous access restrictions) storing backup copies in an environment totally separate from any production network.

Types of Air-Gapping:

• Physical: Offline tapes or disks, manually disconnected from the network.
• Logical: Isolated systems or networks with strict access controls, segmentation, or one-way data transfer mechanisms.

Key Benefits:

• Ultimate isolation: Prevents lateral movement of malware to backups.
• Survivability: Data remains safe even in the case of a full production environment compromise.
• Resilience during disasters: Ensures recovery capacity even when networks are down or compromised.

Comparison Table: Traditional Backups vs. Immutability vs. Air-Gapping

Together, they provide layered protection. Immutable backups protect against tampering, while air-gapping ensures backups remain unreachable by attackers.

Use Cases in European Business Environments

SaaS Providers and Cloud Services 

Companies hosting customer data under GDPR must ensure availability and recoverability. Combining immutable snapshots with logically air-gapped storage helps meet resilience and compliance requirements.

Manufacturing and IoT-Driven Sectors 

With the Data Act mandating user access to IoT-generated data, manufacturers must store and protect vast volumes of telemetry. Immutability ensures these datasets remain accurate and auditable; air-gapping protects against targeted OT attacks.

Healthcare and Public Sector 

These sectors are highly regulated and often targeted by ransomware. Immutability secures patient records against tampering, while air-gapping ensures continuity even during a breach.

Agriculture and Smart Infrastructure 

Farmers using precision agriculture tools generate sensitive location and environmental data. Air-gapped storage can help protect this data from being exploited, while immutability ensures it remains accurate for subsidies, audits, or sustainability reports.

Preparing for the Future: Security Meets Regulation

The Data Act is pushing organizations to open up their data, but doing so without compromising security will be the real challenge. With the EU emphasizing accessibility and user rights, businesses must find ways to share data without increasing exposure.

Immutability and air-gapping provide the foundational safeguards to enable this. They ensure that data is unaltered even if it is widely shared. And even in cases of network breaches, a secure, offline recovery path exists.

In this way, these technologies are not just about cyber defense. They are enablers of digital trust, the cornerstone of Europe’s data-driven future.

Final Thoughts

European data protection strategies are evolving toward a model that assumes breach readiness as much as it assumes legal compliance. Immutability and air-gapping are central to this paradigm. When implemented correctly, they help businesses meet their obligations under GDPR, ISO 27001, and the Data Act and ensure that data can survive the threats that regulations can’t predict.

Security now means continuity. In Europe’s digital future, continuity requires architecture built for the worst day, not just the best intentions.

The growing need for resource maximization in daily businesses has led to the need to embrace virtualization. This modern innovation offers swift data recovery and continuity and saves costs. Two names commonly arise when assessing virtualization or private cloud platforms: Proxmox VE and OpenStack. Though they have somewhat diverse application uses, both are open-source and powerful.

Whether you manage a home lab, run SMB infrastructure, or build enterprise-grade clouds, this guide compares Proxmox vs. OpenStack to help you choose the right solution.

Quick Comparison Table

What Is Proxmox VE?

Proxmox virtual environment (VE) is a broad, open-source server management tool for enterprise virtualization. It combines the KVM hypervisor, Linux Containers (LXC), software-defined storage, and networking features into a single platform. This Debian-based VE offers an integrated web-based user interface that allows you to easily manage VMs and containers, high availability for clusters, and disaster recovery solutions.

Small—to medium-sized firms and labs seeking simplicity, speed, and control will find this “all-in-one” virtualization solution perfect.

Key Benefits of Proxmox

• Its setup is easy and installable in under 30 minutes with bootable ISOs.
• It offers an all-in-one stack with built-in storage management, high availability, backups, and a firewall.
• The user-friendly interface manages nodes, VMs, containers, and clusters from a unified web GUI.
• Offers ZFS support for robust storage capabilities with snapshots and replication.
• Low management overhead with zero need for multiple services or extensive orchestration.

Limitations of Proxmox

• No official plugins or native integrations with AWS, Azure, or Google Cloud.
• Proxmox updates can occasionally break clusters or kernel compatibility if not properly staged or tested.
• Some advanced features (e.g., fine-grained ZFS tuning, advanced network configs) often require manual CLI configuration.

Backup and Recovery for Proxmox VE

Today, securing virtual and container environments is just as important as the efficient and stable operation of the entire infrastructure. Storware extends the capabilities of standard data protection with a layer of cyber resilience, automation, no vendor lock-in, and a multitude of backup destinations. Learn more

What Is OpenStack?

OpenStack is a popular modular cloud operating system that handles large pools of resources. This open-source system facilitates the building and administration of both public and private clouds. The OpenStack platform’s tools, known as “projects,” manage the key cloud computing services of computation, networking, storage, identity, and imaging services. It can combine over a dozen optional projects to form unique, deployable clouds.

OpenStack consists of multiple components, such as:

• Nova (Compute)
• Neutron (Networking)
• Cinder (Block Storage)
• Glance (Image Services)
• Keystone (Identity)
• Horizon (Dashboard)

Key Benefits of OpenStack:

• Supports plugins, APIs, and third-party integrations using flexible frameworks.
•  Its broad ecosystem integrates with Red Hat, Canonical, Mirantis, and other vendors.
• Built for deep multi-tenant systems with hundreds of nodes, unparalleled scalability
• Integration of multiple hypervisors, including KVM, Xen, Hyper-V, and VMware.

Drawbacks of OpenStack:

• Requires a thorough understanding of distributed systems, virtualization, and networking.
• Particularly in production, upgrades between versions can be dangerous and disruptive, needing either complicated migration methods or downtime.
• Community-driven, so some bugs or features take a long time to be addressed unless they’re prioritized by large contributors (like Red Hat, Huawei, or Canonical).

Backup and Recovery for OpenStack

Storware, as an official partner of the OpenInfra Foundation, emphasizes its commitment to comprehensive security of OpenStack-based infrastructure. Learn more

Key Differences Between Proxmox and OpenStack

While both are two of the industry’s popular choices, they have clear differences, including:

Deployment & Complexity

Proxmox:

• Setup takes under an hour with an ISO installer.
• Cluster creation is simple and often GUI-based.
• No need for orchestration tools like Juju, Ansible, or Helm.
• Ideal for IT teams with limited resources or sysadmin skillsets.

OpenStack:

• Installation is modular but complex; it is typically done via deployment tools like DevStack, Packstack, or TripleO.
• Requires orchestration and configuration management tools (e.g., Ansible, Helm, Juju).
• It demands deep architectural planning, such as authentication, storage backend, SDN, etc.
• Better suited for teams with cloud architects, DevOps engineers, and dedicated support.

Scalability and Performance

Proxmox:

• Supports clustering and high availability for up to 32 nodes easily.
• Built for single-site deployments or modest multi-node setups.
• Performance is excellent with KVM and LXC, but bottlenecks at hyperscale.

OpenStack:

• Built for hyperscale environments, with the ability to support thousands of compute nodes.
• Designed for multi-tenant, geographically distributed clouds.
• Can dynamically allocate resources via APIs, orchestration tools, and service layers.

Use Cases

Proxmox Excels In:

• Homelabs and personal virtualization.
• Small-to-medium enterprise data centers.
• On-premise VMs and containers without cloud abstraction.
• Rapid deployment of virtualized test environments.

OpenStack Excels In:

• Telcos and service providers who need NFV (Network Functions Virtualization).
• Enterprises that are building private or hybrid cloud infrastructure.
• Public cloud providers offering IaaS with tenant isolation.
• Organizations requiring fine-grained RBAC, automation, and multi-region deployments.

Storage and Networking

Proxmox:

• Integrated storage is via ZFS, Ceph, LVM, and NFS.
• Default networking is Linux Bridge, with OVS for advanced setups.
• No SDN controller out of the box.

OpenStack:

• Software-defined storage via Cinder (block), Swift (object), Manila (file).
• Advanced SDN features through Neutron.
• Can integrate with Open vSwitch, Calico, and commercial SDNs.

Management and Automation

Proxmox:

• Clean web UI with monitoring, backup, and cluster views.
• Basic automation via API and CLI.
• Limited orchestration, but low-maintenance and straightforward.

OpenStack:

• Total control is available via CLI, API, and Horizon dashboard.
• Compatible with Terraform, Ansible, and Heat templates for IaC.
• Designed for CI/CD pipelines, DevOps workflows, and self-service portals.

Final Verdict: Which One Should You Choose?

Conclusion

Proxmox VE and OpenStack are powerful platforms. However, they serve very different purposes. If you’re after simplicity, fast deployment, and a streamlined virtualization experience, Proxmox is your best bet. OpenStack is the clear choice if you need enterprise-grade scalability, custom networking, and a multi-tenant cloud platform. Ultimately, your decision should come from your technical skill set, infrastructure goals, and operational scale.

As for the backup for both Proxmox VE and OpenStack, you can test Storware Backup and Recovery for free or book a one-on-one demo session with our engineer who will be happy to answer all your questions and concerns.

Updating software is one of the simplest and most effective ways to protect data. Unfortunately, many companies postpone or ignore this task.

In recent months, many vulnerabilities have been discovered and actively exploited in storage and backup solutions. These include tools such as Veeam Backup & Replication, MinIO, Veritas Backup Exec, Arcserve UDP, Rubrik CDM, Nakivo, QNAP QuTS Hero OS, and Pure Storage FlashArray and FlashBlade. Notably, some of the vulnerabilities in the latter were rated as a CVSS 10—requiring immediate action. Yet many companies still don’t take update warnings seriously.

Protecting sensitive and confidential data is a top priority for most CIOs. TLS encryption for internet-transmitted messages, AES-256 for data at rest, multi-factor authentication, and zero trust policies are commonly used. However, regular software updates and patching vulnerabilities are discussed far less. Experts agree that outdated software is a ticking bomb. Hackers closely monitor security patch release dates to exploit vulnerabilities in older system versions. Many users fail to follow vendor recommendations or delay updates, creating ideal attack conditions. The best-known example is WannaCry, one of the largest ransomware attacks in history. In May 2017, it infected over 300,000 computers in 99 countries, despite Microsoft releasing a patch two months earlier.

Think of software updates like car maintenance—even the best vehicle will break down without regular oil changes, and worn brake pads will eventually damage the braking system.

Similarly, not updating applications will sooner or later lead to data security breaches and reduced performance. For businesses handling sensitive customer data—such as accounting firms or financial institutions—this could mean financial losses, reputation damage, or even bankruptcy. According to research by NinjaOne, 57% of data breaches could have been prevented with regular updates.

Hitting the Last Line of Defense

While there has been progress in updating OSes and antivirus tools, storage systems and backup software are still neglected. Why? For years, backups weren’t a primary target for hackers. That changed with the rise of ransomware. IDC reports that over half of ransomware attacks target backup systems, and 60% succeed. Veeam’s 2024 Ransomware Trends Report reveals that backup repositories are attacked in 96% of cases, and cybercriminals successfully interfere in 76% of them.

Hackers know that backups are a company’s last resort. That’s why they increasingly encrypt or delete them—limiting recovery options and forcing victims to pay ransoms. Compromising backups threatens business continuity. And ransomware attacks aim not just for extortion, but also to disrupt operations and cause financial harm. Victims with compromised backups are in a weaker negotiation position. According to Sophos, companies whose backups were encrypted paid on average twice as much—a median ransom of $2.3M vs. $1M for those with intact backups.

Ransomware uses various infection vectors: phishing, remote access (RDP), and exploiting software vulnerabilities—often due to missed updates. Whether it’s a backup application or an operating system, unpatched software is a gateway. For example, Veeam CVE-2024-40711 was exploited by groups like Monti and Yanluowang. Similarly, CVE-2023-27532 was used by EstateRansomware to attack corporate environments.

Real-world impact stories stick

Example: In 2023, a mid-sized logistics firm lost all customer data after its backup server running an outdated version of Nakivo was compromised. Despite having backups, the encryption rendered recovery impossible—and the company paid over $1.5M in ransom.

Updating Backup Software = More than Just Security

The backup and disaster recovery (DR) market is evolving rapidly. Vendors regularly release new solutions or update existing ones. While security is key, it’s not the only reason to stay current. Over time, backup tools become incompatible with newer OSes, hardware, and applications.

Updated backup software often includes performance improvements—faster backups and restores, better resource usage, and support for large datasets. These enhancements reduce downtime and boost operational efficiency. Updates may also bring new data recovery features, like instant VM recovery or cross-platform restores.

While backup expenses can be high, proper updates can help reduce costs. New versions often include deduplication, compression, and other optimizations—cutting storage needs and data transfer times. This reduces storage expenses and speeds up backup processes, lightening the load on IT infrastructure.

Another major challenge for IT departments is regulatory compliance. Many industries are bound by strict data protection laws. Updated backup software often includes features that support compliance—such as data retention policies, audit logs, and reporting capabilities.

Summary Table

A Dozen Security Gaps on Average

The average enterprise storage or backup device has 14 security vulnerabilities, including three rated as high or critical. These findings come from Continuity’s State of Storage and Backup Security Report 2023, based on an analysis of 245 environments covering 8,589 devices from vendors like Dell, NetApp, Veritas, and Hitachi Vantara. Most participating organizations were in banking, but also included healthcare, telecom, and IT services.

Properly securing storage systems will soon be a core component of organizational cyber resilience strategies. Business users should not only wait for vendor updates but also adopt proactive practices, such as vulnerability scanning. That’s why interest is growing in Application Security Posture Management (ASPM) tools, which provide real-time system security monitoring. Industry regulations increasingly require automated vulnerability management. For instance, PCI DSS v4.0 mandates the use of automated vulnerability scanning tools.

In short, protecting storage and backup systems is no longer just about security—it’s also about compliance and operational efficiency.

Practical Checklist: How to Secure Your Backup Systems Today

• Audit all backup and storage software versions ✅
• Apply the latest vendor patches and security updates ✅
• Implement multi-factor authentication for backup access ✅
• Regularly test backup restore procedures ✅
• Enable immutability and encryption ✅
• Use vulnerability scanners on backup infrastructure ✅
• Isolate backup systems from the main production environment ✅

Consequences of Not Updating Backup Software

• Increased risk of cyberattacks – unpatched systems are open doors for hackers to access sensitive data and critical resources.
• Decreased system performance – outdated software often runs slower, driving up operational costs.
• Incompatibility with new technology – older apps may not work with modern hardware or OSes, causing functionality issues.
• Regulatory non-compliance – many industries have strict data protection laws. Using outdated software can result in fines or loss of certification.

Updating your backup software isn’t just a matter of maintenance—it’s a critical element of business continuity, compliance, and cybersecurity resilience. Don’t let outdated tools be your weakest link.

Storware 7.3 – what’s new?

→ Resilient Backup for VergeOS: Version 7.3 introduces support for a secondary backup destination for Verge.io, delivering enhanced data protection and greater backup resilience for users of this ultra-converged infrastructure platform. → Expanded OpenStack Capabilities: OpenStack users can now restore security groups during instance recovery and take advantage of support for multiattach volumes, making cloud-native protection even more seamless. → Optimized Performance at Scale: The Storage Area component has been optimized to improve performance, particularly in environments managing thousands of volumes — including those leveraging Ceph RBD, Nutanix Files, and other enterprise-grade storage backends. → Microsoft 365 Throttling Compliance: Storware now enforces a single-node usage per Microsoft 365 organization in response to Microsoft’s service limitations, ensuring compliant and stable backup operations. → Improved OS Agent Restore: Enhancements to the OS Agent restore process deliver faster and more reliable file-level recovery for endpoints and physical servers. → User Interface Enhancements: A redesigned, unified filter modal now provides a consistent experience across all list views. Additionally, the Mounted Backup view now matches the design of VM detail views, along with a series of minor UX upgrades to streamline daily tasks.

Storware 7.3 high level architecture:

Backup → Recover → Thrive

Storware Backup and Recovery ability to manage and protect vast amounts of data provides uninterrupted development and security against ransomware and other threats, leverages data resilience, and offers stability to businesses in today’s data-driven landscape. Get started with a free version or unlock the full potential of Storware Backup and Recovery with a 60-day trial! Choose Storware and protect your success today. For detailed changes, fixes and improvements, see →Press Release.