wiki:policies:disaster
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
wiki:policies:disaster [2023/10/03 15:29] kevinkallmes |
wiki:policies:disaster [2024/03/04 00:00] (current) katcow |
||
|---|---|---|---|
| Line 50: | Line 50: | ||
| |OBS Studio| |No|No| | | |OBS Studio| |No|No| | | ||
| |Metabase| |No|No|Include sensitive and confidential data.| | |Metabase| |No|No|Include sensitive and confidential data.| | ||
| - | |Scite| |Yes|Yes|When a disruption occurs, the scite badge no longer displays. | | + | |Scite| |Yes|Yes|When a disruption occurs, the scite badge no longer displays.| |
| |[[http:// | |[[http:// | ||
| |EuropePMC| |Yes|Yes|When a disruption occurs, manual and recurring searches fail. Upon recovery, our system automatically begins rerunnning scheduled failed searches.| | |EuropePMC| |Yes|Yes|When a disruption occurs, manual and recurring searches fail. Upon recovery, our system automatically begins rerunnning scheduled failed searches.| | ||
| |DOAJ| |Yes|Yes|When a disruption occurs, manual and recurring searches fail. Upon recovery, our system automatically begins rerunnning scheduled failed searches.| | |DOAJ| |Yes|Yes|When a disruption occurs, manual and recurring searches fail. Upon recovery, our system automatically begins rerunnning scheduled failed searches.| | ||
| + | |Abstra|Abstra|Yes|No|Disruptions may impact the timeliness of customer support actions. | | ||
| ==== Roles and Contacts ==== | ==== Roles and Contacts ==== | ||
| Line 60: | Line 61: | ||
| |Kevin Kallmes|CEO|Executive decisions; personnel management| \\ [[kevinkallmes@supedit.com|kevinkallmes@supedit.com]] \\ | |Kevin Kallmes|CEO|Executive decisions; personnel management| \\ [[kevinkallmes@supedit.com|kevinkallmes@supedit.com]] \\ | ||
| |Karl Holub|CTO|Technical Lead|[[karl.holub@nested-knowledge.com|karl.holub@nested-knowledge.com]]| | |Karl Holub|CTO|Technical Lead|[[karl.holub@nested-knowledge.com|karl.holub@nested-knowledge.com]]| | ||
| - | |Kathryn Cowie|COO|Administrative Support; operational | + | |Kathryn Cowie|COO|Operational |
| ==== Business Continuity Strategies ==== | ==== Business Continuity Strategies ==== | ||
| Line 66: | Line 67: | ||
| === Loss of Function of Critical Applications === | === Loss of Function of Critical Applications === | ||
| - | * In the case of the loss of functionality to AutoLit or Synthesis, the CTO will be notified and we will send out a Site Disruption message to all users. The CTO and development team will assess the extent of any lost capabilities and timeline to restoration, | + | * In the case of the loss of functionality to AutoLit or Synthesis |
| * In the case of the loss of functionality to any other key/ | * In the case of the loss of functionality to any other key/ | ||
| - | * In case of outages, the CEO will email account representatives for customers with a proposed restoration timeline and details regarding the outage. | + | * In case of outages, the CEO or another leader |
| - | * Outages will also be communicated on Twitter @nestedknowledge | + | |
| === Recession Planning === | === Recession Planning === | ||
| Line 78: | Line 78: | ||
| * In the event that Nested Knowledge loses our CTO, we will elevate our head engineer to replace the duties and hire an additional engineer as soon as feasible. | * In the event that Nested Knowledge loses our CTO, we will elevate our head engineer to replace the duties and hire an additional engineer as soon as feasible. | ||
| - | * In the event that Nested Knowledge loses our COO, we will hire an already trained | + | * In the event that Nested Knowledge loses our COO, we will hire an already trained |
| ==== Compliance Statement ==== | ==== Compliance Statement ==== | ||
| Line 188: | Line 188: | ||
| If applicable, assigned staff will coordinate with the media, working according to guidelines that have been previously approved and issued for dealing with post-disaster communications. | If applicable, assigned staff will coordinate with the media, working according to guidelines that have been previously approved and issued for dealing with post-disaster communications. | ||
| + | |||
| + | ==== Insurance Requirements ==== | ||
| + | |||
| + | As a mitigation of financial risk, legal exposure, data privacy breach, and other key company functions, the company will maintain the following insurance policies: | ||
| + | |||
| + | * General Business / Professional Liability Insurance | ||
| + | * Network Security and Privacy Liability Insurance | ||
| + | * Cyber Crime Insurance | ||
| + | * System Damage and Business Interruption Insurance | ||
| ==== Finances and Legal Action ==== | ==== Finances and Legal Action ==== | ||
| Line 208: | Line 217: | ||
| * Upcoming payments for taxes, payroll taxes, Social Security, etc. | * Upcoming payments for taxes, payroll taxes, Social Security, etc. | ||
| * Availability of company credit cards to pay for supplies and services required post- disaster. | * Availability of company credit cards to pay for supplies and services required post- disaster. | ||
| - | |||
| - | === Insurance Requirements === | ||
| - | |||
| - | As a mitigation of financial risk, legal exposure, data privacy breach, and other key company functions, the company will maintain the following insurance policies: | ||
| - | |||
| - | * General Business / Professional Liability Insurance | ||
| - | * Network Security and Privacy Liability Insurance | ||
| - | * Cyber Crime Insurance | ||
| - | * System Damage and Business Interruption Insurance | ||
| === Legal Actions === | === Legal Actions === | ||
wiki/policies/disaster.1696346976.txt.gz · Last modified: 2023/10/03 15:29 by kevinkallmes
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
