# Cloud-Dependency and Outage Safety Kit **Purpose.** This kit helps a small business find which physical systems (pool or water treatment, refrigeration, door access, alarms, heating and cooling, point of sale) quietly depend on a cloud login or vendor service, decide what fails safe and what fails dangerous, and set cheap manual fallbacks before an outage. It was prompted by public reporting that a Microsoft outage reportedly left 15 hotel guests in Germany poisoned by chlorine; the details of that incident are thin, so the kit works from the general lesson, not from a confirmed cause. Print it and keep a copy somewhere that doesn't need the internet. ## Checklist - [ ] Walk the whole building and list every device that has an antenna, network cable or monthly "platform" fee. - [ ] Check vendor invoices and card statements for cloud subscriptions tied to building equipment. - [ ] For each device, write what happens if the cloud or login is down for 4 hours. - [ ] Mark each device FAIL-SAFE, FAIL-DANGEROUS or UNKNOWN. - [ ] Put a hand-test log and a shutoff rule in place for anything involving chemicals (pool, spa, water treatment). - [ ] Buy a standalone battery thermometer with a visible display for every cooler and freezer. - [ ] Confirm physical keys exist for every smart lock, and know who holds them. - [ ] Print a contact sheet with night and weekend numbers for each vendor and keep it off the cloud. - [ ] Email each vendor the questionnaire below and file the replies. - [ ] Separate building-system admin logins from everyday email logins and turn on MFA. - [ ] Keep a paper copy of the emergency steps at each site. - [ ] Read your general liability and business-interruption wording for technology or vendor-outage exclusions. - [ ] Ask your insurance agent the questions below and write down the answers and the date. - [ ] Run the 30-minute tabletop drill and fix whatever it exposes. - [ ] Put a recurring reminder in your calendar to repeat the inventory twice a year. ## Worksheet 1: System inventory Make one copy of this block per system. ```text System name: ______________________ Location: ______________ Vendor / product: ________________ Vendor support phone (24h?): ____________ What the cloud controls or reports (alerts, remote control, logs, billing): _____ Who owns the admin login (name/role): ______________ MFA on? Y / N Shared with everyday email login? Y / N If cloud is down for 4 hours, the device: [ ] keeps working normally [ ] works but sends no alerts [ ] stops working [ ] keeps doing something risky [ ] unknown Rating: FAIL-SAFE / FAIL-DANGEROUS / UNKNOWN Manual fallback (what, who, how often): ______________________________ Where the fallback supplies are kept: _________________________________ Vendor reply received (date): ________ Offline mode confirmed? Y / N / unclear ``` ## Worksheet 2: Manual fallback quick reference | System | Fallback | Frequency | Owner | Done | |---|---|---|---|---| | Pool / spa chemistry | Hand test kit and written log; closure rule if test is overdue | e.g. 3 times a day | | [ ] | | Walk-in cooler / freezer | Standalone battery thermometer, read and initial | open, mid-shift, close | | [ ] | | Door access / smart locks | Physical key set, key log | check monthly | | [ ] | | Fire / alarm notifications | Printed call tree, on-site check of panel | during outage | | [ ] | | HVAC | Local thermostat access, written setpoints | daily during outage | | [ ] | | Point of sale | Paper order pad, offline card-reader plan | during outage | | [ ] | Time and cost check (fill in your numbers): hand-test checks per day ____ x minutes each ____ x 30 days = ____ minutes per month. Staff cost per hour $____ gives $____ per month. Standalone thermometers: ____ units x $____ = $____. Compare against value of inventory or claim exposure: $____. ## Template A: Vendor questionnaire email ```text Subject: Outage behavior for [product name] at [site name] Hello, We use [product name] at [site name]. To plan for internet or cloud outages, could you reply in writing to these questions? 1. What does the device or system do if internet or cloud service is lost? Does it keep running, stop, or hold its last setting? 2. Is there an offline or local mode? How do we use it and who can switch it on? 3. How are alerts delivered, and do they still reach us if your cloud is down? 4. Where is your status page, and what is your uptime history for the past 12 months? 5. What is your emergency support phone number outside business hours? 6. Can we split our locations across separate admin accounts? Thank you, [Name, role, phone] ``` ## Template B: Questions for your insurance agent Ask these and write down the answers and the date. ```text 1. Does my general liability policy cover injury to a guest or customer where the cause involves a third-party cloud or software outage? 2. Does my business-interruption policy cover lost income when a vendor's cloud service is down, and is there a waiting period (how many hours)? 3. Are there exclusions or sub-limits for technology failure, utility or service interruption, or cyber events? 4. Does cover depend on the outage starting at my premises or at my vendor's? 5. What documentation would I need to show for a claim (logs, test records, vendor notices)? 6. Do manual hand-test logs and written outage procedures affect my coverage or premium? 7. Is spoiled-stock cover included, and does it require a temperature monitoring device? 8. What is the deductible for each of these situations? 9. Is there a separate cyber policy, and what does it cover that the others don't? 10. Can I get the answers in writing? ``` ## Template C: One-page outage plan and call tree ```text OUTAGE PLAN for [business / site] Last updated: ______ Trigger: email, booking, point of sale or any building system dashboard is unreachable for more than ____ minutes. Safety-critical systems and who checks them by hand: - Pool / water chemistry: ____________ every ____ hours. Closure rule: ____________ - Coolers / freezers: ____________ every ____ hours. Discard rule: ____________ - Doors / alarms: ____________ Key holder: ____________ Decision owner during an outage: ____________ Backup: ____________ Call tree (night and weekend numbers): 1. Manager: ____________ 2. Owner: ____________ 3. Vendor 1 (____): ____________ 4. Vendor 2 (____): ____________ 5. Insurance agent: ____________ 6. Local authority / emergency: ____________ Customer communication: who speaks, what is said, where it is posted: ____________ Close or evacuate an area when: ____________ (confirm thresholds with your equipment manual or local authority). Restore: who confirms systems are back, and who logs the end time: ____________ ``` ## Template D: 30-minute tabletop drill script Run with the people who would be on shift. One person reads the events; one takes notes. ```text Setup (5 min): It is your busiest hour. Your cloud tools, including email and vendor dashboards, are unreachable. Nobody knows when they'll return. Event 1 (5 min): The cooler alarm text never arrives. Who finds out, and how? Event 2 (5 min): Guests ask why the pool or spa looks cloudy. Who tests, who decides to close? Event 3 (5 min): A smart lock fails to open at one entrance. Who has a key? Event 4 (5 min): Point of sale is down. How do you take orders and payments? Event 5 (5 min): A guest or customer reports feeling unwell. Who calls whom, and what is written down? Event 6 (5 min): The vendor's phone line goes to voicemail. What is the next step? Debrief (5 min): What did we not know? What supplies were missing? Who didn't know their role? Assign each fix an owner and a date. ``` ## Prompts (paste-ready) Always tell the AI to use only the documents you paste and to say when it is unsure. Don't paste passwords or account numbers. ```text I run a [type of business] with these systems that connect to the internet: [list]. Using only what I've told you and any vendor documents I paste, tell me for each system what could go wrong if the vendor cloud or my Microsoft 365 login is down for 4 hours. Rate each fail-safe or fail-dangerous and propose a cheap manual fallback. If you don't know how a product behaves offline, say "unknown, ask the vendor". ``` ```text Write a one-page outage plan from the notes I paste below, with sections for safety-critical systems, who to call, manual checks and how often, customer communication, and when to close or evacuate. Leave blanks. Don't invent phone numbers, regulations or thresholds; write "confirm with [authority or manual]" where a number is needed. ``` ```text Draft a short email asking my vendor what [product] does if internet or cloud service is lost, whether there is an offline mode, how alerts are delivered, their uptime history, and their emergency phone number. Under 150 words. Don't claim things about the product that aren't in the details I pasted. ``` ```text Using the policy wording I paste below, list 10 questions for my insurance agent about whether my general liability and business-interruption policies cover injury or lost income from a third-party cloud outage. Quote any relevant exclusions exactly. If the text doesn't address something, say "not stated in what you gave me". This is not legal advice. ``` ```text Design a 30-minute tabletop exercise for my staff simulating a long cloud outage during our busiest shift, using the system list I paste. Give 6 scripted events, who decides what, and a debrief checklist. If an event depends on something I haven't told you, ask me first. ``` ## Sources - https://securityaffairs.com/203189/security/the-microsoft-outage-left-15-hotel-guests-poisoned-by-chlorine.html - https://apprised.news/desk/tech/2026-11-16 - https://www.bleepingcomputer.com/news/security/fbi-warns-artex-ai-hacking-tool-is-powering-global-cyberattacks/ - https://www.bleepingcomputer.com/news/security/cursor-confirms-security-breach-led-to-malicious-claude-code-extension/ - https://apprised.news/desk/insurance/2026-11-15 - https://apprised.news/desk/insurance/2026-11-16 *Informational only, not legal, financial or security-consulting advice. Check the sources and your own policy wording before acting.*