doc: add project security docs

While we're working on doc publishing that separates kernel docs that are release-specific from project docs that aren't, (temporarily) put the security documents here so they'll be published with the 1.9 release. Signed-off-by: David B. Kinder <[email protected]>
zephyrproject-rtos · Aug 18, 2017 · 1257bdc · 1257bdc
1 parent 0873540
commit 1257bdc
Show file tree

Hide file tree

Showing 8 changed files with 839 additions and 15 deletions.
diff --git a/doc/contribute/contribute.rst b/doc/contribute/contribute.rst
@@ -10,4 +10,3 @@ patches for code, documentation, tests, and more, directly to the project.
    :maxdepth: 1
 
    contribute_guidelines.rst
-   security.rst
diff --git a/doc/index.rst b/doc/index.rst
@@ -46,6 +46,7 @@ Sections
    api/api.rst
    samples/samples.rst
    reference/kconfig/index.rst
+   security/security.rst
    contribute/contribute.rst
    release-notes.rst
    LICENSING.rst

diff --git a/doc/security/media/security-process-steps.png b/doc/security/media/security-process-steps.png
diff --git a/doc/security/media/security-zephyr-system-architecture.png b/doc/security/media/security-zephyr-system-architecture.png
diff --git a/doc/contribute/security.rst → doc/security/secure-coding.rst b/doc/contribute/security.rst → doc/security/secure-coding.rst
@@ -79,7 +79,7 @@ help prevent security violations and limit their impact:
   protection scheme, e.g., after successful authentication.
   Furthermore, default settings for services shall be chosen in a way
   to provide maximum security.  This corresponds to the "Secure by
-  Default" paradigm [MICRO12]_.
+  Default" paradigm [MS12]_.
 
 - **Separation of privilege** is the principle that two conditions or
   more need to be satisfied before access is granted. In the context
@@ -108,13 +108,13 @@ specific to the development of a secure RTOS:
   threat mitigation approach. In case of the complementary security
   approach, parts of the threat mitigation are performed by the
   underlying platform. In case such mechanisms are not provided by the
-  platform, or are not trusted, a defense in depth [MICRO12]_ paradigm
+  platform, or are not trusted, a defense in depth [MS12]_ paradigm
   shall be used.
 
 - **Less commonly used services off by default**: to reduce the
   exposure of the system to potential attacks, features or services
   shall not be enabled by default if they are only rarely used (a
-  threshold of 80% is given in [MICRO12]_). For the Zephyr project, this can
+  threshold of 80% is given in [MS12]_). For the Zephyr project, this can
   be realized using the configuration management. Each functionality
   and module shall be represented as a configuration option and needs
   to be explicitly enabled. Then, all features, protocols, and drivers
@@ -279,14 +279,3 @@ and approved by consensus.
    infrastructure being taken down.
 
 .. _attack: http://www.theverge.com/2016/10/21/13362354/dyn-dns-ddos-attack-cause-outage-status-explained
-
-.. [MICRO12] Microsoft Corporation, Security Development Lifecycle - SDL
-   Process Guidance Version 5.2, 2012.
-
-.. [PAUL09] M. Paul, "The Ten Best Practices for Secure Software
-   Development," International Information Systems Security Certification
-   Consortium, Inc. [(ISC)2], Palm Harbor, FL, USA, 2009.
-
-.. [SALT75] J. H. Saltzer and M. D. Schroeder, "The protection of
-   information in computer systems," Proceedings of the IEEE,
-   vol. 63, no. 9, pp. 1278- 1308, Sep 1975.
diff --git a/doc/security/security-citations.rst b/doc/security/security-citations.rst
@@ -0,0 +1,30 @@
+:orphan:
+
+.. _security-citations:
+
+Security Document Citations
+###########################
+
+.. [SALT75] J. H. Saltzer and M. D. Schroeder, "The protection of
+   information in computer systems," Proceedings ofthe IEEE, vol. 63, no.
+   9, pp. 1278-1308, Sep 1975.
+
+.. [PAUL09] M. Paul, "The Ten Best Practices for Secure Software
+   Development," International Information Systems Security Certification
+   Consortium, Inc. [(ISC)2 |reg|], Palm Harbor, FL, USA, 2009.
+
+.. [MS12] Microsoft Corporation, Security Development Lifecycle - SDL
+   Process Guidance Version 5.2,2012.
+
+.. [CCITSE12] Common Criteria for Information Technology Security
+   Evaluation ver. 3.1 rev. 4, 2012.
+
+.. [MICR16] Micrium, "Certification Kits," 2016. [Online]. Available:
+   https://www.micrium.com/certification/certification-kits/.
+
+.. [NIST02] National Institute of Standards and Technology, FIPS PUB 140-2:
+   Security Requirements for COMPANY PUBLIC Application note Cryptographic
+   Modules, Gaithersburg, 2002.
+
+.. [GHS10] Green Hills Software, "INTEGRITY-178B Separation Kernel Security
+   Target v4.2," 2010.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -10,4 +10,3 @@ patches for code, documentation, tests, and more, directly to the project.
		:maxdepth: 1

		contribute_guidelines.rst
		security.rst