<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by NAKIVO on Medium]]></title>
        <description><![CDATA[Stories by NAKIVO on Medium]]></description>
        <link>https://medium.com/@nakivo?source=rss-ed7c6986c0f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Rzy5d7fPp8_nHq-WqhZ2WQ.png</url>
            <title>Stories by NAKIVO on Medium</title>
            <link>https://medium.com/@nakivo?source=rss-ed7c6986c0f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 02:17:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nakivo/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Final Call: The MSP Recovery Readiness Webinar]]></title>
            <link>https://nakivo.medium.com/final-call-the-msp-recovery-readiness-webinar-22c014e95afd?source=rss-ed7c6986c0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/22c014e95afd</guid>
            <category><![CDATA[managed-it-services]]></category>
            <category><![CDATA[managed-services]]></category>
            <category><![CDATA[webinar]]></category>
            <category><![CDATA[cyber-security-solutions]]></category>
            <category><![CDATA[msp]]></category>
            <dc:creator><![CDATA[NAKIVO]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 10:00:53 GMT</pubDate>
            <atom:updated>2026-10-14T10:00:53.647Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iuzgIep17NcPP3cehMtXDg.png" /></figure><p>Different customers. Different incidents. Different recovery deadlines.</p><p>As an MSP, how do you prepare for them all?</p><p><a href="https://www.nakivo.com/webinar/from-backup-to-recovery-readiness-practical-guide-for-msps/?utm_source=Medium&amp;utm_campaign=MSP_webinar">Register for our upcoming webinar</a> on October 15 to explore how to address those challenges and assess your recovery readiness.</p><p><strong>What it covers:</strong></p><ul><li>Why recovery readiness has become more complex for MSPs (more distributed infrastructure, higher recovery expectations, etc.)</li><li>The 7 checks that separate a backup service from a recovery-ready service</li><li>Real recovery scenarios: a ransomware hit, a site outage and everyday restores</li><li>MSP customer stories and a live NAKIVO Backup &amp; Replication demo</li><li>Open Q&amp;A with our experts</li></ul><p><strong>Only a few days left to register</strong>; don’t miss it.</p><p><strong>When to attend</strong></p><p><strong>📅 </strong>Thursday, October 15, 2026</p><ul><li><strong>EMEA: </strong>11 AM — 12 PM CEST</li><li><strong>AMERICAS: </strong>11 AM — 12 PM EDT</li></ul><p><a href="https://www.nakivo.com/webinar/from-backup-to-recovery-readiness-practical-guide-for-msps/?utm_source=Medium&amp;utm_campaign=MSP_webinar"><strong>REGISTER NOW</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22c014e95afd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Live Webinar: From Backup to Recovery Readiness: A Practical Guide for MSPs]]></title>
            <link>https://cybersecuritywriteups.com/live-webinar-from-backup-to-recovery-readiness-a-practical-guide-for-msps-2da2da232efc?source=rss-ed7c6986c0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2da2da232efc</guid>
            <category><![CDATA[webinar]]></category>
            <category><![CDATA[msp]]></category>
            <category><![CDATA[managed-service-provider]]></category>
            <category><![CDATA[managed-it-services]]></category>
            <category><![CDATA[disaster-recovery]]></category>
            <dc:creator><![CDATA[NAKIVO]]></dc:creator>
            <pubDate>Tue, 06 Oct 2026 13:05:53 GMT</pubDate>
            <atom:updated>2026-10-06T13:44:58.533Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fWpAPRRAVMCGX723_zWh2Q.png" /></figure><p>MSPs are defined not by successful backups, but by how fast they can restore operations during an outage or ransomware attack.</p><p><a href="https://www.nakivo.com/webinar/from-backup-to-recovery-readiness-practical-guide-for-msps/?utm_source=Medium&amp;utm_campaign=MSP_webinar"><strong>Register for NAKIVO’s live webinar</strong></a><strong> </strong>to work through a practical 7-point checklist for recovering every customer, not just backing them up. Explore the capabilities MSPs need to deliver reliable recovery across workloads, customers and incidents while keeping operations manageable at scale.</p><p><strong>What we’ll cover:</strong></p><ul><li>Recovery across mixed environments without building a separate process for every platform</li><li>Choosing the right recovery method for everyday incidents, ransomware and site outages</li><li>How to align recovery workflows with customer RTOs and RPOs</li><li>Managing recovery readiness across customers and building differentiated service tiers</li><li>Plus, practical recovery scenarios, a live demo and expert Q&amp;A.</li></ul><p><strong>When to attend</strong></p><p><strong>📅 </strong>Thursday, October 15, 2026</p><ul><li><strong>EMEA: </strong>11 AM — 12 PM CEST</li><li><strong>AMERICAS: </strong>11 AM — 12 PM EDT</li></ul><p><a href="https://www.nakivo.com/webinar/from-backup-to-recovery-readiness-practical-guide-for-msps/?utm_source=Medium&amp;utm_campaign=MSP_webinar"><strong>REGISTER NOW</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2da2da232efc" width="1" height="1" alt=""><hr><p><a href="https://cybersecuritywriteups.com/live-webinar-from-backup-to-recovery-readiness-a-practical-guide-for-msps-2da2da232efc">Live Webinar: From Backup to Recovery Readiness: A Practical Guide for MSPs</a> was originally published in <a href="https://cybersecuritywriteups.com/">Cyber Security Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Proxmox Storage Options: A Practical Guide for Different Workloads]]></title>
            <link>https://medium.com/beyond-localhost/proxmox-storage-options-a-practical-guide-for-different-workloads-d20c041fabd7?source=rss-ed7c6986c0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d20c041fabd7</guid>
            <category><![CDATA[storage-solutions]]></category>
            <category><![CDATA[data-storage]]></category>
            <category><![CDATA[virtualization]]></category>
            <category><![CDATA[virtual-machine]]></category>
            <category><![CDATA[proxmox]]></category>
            <dc:creator><![CDATA[NAKIVO]]></dc:creator>
            <pubDate>Mon, 21 Sep 2026 13:42:09 GMT</pubDate>
            <atom:updated>2026-09-21T13:42:09.369Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E97I7TLeebl_wlXCFe3BNg.jpeg" /></figure><p>Choosing the right storage in Proxmox VE directly affects VM performance, reliability, scalability and manageability. Proxmox supports options ranging from simple local directories to distributed cluster storage, each with different tradeoffs in speed, redundancy, features and complexity.</p><p><strong>Why Storage Choice Matters</strong></p><p>Different virtual machines have different requirements. A production database with heavy I/O and low-latency demands needs a different storage architecture from a test VM, template repository or lab environment.</p><p>Choosing an unsuitable storage type can limit performance, reduce available data integrity or redundancy features or introduce unnecessary management complexity.</p><p>Key factors to consider include performance, reliability, cost, ease of management, snapshot capabilities, provisioning type (<a href="https://www.nakivo.com/blog/thick-and-thin-provisioning-difference/?utm_source=Medium">thin or thick</a>) and whether storage is local or network-based.</p><p><strong>Local Storage Options</strong></p><p><strong>Directory storage</strong> is one of the simplest Proxmox options and can run on almost any supported filesystem. It works well for straightforward deployments and can also inherit redundancy from underlying technologies such as RAID or other storage layers.</p><p><strong>LVM</strong> provides flexible block-storage management, while <strong>LVM-Thin</strong> adds thin provisioning, snapshots and clones for more efficient VM deployment.</p><p><strong>ZFS</strong> combines Copy-on-Write, snapshots, cloning, checksumming, self-healing, compression and integrated redundancy through mirrors and RAID-Z configurations. These capabilities make it well-suited to workloads that benefit from strong data-integrity features, although ZFS generally requires more memory and processing resources than lighter storage options.</p><p><strong>Network and Cluster Storage Options</strong></p><p>In shared environments,<a href="https://www.nakivo.com/blog/nfs-vs-smb/?utm_source=Medium"> SMB and NFS</a> provide file-level network storage that is relatively straightforward to configure.</p><p><strong>iSCSI</strong> provides block-level access to external storage and is commonly associated with NAS or SAN infrastructure.</p><p><strong>Ceph RBD</strong> provides distributed block storage designed for scalable Proxmox clusters. It supports shared storage, thin provisioning, snapshots, cloning and replicated data across cluster nodes.</p><p><strong>CephFS</strong> provides shared file-level storage on top of a Ceph cluster.</p><p><strong>ZFS over iSCSI</strong> combines networked block storage with ZFS functionality, but its HA characteristics depend on the underlying design. In the standard configuration described in the NAKIVO guide, the ZFS pool is active on a single Proxmox node and does not provide the same shared-storage model as Ceph RBD.</p><p><strong>Matching Storage to the Environment</strong></p><p>There is no fixed storage choice based solely on cluster size.</p><p>Smaller environments may favor simpler options such as ZFS, LVM-Thin or NFS, depending on performance, redundancy and management requirements.</p><p>For larger clusters where shared storage, high availability and fast live migration are priorities, options such as Ceph RBD, NFS or SAN-based iSCSI storage may be more appropriate. Proxmox supports multiple shared-storage backends, so the best choice depends on workload requirements and existing infrastructure rather than a specific node-count threshold.</p><p>Labs and test environments can often use lower-complexity storage such as Directory or LVM-Thin, particularly when advanced redundancy is not required.</p><p><strong>Final Thoughts</strong></p><p>There is no single best Proxmox storage type. The right option depends on the workload, infrastructure size, performance requirements, availability goals and level of management complexity the organization is prepared to support.</p><p>One of Proxmox VE’s strengths is its flexible storage model: Multiple local and shared storage types can coexist in the same environment, allowing administrators to match storage to different workload requirements.</p><p>For a full comparison table, detailed use cases and practical recommendations for clusters, labs and production environments, read the <a href="https://www.nakivo.com/blog/proxmox-storage-options/?utm_source=Medium">complete guide to Proxmox storage options</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d20c041fabd7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/beyond-localhost/proxmox-storage-options-a-practical-guide-for-different-workloads-d20c041fabd7">Proxmox Storage Options: A Practical Guide for Different Workloads</a> was originally published in <a href="https://medium.com/beyond-localhost">Beyond Localhost</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NEW: NAKIVO Backup & Replication v11.2.2 Is Available For Download]]></title>
            <link>https://nakivo.medium.com/new-nakivo-backup-replication-v11-2-2-is-available-for-download-8fb3e4520ffd?source=rss-ed7c6986c0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fb3e4520ffd</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[virtualization]]></category>
            <category><![CDATA[backup]]></category>
            <category><![CDATA[data-protection]]></category>
            <category><![CDATA[cyber-security-solutions]]></category>
            <dc:creator><![CDATA[NAKIVO]]></dc:creator>
            <pubDate>Fri, 11 Sep 2026 09:39:54 GMT</pubDate>
            <atom:updated>2026-09-11T09:39:54.419Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KBtAGMeXMRuvH85Up4dW0g.jpeg" /></figure><p>NAKIVO v11.2.2 is out and available to download. This update is centered on wider hypervisor coverage, smoother day-to-day use and expanded platform compatibility.</p><h3><strong>Key Updates in v11.2.2</strong></h3><p><strong>Proxmox VE 9.1 and 9.2 Support:</strong> Full support for backup, replication and recovery operations on the latest Proxmox VE releases.</p><p><strong>VMware Cloud Foundation 9.1 Compatibility:</strong> Compatible support for the vSphere components in VCF 9.1. All existing features for VMware remain fully supported, including backup, recovery, replication, Site Recovery, Real-Time Replication and IT Monitoring.</p><p><strong>Real-Time Replication for vSphere 9.1:</strong> Protect vSphere 9.1 workloads with continuous replication, replicas updated as source VMs change and failover with RPOs as low as 1 second.</p><p><strong>NAS Backup Licensing:</strong> New capacity-based TB subscription SKUs for file share backup, with UI updates displaying purchased and consumed NAS backup capacity.</p><p><strong>Buffalo NAS Deployment</strong>: Deploy NAKIVO Backup &amp; Replication directly on Buffalo NAS devices running Windows OS.</p><p><strong>Expanded Platform Compatibility:</strong> The release includes compatibility updates for:</p><ul><li>VMware Cloud Director</li><li>vCenter Server and ESXi</li><li>Nutanix AHV</li><li>Linux/Windows operating systems</li><li>Oracle RMAN deployments</li><li>Dell EMC appliances</li><li>QNAP</li></ul><p><strong>General Improvements:</strong> Multiple fixes plus stability, usability, performance and compatibility enhancements across the platform.</p><p>For the full list of improvements and fixes, check out the <a href="https://helpcenter.nakivo.com/Release-Notes/Content/v11-Release-Notes/v11.2.2-Release-Notes.htm">release notes</a>.</p><h3>Get Started with v11.2.2</h3><p>If you’re already running NAKIVO Backup &amp; Replication, upgrade your instance and try the latest improvements today!</p><p><a href="https://www.nakivo.com/resources/download/update/"><strong>UPDATE TO v11.2.2</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fb3e4520ffd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Proxmox Backup to NAS: A Simple How-To Guide]]></title>
            <link>https://medium.com/devops-ai-decoded/proxmox-backup-to-nas-a-simple-how-to-guide-fc6dda074e8a?source=rss-ed7c6986c0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc6dda074e8a</guid>
            <category><![CDATA[data-storage]]></category>
            <category><![CDATA[proxmox]]></category>
            <category><![CDATA[network-attached-storage]]></category>
            <category><![CDATA[data-protection]]></category>
            <category><![CDATA[backup]]></category>
            <dc:creator><![CDATA[NAKIVO]]></dc:creator>
            <pubDate>Fri, 04 Sep 2026 10:22:51 GMT</pubDate>
            <atom:updated>2026-09-04T10:22:51.172Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lSB115wN1fGUJJk4s_pzqQ.jpeg" /></figure><p>Backing up Proxmox virtual machines is critical for protecting workloads and supporting recovery after data loss, infrastructure failure, or other disruptions. A Network Attached Storage (NAS) can provide a centralized and expandable option for storing Proxmox backups without recurring per-GB cloud storage charges.</p><h3>Why Back Up Proxmox to NAS?</h3><p>NAS provides a separate storage system for backup data, helping reduce the storage burden on Proxmox hosts. Many NAS devices also support RAID for storage redundancy, while expandable capacity can accommodate growing backup requirements.</p><p>For small and medium-sized businesses, NAS can also provide a cost-effective alternative to continually expanding cloud storage, depending on capacity, infrastructure, and retention requirements.</p><h3>What You Need</h3><p>To back up Proxmox to NAS, you need:</p><ul><li>A NAS with sufficient storage capacity</li><li>A configured file share</li><li>Enough free space for backup retention</li><li>Appropriate read/write permissions</li><li>NFS or SMB/CIFS connectivity</li></ul><p>There are two main approaches covered in this guide: Using native Proxmox VE backup capabilities or a dedicated backup solution.</p><h3>Native Proxmox Backup to NAS</h3><p>Proxmox VE can use NFS or SMB/CIFS storage on a NAS as a backup destination. Its integrated vzdump backup tool can create VM backups and store them on supported network storage.</p><p>The basic workflow is to connect the NAS share to Proxmox, select it as the backup destination, and configure options such as backup mode, compression, scheduling, and retention.</p><p>Administrators can then run scheduled backup jobs for selected VMs and restore them from available backups when needed.</p><h3>Proxmox Backup with NAKIVO</h3><p>A dedicated backup solution provides another option for protecting Proxmox VMs.</p><p>NAKIVO Backup &amp; Replication supports agentless Proxmox VM backup to NFS and SMB shares on NAS. It also provides <a href="https://www.nakivo.com/blog/what-is-incremental-backup/?utm_source=Medium">incremental backups</a>, native and proprietary change tracking, <a href="https://www.nakivo.com/blog/backup-encryption-options/?utm_source=Medium">encryption</a>, and flexible retention policies.</p><p>The setup involves adding the Proxmox host or cluster to the NAKIVO inventory, creating a<a href="https://www.nakivo.com/blog/nakivo-backup-and-replication-component-backup-repository/?utm_source=Medium"> backup repository</a> on the NAS share, and configuring a Proxmox backup job with the required schedule and retention settings.</p><p>NAKIVO can also be installed directly on supported NAS devices, combining backup software components and storage on the NAS to create an integrated backup appliance.</p><h3>Final Thoughts</h3><p>Backing up Proxmox to NAS can provide centralized backup storage on a separate system instead of consuming capacity on the Proxmox hosts.</p><p>Organizations can use native Proxmox VE backup capabilities or a dedicated solution such as NAKIVO Backup &amp; Replication, depending on their recovery, retention, security, and management requirements.</p><p>Read the complete guide on<a href="https://www.nakivo.com/blog/how-to-backup-proxmox-to-nas/?utm_source=chatgpt.com"> backing up Proxmox to NAS</a> for step-by-step instructions and screenshots covering both approaches.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc6dda074e8a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devops-ai-decoded/proxmox-backup-to-nas-a-simple-how-to-guide-fc6dda074e8a">Proxmox Backup to NAS: A Simple How-To Guide</a> was originally published in <a href="https://medium.com/devops-ai-decoded">Devops &amp; AI Hub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MSP Cybersecurity: A Checklist for Protecting Against Ransomware and Emerging Threats]]></title>
            <link>https://meetcyber.net/msp-cybersecurity-a-checklist-for-protecting-against-ransomware-and-emerging-threats-a8b4a932fff4?source=rss-ed7c6986c0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8b4a932fff4</guid>
            <category><![CDATA[ransomware]]></category>
            <category><![CDATA[managed-service-provider]]></category>
            <category><![CDATA[managed-it-services]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ransomware-protection]]></category>
            <dc:creator><![CDATA[NAKIVO]]></dc:creator>
            <pubDate>Mon, 31 Aug 2026 16:36:10 GMT</pubDate>
            <atom:updated>2026-08-31T16:36:10.528Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*REbH4BBO_Osn6VhcOLc49w.jpeg" /></figure><p>Managed Service Providers manage infrastructure, applications, and data across multiple customer environments, making them high-value targets for cyberattacks. A compromise at the provider level can potentially expose multiple clients at once, particularly when attackers gain access to privileged credentials or centralized management tools.</p><h3><strong>Why Cybersecurity Is Critical for MSPs</strong></h3><p>MSPs often hold privileged access that allows them to administer client infrastructure remotely. If those accounts or management systems are compromised, attackers may be able to move beyond the MSP’s own environment and reach customer systems.</p><p>That concentration of access makes strong security controls essential, not only for protecting the provider, but also for limiting downstream risk to clients.</p><h3><strong>Common Threats: Ransomware, Phishing, and Compromised RMM Tools</strong></h3><p>Ransomware remains a serious threat to MSPs. Double-extortion attacks can combine data theft with encryption, adding the threat of publicly leaking stolen information to the operational disruption caused by ransomware. <a href="https://www.nakivo.com/blog/ransomware-as-a-service-raas-guide/?utm_source=Medium&amp;utm_medium=social&amp;utm_campaign=blog_post_MSP_cybersecurity_checklist">Ransomware-as-a-Service</a> has also lowered the barrier to entry, enabling more attackers to launch ransomware campaigns without developing the malware themselves.</p><p>Credential theft is another major concern. Phishing, social engineering, infostealers, and other credential-abuse techniques can expose privileged accounts used to manage client environments.</p><p>RMM platforms require particular attention because they provide centralized administrative capabilities across endpoints and customer networks. Cybercriminals have repeatedly abused legitimate remote-management software and exploited vulnerable RMM platforms during attacks.</p><h3><strong>The Core Checklist</strong></h3><p>A resilient MSP security strategy should combine several layers of defense:</p><ul><li>Restrict network access using least privilege, segmentation, and zero-trust principles.</li><li>Harden and monitor infrastructure by patching vulnerabilities, enabling MFA, and eliminating unnecessary accounts and services.</li><li>Secure RMM and PSA platforms with strong access controls, monitoring, and timely security updates.</li><li>Strengthen endpoint and user security through behavioral threat detection and regular security-awareness training.</li><li>Protect critical data with tested backup and disaster recovery procedures.</li><li>Maintain strong identity and access management to reduce the risk posed by compromised credentials.</li><li>Build and regularly test an incident-response plan so teams have clear procedures during an active attack.</li></ul><h3><strong>Speed Matters</strong></h3><p>Detecting suspicious activity quickly can limit the time attackers have to move laterally, steal data, or disrupt client systems.</p><p>Continuous monitoring and automated response can help security teams shorten the path from detection to containment. Depending on the security platform and configuration, automated playbooks can isolate compromised hosts, disable affected accounts, block malicious connections, and escalate incidents for investigation.</p><p>The objective is not simply to generate alerts faster, but to reduce the time attackers remain active in the environment.</p><h3><strong>Identity Remains Critical</strong></h3><p>Compromised credentials remain an important attack vector, particularly for MSPs, because privileged accounts can provide access to sensitive management systems.</p><p>The 2026 Verizon DBIR found that vulnerability exploitation has overtaken stolen credentials as the leading known initial-access vector overall, reinforcing the need for MSPs to address both identity security and vulnerability management rather than relying on either one alone.</p><p>Strong MFA, granular privileges, contextual access controls, just-in-time administrative access, and careful identity lifecycle management can all reduce exposure.</p><h3><strong>What’s Next for MSP Security</strong></h3><p>Beyond foundational controls, MSPs can consider additional measures such as zero-trust architecture, behavioral threat detection, cyber-insurance planning, and tighter vendor-risk management across their software supply chain.</p><p>Compliance requirements also need to be evaluated client by client. Depending on the industry, geography, and services provided, an MSP may need to account for requirements or frameworks such as GDPR, HIPAA, PCI DSS, SOC 2, or ISO 27001.</p><p>Software suppliers deserve particular scrutiny because MSP environments rely heavily on third-party RMM, PSA, backup, security, and cloud platforms. A weakness in one component can create an attack path into the broader service environment.</p><h3><strong>Final Thoughts</strong></h3><p>MSP cybersecurity requires in-depth defense. No single control can address ransomware, credential compromise, vulnerable software, supply-chain attacks, and malicious use of remote-management tools.</p><p>Combining access controls, infrastructure hardening, continuous monitoring, secure management tools, incident-response planning, and tested backup and disaster recovery can help MSPs reduce risk and improve their ability to recover when incidents occur.</p><p>Read the full<a href="https://www.nakivo.com/blog/msp-cybersecurity-checklist/?utm_source=Medium&amp;utm_medium=social&amp;utm_campaign=blog_post_MSP_cybersecurity_checklist"> MSP Cybersecurity Checklist</a> for a detailed breakdown of threats and practical measures for strengthening security across MSP and client environments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8b4a932fff4" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/msp-cybersecurity-a-checklist-for-protecting-against-ransomware-and-emerging-threats-a8b4a932fff4">MSP Cybersecurity: A Checklist for Protecting Against Ransomware and Emerging Threats</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Practical Guide to Backing Up SharePoint Online to Amazon S3]]></title>
            <link>https://medium.com/codex/a-practical-guide-to-backing-up-sharepoint-online-to-amazon-s3-9acc81b3f769?source=rss-ed7c6986c0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9acc81b3f769</guid>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[data-protection]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[sharepoint]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[NAKIVO]]></dc:creator>
            <pubDate>Wed, 26 Aug 2026 11:12:54 GMT</pubDate>
            <atom:updated>2026-08-27T12:09:56.403Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v0OyuXvcs9hUN_xhL14qJg.jpeg" /></figure><p>Microsoft 365 provides native resiliency and recovery capabilities for SharePoint Online, but some organizations also want a backup copy stored outside the Microsoft 365 environment. An independent copy in Amazon S3 can add another layer of separation and provide greater control over backup storage, retention, and immutability.</p><h4>Why Amazon S3 for SharePoint Backup</h4><p><a href="https://www.nakivo.com/blog/backup-sharepoint-online-to-amazon-s3/?utm_source=medium">SharePoint backup to Amazon S3</a> gives organizations an additional recovery copy stored outside their production Microsoft 365 environment.</p><p>A separately secured S3 backup can preserve independent recovery points for restoration in case ransomware-encrypted files are synchronized to SharePoint Online or data is accidentally or maliciously changed.</p><p>Starting with NAKIVO Backup &amp; Replication v11.0, Microsoft 365 data — including SharePoint Online, Exchange Online, OneDrive for Business, and Microsoft Teams — can be backed up directly to Amazon S3, as well as other supported cloud and S3-compatible storage platforms.</p><h4>What the Setup Actually Involves</h4><p>The configuration involves several coordinated components:</p><ul><li>An AWS account added to the NAKIVO inventory with the permissions required to access and write to the target S3 bucket</li><li>A Microsoft 365 account connected through Microsoft Entra ID, using automatic application registration or an existing registered application</li><li>A Transporter assigned to process backup data, either in AWS or elsewhere in the NAKIVO infrastructure</li><li>An Amazon S3 backup repository, with S3 Object Lock enabled if immutable recovery points are required</li></ul><p>NAKIVO supports both automatic application registration and existing registered applications for Microsoft 365 connectivity. An AWS-based Transporter can be used, but a locally deployed Transporter can also transfer backup data to Amazon S3.</p><h4>Retention and Immutability Matter Too</h4><p>Storing a backup in Amazon S3 is only part of the strategy. Recovery points also need appropriate retention and protection against unwanted modification or deletion.</p><p>With S3 Object Lock and backup immutability configured through NAKIVO, recovery points can be protected from any change during the defined immutability period.</p><p>Combined with a <a href="https://www.nakivo.com/blog/gfs-retention-policy-explained/?utm_source=medium">GFS retention policy</a>, organizations can retain frequent short-term recovery points alongside selected weekly, monthly, and yearly recovery points.</p><h4>Backup Independence Is the Point</h4><p>The value of this architecture is not simply creating another copy. It places recovery data on a separate infrastructure outside the Microsoft 365 environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9acc81b3f769" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex/a-practical-guide-to-backing-up-sharepoint-online-to-amazon-s3-9acc81b3f769">A Practical Guide to Backing Up SharePoint Online to Amazon S3</a> was originally published in <a href="https://medium.com/codex">CodeX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Simple Guide to Backing Up Microsoft Office 365 Emails]]></title>
            <link>https://blog.developersglobal.got-a.page/a-simple-guide-to-backing-up-microsoft-office-365-emails-d4946997a126?source=rss-ed7c6986c0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4946997a126</guid>
            <category><![CDATA[data-protection]]></category>
            <category><![CDATA[office-365]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[email-security]]></category>
            <dc:creator><![CDATA[NAKIVO]]></dc:creator>
            <pubDate>Tue, 18 Aug 2026 12:13:43 GMT</pubDate>
            <atom:updated>2026-08-28T07:01:21.788Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4gn5J2KYt60pvZkAQbnVBA.jpeg" /></figure><p>Email can become a blind spot in an organization’s data protection strategy. Contracts, approvals, client communications, and financial records often reside in Exchange Online mailboxes, making recovery planning an important part of Microsoft 365 administration.</p><p>Microsoft provides several native retention and recovery capabilities, including Microsoft 365 Backup. However, IT teams still need to decide whether the available retention, storage model, recovery options, and administrative controls meet their organization’s requirements.</p><h3>Understanding Native Microsoft 365 Recovery</h3><p>Traditional Microsoft 365 features such as retention policies, litigation holds, eDiscovery, and archiving serve specific data-management and compliance purposes. For example, Exchange Online retains deleted items for 14 days by default, with the option to extend that period to 30 days. Deleted mailboxes can generally be recovered for 30 days.</p><p>Microsoft 365 Backup adds dedicated backup capabilities for Exchange Online. It retains backup data for one year and provides Exchange restore points at 10-minute intervals throughout that period.</p><p>This means the question is no longer simply whether Microsoft 365 provides backup. Instead, organizations should evaluate whether their native backup model provides the storage independence, retention control, recovery flexibility, and operational model they require.</p><h3>Why Consider a Dedicated Backup Solution?</h3><p>A third-party backup solution can provide greater control over where backup data is stored.</p><p>Microsoft 365 Backup data remains within the Microsoft 365 tenant and follows Microsoft 365 data-residency rules. Data protection solutions like NAKIVO Backup &amp; Replication, by comparison, can store Microsoft 365 backups in local repositories, NAS devices, SMB/NFS shares, Amazon S3, Wasabi, other S3-compatible storage, and other supported destinations.</p><p>This can help organizations build a data protection architecture with backup copies stored separately from their primary Microsoft 365 environment.</p><p>NAKIVO also provides additional capabilities, including backup encryption, configurable retention, immutability on supported repositories, automated scheduling, and granular Exchange Online recovery.</p><h3>Planning for Email Recovery</h3><p>A Microsoft 365 backup strategy should start with <a href="https://www.nakivo.com/blog/how-to-recover-deleted-emails-office-365-guide/?utm_source=Medium&amp;utm_medium=social&amp;utm_campaign=blog-post-backup-office365-emails-guide">recovery requirements</a> rather than with a specific tool.</p><p>IT teams should consider:</p><ul><li>How much email data can the organization afford to lose?</li><li>How quickly must individual messages or entire mailboxes be recovered?</li><li>How long should recovery points be retained?</li><li>Where should backup copies reside?</li><li>Should copies be stored outside the Microsoft 365 environment?</li><li>Are backup and recovery procedures tested regularly?</li></ul><p>The answers help determine whether native Microsoft 365 Backup is sufficient or whether a third-party solution provides additional value.</p><h3>Backup and Compliance</h3><p>Backup can also support broader resilience and compliance requirements.</p><p>For example, <a href="https://www.nakivo.com/blog/digital-operational-resilience-act/?utm_source=Medium&amp;utm_medium=social&amp;utm_campaign=blog-post-backup-office365-emails-guide">DORA</a> requires covered financial entities to establish backup, restoration, and recovery procedures and periodically test them. The regulation has been applied since January 17, 2025.</p><p>The applicable requirements depend on the organization, industry, jurisdiction, and type of data involved, so backup should be treated as one component of a broader compliance and resilience strategy rather than as a compliance guarantee.</p><h3>Final Thoughts</h3><p>The native backup capabilities of Microsoft 365 do not eliminate the need for organizations to define their own recovery strategy.</p><p>For organizations that want additional storage flexibility, independent backup repositories, configurable retention, immutability, and granular recovery, a third-party solution such as NAKIVO Backup &amp; Replication can extend the available protection options.</p><p><a href="https://www.nakivo.com/blog/backup-office-365-emails/?utm_source=Medium&amp;utm_medium=social&amp;utm_campaign=blog-post-backup-office365-emails-guide">Read the complete NAKIVO guide</a> for a step-by-step walkthrough of backing up and recovering Exchange Online data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WDTqQYyZ-NvMc0vnxic2Gw.png" /></figure><h4>Thank you for being a part of the community</h4><p><em>Before you go:</em></p><ul><li>Be sure to <strong>clap</strong> and <strong>follow</strong> the writer ️👏️️</li><li>Follow us:<a href="https://www.linkedin.com/company/developersglobal/"> LinkedIn</a> |<a href="https://medium.com/developersglobal"> Medium</a> |<a href="https://github.com/DevelopersGlobal"> GitHub</a> 🐙</li><li><a href="https://discord.com/invite/Yn9g6KuWyA">Join our Developers Global Community on Discord</a> 🧑🏻‍💻</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WDTqQYyZ-NvMc0vnxic2Gw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4946997a126" width="1" height="1" alt=""><hr><p><a href="https://blog.developersglobal.got-a.page/a-simple-guide-to-backing-up-microsoft-office-365-emails-d4946997a126">A Simple Guide to Backing Up Microsoft Office 365 Emails</a> was originally published in <a href="https://blog.developersglobal.got-a.page/">DevelopersGlobal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Small Businesses Are Not Too Small to Be a Target for Cybercriminals]]></title>
            <link>https://cybersecuritywriteups.com/small-businesses-are-not-too-small-to-be-a-target-for-cybercriminals-94edc6f3dee2?source=rss-ed7c6986c0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/94edc6f3dee2</guid>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[ransomware]]></category>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[data-protection]]></category>
            <dc:creator><![CDATA[NAKIVO]]></dc:creator>
            <pubDate>Fri, 14 Aug 2026 11:49:24 GMT</pubDate>
            <atom:updated>2026-08-14T14:12:52.260Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tc1a3gPkPnWNXclzmhV5_A.jpeg" /></figure><p>Small businesses can no longer assume they are too small to attract cybercriminals. SMBs often hold valuable customer, financial, and business data while operating with fewer cybersecurity resources than larger organizations. That combination can make them attractive targets for both opportunistic and targeted attacks.</p><p>For SMBs, cybersecurity strategy is not simply an IT consideration. A serious incident can disrupt operations, generate substantial recovery costs, damage customer trust, and threaten business continuity.</p><p><strong>Understanding Why SMBs Are Attractive Targets</strong></p><p>The assumption that smaller organizations are ignored by attackers is a costly misconception.</p><p>Limited security budgets, understaffed IT teams, inconsistent security practices, and delayed patching or monitoring can leave SMBs more exposed. At the same time, the data these organizations hold (customer records, financial details, payment information, and business communications) can be valuable regardless of company size. Attackers may steal this information for financial gain or use a smaller organization as a route toward customers, partners, or other connected businesses.</p><p>Ransomware as a Service (RaaS) has also lowered the barrier to entry for cybercriminals. By separating ransomware development from attack execution, the model allows affiliates to conduct campaigns without developing sophisticated ransomware themselves.</p><h4><strong>The Threat Landscape</strong></h4><p>Many cyberattacks exploit familiar weaknesses rather than entirely new techniques.</p><p>Common threats include phishing and social engineering, ransomware, <a href="https://www.nakivo.com/blog/exchange-online-protection-overview/?utm_source=Medium">business email compromise</a>, software vulnerabilities, and attacks using stolen or reused credentials. These techniques can also be combined: Compromised credentials may provide initial access, for example, before an attacker moves deeper into the environment or deploys ransomware.</p><p>Human involvement remains a major factor. Verizon’s 2026 Data Breach Investigations Report found that the human element was present in 62% of breaches, demonstrating why employee awareness remains an important part of an SMB cybersecurity strategy.</p><p><strong>The Average Cost of a Cyberattack</strong></p><p>The true cost of a cyberattack extends far beyond a ransom demand.</p><p>Organizations may face lost revenue during downtime, incident-response and forensic costs, legal expenses, infrastructure recovery, regulatory consequences, and long-term reputational damage. The average cost of a cyberattack in 2026 ranges from $120,000 to $1.24 million, depending on the incident.</p><p>For a smaller organization with limited financial and operational reserves, these combined costs can put significant pressure on business continuity.</p><p><strong>Building Resilience Without an Enterprise Budget</strong></p><p>Improving cybersecurity does not necessarily require enterprise-scale spending.</p><p>Strong, unique passwords managed through a password manager, <a href="https://www.nakivo.com/blog/office-365-app-password-and-multi-factor-authentication/?utm_source=Medium">multi-factor authentication</a>, timely software updates, appropriate access controls, and <a href="https://www.nakivo.com/blog/all-you-should-know-about-it-infrastructure-monitoring/?utm_source=Medium">security monitoring</a> can significantly reduce exposure to common attack methods. CISA recommends many of these measures specifically for small and medium-sized businesses.</p><p>Employee education is equally important. Team members should know how to recognize phishing, suspicious links, unusual authentication requests, and other social-engineering techniques.</p><p><strong>Backups: A Critical Part of Business Continuity</strong></p><p>Preventive security controls reduce the likelihood of a successful attack, but organizations also need a plan for what happens when prevention fails.</p><p>A reliable backup and recovery strategy can help restore data after ransomware, hardware failure, accidental deletion, and other disruptive events.</p><p>This is particularly important because ransomware can target backup infrastructure as well as production systems. CISA recommends maintaining offline or immutable backups and regularly testing recovery processes to confirm that backup data can actually be restored.</p><p>Organizations should also consider the <a href="https://www.nakivo.com/blog/3-2-1-backup-rule-efficient-data-protection-strategy/?utm_source-Medium">3–2–1 backup approach</a>, maintain copies in separate locations or storage systems, and routinely validate their recovery procedures.</p><p>Read the complete guide on the <a href="https://www.nakivo.com/blog/why-smbs-are-targets-of-cyberattacks/?utm_source=Medium">NAKIVO blog</a> to learn why SMBs are attractive targets for cybercriminals and how practical, budget-conscious measures can help reduce cybersecurity risk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94edc6f3dee2" width="1" height="1" alt=""><hr><p><a href="https://cybersecuritywriteups.com/small-businesses-are-not-too-small-to-be-a-target-for-cybercriminals-94edc6f3dee2">Small Businesses Are Not Too Small to Be a Target for Cybercriminals</a> was originally published in <a href="https://cybersecuritywriteups.com/">Cyber Security Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Enable Immutable Backups on Your NAS with NAKIVO]]></title>
            <link>https://blog.developersglobal.got-a.page/how-to-enable-immutable-backups-on-your-nas-with-nakivo-b3cc4b6c71db?source=rss-ed7c6986c0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3cc4b6c71db</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[backup]]></category>
            <category><![CDATA[immutability]]></category>
            <category><![CDATA[nas]]></category>
            <category><![CDATA[developersglobal]]></category>
            <dc:creator><![CDATA[NAKIVO]]></dc:creator>
            <pubDate>Fri, 07 Aug 2026 10:39:51 GMT</pubDate>
            <atom:updated>2026-08-09T15:21:21.203Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nlO3A0C7YuUUONptyuEP7g.jpeg" /></figure><p>Organizations continue to invest in backup infrastructure, but ransomware increasingly targets backup repositories alongside production systems. When attackers can modify or delete recovery data, even a well-designed backup strategy can fail during an incident.</p><p>This makes immutability an important component of a cyber-resilient data protection strategy.</p><h3>Why Backup Immutability Matters</h3><p>Immutable backups are protected from modification and deletion during a specified period. This helps preserve backup data when ransomware reaches the production environment, backup infrastructure, or administrative credentials.</p><p>Immutability can also strengthen the traditional <a href="https://www.nakivo.com/blog/3-2-1-backup-rule-efficient-data-protection-strategy/?utm_source=Medium">3–2–1 backup strategy</a>. The extended 3–2–1–1–0 approach adds an immutable or offline copy and emphasizes backup verification with no unresolved errors.</p><p>However, immutability does not confirm that a recovery point is clean or recoverable. Backup verification, malware scanning, and recovery testing remain necessary.</p><h3>Why NAS Is a Popular Backup Target</h3><p>Network-attached storage (NAS) devices are a popular choice for backup targets because they provide centralized capacity, flexible expansion, and relatively cost-effective storage.</p><p>Some NAS platforms can also host backup software components directly. This can simplify deployment, reduce the need for separate infrastructure, and improve data-transfer efficiency in certain environments.</p><p>Storing backups on a NAS does not automatically make them resistant to ransomware. The device, backup repository, permissions, and immutability settings must all be configured correctly.</p><h3>Preparing Your NAS for Immutable Backups</h3><p>Before enabling immutability, administrators should confirm that the <a href="https://helpcenter.nakivo.com/User-Guide/Content/Deployment/System-Requirements/Deployment-Requirements.htm#Network2?utm_source=Medium">NAS and its file system support the required functionality</a>, which includes:</p><ol><li>Creating a Local Folder backup repository</li><li>Storing backups as separate files</li><li>Preparing the required folder on the NAS</li><li>Installing the appropriate NAKIVO components, including a Transporter where required</li><li>Restricting access to the repository and its administrative interfaces.</li></ol><h3>Configuring Immutable Backup Storage</h3><p>The general process involves installing the required NAKIVO components, preparing a backup folder on the NAS, adding that folder as a backup repository, and enabling immutability in the backup job settings.</p><p>Once configured, protected recovery points cannot be deleted or modified through normal operations until their immutability period expires. Scheduled backup jobs can continue creating new recovery points according to the configured retention policy.</p><h3>More Than Just Backup Storage</h3><p>Immutability is only one part of ransomware recovery planning.</p><p>Organizations should also:</p><ul><li>Verify backups automatically</li><li>Scan recovery points for malware where appropriate</li><li>Test file, application, and full-workload recovery</li><li>Restrict administrative access</li><li>Monitor backup infrastructure for unusual activity</li><li>Maintain additional offsite or isolated copies</li></ul><p>Together, these controls provide stronger evidence that protected workloads can be restored within the required recovery objectives.</p><h3>Final Thoughts</h3><p>Protecting backup data is now as important as protecting production systems. Immutable storage adds an important safeguard by preventing recovery points from being changed or deleted during their retention period.</p><p>It does not replace verification, security monitoring, or recovery testing. Instead, it helps preserve the recovery data that those processes depend on.</p><p>For a detailed walkthrough of preparing a NAS, configuring the repository, and enabling immutable backups with NAKIVO Backup &amp; Replication, read the complete guide to <a href="https://www.nakivo.com/blog/nas-immutable-backup/?utm_source=Medium&amp;utm_medium=social">configuring immutable NAS backups with NAKIVO</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WDTqQYyZ-NvMc0vnxic2Gw.png" /></figure><h4>Thank you for being a part of the community</h4><p><em>Before you go:</em></p><ul><li>Be sure to <strong>clap</strong> and <strong>follow</strong> the writer ️👏️️</li><li>Follow us:<a href="https://www.linkedin.com/company/developersglobal/"> LinkedIn</a> |<a href="https://medium.com/developersglobal"> Medium</a> |<a href="https://github.com/DevelopersGlobal"> GitHub</a> 🐙</li><li><a href="https://discord.com/invite/Yn9g6KuWyA">Join our Developers Global Community on Discord</a> 🧑🏻‍💻</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WDTqQYyZ-NvMc0vnxic2Gw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3cc4b6c71db" width="1" height="1" alt=""><hr><p><a href="https://blog.developersglobal.got-a.page/how-to-enable-immutable-backups-on-your-nas-with-nakivo-b3cc4b6c71db">How to Enable Immutable Backups on Your NAS with NAKIVO</a> was originally published in <a href="https://blog.developersglobal.got-a.page/">DevelopersGlobal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>