{"id":975,"date":"2021-09-30T21:06:43","date_gmt":"2021-09-30T21:06:43","guid":{"rendered":"http:\/\/box5442.temp.domains\/~arpioio\/?p=975"},"modified":"2021-09-30T21:06:43","modified_gmt":"2021-09-30T21:06:43","slug":"11-different-saas-disaster-scenario-s","status":"publish","type":"post","link":"https:\/\/arpio.io\/staging\/8013\/11-different-saas-disaster-scenario-s\/","title":{"rendered":"11 Different SaaS Disaster Scenario&#8217;s"},"content":{"rendered":"<body>\n<h2 class=\"wp-block-heading\">.. and How to Recover From Them and Prevent Them.<\/h2>\n\n\n\n<p>Consider yourself one of the lucky ones if you\u2019ve never experienced a SaaS Disaster. Whether it\u2019s a simple hacking, a network fail, or even a natural disaster, having a recovery strategy is critical!  Here are 11 Different SaaS Disaster Scenarios, ways to recover, and our thoughts on how to prevent them from affecting your systems to begin with.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Malware \/ ransomware attack<\/h3>\n\n\n\n<p><strong>Scenario:<\/strong> <br>Malicious code makes it onto your server, gains root access and effectively takes control of your system.<\/p>\n\n\n\n<p><strong>Severity:<\/strong> <br>Worst case scenario. Often very hard (or impossible, unless payments are made) to recover from.<\/p>\n\n\n\n<p><strong>Recovery Strategy: <\/strong><br>Recover in a completely new, clean environment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Regional AWS service failure<\/h3>\n\n\n\n<p><strong>Prevention best practice:<\/strong> <br>Strict security patch policies, Clean recovery (Arpio) software to start \u2018from scratch\u2019 and making sure you have a long enough backup trail to be able to go back to \u2018pre-infection\u2019 status.<\/p>\n\n\n\n<p><strong>Scenario:<\/strong> <br>One of the many AWS regional services has an outage.\u00a0 Your application depends on that service (or depends on a service that depends on that service) and their outage has become your outage.<\/p>\n\n\n\n<p><strong>Severity: <\/strong><br>Moderate.\u00a0 You may be dead in the water until AWS fixes the root cause, but usually you\u2019re only offline for a few hours.\u00a0 Worst case scenario, you\u2019re offline for a few days.<\/p>\n\n\n\n<p><strong>Recovery Strategy: <\/strong><br>Recover in an alternate region<\/p>\n\n\n\n<p><strong>Prevention Best Practice:<\/strong> <br>Avoiding this outage requires a multi-region strategy.\u00a0 Multi-region-active architectures are best here, but they\u2019re very hard to build.\u00a0 For most organizations, cross-region failover is more attainable.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">AWS access tokens committed to public source repo<\/h3>\n\n\n\n<p><strong>Scenario: <\/strong><br>You\u2019re using IAM users to access AWS from your runtime compute environment, and you\u2019ve got the access tokens stored in a file on disk.\u00a0 And then you commit that file to source control.\u00a0 Oops.<\/p>\n\n\n\n<p><strong>Severity: <\/strong><br>Moderate to bad.\u00a0 Attackers monitor public repos for this very scenario.\u00a0 If your IAM user has privileged access, you could be in hot water.<\/p>\n\n\n\n<p><strong>Recovery Strategy: <\/strong><br>Discard those access tokens pronto. Make sure to verify possible damage \/ access including injection of malicious code depending on the access levels exposed.<\/p>\n\n\n\n<p><strong>Prevention Best Practice:<\/strong> <br>If your runtime compute environment runs in AWS, use <strong>IAM Roles<\/strong> instead of <strong>IAM Users<\/strong>.\u00a0 If you must use IAM Users, treat those credentials as you would any other critical operations secret.\u00a0 And if you are launching these applications directly from a logged on session, protect the access with MFA.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Disgruntled employee does something unfathomable<\/h3>\n\n\n\n<p><strong>Scenario:<\/strong> <br>You had a bad seed on the team, and you let him go. But you didn\u2019t realize all of the routes he had into your production environment, and you didn\u2019t get him locked out.\u00a0 He decided to seek revenge, and now your environment is toast.\u00a0 <a href=\"https:\/\/www.itnews.com.au\/news\/ex-cisco-engineer-deleted-456-vms-for-webex-teams-after-exit-552494\" target=\"_blank\" rel=\"noreferrer noopener\">It happened to WebEx<\/a>.<\/p>\n\n\n\n<p>S<strong>everity: <\/strong><br>Worst case scenario, the insider job.<\/p>\n\n\n\n<p>R<strong>ecovery Strategy: <\/strong><br>Cross-account backup\/recovery to an account that he was unable to access.<\/p>\n\n\n\n<p><strong>Prevention Best Practice:<\/strong> <br>Single sign-on everywhere you can, <a href=\"https:\/\/docs.aws.amazon.com\/cli\/latest\/userguide\/cli-configure-sso.html#sso-using-profile\" target=\"_blank\" rel=\"noreferrer noopener\">including at the command line<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Automation goes haywire<\/h3>\n\n\n\n<p><strong>Scenario:<\/strong> <br>You\u2019re using an infrastructure-as-code solution to manage your environment.\u00a0 It has been an extremely reliable mode of operation, until you fail just once to realize that the change you\u2019re pushing live will replace (instead of update) a stateful resource.<\/p>\n\n\n\n<p><strong>Severity:<\/strong> <br>Moderate to severe.\u00a0 You hopefully have backups, but it\u2019ll take a while to restore them.<\/p>\n\n\n\n<p><strong>Recovery Strategy: <\/strong><br>In-place restore of your data<\/p>\n\n\n\n<p><strong>Prevention Best Practice:<\/strong> <br>Always run \u201cterraform plan\u201d or use CloudFormation changesets before applying changes to prod.\u00a0 And pay close attention to what they\u2019re telling you!<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Human error in the cloud console<\/h3>\n\n\n\n<p><strong>Scenario:<\/strong> <br>This can happen in so many ways, but a catastrophic example is that while trying to clean-up a non-production resource (like a database), somebody accidentally cleans up the production resource.\u00a0 And if they didn\u2019t check the box to \u201ccreate one final snapshot\u201d before launching the request, there may not be a good backup to restore.<\/p>\n\n\n\n<p><strong>Severity:<\/strong> <br>Moderate to severe \u2013 it just depends on what the mistake was.<\/p>\n\n\n\n<p><strong>Recovery:<\/strong> <br>You need to re-create that resource, through whatever means makes sense.\u00a0 If it\u2019s a stateful resource (a database, a server, etc.) then you also need to restore its data.<\/p>\n\n\n\n<p><strong>Prevention Best Practice:<\/strong> <br>Aside from limiting access to production environments so that a minimal number of people can potentially make this mistake, you <em>definitely <\/em>want to have good backups that you store outside of the production environment.\u00a0 You wouldn\u2019t want the human error to delete your data and your backups.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Mistakenly ran a pre-prod command in production<\/h3>\n\n\n\n<p><strong>Scenario:<\/strong> <br>You thought you were logged into the test environment, but you were wrong.\u00a0 And now the production environment is broken.<\/p>\n\n\n\n<p><strong>Severity:<\/strong> <br>Again, depends on what you mistakenly deleted.\u00a0 This can be really bad.<\/p>\n\n\n\n<p><strong>Recovery: <\/strong><br>Restore whatever was broken.\u00a0 If that\u2019s a catastrophic mistake, you may need to restore much of the environment.<\/p>\n\n\n\n<p><strong>Prevention Best Practice:\u00a0 <\/strong><br>Again, limit access to production so you\u2019ve minimized the number of people who can make this mistake.\u00a0 And ensure you\u2019ve got a solid recovery plan in place in case it still happens.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Bad actor deletes your servers and your backups<\/h3>\n\n\n\n<p><strong>Scenario:\u00a0<\/strong> <br>The bad actor that hacked into your environment and held you for ransom was smart enough to find your backups and delete them in the process.\u00a0 If those were your only backups, you might not be able to get your data back.\u00a0 Ever.<\/p>\n\n\n\n<p><strong>Severity:<\/strong> <br>Severe, maybe even existential.<\/p>\n\n\n\n<p>R<strong>ecovery:<\/strong> <br>Restore in a clean environment (the hacked one is tainted \u2013 don\u2019t go back there) from the backups that you\u2019re storing outside of your primary environment.\u00a0 You have those backups, right?<\/p>\n\n\n\n<p><strong>Prevention Best Practice:<\/strong> <br>It\u2019s best if the bad actor never gets into your environment in the first place, but somehow cyber attackers and insider threats keep breaking through.\u00a0 Even if you\u2019ve severely locked down the ship, make sure you\u2019re storing backups outside of your production environment.\u00a0 Copying them to a locked-down AWS account will do the trick.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Natural Disaster<\/h3>\n\n\n\n<p><strong>Scenario: <\/strong><br>An earthquake in Northern California, a wild fire in Oregon, a tornado in Ohio, or hurricane Sandy #2 in Northern Virginia.\u00a0 Natural disasters have a habit of destroying data centers (or the infrastructure they rely upon) in very unpredictable ways.<\/p>\n\n\n\n<p><strong>Severity:<\/strong> <br>Moderate.\u00a0 Usually the downtime from these events is capped at \u201cdays\u201d not \u201cmonths.\u201d<\/p>\n\n\n\n<p>R<strong>ecovery: <\/strong><br>Restore in a different region to continue operating while the dust clears.<\/p>\n\n\n\n<p><strong>Prevention Best Practice:\u00a0<\/strong> <br>Certainly it helps to be distributed across multiple AZs in a region, but AZs and workloads have interdependencies that can undermine this resilience.<\/p>\n\n\n\n<p><strong>Recovery:<\/strong> <br>Restore service in an alternate region that isn\u2019t impacted.\u00a0 Make sure you can recover quickly to beat the stampede of other users who are attempting the same.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">State actor hacks your cloud provider<\/h3>\n\n\n\n<p><strong>Scenario:<\/strong> <br>Really sophisticated hackers get into some really prized locations, and you can\u2019t exactly air-gap (disconnect from the internet) a cloud provider.\u00a0 If a state actor compromised a cloud provider, and decided to torch their environment, it\u2019s probably an act of war.<\/p>\n\n\n\n<p><strong>Severity:<\/strong> <br>Catastrophic<\/p>\n\n\n\n<p><strong>Recovery:<\/strong> <br>Rebuild in a completely different infrastructure, probably on a completely different cloud provider.\u00a0 Make sure you have a copy of your data.<\/p>\n\n\n\n<p><strong>Prevention Best Practice:<\/strong> <br>You really can\u2019t do anything to prevent this.\u00a0 But you can mitigate the risk by ensuring that your critical systems are backed up outside of your cloud provider.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Compute vulnerability discloses instance role access tokens<\/h3>\n\n\n\n<p><strong>Scenario:<\/strong> <br>The code you\u2019re running in production has a bug, and an attacker has figured out how to leverage it to dump your environment variables.\u00a0 Conspicuously on display are the access tokens that your production compute role uses to access AWS.<\/p>\n\n\n\n<p><strong>Severity:<\/strong> <br>Moderate to Severe<\/p>\n\n\n\n<p><strong>Recovery:<\/strong> <br>Revoke those access tokens, harden the compute instance, and start repairing the damage that was done.\u00a0 If it\u2019s bad enough, it might be time to rebuild in a clean, uncompromised environment.<\/p>\n\n\n\n<p><strong>Prevention Best Practice:<\/strong>\u00a0 <br>Make sure your production roles and instance profiles have the minimum privilege necessary to do their job, and stay up to date on your patches.<\/p>\n<\/body>","protected":false},"excerpt":{"rendered":"<p>.. and How to Recover From Them and Prevent Them. Consider yourself one of the lucky ones if you\u2019ve never experienced a SaaS Disaster. Whether it\u2019s a simple hacking, a&#8230;<\/p>\n","protected":false},"author":1,"featured_media":982,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","content-type":"","inline_featured_image":false,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-975","post","type-post","status-publish","format-standard","has-post-thumbnail","category-blog"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>11 Different SaaS Disaster Scenario&#039;s - Arpio Disaster Recovery Made Easy<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"11 Different SaaS Disaster Scenario&#039;s - Arpio Disaster Recovery Made Easy\" \/>\n<meta property=\"og:description\" content=\".. and How to Recover From Them and Prevent Them. Consider yourself one of the lucky ones if you\u2019ve never experienced a SaaS Disaster. Whether it\u2019s a simple hacking, a...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/\" \/>\n<meta property=\"og:site_name\" content=\"Arpio Disaster Recovery Made Easy\" \/>\n<meta property=\"article:published_time\" content=\"2021-09-30T21:06:43+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/arpio.io\/wp-content\/uploads\/2021\/09\/cyclone-g892652316_1280.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1280\" \/>\n\t<meta property=\"og:image:height\" content=\"854\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"6805pwpadmin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"6805pwpadmin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/\"},\"author\":{\"name\":\"6805pwpadmin\",\"@id\":\"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/0a2437a37056190db7e46201a6a65095\"},\"headline\":\"11 Different SaaS Disaster Scenario&#8217;s\",\"datePublished\":\"2021-09-30T21:06:43+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/\"},\"wordCount\":1349,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2021\/09\/cyclone-g892652316_1280.jpg\",\"articleSection\":[\"Blog\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/\",\"url\":\"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/\",\"name\":\"11 Different SaaS Disaster Scenario's - Arpio Disaster Recovery Made Easy\",\"isPartOf\":{\"@id\":\"https:\/\/arpio.io\/staging\/8013\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2021\/09\/cyclone-g892652316_1280.jpg\",\"datePublished\":\"2021-09-30T21:06:43+00:00\",\"author\":{\"@id\":\"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/0a2437a37056190db7e46201a6a65095\"},\"breadcrumb\":{\"@id\":\"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/#primaryimage\",\"url\":\"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2021\/09\/cyclone-g892652316_1280.jpg\",\"contentUrl\":\"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2021\/09\/cyclone-g892652316_1280.jpg\",\"width\":1280,\"height\":854},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/arpio.io\/staging\/8013\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"11 Different SaaS Disaster Scenario&#8217;s\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/arpio.io\/staging\/8013\/#website\",\"url\":\"https:\/\/arpio.io\/staging\/8013\/\",\"name\":\"Arpio Disaster Recovery Made Easy\",\"description\":\"AWS Disaster Recovery\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/arpio.io\/staging\/8013\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/0a2437a37056190db7e46201a6a65095\",\"name\":\"6805pwpadmin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/bbce7316dd4979a6199ddcdaed836e357939826f60c7be919373136535d247b6?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/bbce7316dd4979a6199ddcdaed836e357939826f60c7be919373136535d247b6?s=96&d=mm&r=g\",\"caption\":\"6805pwpadmin\"},\"sameAs\":[\"http:\/\/support.pagely.com\"],\"url\":\"https:\/\/arpio.io\/staging\/8013\/author\/6805pwpadmin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"11 Different SaaS Disaster Scenario's - Arpio Disaster Recovery Made Easy","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/","og_locale":"en_US","og_type":"article","og_title":"11 Different SaaS Disaster Scenario's - Arpio Disaster Recovery Made Easy","og_description":".. and How to Recover From Them and Prevent Them. Consider yourself one of the lucky ones if you\u2019ve never experienced a SaaS Disaster. Whether it\u2019s a simple hacking, a...","og_url":"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/","og_site_name":"Arpio Disaster Recovery Made Easy","article_published_time":"2021-09-30T21:06:43+00:00","og_image":[{"width":1280,"height":854,"url":"https:\/\/arpio.io\/wp-content\/uploads\/2021\/09\/cyclone-g892652316_1280.jpg","type":"image\/jpeg"}],"author":"6805pwpadmin","twitter_card":"summary_large_image","twitter_misc":{"Written by":"6805pwpadmin","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/#article","isPartOf":{"@id":"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/"},"author":{"name":"6805pwpadmin","@id":"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/0a2437a37056190db7e46201a6a65095"},"headline":"11 Different SaaS Disaster Scenario&#8217;s","datePublished":"2021-09-30T21:06:43+00:00","mainEntityOfPage":{"@id":"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/"},"wordCount":1349,"commentCount":0,"image":{"@id":"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/#primaryimage"},"thumbnailUrl":"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2021\/09\/cyclone-g892652316_1280.jpg","articleSection":["Blog"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/","url":"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/","name":"11 Different SaaS Disaster Scenario's - Arpio Disaster Recovery Made Easy","isPartOf":{"@id":"https:\/\/arpio.io\/staging\/8013\/#website"},"primaryImageOfPage":{"@id":"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/#primaryimage"},"image":{"@id":"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/#primaryimage"},"thumbnailUrl":"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2021\/09\/cyclone-g892652316_1280.jpg","datePublished":"2021-09-30T21:06:43+00:00","author":{"@id":"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/0a2437a37056190db7e46201a6a65095"},"breadcrumb":{"@id":"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/#primaryimage","url":"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2021\/09\/cyclone-g892652316_1280.jpg","contentUrl":"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2021\/09\/cyclone-g892652316_1280.jpg","width":1280,"height":854},{"@type":"BreadcrumbList","@id":"https:\/\/arpio.io\/11-different-saas-disaster-scenario-s\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/arpio.io\/staging\/8013\/"},{"@type":"ListItem","position":2,"name":"11 Different SaaS Disaster Scenario&#8217;s"}]},{"@type":"WebSite","@id":"https:\/\/arpio.io\/staging\/8013\/#website","url":"https:\/\/arpio.io\/staging\/8013\/","name":"Arpio Disaster Recovery Made Easy","description":"AWS Disaster Recovery","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/arpio.io\/staging\/8013\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/0a2437a37056190db7e46201a6a65095","name":"6805pwpadmin","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/bbce7316dd4979a6199ddcdaed836e357939826f60c7be919373136535d247b6?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/bbce7316dd4979a6199ddcdaed836e357939826f60c7be919373136535d247b6?s=96&d=mm&r=g","caption":"6805pwpadmin"},"sameAs":["http:\/\/support.pagely.com"],"url":"https:\/\/arpio.io\/staging\/8013\/author\/6805pwpadmin\/"}]}},"_links":{"self":[{"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/posts\/975","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/comments?post=975"}],"version-history":[{"count":0,"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/posts\/975\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/media\/982"}],"wp:attachment":[{"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/media?parent=975"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/categories?post=975"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/tags?post=975"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}