Todd Gifford / en Data Resilience 101 /resources/blog/december-2021/data-resilience-101 <span> Data Resilience 101</span> <span><span lang="" about="/user/1" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">admin</span></span> <span>Wed, 12/22/2021 - 17:49</span> <a href="/taxonomy/term/14" hreflang="en">Backup</a> <a href="/taxonomy/term/255" hreflang="en">Todd Gifford</a> <article><img src="/sites/default/files/2021-12/Todd%20Gifford.png" width="2240" height="1260" alt="""" loading="lazy" typeof="foaf:Image" /></article><h2><span><span><span><strong>What is data resilience?</strong></span></span></span></h2> <p><span><span><span>You know when your car breaks down or when the fuses blow, and the lights go out at your house? Often both of those things are problems, but you can work around them:  You can call breakdown recovery or grab a taxi, and if the lights go off, sometimes the power is still on elsewhere, or you have a torch. Both of those situations and the workarounds supply a level of resilience – when there is a problem or something breaks, you can still walk around the house at night and see where you are going or make it work or the airport on time.</span></span></span></p> <p><span><span><span>Data resilience is your ability to take a hit on your data availability or integrity and keep your organization running. </span></span></span></p> <h2><span><span><span><strong>Why do you need data resilience?</strong></span></span></span></h2> <p><span><span><span>Let’s get this out there:  All organizations rely on their data; they always have. That accountancy firm from a hundred years ago had loads of data – it was just on paper. Architects, mechanics, the hospital, manufacturers, software developers, those of us who write blogs – everything we do has data at its core or associated with it. Many organizations even have data about their data – how much there is, where it is, who has access to it, how long they should hold it – the list goes on.</span></span></span></p> <p><span><span><span>Let’s take an example – an oil pipeline. How much data is associated with pumping oil through a pipe? Probably quite a bit:  flow rates, volumes pumped, pressure, leaks, maintenance records, valves, staff, locations, emails, diagrams, bills, wages, security information, etc.</span></span></span></p> <p><span><span><span>What happens if all that data is lost or modified? No oil. No bills are issued, or revenue paid. Maybe a massive environmental disaster. </span></span></span></p> <p><span><span><span>So – data. How about that – it’s <strong><em>critical</em></strong> to your organisation.</span></span></span></p> <h2><span><span><span><strong>How to make data resilient</strong></span></span></span></h2> <p><span><span><span>Data resilience requires planning. All organizations have some of the same types of data (like finance or HR) – but its value is different depending on the organisation. </span></span></span></p> <p><span><span><span><strong>Step 1</strong>:  Collect the business requirements for data resilience – these will inform what to protect, how often to protect it, and how quickly it may need restoring after a data resilience event:</span></span></span></p> <ul><li><span><span><span>Know what data is essential to your organization. Work with department heads and those who use the data to perform their jobs. Categorise the data into high, medium and low based on the sensitivity of data (such as HR or medical) and how it would affect your organization if it were changed or unavailable.</span></span></span></li> <li><span><span><span>Know where the data is – if you can’t find the data, you can’t control it and protect it.</span></span></span></li> <li><span><span><span>Know who needs access to the data and how often</span></span></span></li> <li><span><span><span>Work out how long each area of your organization could function <em>without </em>access to its data. This will allow you to work out the maximum time you could be without access to data, known as the RTO or ‘Recovery Time Objective.’</span></span></span></li> <li><span><span><span>Work out how much data you can afford to lose – this is known as the RPO or ‘Recovery Point Objective’.</span></span></span></li> </ul><p><span><span><span>For some organizations – those last two will be zero. As in, the data needs to be ‘always available’ with ‘no loss’.  Ouch – those are some tough asks – but not impossible. There will always be <em>some </em>risk of data loss due to Murphy’s Law – (if something can happen, it will) – but we can do our best to minimize the likelihood. </span></span></span></p> <p><span><span><span><strong><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Step 2:  </span></span></strong><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Data resilience design</span></span></span></span></span></p> <p><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Data resilience design requires answers to the previous questions, but it also needs to consider the systems you are using. Is all of your CRM in Salesforce? Staff using Dropbox for corporate data without permission? Email and finance data in Microsoft 365? </span></span></span></span></span></p> <p><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Here are some pointers for design:</span></span></span></span></span></p> <ul><li><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Control where the data is and where it can go</span></span></span></span></span></li> <li><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Secure those locations – understand who can access the data</span></span></span></span></span></li> <li><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Make those systems and locations as available as they <em>need</em> to be. This is key as the budget likely won’t stretch to allow every system to have 99.999% uptime. The payroll server only needs to run once a month, for example. That real-time ambulance tracking system – that one needs those five-nines of availability.</span></span></span></span></span></li> <li><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Despite all that resilience – you do need to take a backup. </span></span></span></span></span></li> </ul><p><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>For me – the cloud offers a cost-effective way of achieving a high level of availability at an affordable price, as those expensive infrastructure and maintenance costs are shared across many organisations. </span></span></span></span></span></p> <p><span><span><span><strong><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Step 3:  </span></span></strong><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Back up the data</span></span></span></span></span></p> <p><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>This is probably the number one thing on the list of data resilience must-haves. Backups. Back up your data somewhere that lives separately from your primary data (i.e. – consider AWS instead of Azure if your primary data is hosted in Microsoft, and vice-versa). </span></span></span></span></span></p> <p><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>All the security and outsourced hosting won’t protect you from every incident – in fact, most cloud service providers bury it in their terms of agreement that they are not responsible for your data loss. When looking at your resilience plan, it’s important to ask - are you hosting your data in the cloud? In someone else’s cloud platform? </span></span></span></span></span></p> <p><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>There is a </span></span><a href="https://appriver.com/products/backup-recovery" rel="nofollow"><span><span>backup</span></span></a><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span> for that as well – often called cloud-to-cloud backup or SaaS Backup</span></span></span></span></span></p> <p><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Backups provide you with a point-in-time recovery option. Between those points-in-time, however, there could be some data loss (most enterprises backup systems every hour, for example).</span></span></span></span></span></p> <p><span><span><span><strong><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Step 4:</span></span></strong><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span> Archive or backup? You may need both.</span></span></span></span></span></p> <p><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Need to make sure there is as close to zero loss on those legal emails or conversations about patients? For that, you need a real-time copy of everything that happens. This can be in the form of replication to an offsite location for virtual systems or an </span></span><a href="https://appriver.com/product/information-archiving" rel="nofollow"><span><span>information archive</span></span></a><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span> for cloud systems to capture real-time data, like emails or Teams conversations.</span></span></span></span></span></p> <p><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Even if you have backups in place, if you work in an industry with any level of compliance requirement, having an archive can be the fastest and easiest way to source a copy of your communications. Where a backup brings you a step further – it can back up files, images, projects and other data in addition to your communications. When it comes to legal requirements, it’s crucial to practice as much due diligence as possible. You can read more about the difference in archive and backup <a href="/resources/solution-brief/backup-or-archiving" rel="nofollow">here.</a></span></span></span></span></span></p> <h2><span><span><span><strong><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Summary – data resilience</span></span></strong></span></span></span></h2> <p><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>The first rule of data resilience is to ensure you implement backup. The second rule of data resilience is to always have a backup. You can hone your data resilience approach by taking input from your organization. Likely nobody will be comfortable with data loss, but they may be able to operate without some data for a period of time (RPO vs RTO).</span></span></span></span></span></p> <p><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Follow the steps and plan your approach. Not only will this enable you to concentrate your efforts and budget in the right areas, but it will also enable you to <em>show </em>the board or the regulator what you are doing and why.</span></span></span></span></span></p> <p><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>And don’t forget the third rule of data resilience – always have a backup, and make sure it is stored away from where the primary system is. Run all of your environment inside Microsoft 365? An excellent choice – but don’t keep the backups there as well, just in case.</span></span></span></span></span></p> <p> </p> <article class="align-left"><img src="/sites/default/files/2021-12/Picture1.jpg" width="100" height="100" alt="""" loading="lazy" typeof="foaf:Image" /></article><p><span><span><a href="https://link.edgepilot.com/s/d18b5dab/bzc8qTiGakK89XEJUvHEhQ?u=https://eur03.safelinks.protection.outlook.com/?url=https%253A%252F%252Fwww.linkedin.com%252Fin%252Ftodd-gifford%252F%26data=04%257C01%257Ctodd.gifford%2540optimisingit.co.uk%257C830cc0de55324d65cb4c08d94e0a0a26%257C6ddb60aff59f491c91abca97310261cd%257C0%257C0%257C637626628799039669%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C2000%26sdata=E0RHq%252FmEmXxL1hT5%252FqcLXuiAub0FS0yq6ullu8YoXik%253D%26reserved=0" rel="nofollow">Todd Gifford</a>, BEng, CISSP, has 22 years of cybersecurity experience and is the CTO of Optimising IT, a UK-based Managed Service Provider whose goal is to help you pragmatically manage risk. Connect with Todd on LinkedIn or <a href="https://www.optimisingit.co.uk/cloud-services/backups-and-recovery/" rel="nofollow">visit Optimising IT</a> to learn more about how they can help you choose and implement the best cloud-to-cloud backup solution for your business.</span></span></p> <p> </p> <a href="/resources/blog/secure-modern-workplace" hreflang="en">Secure Modern Workplace</a> Wed, 22 Dec 2021 23:49:19 +0000 admin 508 at Should you backup your cloud communications and apps? The answer is yes, and here’s why. /resources/blog/october-2021/should-you-backup-your-cloud-communications-and-apps-answer-yes-and <span>Should you backup your cloud communications and apps? The answer is yes, and here’s why. </span> <span><span lang="" about="/user/1" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">admin</span></span> <span>Tue, 10/12/2021 - 14:51</span> <a href="/taxonomy/term/14" hreflang="en">Backup</a> <a href="/taxonomy/term/255" hreflang="en">Todd Gifford</a> <article><img src="/sites/default/files/2021-10/phone_computers_cloud_graphics.jpg" width="1400" height="700" alt="""" loading="lazy" typeof="foaf:Image" /></article><h2><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Why do I need to back up the cloud?</span></span></span></span></span></h2> <p><span><span><span>Let’s rewind for a moment, to address a question you may be asking: “wait, what do you mean ‘back up THE CLOUD’”?  </span></span></span></p> <p><span><span><span>We are talking about any existing cloud service you’re using today, whether that’s Microsoft 365, Dropbox, Google, Salesforce or other SaaS-based services that house your business data.  </span></span></span></p> <p><span><span><span>Okay, now back to the question: do you <em>really </em>need to backup 'the cloud'?  Yep, you <em>really</em> do.  As great as it would be to leave it at that and have everyone reading this run-out and purchase SaaS (aka cloud-to-cloud backup) immediately – let's explore <em>why</em> it is necessary to do that.</span></span></span></p> <h2><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Cloud is secure and resilient, right?</span></span></span></span></span></h2> <p><span><span><span>Well, yes.  BUT (and it is a massive but) it is possible for a cloud service provider to lose the data your business has stored in their cloud servers.  <a href="https://time.com/4004192/google-data-lightning-belgium/" rel="nofollow">It has happened before</a>, which means it’s likely to happen again. It’s often a simple shrug when it happens to someone else's data, but what if happens to yours?</span></span></span></p> <h2><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>Reasons why cloud storage isn't 100% reliable</span></span></span></span></span></h2> <p><span><span><span>Let's check out three of the most common reasons why the cloud can fail, and you can lose your data.   </span></span></span></p> <p><span class="text-small"><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB">Reason #1:  Ransomware</span></span></p> <p><span><span><span>Yes, ransomware can <a href="https://www.reddit.com/r/dropbox/comments/oq5e16/warning_dropbox_is_useless_against_ransomware/" rel="nofollow">encrypt files</a> in cloud storage systems and defeat any fail-safe capabilities in your chosen cloud provider.  Ouch.   </span></span></span></p> <p><span class="text-small"><em><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB">Reason #2:   Physical failure</span></em></span></p> <p><span><span><span>From <a href="https://www.bbc.co.uk/news/technology-33989384" rel="nofollow">lightning strikes</a> to <a href="https://www.reuters.com/article/us-france-ovh-fire-idUSKBN2B20NU" rel="nofollow">fires</a> – physical failures in someone else’s cloud can and does have the capability to permanently delete data.  </span></span></span></p> <p><span class="text-small"><em><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB">Reason #3: User error</span></em></span></p> <p><span><span><span>And the third critical reason – users.  Last week, we were working with a new client who got in touch because one of their users had accidentally deleted 70,000  files from a SharePoint site.  No problem -let's take a look in the recycle bin.  Ah – over 100,000 files in here.   The challenge came as the client didn't want all of the files back, just those that were accidentally deleted.  To identify them to restore would mean multiple PowerShell scripts or manually selecting the correct files - no small task and likely to miss at least some of the critical files.  Did I mention this type of data recovery process is hugely time-consuming?  Luckily, the customer noticed in time, and the files were available to recover, but there is limited time to do that.  What would have happened if the client didn't notice for a few months?  Likely the data would be gone and irrecoverable.</span></span></span></p> <h2><span><span><span><span lang="EN-GB" xml:lang="EN-GB" xml:lang="EN-GB"><span>How does cloud-to-cloud backup help?</span></span></span></span></span></h2> <p><span><span><span>In the case of ransomware, physical damage and accidental deletion – nothing beats having an offline copy.  By offline, I mean a copy that is stored in another platform, with physical and logical separation beyond the reach of a logged-in user, malicious software running on an endpoint somewhere or indeed a fire that destroys a data center.  It will also save vast amounts of time trying to recover data with tools that were just not designed for data recovery as part of business-as-usual. Those 70,000 Sharepoint files?  Restored in a few clicks with the right backup platform.</span></span></span></p> <p><span><span><span>Encrypted files with no roll-back option?  No problem - head to the last known good backup date in your cloud backup solution and hit the restore button. With unlimited data retention and restore capability for the price of a coffee and a pastry – it's a small price to pay by comparison to the value of your data and potentially your business.</span></span></span></p> <p><span><span><span>To explore more on this topic, download our ebook “<a href="/resources/guide/7-reasons-every-business-needs-saas-backup" rel="nofollow">7 Reasons Every Business Needs SaaS Backup</a>”.</span></span></span></p> <p> </p> <article class="align-left"><img src="/sites/default/files/2021-10/Todd_Gifford.jpg" width="100" height="100" alt="Todd Gifford" loading="lazy" typeof="foaf:Image" /></article><p> </p> <p><span><span><a href="https://link.edgepilot.com/s/d18b5dab/bzc8qTiGakK89XEJUvHEhQ?u=https://eur03.safelinks.protection.outlook.com/?url=https%253A%252F%252Fwww.linkedin.com%252Fin%252Ftodd-gifford%252F%26data=04%257C01%257Ctodd.gifford%2540optimisingit.co.uk%257C830cc0de55324d65cb4c08d94e0a0a26%257C6ddb60aff59f491c91abca97310261cd%257C0%257C0%257C637626628799039669%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C2000%26sdata=E0RHq%252FmEmXxL1hT5%252FqcLXuiAub0FS0yq6ullu8YoXik%253D%26reserved=0" rel="nofollow">Todd Gifford</a>, BEng, CISSP has 22 years of cybersecurity experience and is the CTO of Optimising IT, a UK-based Managed Service Provider whose goal is to help you manage risk in a pragmatic way. Connect with Todd on LinkedIn or <a href="https://www.optimisingit.co.uk/cloud-services/backups-and-recovery/" rel="nofollow">visit Optimising IT</a> to learn more about how they can help you choose and implement the best cloud-to-cloud backup solution for your business.</span></span></p> <a href="/resources/blog/secure-modern-workplace" hreflang="en">Secure Modern Workplace</a> Tue, 12 Oct 2021 19:51:02 +0000 admin 470 at