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 [2022/10/24 19:05] peaceolaniran |
wiki:policies:disaster [2024/03/04 00:00] (current) katcow |
||
|---|---|---|---|
| Line 30: | Line 30: | ||
| ==== Application Profile ==== | ==== Application Profile ==== | ||
| - | ^Name^Manufactuer^Critical to Business? | + | ^Name^Manufacturer^Critical to Business? |
| |AWS|Amazon|Yes|Yes|Essential for running AutoLit/ | |AWS|Amazon|Yes|Yes|Essential for running AutoLit/ | ||
| |NPM|Microsoft|Yes|Yes|Essential for building production deployments. In the event of repository outage, dependencies may be transferred from backups via FTP.| | |NPM|Microsoft|Yes|Yes|Essential for building production deployments. In the event of repository outage, dependencies may be transferred from backups via FTP.| | ||
| |PyPi| |Yes|Yes|Essential for building production deployments. In the event of repository outage, dependencies may be transferred from backups via FTP.| | |PyPi| |Yes|Yes|Essential for building production deployments. In the event of repository outage, dependencies may be transferred from backups via FTP.| | ||
| |Auth0| |Yes|Yes|Essential for providing authorization & username/ | |Auth0| |Yes|Yes|Essential for providing authorization & username/ | ||
| - | |Stripe| |No|No |Stripe enables pay-on-the-site. Both paying and non-paying users may continue accessing the site in the event of an outage, and payments & subscriptions may be manually managed by the NK team in the event of a long-term outage.| | + | |Stripe| |No|No|Stripe enables pay-on-the-site. Both paying and non-paying users may continue accessing the site in the event of an outage, and payments & subscriptions may be manually managed by the NK team in the event of a long-term outage.| |
| |Google Suite|Google|Yes|No|In the event of an email disruption, we will shift to Outlook-based or other email platforms. In the event of a disruption to Google Meets, we will utilize Zoom for video calls. In the event of a document storage disruption, we will utilize Box for storing company documents.| | |Google Suite|Google|Yes|No|In the event of an email disruption, we will shift to Outlook-based or other email platforms. In the event of a disruption to Google Meets, we will utilize Zoom for video calls. In the event of a document storage disruption, we will utilize Box for storing company documents.| | ||
| |Toggl|Toggl|No|No|Used for employee and contractor time tracking. If a disruption occurs, we will require manual time tracking| | |Toggl|Toggl|No|No|Used for employee and contractor time tracking. If a disruption occurs, we will require manual time tracking| | ||
| Line 43: | Line 43: | ||
| |GitLab| |Yes|Yes|If a temporary disruption occurs, we will employ FTP & patch files.| | |GitLab| |Yes|Yes|If a temporary disruption occurs, we will employ FTP & patch files.| | ||
| |Carta| |No|No| | | |Carta| |No|No| | | ||
| - | |Pubmed Entrez API| |No|No| \\ When a disruption occurs, manual and recurrng searches fail. Upon recovery, our system automatically begins rerunnning scheduled failed searches. | + | |Pubmed Entrez API| |No|No| \\ When a disruption occurs, manual and recurrng searches fail. Upon recovery, our system automatically begins rerunnning scheduled failed searches.| |
| |Unpaywall| |No|No|When a disruption occurs, the full text import feature is shown as "Not Available" | |Unpaywall| |No|No|When a disruption occurs, the full text import feature is shown as "Not Available" | ||
| |HubSpot| |No|No| | | |HubSpot| |No|No| | | ||
| 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.| | ||
| + | |[[http:// | ||
| + | |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.| | ||
| + | |Abstra|Abstra|Yes|No|Disruptions may impact the timeliness of customer support actions. | | ||
| ==== Roles and Contacts ==== | ==== Roles and Contacts ==== | ||
| Line 56: | 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 62: | 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 74: | 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 184: | 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 219: | Line 232: | ||
| ^Author^Date of Revision/ | ^Author^Date of Revision/ | ||
| |K. Cowie|11/ | |K. Cowie|11/ | ||
| - | |K. Holub|06/ | ||
| |K. Kallmes|11/ | |K. Kallmes|11/ | ||
| - | |P. Olaniran|10/ | + | |K. Holub|06/ |
| + | |P. Olaniran|10/ | ||
| + | |K. Kallmes|1/ | ||
| [[: | [[: | ||
wiki/policies/disaster.1666638309.txt.gz · Last modified: 2022/10/24 19:05 by peaceolaniran
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
