Create Essential DOC Structure for AAF

Issue-ID: AAF-328
Change-Id: I9508611149405bd95d0d1bf2ebe1e0ed37ba333b
Signed-off-by: Instrumental <jonathan.gathman@att.com>

1 files changed, 29 insertions, 0 deletions

diff --git a/docs/sections/architecture/security.rst b/docs/sections/architecture/security.rst
new file mode 100644
index 00000000..fd10dc98
--- /dev/null
+++ b/docs/sections/architecture/security.rst
@@ -0,0 +1,29 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. Copyright © 2017 AT&T Intellectual Property. All rights reserved.
+
+Security Architecture
+=====================
+Communicating
+-------------
+When one compute process needs to communicate to another, it does so with networking.
+
+The service side is always compute process, but the client can be of two types:
+ - People (via browser, or perhaps command line tool)
+ - Compute process talking to another computer process.
+
+Thus, the essential building blocks of any networked system is made up of 
+
+
+In larger systems, it is atypical 
+
+Communicating *Securely*
+------------------------
+Whenever two processing entities exist that need to communicate securely, it is *essential* that 
+ - The communications between the two are encrypted
+ - The identities of the caller and callee are established (authentication)
+ - The caller must be allowed to do what it is asking to do (authorization)
+
+
+
+