update docs and script

Mirantis · Jul 31, 2017 · 7c8b3f5 · 7c8b3f5
1 parent 753ff99
commit 7c8b3f5
Show file tree

Hide file tree

Showing 13 changed files with 1,072 additions and 653 deletions.
diff --git a/docs/compliance/reference/800-53/AC.md b/docs/compliance/reference/800-53/AC.md
diff --git a/docs/compliance/reference/800-53/AU.md b/docs/compliance/reference/800-53/AU.md
diff --git a/docs/compliance/reference/800-53/CA.md b/docs/compliance/reference/800-53/CA.md
@@ -219,20 +219,23 @@ The organization develops a continuous monitoring strategy and implements a cont
 **Implemenation Details:**
 
 <ul class="nav nav-tabs">
-<li class="active"><a data-toggle="tab" data-target="#b5vapgr5uce000dismbg">Engine</a></li>
+<li class="active"><a data-toggle="tab" data-target="#b5vm471llv0000avmv60">Engine</a></li>
 </ul>
 
 <div class="tab-content">
-<div id="b5vapgr5uce000dismbg" class="tab-pane fade in active">
+<div id="b5vm471llv0000avmv60" class="tab-pane fade in active">
 The CIS Docker Benchmark can be used as a baseline for securing Docker
 Enterprise Edition and for helping the organization meet the
 continuous monitoring requirements of this control. Additional
 information can be found at the following resources:
 
-- https://benchmarks.cisecurity.org/tools2/docker/CIS_Docker_1.13.0_Benchmark_v1.0.0.pdf
-- http://www.cisecurity.org/critical-controls/tools/CISControlsv4_MaptoNIST800-53rev4.xlsx
-- https://success.docker.com/Architecture/Docker_Reference_Architecture%3A_Securing_Docker_EE_and_Security_Best_Practices#Controls_from_the_CIS_Benchmark
 
+<ul>
+<li><a href="https://benchmarks.cisecurity.org/tools2/docker/CIS_Docker_1.13.0_Benchmark_v1.0.0.pdf">https://benchmarks.cisecurity.org/tools2/docker/CIS_Docker_1.13.0_Benchmark_v1.0.0.pdf</a></li>
+<li><a href="http://www.cisecurity.org/critical-controls/tools/CISControlsv4_MaptoNIST800-53rev4.xlsx">http://www.cisecurity.org/critical-controls/tools/CISControlsv4_MaptoNIST800-53rev4.xlsx</a></li>
+<li><a href="https://success.docker.com/Architecture/Docker_Reference_Architecture%3A_Securing_Docker_EE_and_Security_Best_Practices#Controls_from_the_CIS_Benchmark">https://success.docker.com/Architecture/Docker_Reference_Architecture%3A_Securing_Docker_EE_and_Security_Best_Practices#Controls_from_the_CIS_Benchmark</a></li>
+
+</ul>
 </div>
 </div>
 

diff --git a/docs/compliance/reference/800-53/CM.md b/docs/compliance/reference/800-53/CM.md
diff --git a/docs/compliance/reference/800-53/CP.md b/docs/compliance/reference/800-53/CP.md
@@ -525,28 +525,36 @@ The information system implements transaction recovery for systems that are tran
 **Implemenation Details:**
 
 <ul class="nav nav-tabs">
-<li class="active"><a data-toggle="tab" data-target="#b5vaph35uce000dismpg">DTR</a></li>
-<li><a data-toggle="tab" data-target="#b5vaph35uce000dismq0">UCP</a></li>
+<li class="active"><a data-toggle="tab" data-target="#b5vm479llv0000avmvk0">DTR</a></li>
+<li><a data-toggle="tab" data-target="#b5vm479llv0000avmvkg">UCP</a></li>
 </ul>
 
 <div class="tab-content">
-<div id="b5vaph35uce000dismpg" class="tab-pane fade in active">
+<div id="b5vm479llv0000avmvk0" class="tab-pane fade in active">
 Docker Trusted Registry maintains its cluster state via an internal
 key-value store. This, and other DTR transactions can be backed up and
 recovered. Additional information can be found at the following
 resources:
 
-- https://docs.docker.com/datacenter/dtr/2.2/guides/admin/backups-and-disaster-recovery/
-- https://success.docker.com/Architecture/Docker_Reference_Architecture%3A_Docker_EE_Best_Practices_and_Design_Considerations#DTR_Backup
+
+<ul>
+<li><a href="https://docs.docker.com/datacenter/dtr/2.2/guides/admin/backups-and-disaster-recovery/">https://docs.docker.com/datacenter/dtr/2.2/guides/admin/backups-and-disaster-recovery/</a></li>
+<li><a href="https://success.docker.com/Architecture/Docker_Reference_Architecture%3A_Docker_EE_Best_Practices_and_Design_Considerations#DTR_Backup">https://success.docker.com/Architecture/Docker_Reference_Architecture%3A_Docker_EE_Best_Practices_and_Design_Considerations#DTR_Backup</a></li>
+
+</ul>
 </div>
-<div id="b5vaph35uce000dismq0" class="tab-pane fade">
+<div id="b5vm479llv0000avmvkg" class="tab-pane fade">
 Universal Control Plane maintains its cluster state via an internal
 key-value store. This, and other UCP transactions can be backed up and
 recovered. Additional information can be found at the following
 resources:
 
-- https://docs.docker.com/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery/
-- https://success.docker.com/Architecture/Docker_Reference_Architecture%3A_Docker_EE_Best_Practices_and_Design_Considerations#UCP_Backup
+
+<ul>
+<li><a href="https://docs.docker.com/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery/">https://docs.docker.com/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery/</a></li>
+<li><a href="https://success.docker.com/Architecture/Docker_Reference_Architecture%3A_Docker_EE_Best_Practices_and_Design_Considerations#UCP_Backup">https://success.docker.com/Architecture/Docker_Reference_Architecture%3A_Docker_EE_Best_Practices_and_Design_Considerations#UCP_Backup</a></li>
+
+</ul>
 </div>
 </div>