--- title: "Hot, Warm and Cold Storage Explained: Tiers, Cost and Recov…" description: "An independent explainer on hot, warm, cold and offline storage tiers: access latency, retrieval charges, minimum durations, cloud archive behaviour on…" lang: en-GB json-ld: | [ { "@context": "https://schema.org", "@type": "Organization", "@id": "https://fire-vault.com/#organization", "name": "Firevault", "legalName": "Firevault Limited", "url": "https://fire-vault.com", "logo": { "@type": "ImageObject", "url": "https://fire-vault.com/logo.png", "width": 200, "height": 60 }, "foundingDate": "2025-03", "description": "Protect what matters with Offline Secure Storage and control what moves with Control by Firevault. Physically disconnected, always reachable by you.", "address": { "@type": "PostalAddress", "addressCountry": "GB", "addressLocality": "United Kingdom" }, "contactPoint": [ { "@type": "ContactPoint", "contactType": "customer service", "email": "hello@fire-vault.com", "availableLanguage": "English", "areaServed": [ "GB", "EU", "US", "AE" ] } ], "sameAs": [ "https://www.linkedin.com/company/firevault", "https://x.com/firevaultuk" ], "slogan": "Disconnect to Protect", "knowsAbout": [ "Offline Secure Storage", "Physical Air Gap Data Protection", "Ransomware Protection", "Data Sovereignty", "GDPR Compliance", "NIS2 Compliance" ] }, { "@context": "https://schema.org", "@type": "WebSite", "@id": "https://fire-vault.com/#website", "name": "Firevault", "alternateName": [ "Firevault", "Firevault UK", "Firevault Limited" ], "url": "https://fire-vault.com", "publisher": { "@id": "https://fire-vault.com/#organization" }, "inLanguage": "en-GB", "description": "Protect what matters with Offline Secure Storage and control what moves with Control by Firevault. Physically disconnected, always reachable by you.", "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://fire-vault.com/learn?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@context": "https://schema.org", "@type": "WebPage", "@id": "https://fire-vault.com/learn/hot-vs-cold-storage#webpage", "url": "https://fire-vault.com/learn/hot-vs-cold-storage", "name": "Hot, Warm and Cold Storage Explained: Tiers, Cost and Recov…", "description": "An independent explainer on hot, warm, cold and offline storage tiers: access latency, retrieval charges, minimum durations, cloud archive behaviour on…", "isPartOf": { "@id": "https://fire-vault.com/#website" }, "about": { "@id": "https://fire-vault.com/#organization" }, "primaryImageOfPage": { "@type": "ImageObject", "url": "https://fire-vault.com/images/og/og-base-learn.jpg" }, "inLanguage": "en-GB", "breadcrumb": { "@id": "https://fire-vault.com/learn/hot-vs-cold-storage#breadcrumb" } }, { "@context": "https://schema.org", "@type": "BreadcrumbList", "@id": "https://fire-vault.com/learn/hot-vs-cold-storage#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://fire-vault.com" }, { "@type": "ListItem", "position": 2, "name": "Home", "item": "https://fire-vault.com/" }, { "@type": "ListItem", "position": 3, "name": "Knowledge Vault", "item": "https://fire-vault.com/learn/knowledge" }, { "@type": "ListItem", "position": 4, "name": "Hot, Warm and Cold Storage Explained", "item": "https://fire-vault.com/learn/hot-vs-cold-storage" } ] }, { "@context": "https://schema.org", "@type": "Article", "headline": "Hot, Warm and Cold Storage Explained: Tiers, Cost and Recov…", "description": "An independent explainer on hot, warm, cold and offline storage tiers: access latency, retrieval charges, minimum durations, cloud archive behaviour on…", "image": "https://fire-vault.com/images/og/og-base-learn.jpg", "author": { "@type": "Organization", "name": "Firevault" }, "publisher": { "@type": "Organization", "name": "Firevault", "logo": { "@type": "ImageObject", "url": "https://fire-vault.com/logo.png" } }, "datePublished": "2025-11-18", "dateModified": "2026-08-27", "mainEntityOfPage": "https://fire-vault.com/learn/hot-vs-cold-storage" }, { "@context": "https://schema.org", "@type": "TechArticle", "@id": "https://fire-vault.com/learn/hot-vs-cold-storage#article", "headline": "Hot, Warm and Cold Storage Explained", "description": "An independent explainer on hot, warm, cold and offline storage tiers: access latency, retrieval charges, minimum durations, cloud archive behaviour on restore, and why storage tiering is not the same as backup.", "about": [ { "@type": "Thing", "name": "Hot storage" }, { "@type": "Thing", "name": "Cold storage" }, { "@type": "Thing", "name": "Cloud archive tiers" }, { "@type": "Thing", "name": "Storage tiering" }, { "@type": "Thing", "name": "Data backup" } ], "keywords": "hot storage vs cold storage, cold storage, warm storage, offline storage, storage tiers, cloud archive tier, data retrieval time, total cost of ownership storage, storage tiering strategy, backup vs storage", "articleSection": "Storage architecture", "inLanguage": "en-GB", "isAccessibleForFree": true, "wordCount": 2300, "image": [ "https://fire-vault.com/assets/explainer-hot-vs-cold-storage-D7AmNo4Y.jpg" ], "author": { "@type": "Person", "name": "Mark Fermor", "url": "https://fire-vault.com/about", "jobTitle": "Director and Co-Founder, Firevault" }, "publisher": { "@type": "Organization", "name": "Firevault", "url": "https://fire-vault.com" }, "datePublished": "2025-11-18", "dateModified": "2026-08-27", "url": "https://fire-vault.com/learn/hot-vs-cold-storage", "mainEntityOfPage": { "@type": "WebPage", "@id": "https://fire-vault.com/learn/hot-vs-cold-storage" }, "citation": [ { "@type": "CreativeWork", "name": "ISO/IEC 27040:2024, Information technology — Security techniques — Storage security", "url": "https://www.iso.org/standard/86795.html" }, { "@type": "CreativeWork", "name": "NIST SP 800-209, Security Guidelines for Storage Infrastructure", "url": "https://csrc.nist.gov/pubs/sp/800/209/final" }, { "@type": "CreativeWork", "name": "NIST SP 1800-11, Data Integrity: Recovering from Ransomware and Other Destructive Events", "url": "https://www.nccoe.nist.gov/projects/data-integrity-recovering-ransomware-and-other-destructive-events" }, { "@type": "CreativeWork", "name": "NIST Cybersecurity Framework 2.0", "url": "https://www.nist.gov/cyfr/framework" }, { "@type": "CreativeWork", "name": "NCSC UK, Offline backups in an online world", "url": "https://www.ncsc.gov.uk/blog-post/offline-backups-in-an-online-world" } ] }, { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What is the difference between hot, warm and cold storage?", "acceptedAnswer": { "@type": "Answer", "text": "Hot storage is optimised for frequent, low latency access and costs the most per terabyte. Warm storage serves data accessed occasionally, with a moderate price and slightly higher latency. Cold storage is optimised for data that is rarely read, offering the lowest price per terabyte in exchange for slower retrieval and, usually, minimum retention periods and retrieval charges." } }, { "@type": "Question", "name": "Is cold storage the same as offline storage?", "acceptedAnswer": { "@type": "Answer", "text": "No. Cold storage tiers such as archive classes in public cloud remain connected to the provider network and are managed through the same identity and API plane as hot storage. Offline storage means the media has no active network connection while it is disconnected, which is a physically different guarantee." } }, { "@type": "Question", "name": "How long does it take to retrieve data from cold storage?", "acceptedAnswer": { "@type": "Answer", "text": "It depends on the retrieval option chosen and the provider. Standard retrieval from archive tiers commonly takes several hours, expedited options can return data within minutes at a much higher price, and bulk retrieval of large volumes can take up to 48 hours. None of this is instantaneous the way hot storage is." } }, { "@type": "Question", "name": "Does cold storage charge for retrieval?", "acceptedAnswer": { "@type": "Answer", "text": "Yes, in almost every commercial cloud archive tier. Charges typically include a per gigabyte retrieval fee, a per gigabyte egress fee to move data out of the provider network, and early deletion charges if data is removed before the minimum storage duration has elapsed." } }, { "@type": "Question", "name": "Is storage tiering the same as having a backup?", "acceptedAnswer": { "@type": "Answer", "text": "No. Storage tiering describes where a single copy of data lives based on how often it is accessed. Backup describes having independent, additional copies of data that can be restored if the primary copy is lost, corrupted or encrypted. A dataset can be correctly tiered and still have no usable backup at all." } }, { "@type": "Question", "name": "Why is cold storage cheaper than hot storage?", "acceptedAnswer": { "@type": "Answer", "text": "Cold storage tiers use denser, lower performance media and provision far less concurrent throughput, because providers assume the data will be read rarely. That lower infrastructure cost is passed on as a lower monthly price per terabyte, with the trade-off recovered through retrieval fees and minimum retention commitments." } }, { "@type": "Question", "name": "What is total cost of ownership for storage tiers?", "acceptedAnswer": { "@type": "Answer", "text": "Total cost of ownership includes the monthly storage price, retrieval and egress fees, early deletion penalties, management overhead and the cost of an actual recovery event. A cold tier that looks cheapest on the storage line item can be the most expensive option once a real restore is priced in." } }, { "@type": "Question", "name": "How should I classify data across storage tiers?", "acceptedAnswer": { "@type": "Answer", "text": "Classify by measured access frequency and recovery time requirement, not by data age alone. Data read daily belongs in a hot tier. Data read occasionally for reporting or compliance belongs in warm or cold storage. Data that represents the last line of recovery, such as a gold backup copy, belongs offline regardless of how often it is theoretically accessed." } }, { "@type": "Question", "name": "Can cold cloud storage be affected by ransomware?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Cold storage tiers remain reachable over the network and are administered through the same accounts and APIs as hot storage. An attacker with sufficient privilege can delete objects, disable protective settings, or exhaust a retention lock given enough time, because the storage never physically disconnects." } }, { "@type": "Question", "name": "What does minimum storage duration mean in cloud archive tiers?", "acceptedAnswer": { "@type": "Answer", "text": "It is the minimum period a provider commits an object to remain in an archive tier before it can be deleted or moved without an early deletion charge. Common minimums range from 90 to 180 days depending on the tier, and deleting data earlier incurs a fee equivalent to the remaining committed period." } } ] } ] --- Recent Breaches Breaches [2026 PowerSchool 62.4M records ](/learn/breaches)[2026 DISA Global Solutions 3.3M records ](/learn/breaches)[2026 Globe Life 850K records ](/learn/breaches)[2026 Lidl GB Customer contact data ](/learn/breaches)[2026 Asahi Group Production systems disrupted ](/learn/breaches)[2026 Kido International 8K records ](/learn/breaches)[2026 Collins Aerospace (RTX) Check-in and boarding disruptio... ](/learn/breaches)[2026 Jaguar Land Rover Production and IT systems disru... ](/learn/breaches)[2026 Peter Green Chilled Order and logistics data ](/learn/breaches)[2026 Adidas UK Customer contact details ](/learn/breaches)[2026 PowerSchool 62.4M records ](/learn/breaches)[2026 DISA Global Solutions 3.3M records ](/learn/breaches)[2026 Globe Life 850K records ](/learn/breaches)[2026 Lidl GB Customer contact data ](/learn/breaches)[2026 Asahi Group Production systems disrupted ](/learn/breaches)[2026 Kido International 8K records ](/learn/breaches)[2026 Collins Aerospace (RTX) Check-in and boarding disruptio... ](/learn/breaches)[2026 Jaguar Land Rover Production and IT systems disru... ](/learn/breaches)[2026 Peter Green Chilled Order and logistics data ](/learn/breaches)[2026 Adidas UK Customer contact details ](/learn/breaches) [View All →](/learn/breaches) [![Firevault - offline secure storage, physically disconnected from the internet](/assets/logo-color-DBVl0KCg.png)](/) Products Solutions [Why OSS](/why-oss) More [Help](/help)[Get started](/get-started) [Knowledge Vault](/learn/knowledge) Explainer Storage architecture # Hot, Warm and Cold Storage Explained Storage tiers trade speed for cost. This explainer sets out how hot, warm, cold and offline tiers actually behave on retrieval, what they charge for, and why picking a tier is a different question from having a backup. ![Mark Fermor](/assets/mark-fermor-aWtKNSv7.jpg) Mark Fermor Director & Co-Founder, Firevault 18 November 2025 15 min read Share [](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Ffire-vault.com%2Flearn%2Fhot-vs-cold-storage)[](https://twitter.com/intent/tweet?url=https%3A%2F%2Ffire-vault.com%2Flearn%2Fhot-vs-cold-storage&text=Hot%2C%20Warm%20and%20Cold%20Storage%20Explained%0A%0AStorage%20tiers%20trade%20speed%20for%20cost.%20This%20explainer%20sets%20out%20how%20hot%2C%20warm%2C%20cold%20and%20offline%20tiers%20actually%20behave%20on%20retrieval%2C%20what%20they%20charge%20for%2C%20and%20why%20picking%20a%20tier%20is%20a%20different%20question%20from%20having%20a%20backup.)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ffire-vault.com%2Flearn%2Fhot-vs-cold-storage)[](mailto:?subject=Hot%2C%20Warm%20and%20Cold%20Storage%20Explained&body=Storage%20tiers%20trade%20speed%20for%20cost.%20This%20explainer%20sets%20out%20how%20hot%2C%20warm%2C%20cold%20and%20offline%20tiers%20actually%20behave%20on%20retrieval%2C%20what%20they%20charge%20for%2C%20and%20why%20picking%20a%20tier%20is%20a%20different%20question%20from%20having%20a%20backup.%0A%0Ahttps%3A%2F%2Ffire-vault.com%2Flearn%2Fhot-vs-cold-storage) ![Rows of enterprise storage arrays and archive media representing hot, warm and cold data tiers](/assets/explainer-hot-vs-cold-storage-D7AmNo4Y.jpg) Hot, warm and cold storage describe access frequency and latency, not resilience. A cold tier that is still online is still reachable over the network. Written by Mark Fermor, Co-Founder, Firevault Technical review Firevault architecture team First published 18 November 2025 Last reviewed 27 August 2026 Review cycle At least annually, or following material changes to NIST, NCSC or ISO guidance. How we built this explainer: This explainer draws on published cloud provider documentation for archive tier retrieval behaviour, ISO/IEC 27040 storage security concepts, and NIST guidance on data protection and recovery. It sets out neutral, vendor independent definitions before describing where Firevault's approach fits. **On this page**[What are hot, warm and cold storage?](#definition)[How storage tiers actually work](#how-it-works)[Retrieval latency, charges and minimum durations](#retrieval)[Why cold is not the same as disconnected](#cold-is-not-offline)[Storage tiering is not backup](#tiering-vs-backup)[How this maps to storage and recovery standards](#standards)[Total cost of ownership across tiers](#tco)[How to classify data across tiers](#classification)[A practical decision checklist](#decision)[Limits and common failure modes](#limits)[How Firevault applies these principles](#firevault)[The key takeaway](#takeaway)[Sources and further reading](#sources) On this page 1. [What are hot, warm and cold storage?](#definition) 2. [How storage tiers actually work](#how-it-works) 3. [Retrieval latency, charges and minimum durations](#retrieval) 4. [Why cold is not the same as disconnected](#cold-is-not-offline) 5. [Storage tiering is not backup](#tiering-vs-backup) 6. [How this maps to storage and recovery standards](#standards) 7. [Total cost of ownership across tiers](#tco) 8. [How to classify data across tiers](#classification) 9. [A practical decision checklist](#decision) 10. [Limits and common failure modes](#limits) 11. [How Firevault applies these principles](#firevault) 12. [The key takeaway](#takeaway) 13. [Sources and further reading](#sources) Every organisation with more than a few terabytes of data eventually asks the same question: which storage tier should this dataset live on. The answer is usually framed as hot versus cold, but there are really four tiers in common use, hot, warm, cold and offline, and each makes a different promise about latency, cost and reachability. Getting the tier right matters for the budget. It does not, by itself, answer whether the data can be recovered after an incident. That is a separate question, and conflating the two is one of the most common and most expensive mistakes in storage planning. ## What are hot, warm and cold storage? The terms describe how frequently data is expected to be read, and the storage architecture is optimised accordingly. There is no single universal standard defining the boundaries between tiers, but cloud providers and enterprise storage vendors use broadly consistent definitions. Hot storage Online, low latency media for data accessed constantly. Millisecond response, highest cost per terabyte. Warm storage Online media for data accessed occasionally, such as weekly reporting. Moderate cost, moderate latency. Cold storage Archive class cloud tiers for data rarely read. Lowest cost per terabyte, retrieval measured in minutes to hours. Offline storage Media with no active network connection while disconnected. Not priced by access frequency but by physical isolation. Hot, warm and cold all describe storage that remains connected to a network at all times, even when the data itself is untouched for months. Offline is a different axis entirely: it describes whether a network path to the storage exists at all, not how often the data is read. ## How storage tiers actually work Cloud providers implement tiers with different underlying media and provisioning. Hot tiers use fast solid-state or high-performance disk arrays with generous concurrent throughput reserved for the account. Cold and archive tiers use denser, lower-performance media, and providers deliberately under-provision retrieval capacity because they assume most archived objects will never be read again. HOT Production SSD or high-performance object storage Millisecond latency, always reachable, highest monthly cost per terabyte. WARM Standard cloud object storage or secondary NAS Access measured in tens of milliseconds to seconds, moderate cost. COLD Cloud archive tier (for example Glacier, Archive, Coldline classes) Minutes to hours to retrieve, low storage cost, retrieval and egress fees apply. OFFLINE Physically disconnected media No network path while disconnected. Retrieval requires a deliberate, scheduled reconnection. A typical four-tier storage stack, ordered from most to least frequently accessed. Moving an object between tiers, sometimes called lifecycle management, is usually automated through policies based on age or last-access time. This is efficient for cost control but says nothing about whether the object is protected against deletion, encryption or corruption while it sits in any tier. ## Retrieval latency, charges and minimum durations The economics of cold storage only make sense once the retrieval side of the equation is understood. A cheap monthly storage rate is subsidised by three mechanisms that only apply when data actually needs to come back. 1. Retrieval latency. Standard retrieval from an archive tier commonly takes several hours. Expedited options exist at a much higher per-gigabyte price and are not always guaranteed. Bulk retrieval of large volumes can take up to 48 hours. 2. Retrieval and egress charges. Providers typically charge per gigabyte to read an object out of an archive tier, plus a separate egress charge to move the data out of the provider's network. These charges do not appear on the resting storage bill. 3. Minimum storage duration. Archive tiers commonly commit data to a minimum period, often 90 to 180 days, before it can be deleted or moved tier without an early deletion charge equivalent to the remaining committed period. Tier Typical retrieval time Retrieval and egress fees Minimum duration Hot Milliseconds None beyond standard transfer None Warm Milliseconds to seconds Minimal Often none or short Cold (archive) Minutes to hours Per gigabyte retrieval plus egress Commonly 90 to 180 days Offline Time to physically reconnect None from the media itself Set by organisational policy, not the provider Indicative characteristics across tiers. Exact figures vary by provider and should be checked against current provider documentation before budgeting. Model the incident, not the invoice: A restore under time pressure, during an incident, is when retrieval charges and latency matter most. A cold tier that looks inexpensive at rest can cost more to recover from than a year of hot storage once expedited retrieval and egress on a large dataset are included. ## Why cold is not the same as disconnected Cold storage and offline storage are frequently used as if they were interchangeable. They are not. A cloud archive tier is cold in price and slow in retrieval, but the underlying media never stops being reachable over a network, and it is administered through exactly the same identity and API plane as the provider's hot storage. Cold cloud tier (always connected) Network Data - Reachable through the provider's API and console - Governed by identity, tokens and access keys - A compromised privileged account can reach it Offline storage (disconnected by default) Network Data - No network interface active while offline - Reconnection requires a deliberate, scheduled action - Not reachable through any credential compromise Cold cloud storage keeps a network path open at all times. Offline storage removes that path entirely between access windows. ### The practical consequence An attacker who compromises an administrator account, an expired multi-factor setup or an exposed access key can, in principle, reach a cold storage object just as they can reach a hot one, given enough time and patience. Object Lock, versioning and retention policy reduce that risk but remain logical controls enforced by configuration, not physical barriers. Only removing the network path itself removes that class of exposure. ## Storage tiering is not backup This distinction is worth stating plainly because it is so often blurred in vendor material. Storage tiering is a decision about where a single copy of data lives, based on how often it needs to be read. Backup is a decision about how many independent copies of data exist, and whether they can be restored if the primary copy is lost. - A dataset can be perfectly tiered for cost and still have zero independent backup copies. - Moving a dataset to a cold tier does not create a second copy; it is usually still the only copy. - A backup that lives on the same cloud account as production, even in cold storage, shares the same failure and attack domain. - Tiering optimises cost. Backup, done correctly, protects against loss regardless of cost. A resilient architecture treats tiering and backup as two separate exercises that happen to interact: pick the tier for the production copy based on access needs, then separately ensure genuinely independent backup copies exist and are tested, regardless of which tier they happen to sit in. ## How this maps to storage and recovery standards [ISO/IEC 27040](https://www.iso.org/standard/86795.html) sets out storage security concepts that apply across tiers, including data protection in transit, at rest and during media disposal, and it treats tiering and data protection as related but distinct concerns. [NIST SP 800-209](https://csrc.nist.gov/pubs/sp/800/209/final) gives similar guidance for storage infrastructure security, covering access control and protection requirements that apply regardless of which performance tier data sits in. On the recovery side, [NIST SP 1800-11](https://www.nccoe.nist.gov/projects/data-integrity-recovering-ransomware-and-other-destructive-events) and the recovery function of the [NIST Cybersecurity Framework 2.0](https://www.nist.gov/cyfr/framework) are explicit that recoverability depends on tested, independent backup capability, not on the storage tier a dataset happens to occupy. The [NCSC's guidance on offline backups](https://www.ncsc.gov.uk/blog-post/offline-backups-in-an-online-world) makes the same point from a UK operational perspective: an online copy, however cheap or slow to access, is not equivalent to a genuinely offline one. ## Total cost of ownership across tiers Comparing tiers on the monthly price per terabyte alone systematically understates the cost of cold storage and systematically overstates the cost of alternatives. A proper total cost of ownership comparison includes several components. 1. Resting storage cost. The advertised monthly rate per terabyte, which is genuinely lower for colder tiers. 2. Retrieval and egress cost. Charged only when data is read back, and easy to omit from budget comparisons that focus on storage alone. 3. Early deletion and minimum duration cost. Penalties for moving data before the committed retention period has elapsed. 4. Management overhead. Time spent configuring lifecycle policies, monitoring retention locks and reconciling which copies exist where. 5. Incident recovery cost. The cost of an actual, unplanned, time pressured restore, including expedited retrieval fees and the business cost of extended downtime. Modelling that last line item honestly is usually what changes the decision. A rarely accessed archive can remain in a cold tier indefinitely. A dataset that represents the organisation's only recovery path from a catastrophic event should not be selected for the cheapest possible tier purely on the resting storage price. ## How to classify data across tiers Classification should be driven by two measurable factors: actual access frequency and the acceptable recovery time if the data were lost or encrypted, not by data age or file type alone. Access daily or hourly Hot tier - Live production databases - Active file shares - Current-year transactional data Access occasionally Warm or cold tier - Quarterly reporting datasets - Prior-year archives - Reference data accessed for audits Last line of recovery Offline tier - Gold backup copies - Regulatory retention masters - Data the business cannot afford to lose A practical classification approach based on access pattern and recovery importance. A dataset can sit in more than one tier at once, for good reason. Production data lives hot for daily use; a backup copy of the same data can sit cold for cost efficiency; and a further copy of the same data, kept offline, satisfies the resilience requirement that neither the hot nor the cold copy can provide alone. ## A practical decision checklist - How many times per month is this data actually read, not how often policy assumes it should be? - What is the acceptable time to retrieve this data if it were needed urgently? - What would a full restore of this dataset cost in retrieval and egress fees today? - Is this the only copy of the data, or one of several independent copies? - If this is a backup copy, does it share an identity plane or account with the data it protects? - Has a restore from this tier actually been tested, or only assumed to work? ## Limits and common failure modes Tiering strategies fail in predictable ways. The most common is treating archive tier storage as a backup strategy on its own, without an independent, offline copy, which leaves the organisation exposed to any compromise of the account or platform holding that tier. Object Lock and retention policies are frequently assumed to be equivalent to a physical air gap; they are not, because they can be altered by anyone with sufficient privilege in that account. A second common failure is underestimating retrieval time during an actual incident. Recovery plans built around a theoretical retrieval time, rather than a tested one, routinely discover that expedited retrieval options are limited in volume, contended during widespread incidents, or simply more expensive than budgeted. A third failure is neglecting minimum storage duration when planning data lifecycle changes, which produces unexpected early deletion charges at the least convenient time. ## How Firevault applies these principles Firevault does not compete with hot or cold cloud storage tiers, and does not claim to replace them. Production data should stay hot for operational performance, and infrequently accessed data can legitimately sit in cold cloud storage for cost efficiency. Firevault Offline Secure Storage® is designed to be the fourth tier described in this explainer: the offline copy that neither hot nor cold cloud storage can provide, because both remain reachable over a network. The storage media is disconnected between scheduled, identity-verified access windows managed through Firevault Control, an out-of-band management plane, so there is no listening service and no credential path for an attacker to exploit while the copy is offline. Retrieval, when genuinely required, happens over your own network on a fixed subscription rather than a per-gigabyte cloud egress model, so the cost of an actual recovery is known in advance rather than discovered during an incident. This sits alongside, not instead of, whatever hot and cold tiering strategy the organisation already uses. Key takeaway ## Tiering answers speed and cost. It does not answer resilience. Hot, warm and cold storage are a spectrum of access frequency and price. Choosing the right tier for a dataset lowers cost without harming the working day. But no combination of hot and cold cloud tiers, on its own, provides a resilient recovery position, because both remain reachable over the network and administered by the same identity plane. A sound architecture picks tiers for cost and performance, then separately ensures at least one copy of the data that matters is genuinely offline and independently verified as restorable. Questions ## Frequently Asked Questions Straight answers on how Offline Secure Storage® behaves in practice. ### What is the difference between hot, warm and cold storage? ### Is cold storage the same as offline storage? ### How long does it take to retrieve data from cold storage? ### Does cold storage charge for retrieval? ### Is storage tiering the same as having a backup? ### Why is cold storage cheaper than hot storage? ### What is total cost of ownership for storage tiers? ### How should I classify data across storage tiers? ### Can cold cloud storage be affected by ransomware? ### What does minimum storage duration mean in cloud archive tiers? ## Sources and further reading - [ISO/IEC 27040:2024, Information technology — Security techniques — Storage security](https://www.iso.org/standard/86795.html) International standard covering storage security concepts, including data protection, retention and media handling across storage tiers. - [NIST SP 800-209, Security Guidelines for Storage Infrastructure](https://csrc.nist.gov/pubs/sp/800/209/final) Guidance on storage architecture security, including access control and data protection across online and offline media. - [NIST SP 1800-11, Data Integrity: Recovering from Ransomware and Other Destructive Events](https://www.nccoe.nist.gov/projects/data-integrity-recovering-ransomware-and-other-destructive-events) Practical guidance distinguishing storage architecture decisions from backup and recovery capability. - [NIST Cybersecurity Framework 2.0](https://www.nist.gov/cyfr/framework) Recovery function guidance on maintaining and testing backup capability independent of storage medium selection. - [NCSC UK, Offline backups in an online world](https://www.ncsc.gov.uk/blog-post/offline-backups-in-an-online-world) UK guidance on the distinction between online storage tiers, including cloud archive, and genuinely offline backup copies. Related Firevault guides [Air gap vs immutable backup](/learn/air-gap-vs-immutable-backup) [The 3-2-1-1-0 backup rule](/learn/3-2-1-1-0-backup-rule) [Physical air gap storage for ransomware protection](/learn/physical-air-gap-ransomware-protection) [What is Offline Secure Storage](/offline-secure-storage) About the author ![Mark Fermor](/assets/mark-fermor-aWtKNSv7.jpg) ### Mark Fermor [](https://www.linkedin.com/in/mfermor) Director & Co-Founder Co-founder of Firevault, focused on offline secure storage and protecting individuals and businesses from fraud, fines, loss and damage. Speaker, owner and advisor. Share this explainer Share [](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Ffire-vault.com%2Flearn%2Fhot-vs-cold-storage)[](https://twitter.com/intent/tweet?url=https%3A%2F%2Ffire-vault.com%2Flearn%2Fhot-vs-cold-storage&text=Hot%2C%20Warm%20and%20Cold%20Storage%20Explained%0A%0AStorage%20tiers%20trade%20speed%20for%20cost.%20This%20explainer%20sets%20out%20how%20hot%2C%20warm%2C%20cold%20and%20offline%20tiers%20actually%20behave%20on%20retrieval%2C%20what%20they%20charge%20for%2C%20and%20why%20picking%20a%20tier%20is%20a%20different%20question%20from%20having%20a%20backup.)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ffire-vault.com%2Flearn%2Fhot-vs-cold-storage)[](mailto:?subject=Hot%2C%20Warm%20and%20Cold%20Storage%20Explained&body=Storage%20tiers%20trade%20speed%20for%20cost.%20This%20explainer%20sets%20out%20how%20hot%2C%20warm%2C%20cold%20and%20offline%20tiers%20actually%20behave%20on%20retrieval%2C%20what%20they%20charge%20for%2C%20and%20why%20picking%20a%20tier%20is%20a%20different%20question%20from%20having%20a%20backup.%0A%0Ahttps%3A%2F%2Ffire-vault.com%2Flearn%2Fhot-vs-cold-storage) The Firevault view**Offline Secure Storage® keeps a clean copy beyond the reach of an attacker.**[Why #OSS →](/why-oss) Control systems and access**Cut the physical paths attackers and third parties depend on.**[Explore Control →](/solutions/control) Get started**Get started, or talk to a member of the team.**[Get started →](/get-started)