Merge pull request circleci#1948 from circleci/gloassary-entries-for-security

Glossary entries for security

Author: michelle-luna

jekyll/__glossary/admin.md

@@ -0,0 +1,5 @@
+---
+term: CircleCI Administrator
+---
+
+he first user to log into a private installation of CircleCI. Administrators have the ability to add and remove users.

jekyll/__glossary/authenticate.md

@@ -0,0 +1,7 @@
+---
+term: Authentication
+--- 
+
+Authentication of CircleCI projects using the hosted application is handled by GitHub, Bitbucket, or Google OAuth. Sessions last for 14 days. See the [Permissions Overview]({{ site.baseurl }}/2.0/gh-bb-integration/#permissions-overview) and [Permissions for Team Accounts]({{ site.baseurl }}/2.0/gh-bb-integration/#permissions-for-team-accounts) sections of the GitHub and Bitbucket Integrations document for additional details.
+
+User authentication may use LDAP for an instance of the CircleCI application that is installed on your private server or cloud, see the [Authentication]({{ site.baseurl }}/2.0/authentication/) document for setup instructions.

jekyll/__glossary/context.md

@@ -0,0 +1,5 @@
+---
+term: Context
+---
+
+Contexts provide a mechanism for securing and sharing environment variables across projects. The environment variables are defined as name/value pairs and are injected at runtime. Environment variables are set on the Contexts page. To use these variables in a workflow, users must be members of the context's organization. The rule must allow access to all projects in the org. See the [Contexts]({{ site.baseurl }}/2.0/contexts/) document for instructions.

jekyll/__glossary/envvars.md

@@ -0,0 +1,5 @@
+---
+term: Environment Variables
+---
+
+Environment variables store customer data that is used by a project. Only project administrators and owners are allowed to view or modify environment variables. The values are transmitted using secure protocols, for example, HTTPS and SSH, encrypted at rest, and hashed/salted to prevent CircleCI employees from viewing them.

jekyll/__glossary/layer_caching.md

@@ -0,0 +1,5 @@
+---
+term: Docker Layer Caching
+---
+
+The CircleCI Docker Layer Caching feature allows builds to reuse Docker image layers from previous builds. Image layers are stored in separate volumes in the cloud and are not shared between projects. Layers may only be used by builds from the same project. For additional information about how the secure environment is created, see the [Docker Layer Caching]({{ site.baseurl }}/2.0/docker-layer-caching/) and [Running Docker Commands](({{ site.baseurl }}/2.0/building-docker-images/) documents. 

jekyll/__glossary/owner.md

@@ -0,0 +1,5 @@
+---
+term: Owner
+---
+
+The owner of the team GitHub account or Bitbucket org.

jekyll/__glossary/project.md

@@ -0,0 +1,5 @@
+---
+term: Project
+---
+
+A CircleCI project shares the name of the code repository for which it automates workflows, tests, and deployment. It is visible on the Projects page of the CircleCI app and must be added with the Add Project button. After the project is added, it is possible to configure settings, contexts, environment variables, and team members who may follow the project. Following a project enables a user to subscribe to email notifications for the project build status and adds the project to their CircleCI dashboard.

jekyll/__glossary/project_admin.md

@@ -0,0 +1,5 @@
+---
+term: Project Administrator
+---
+
+The user who adds a GitHub or Bitbucket repository to CircleCI as a Project.

jekyll/__glossary/user.md

@@ -0,0 +1,5 @@
+---
+term: User
+---
+
+An individual user within an org. A CircleCI user is anyone who can log in to the CircleCI platform with a username and password. Users must be added to a GitHub or Bitbucket org to view or follow associated CircleCI projects.  Users may **not** view project data that is stored in environment variables.