Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: disaster recovery best practices #50

Merged
merged 1 commit into from
Jan 18, 2022
Merged

doc: disaster recovery best practices #50

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
31 changes: 31 additions & 0 deletions docs/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -480,6 +480,37 @@ <h2>Threat Model</h2>
</section>
</section>



<section class="informative">
<h2>Disaster Recovery</h2>
<p>
Industry best practices related to disaster recovery should be followed
by implementations compliant with this specification, specifically at a minimum
guidance from the following whitepapers and specifications SHOULD be used:
<ul>
<li>
<a href="https://csrc.nist.gov/publications/detail/white-paper/2020/04/24/protecting-data-from-ransomware-and-other-data-loss-events/final">
Protecting Data from Ransomware and Other Data Loss Events
</a>
</li>
<li>
<a href="https://nvlpubs.nist.gov/nistpubs/cswp/NIST.CSWP.10012020-draft.pdf">
Securing Data Integrity Against Ransomeware Attacks
</a>
</li>
<li>
<a href="https://csrc.nist.gov/publications/detail/sp/1800-11/final">
NIST SP 1800-11 - Data Integrity: Recovering from Ransomware and Other Destructive Events
</a>
</li>
</ul>
Copy link
Collaborator

@mkhraisha mkhraisha Jan 18, 2022 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Probably need another publication on recovery from outages or something that isn't explicitly an external attack, something maybe like this where its more general principles? https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/disaster-recovery-options-in-the-cloud.html , although this is AWS only so a different source might be better.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#52

NB: the above list links out to multiple NIST and other standards, many of which are referenced directly
in this specification, but each of which should be carefully considered and reviewed even if not linked
to directly from this specification.
</p>
</section>

<section class="informative">
<h2>Accessibility Considerations</h2>

Expand Down