Commit 74c17e42 authored by Jeff Burrows's avatar Jeff Burrows
Browse files

Updated link and removed evidence

parent 2334f0fb
Pipeline #81699488 passed with stages
in 26 minutes and 23 seconds
......@@ -55,12 +55,8 @@ The GitLab business continuity plan will have team and departmental pieces that
* [NIST Guidance on Business Continuity](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-34r1.pdf)
* [PCI DSS v3.2.1 - Business Continuity Plan](https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-2-1.pdf?agreement=true&time=1551196697261#page=113)
#### Examples of evidence an auditor might request to satisfy this control
We will need some kind of reasonably comprehensive plan to show auditors that has sufficient detail to get GitLab's backup and restoreation in the event of a disruption, even if some GitLabbers are not able to participate in the process. This might actually be easier for us, as a fully remote company since a part of most business continuity plans involve what to do if certain offices are struck by outages or natural disasters.
## Additional control information and project tracking
Non-public information relating to this security control as well as links to the work associated with various phases of project work can be found in the [Business Continuity Plan issue](https://gitlab.com/gitlab-com/gl-security/compliance/compliance/issues/765) .
Non-public information relating to this security control as well as links to the work associated with various phases of project work can be found in the [Business Continuity Plan issue](https://gitlab.com/gitlab-com/gl-security/compliance/compliance/issues/774) .
## Framework Mapping
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment