From e6e46f545ccb5dd802eb854f9011edf286c17f3e Mon Sep 17 00:00:00 2001
From: Jonah Silas Sheridan <jonah@iecology.org>
Date: Sat, 2 Sep 2017 21:16:53 +0900
Subject: [PATCH] version 2.0 draft initial commit

---
 1_checklist_introduction.md                   | 146 ++----
 ...sment.md => 2_readiness_assessment_tool.md |  48 +-
 3_legend.md                                   |  10 +-
 4_device_security_checklist.md                |  74 +++
 5_authentication_checklist.md                 |  28 +-
 6_public_wireless_checklist.md                |  47 +-
 ...hecklist.md => 7_email_safety_checklist.md |  36 +-
 8_gsuite_security_checklist.md                |  86 ++++
 7_glossary.md => 9_glossary.md                |  30 +-
 LICENSE                                       | 428 ++++++++++++++++++
 README.md                                     |  32 +-
 11 files changed, 760 insertions(+), 205 deletions(-)
 rename 2_readiness_assessment.md => 2_readiness_assessment_tool.md (66%)
 create mode 100644 4_device_security_checklist.md
 rename 4_email_safety_checklist.md => 7_email_safety_checklist.md (58%)
 create mode 100644 8_gsuite_security_checklist.md
 rename 7_glossary.md => 9_glossary.md (59%)
 create mode 100644 LICENSE

diff --git a/1_checklist_introduction.md b/1_checklist_introduction.md
index bf13b8c..4eb1292 100644
--- a/1_checklist_introduction.md
+++ b/1_checklist_introduction.md
@@ -1,141 +1,65 @@
 ---
-document set: DIGITAL SECURITY CHECKLISTS FOR U.S. NON-PROFITS
+document set: DRAFT DIGITAL SECURITY CHECKLISTS FOR U.S. NON-PROFITS
 title: Introduction
 author: Jonah Silas Sheridan, Lisa Jervis
-last modified: 5/12/17
-version: "1.1, INTERNALLY REVIEWED VERSION FOR PUBLIC USE"
+last modified: 9/2/2017
+version: "2.0, DRAFT NOT FOR PUBLIC USE"
 ---
 # Introduction
 
 ## What is this document set?
 
-This set of documents was made to help small non-profits and NGOs improve their digital security outcomes despite limited resources and technical skill availability. The content was commissioned as part of the [Weathering The Storms]("http://www.roadmapconsulting.org/WTS") initiative of [RoadMap Consulting]("http://www.roadmapconsulting.org/WTS") and fiscally sponsored by [Common Counsel Foundation]("http://commoncounsel.org") of [Oakland, California]("https://localwiki.org/oakland/"). The content was researched and prepared by Jonah Silas Sheridan and Lisa Jervis, Principals of [Information Ecology]("https://iecology.org"), a capacity building consultancy specializing in non-profit and movement technology management, and was peer reviewed by generous members of our community. Many other eyes and hands have helped tune the recommendations to ensure technical accuracy and ease of use. We are grateful to all the members of our community that have helped bring these documents to life.
+This set of documents was made to help small non-profit organizations improve their digital security outcomes despite limited resources and technical skill availability. The content was commissioned as part of the [Weathering The Storms]("http://www.roadmapconsulting.org/WTS") initiative of [RoadMap Consulting]("http://www.roadmapconsulting.org/WTS") and fiscally sponsored by [Common Counsel Foundation]("http://commoncounsel.org") of [Oakland, California]("https://localwiki.org/oakland/"). The content was researched and prepared by Jonah Silas Sheridan and Lisa Jervis, Principals of [Information Ecology]("https://iecology.org"), a capacity building consultancy specializing in non-profit and movement buillding technology management, and was peer reviewed by generous members of our community. Many other eyes and hands have helped tune the recommendations to ensure technical accuracy and ease of use. We are grateful to all the members of our community that have helped bring these documents to life.
 
 ## When was this document set created and last updated?
 
-These documents were originally researched and peer reviewed in Fall 2015. Some small edits for clarity have occurred since. A minor 1.1 revision of Spring 2017 updated and improved the [Readiness Assessment Tool](2_readiness_assessment.md) based on field experience. A full review, update and extension of the checklist set is in process as of June 2017 and is expected to be released in Fall 2017. Contact [RoadMap Consulting](https://roadmapconsulting.org) or [Information Ecology](https://iecology.org/contact)
+These documents were originally researched and peer reviewed in Fall 2015. Some small edit and a minor 1.1 revision of Spring 2017 updated and improved the [Readiness Assessment Tool](2_readiness_assessment_tool.md) and other checklist language based on field experience. A major version 2.0 release was completed in September 2017. This version includes a review, update and extension of the checklist set. The version adds a [Device Security Checklist](4_device_security_checklist.md) and [GSuite Security Checklist](8_gsuite_security_checklist.md). All new content was peer reviewed. Contact [RoadMap Consulting](https://roadmapconsulting.org) or [Information Ecology](https://iecology.org/contact) with questions about this process or content.
 
 **If you have feedback or questions about this document set, its contents or how to use it, please contact Information Ecology using [our secure contact form]("https://iecology.org/contact") or PGP encrypted email to info@iecology.org using [this key]("https://iecology.org/0x3C2BACE5E10F3C7A_pub.txt")**
 
 ## About digital security
 
-The typical technical definition of digital security says that it is the set of processes and practices used to **manage the risk**of an **adversary**exploiting **vulnerabilities** in your systems such that they may become a **threat** to the **confidentiality**, **integrity**, or **availability** of **digital assets** (e.g., file stores, cloud services, emails) or communication **channels** (e.g., instant messaging, telephone, video chats). What does that really mean? It means digital security is the work of protecting your organization's information from being accessed, changed, or blocked by anyone — internal or external, intentionally or not — who shouldn't be able to do so. Effective security strategies, digital or operational are based on the specific threats, vulnerabilities, and adversaries of your organization. This does not mean that a detailed analysis is necessary to get started improving your digital security practices. Many small U.S. organizations share a set of basic threats and vulnerabilities, which these documents are meant to help them address.
+The typical technical definition of digital security says that it is the set of processes and practices used to **manage the risk** of an **adversary** taking advantage of **vulnerabilities** in your systems such that they are a **threat** to the **confidentiality**, **integrity**, or **availability** of a **digital asset** (e.g., file stores, cloud services, emails) or communication **channels** (e.g., instant messaging, telephone, video chats). What does that really mean? It means digital security is the work of protecting your organization's information or communications from being accessed, changed, or blocked by anyone — internal or external, intentionally or not — who shouldn't be able to do so. The most effective security strategies, digital or operational are based on the specific threats, vulnerabilities, and adversaries of your organization. This does not mean that a detailed analysis is necessary to get started improving your digital security practices. Many small U.S. organizations face a shared set of baseline threats and vulnerabilities due to a common reliance on the same systems and technologies and similar operating conditions. These documents are meant to help them address the risks associated with these common needs as a first step of improving their security stances.
 
-All security practices require a **strong organizational commitment**, as they dictate changes to how you and your team work together, in addition to demanding ongoing attention to ensure that software and practices are regularly updated and working properly. The more you can understand about the threats your organization faces, the better you can select and commit to practices that will be useful for protecting your organization and its operating environment.
+The adoption of new security practices always requires a **strong organizational commitment** as well as support from **organizational leadership**, because it changes the way you and your team work together. New tools and work flows are disruptive, even as they reduce your risk. It takes ongoing attention to turn policies and procedures into habits and to ensure that secure systems are regularly updated, working properly and free of unexpected activity.  The more you can build awareness about the particular threats your organization faces, the better you can select and commit to practices that will be useful for protecting your organization in its work. The more you can create a culture of learning and mutual support in your organization, the more success you will have in the uptake of secure tools.
 
-We have identified solutions and practices across a range of levels of technical skill and organizational commitment. The effectiveness of these practices to protect from real threats is directly correlated with the level of investment you make in implementing them. With current tools, security measures are nearly always at odds with convenience. The
-more you can understand what actual threats there are to your systems and specific sets of data the more directed (and therefore less impactful to operations) your security practices will be. In this way you assure that the more you put in to securing your systems, the more you will lower your risk of bad outcomes.
+In these checklists we have identified solutions and practices across a range of levels of technical skill and organizational commitment that meet common threats that many, if not all, small organizations face. However, the effectiveness of these practices to protect from real threats is directly correlated with the investment you make in implementing them. Understand that with current tools, security measures are nearly always at odds with convenience. Treat digital security as the important organizational imperative it is by resourcing it appropriately and ensuring someone in your organization is responsible and given time to manage thus ongoing work. Take the time to identify your most sensitive information and communications to prioritize. Provide staff and volunteers the time, support, resources and training needed to adopt any practices you undertake from these lists. In these ways you assure that the more you put in to securing your systems, the more you will lower your risk of bad outcomes.
 
 ## Why digital security checklists?
 
-While computers have revolutionized how non-profits work, the last
-several years have begun to reveal to the general public the many risks
-associated with digital communication and information storage. While all
-organizations want to protect their information—and that of their
-partners and allies—few have a strong understanding of the relevant
-risks and most effective responses. These checklists represent
-recommendations for a set of baseline digital security practices. They
-have been created as a harm reduction step in response to incident
-reports, current research and community feedback about the threats faced
-by non-profits' computer systems.
-
-The public-health concept of harm reduction is a useful approach to any
-situation for which a perfect solution is not available. Despite being
-an incomplete solution, regular hand washing is an important part of
-limiting the risk of getting certain illnesses. Similarly a set of
-standard best practices represented by checklists cannot mitigate all
-risks, yet they can help protect you and your organization from some of
-the serious threats that come with using computers to manage your
-information. These checklists are meant as a starting point in
-understanding and responding to the most basic threats computer users
-face today. They are a necessary first step to secure our movements.
-They are not sufficient for those of us working in extremely hostile
-environments, for instance against highly repressive regimes and in
-risky areas like conflict journalism; in no case should they be a
-substitute for a more aggressive security response where warranted.
+While computers have revolutionized how non-profits work, the last several years have begun to reveal to the general public the many risks associated with digital communication and information storage. While all organizations want to protect their information—and that of their partners and allies—few have a strong understanding of the relevant risks and most effective responses. These checklists represent recommendations for a set of baseline digital security practices. They have been created as a harm reduction and capacity building step in response to experiential knowledge of the shared technical operations of small organizations in addition to incident reports, emerging standards, current research and community feedback about the threats faced by non-profits' computer systems. The aim is to help organizations improve digital security levels, and avoid common incidents and their costs and disruption, so that space can be made for deeper analysis and organizational security efforts. In the process organizations get to build their "security practice muscles" by building new, constrained habits and practices. Building this capacity is critical to taking on more advanced or disruptive security measures as the threat landscape changes.
+
+The public-health concept of harm reduction is a useful approach to any situation for which a perfect solution is not available. Despite being an incomplete solution, regular hand washing is an important part of limiting the risk of getting certain illnesses. Similarly a set of standard best practices represented by checklists cannot mitigate all risks, yet they can help protect you and your organization from some of the serious threats that come with using computers to manage your information. These checklists are meant as a starting point in understanding and responding to the most basic threats computer users face today. They are a necessary first step to secure our movements. They are not sufficient for those of us working in extremely hostile environments, for instance against highly repressive regimes and in risky areas like conflict journalism; in no case should they be a substitute for a more aggressive security response where significant risks of bodily harm, long term detention and death exist.
 
 ## What these checklists are not (and cannot be)
 
-Effective security is an ongoing process. It requires consistent
-practices to be undertaken by all staff, periodic review and adjustment
-to practices, and strong leadership from board and senior staff. Every
-organization faces a specific set of threats to its information, some of
-which may be completely outside the digital realm (e.g., infiltration of
-organizing meetings by a political adversary). As no set of checklists
-can address all situations, these checklists do not represent a complete
-solution for securing your organization.
-
-It is also important to recognize that security and convenience are
-generally at odds. Most security practices, both in the digital realm
-and the “real world,” consist of trade-offs between security and
-efficiency. Following the checklist recommendations will generally not
-make your work smoother and easier. Instead, many will likely create
-some disruption and training needs. In order to make meaningful strides
-in security, your organization must be prepared to make these trade-offs
-whether steep or shallow. These investments in time and attention will
-repay the organization in decreased risk to critical data and systems.
+Effective security is an ongoing process. It requires consistent practices to be undertaken by all staff, periodic review and adjustment to practices, and strong leadership from board and senior staff. Every organization faces a specific set of threats to its information, some of which may be completely outside the digital realm (e.g., infiltration of organizing meetings by a political adversary). As no set of checklists can address all situations, these checklists do not represent a complete solution for securing your organization.
+
+It is also important to recognize that security and convenience are generally at odds. Most security practices, both in the digital realm and the in other aspects of operations consist of trade-offs between security and efficiency. Following the checklist recommendations will generally not make your work smoother and easier. Instead, many will likely create some disruption and training needs. In order to make meaningful strides in security, your organization must be prepared to make these trade-offs whether steep or shallow. These investments in time and attention will repay the organization in decreased risk to critical data and systems.
 
 ## Who these checklists are for
 
-Due to the variety of threats, vulnerabilities, and adversaries that
-arise in different contexts of geopolitics and scale, the
-recommendations in these checklists apply only to organizations meeting
-the following criteria:
-
--   The organization has one or more primary locations in the United
-    States each with an office network that allows staff computers to
-    connect to each other, internal services and the Internet. Each
-    internal network is trusted to be free from outside interference and
-    is segmented from the open Internet or hosting organizations'
-    networks by a firewall device.
-
--   The organization can successfully protect physical access to its
-    office spaces and office network equipment.
-
--   These office networks do not host any websites or other information
-    resources that are meant to accessible to all users on the public
-    Internet (as opposed to resources such as printers and file servers
-    that are available only to users who are connected to the office
-    network).
-
--   The organization uses primarily Windows or Mac computers with some
-    limited use of mobile devices to access its information systems.
-
--   Although the organization may communicate with partners abroad, its
-    staff do not cross international borders while carrying the
-    organization's equipment or data nor regularly work in a foreign
-    country.
-
--   The organization is broadly seeking to protect itself from security
-    threats from non-persistent general adversaries with limited
-    resources (e.g., disgruntled individuals, identity thieves,
-    political opponents, internal threats) rather than the U.S.
-    government, other governments or other large global entities
-    including multinational corporations.
-
-If these assumptions don't apply to you, these recommendations are
-inadequate; a more rigorous information security approach, in
-partnership with a provider of professional security services, is
-strongly recommended. [Contact RoadMap]("mailto:info@roadmapconsulting.org") for help or referrals .
+Due to the variety of threats, vulnerabilities, and adversaries that arise in different contexts of geopolitics and scale, the
+recommendations in these checklists apply only to organizations meeting the following criteria:
+
+-   The organization has one or more primary locations in the United   States. Any office network that allows staff computers to connect to each other, internal services and the Internet is trusted and assumed to be free from outside interference and is segmented from the open Internet or hosting organizations' networks by a well configured firewall device running up-to-date software.
+
+-   The organization can successfully protect physical access to its office spaces and office network equipment.
+
+-   These office networks do not host any websites or other information resources that are meant to accessible to all users on the public Internet (as opposed to resources such as printers and file servers that are available only to users who are connected to the office network).
+
+-   The organization uses primarily Windows or Mac computers with some use of mobile devices to access its information systems.
+
+-   Although the organization may communicate with partners abroad, its staff do not cross international borders while carrying the organization's equipment or data nor regularly work in a foreign country.
+
+-   The organization is broadly seeking to protect itself from security threats from non-persistent general adversaries with limited resources (e.g., disgruntled individuals, identity thieves, political opponents, internal threats) rather than the U.S. government, other governments or other large global entities including multinational corporations.
+
+If these assumptions don't apply to you, these recommendations are inadequate; a more rigorous information security approach, in partnership with a provider of professional security services, is strongly recommended. [Contact RoadMap]("mailto:info@roadmapconsulting.org") or [Information Ecology](https://iecology.org/contact) for help or referrals.
 
 ## How to use these checklists
+The first item in the set is a Digital Security Readiness Assessment Tool. Many foundational technology management and operations tasks underly digital security capacity, or are even digital security tasks themselves. For each item you should honestly grade your organization from 1-10. Organizations that have a total score of 75 on the sheet with no individual item rated under 5 or section subtotal under 25 should feel confident undertaking the rest of these checklists. Otherwise your organization should concentrate first on any areas of very low score and overall on building capacity in these foundational areas before pursuing additional digital security improvements. Continual attention to these foundational capacities is requisite to continue to have success in digital security efforts, so be sure to have a plan to keep improving your organization in these areas.
+
+The items on the rest of these checklists are meant to be actionable and accessible; each checklist item includes a brief explanation of what it means as well as, where possible, next steps for implementation. The icons accompanying each item will help you identify how difficult, disruptive and costly a given step might be to undertake. We recommend pursuing these checklists in the order they are presented in this set, except if you are using a specific platform with a checklist of its own (currently only GSuite) or rely heavily on one of the tools with an associated checklist (public wireless and email as of this writing) in which case you should start there. Select tems that are relevant to your operations and appropriate for the level of technology management resources (as indicated by the :rocket: icon) and technical skill (as indicated by the :wrench: icon) available in your organization. Be aware of the :fire: rating as it indicated disruption so only take on the ones with multiple :fire: icons if you have the space to spend time as an organization absorbing training overhead and work flow transformation.
+
 
-The items on these checklists are meant to be actionable and accessible;
-each checklist item includes a brief explanation of what it means as
-well as, where possible, next steps for implementation. The icons
-accompanying each item will help you identify how difficult, disruptive
-and costly a given step might be to undertake.
-
-The first checklist deals with Digital Security Readiness. If you cannot
-check off the items on that list, your organization should concentrate
-first on building the capacity to address these foundational elements
-before undertaking additional digital security improvements.
-
-***Although these practices are highly recommended they do
-not in and of themselves constitute a successful security practice.
-Information security is an ongoing process of managing risk and no list
-of procedures is an adequate replacement for a thorough review of what
-information you are protecting, why and from whom paired with an
-organizational commitment to shifting operations to mitigate risk.
-Information Ecology, RoadMap Consulting and Common Counsel are not
-liable for negative outcomes associated with following these practices.***
+***Although these practices are highly recommended they do not in and of themselves constitute a successful security practice. Information security is an ongoing process of managing risk and no list of procedures is an adequate replacement for a thorough review of what information you are protecting, why and from whom paired with an organizational commitment to shifting operations to mitigate risk. Information Ecology, RoadMap Consulting and Common Counsel are not liable for negative outcomes associated with following these practices.***
diff --git a/2_readiness_assessment.md b/2_readiness_assessment_tool.md
similarity index 66%
rename from 2_readiness_assessment.md
rename to 2_readiness_assessment_tool.md
index fdeab63..d2a6681 100644
--- a/2_readiness_assessment.md
+++ b/2_readiness_assessment_tool.md
@@ -1,63 +1,73 @@
 ---
-document set: DIGITAL SECURITY CHECKLISTS FOR U.S. NON-PROFITS
+document set: DRAFT DIGITAL SECURITY CHECKLISTS FOR U.S. NON-PROFITS
 title: Digital Security Readiness Assessment Tool
 author: Jonah Silas Sheridan, Lisa Jervis for Information Ecology
-last modified: 5/12/2017
-version: "1.1, INTERNALLY REVIEWED VERSION FOR PUBLIC USE"
+last modified: 9/2/17
+version: "2.0, DRAFT NOT FOR FOR PUBLIC USE"
 ---
 
 # Digital Security Readiness Assessment Tool
 ## Introduction
-This assessment tool contains a list of baseline, ongoing information systems and technology practices that it is recommended your organization already have in place in order to successfully take on a digital security initiative. If you cannot check off more than 75% of the items in the list below, it is recommended you focus on meeting these baselines before proceeding with other digital security work. Even if at 75% or above, be sure to note the unmarked items and make plans to implement them as soon as possible, as not doing so will likely undermine your security efforts.
+This assessment tool is meant to help identify organizations where their most critical security needs lie in their . Many common information systems and technology practices are oriented around providing or supporting security outcomes. Because of that, organizations that have foundational technology capacity issues are best served by putting energy securing existing assets before taking on new security initiatives.
+
+Score each item in the list below from 1-10 for how well your organization meets that description. For each section, fill out the subtotal field at the end. Add up these subtotals to give your self a Total Score in the space for that at the end of this document.
+
+If your total score is lower than 75, any subtotal lower than 25 or any individual item lower than 5, it is recommended you focus on meeting these baselines before proceeding with other digital security work, starting from the place of lowest score. Even if at or above the thresholds indicated, be sure to note the places you have low individual or section scores and talk with your leadership and technology responsible staff to make plans to improve them as soon as possible. Not continually addressing these foundational capacities will likely undermine your security efforts over time.
 
 ## Cultural Hallmarks for Security Success
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have a culture of training and learning, including strong technology training and follow up as part of new staff orientation procedures.**  
+Score: ____ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have a culture of training and learning, including strong technology training and follow up as part of new staff orientation procedures.**  
 *New tools and practices demand end-user training. If your organization doesn't have established practices around training--when new people are hired, when refresher trainings are needed, and when important processes change--implementing improved and possibly complex secure practices is nearly impossible. Beginning with documentation and training for new hires is a wise first step in this area. Following up with new employees at 30-day intervals will ensure they continue to get the support they need to do their work effectively and securely. When a new process is introduced, it is like everyone in your organization is new to it, so initial training with similar follow-up is recommended.*
 
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have a common and clearly communicated set of information systems that are administered by the organization and used with defined processes; ensure that all staff follow these processes effectively and are not using other systems for their work.**
+Score: ____ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have a common and clearly communicated set of information systems that are administered by the organization and used with defined processes; ensure that all staff follow these processes effectively and are not using other systems for their work.**
 *If your staff are using personal file-sharing, email, task management, or other accounts without knowledge or guidance from the organization, not only will your efficiency suffer but the environment becomes impractical to secure. How can you protect things you have no access to at an administrative level or, worse yet, don't even know are in use? A good place to start figuring this out if by making an inventory, collaboratively with all staff, of all the places that your information is currently stored.*
 
 *An important way this issue shows up in your organization is the use of cloud services. While many organizations use their personal accounts on those systems, official organizational accounts are vastly preferable. If your organization is a registered US 501c3 non-profit, most cloud providers provide licenses for their applications for free or reduced cost, providing you significant capacity to centrally manage, back up, and monitor your information at a low cost.*
 
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have technology champions at all levels of the organization, especially leadership, and strong supervisory support and participation in systems adoption.**
+Score: ____ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have technology champions at all levels of the organization, especially leadership, and strong supervisory support and participation in systems adoption.**
 *Leadership for technology and operations within your organization can and should come from all levels. Junior staff and younger "digital natives" on staff often use or are open to using more technology in their work so can be motivated to participate in the planning and deployment of information systems and promote uptake among peers. Of course demonstrations of support for and engagement with technology initiatives from management are also powerful motivators for staff. Visible participation by executive leadership in training on and use of official organizational tools is a powerful modeling of preferred behavior and critical to changing organizational habits and culture.*
 
-
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have a complete policy set describing employees' responsibilities and limitations on their facilities, hardware, and information systems use.**
+Score: ____ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have a complete policy set describing employees' responsibilities and limitations on their facilities, hardware, and information systems use.**
 *Legal and operating risk due to inconsistent expectations and behavior can hamper even the most well-designed security plan. Managing your risk, employee awareness, and compliance through a strong set of workplace policies around technology but also more generally will set you up for security initiative success.*
 
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Develop and evaluate baseline non-technical security practices in an ongoing way**
+Score: ____ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Develop and evaluate baseline non-technical security practices in an ongoing way**
 *If you do not control your office space and access to your computers, your other digital security steps can be easily circumvented by walking into your office. Rotate alarm system codes, door codes, wireless network passwords, and other access mechanisms (for example, emergency building access plans) when staff leave the organization. Sophisticated attackers can gain full control of a computer or network with even a short period of physical access to your space or digital access to unsecured systems. More importantly, non-technical security practices help build healthy habits and a culture of security in your organization.*
 
+Subtotal, Cultural Hallmarks: ____
+
 ## Information Technology Operations that Support Security Outcomes
 
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have a recurrent line item for technology in your budget**  
+Score: ____ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have a recurrent line item for technology in your budget**  
 *Security is an ongoing process and will require regular investments in computer equipment and software to be effective. Work with your technical support provider to determine an appropriate amount to put into this line item.*
 
-
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have regular and adequate technical support provided either by staff assigned via job description or contracted with outside agencies.**  
+Score: ____ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have regular and adequate technical support provided either by staff assigned via job description or contracted with outside agencies.**  
 *If your existing hardware and software are not well supported, introducing new tools and practices will likely meet with significant barriers, as new technologies and tools often demand significant ongoing technical support for proper setup and functioning. Your tech support providers are central to your ability to identify and protect your systems from attack, work they can't do if they don't exist. There are as many ways to obtain technical support as there are organizations. Talking to peer organizations in your area is a good way to find quality help.*
 
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Regardless of technical support solution, have someone on staff assigned via job description to be responsible for technical operations, including managing technical support providers and systems upgrades.**  
+Score: ____ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Regardless of technical support solution, have someone on staff assigned via job description to be responsible for technical operations, including managing technical support providers and systems upgrades.**  
 *No matter how you get your technical support needs, someone needs to have time and responsibility to manage the flow of ongoing support requests, to act as a point person for vendors and consultants, and to lead projects to improve infrastructure. Although this is critical when sourcing technical support services from outside of staff to ensure your organization is owning its own operations, it is perhaps even more important when assigning technical support responsibilities to someone on staff. If internal tech support doesn't have explicit time to put into systems changes and vendor management and can only spend time fixing broken hardware and software systems, your digital security initiatives will suffer from a lack of attention.*
 
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Provide relatively new and adequately powered computers to all staff.**  
+Score: ____ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Provide relatively new and adequately powered computers to all staff.**  
 *Industry standard best practice is to replace laptops and desktops every 3 to 5 years. Encryption tools use a lot of power and can bring older, inadequately powered computers to a near halt, making some security steps untenable for staff. Money for replacing 1/3 to 1/5 of your computers each year should be part of your recurring technology budgeting.*
 
+Subtotal, Technical Operations: ____
+
 ## Digital Security Baseline Capacities
 
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have a process for properly onboarding and offboarding staff and volunteers that includes attention to your information systems.**
+Score: ____ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have a process for properly onboarding and offboarding staff and volunteers that includes attention to your information systems.**
 *The expansion or contraction of your team is a critical change in your security context, and so is an important moment to institute strong security measures. Your onboarding process should include detailed steps for the creation of accounts and instructions on how to determine and grant the correct and minimum permissions needed for that person's role. When a staff member or volunteer departs, ensure that any of the organization's data that is on their personal or work devices is copied and/or destroyed as necessary. Also at offboarding, all individual accounts belonging to the outgoing person should be deleted and any organizational passwords that they used or accessed in their work should be changed to something new.*
 
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Make sure the computers and other devices you use, including personal devices that staff may use to access organizational information, are only running the programs you expect them to by detecting and removing malware, viruses, or other intrusive software.**  
+Score: ____ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Make sure the computers and other devices you use, including personal devices that staff may use to access organizational information, are only running the programs you expect them to by detecting and removing malware, viruses, or other intrusive software.**  
 *As a digital security first step, ensure you are running antivirus software on all computers. Antivirus software for Macs and Windows computers is available to non-profits at a discounted rate through [Tech Soup](http://techsoup.org). If you haven't been running antivirus software or otherwise aren't sure about the status of your devices, you can have the operating system (OS) on them reinstalled to help guarantee the computers are free of malware and viruses. This is one benefit of adopting "cloud"-based tools for your organization's information, in that your data is readily available on a freshly installed system.*
 
 *When reinstalling, use a copy from the OS provider wherever possible. Computer manufacturers often bundle other software in their installs, which may impact privacy and security but may also contain specific tools for the hardware (especially in laptops).*
 
 *Note that there are other ways in which your devices can be compromised at a level underneath the operating system; this cannot be remedied by an OS reinstall. If your computers have been handled by third parties you don't trust or out of your possession in a hostile environment, or if you suspect intrusion by powerful or well-resourced entities, get a new computer and call a security professional.*
 
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Minimize or eliminate the use of shared accounts where more than one person, especially less-vetted parties like volunteers, can log in to your systems using the same credentials.**
+Score: ____ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Minimize or eliminate the use of shared accounts where more than one person, especially less-vetted parties like volunteers, can log in to your systems using the same credentials.**
 *While in the short term sharing accounts and login information can be expedient and lower licensing fees, the long-term ability to monitor and control access is more important to security outcomes. In addition, the disruption and security concerns caused by changing a broadly used password and sharing it around are potential costs that shouldn't be ignored. Sophisticated systems like GSuite or Office365 allow for "account delegation," where two people can share an account using their own distinct login credentials; this is a better way to solve these challenges than account sharing.*
 
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have a disaster recovery plan that includes making and testing regular backups of organizational data that are stored away from your main office site. Backup drives should be at a minimum stored in a physically secure location like a locking file cabinet or safety deposit box, and ideally encrypted so that only you can access them. Do not rely exclusively on third parties to back up and hold your information.**  
+Score: ____ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have a disaster recovery plan that includes making and testing regular backups of organizational data that are stored away from your main office site. Backup drives should be at a minimum stored in a physically secure location like a locking file cabinet or safety deposit box, and ideally encrypted so that only you can access them. Do not rely exclusively on third parties to back up and hold your information.**  
 *This digital security practice is a straightforward way to protect yourself from a whole host of events that could compromise your information's integrity or cause you to lose access to it; it is so critical that it needs to come before any other digital security steps. Talk to your technical support provider about the status of your backups and when restoring data from them they was last tested. Refer to [this guide](http://www.techsoup.org/disaster-planning-and-recovery) and/or [this webinar](http://www.communityit.com/resources/webinar-february-18-2016-backups-and-disaster-recovery-for-nonprofits/) for ideas on how to improve your disaster preparedness.*
+
+Subtotal, Baseline Capacities: ____
+
+Total Score (add up all subtotals): ____
diff --git a/3_legend.md b/3_legend.md
index 64c4fd6..2d79eb9 100644
--- a/3_legend.md
+++ b/3_legend.md
@@ -2,20 +2,20 @@
 document set: DIGITAL SECURITY CHECKLISTS FOR U.S. NON-PROFITS
 title: Legend
 author: Jonah Silas Sheridan, Lisa Jervis
-last modified: 11/18/2015
-version: "1.0, PEER REVIEWED VERSION FOR PUBLIC USE"
+last modified: 9/2/17
+version: "2.0, DRAFT NOT FOR FOR PUBLIC USE"
 ---
 # Legend
 ## What The Icons In These Documents Mean
 
 ## :heavy_check_mark:  
-This check mark icon flags places for you to record actions you have taken. Check them off as you go!
+This check mark icon flags places for you to record actions you have taken. Cross them off or circle them as you go.
 
 ## :rocket:  
-This rocket icon represents the overall difficulty rating for a checklist item. One star items should be doable by most technology capable organizations. Items with two stars may require some outside assistance and work flow shifts. Three stars will require significant organizational commitment of resources and technical assistance. Items with four stars are only for organizations ready to take on advanced security practices, including the ongoing commitment of human and other resources needed to make them effective.
+This rocket icon represents the amount of technology management overhead required to implementation the item, in terms of the attention of technology responsible and leadership staff inside an organization. One star items should be doable by most technology capable organizations that achievs other basic technology competency. Items with two stars may require additional time carved out beyond what regular operations demand, as they possibly require some outside assistance and work flow shifts. Three stars will require significant organizational commitment of resources to manage the project of implementing the recommendation, for support of renewed work flows, and to interface with technical assistance. Items with four stars are only for organizations ready to take on advanced security practices, including a part-to-full time dedicated project manager as well as the ongoing commitment of human and other resources needed for process management, technical configuration, training, and ongoing support.
 
 ## :wrench:    
-This wrench icon represents the amount of technical skill needed to undertake the practice. One set of tools means most skilled computer users can do, or be trained to do, the task. Two wrenches require “power user” technical skills, often found in the “Accidental Techie” on staff. Three wrenches will require a technical support person to do the work. Four wrenches means you will need a technical support person with significant skills in networking or security to undertake the practice.
+This wrench icon represents the amount of technical skill needed to undertake the practice. One set of tools means most skilled computer users can do, or be trained to do, the task. Two wrenches require “power user” technical skills, often found in the “Accidental Techie” on staff. Three wrenches will require a person experienced in technical support or systems administration to do the work. Four wrenches means you will need a technical support person or internal staffer with significant skills in networking or security to undertake the practice.
 
 ## :fire:  
 This flame icon represents the amount of work flow disruption taking on this task entails, and consequently how much staff time for documentation, training and work shifts is required. One flame items will be mostly innocuous and staff can be trained in a brief session. Two flames means the practice will require more training and can disrupt existing work flows dramatically. Three flames signals that significant work flow shifts and training will be required to undertake the practice. Four flames means the task will disrupt work flow completely and is only for organizations where security is of far greater importance than efficiency or convenience.
diff --git a/4_device_security_checklist.md b/4_device_security_checklist.md
new file mode 100644
index 0000000..6522953
--- /dev/null
+++ b/4_device_security_checklist.md
@@ -0,0 +1,74 @@
+---
+document set: DRAFT DIGITAL SECURITY CHECKLISTS FOR U.S. NON-PROFITS
+title: Endpoint Device Security Checklist
+author: Jonah Silas Sheridan, Lisa Jervis for Information Ecology
+last modified: 8/7/17
+version: "2.0 DRAFT NOT FOR FOR PUBLIC USE"
+---
+
+# Endpoint Device Security Checklist
+## Introduction
+
+Securing your computing devices or "endpoints" (meaning that they are one end of all connections you make to a website, online service or another person) are a cornerstone of digital security. Often trainers, security practitioners and the documents and manuals they use assume that your devices are secure from intrusion and not running any programs that you don't expect. This assumption is critical because anyone who can control your endpoints can see and control all the same information you can -- and so any protections of that information as it travels across internal networks or the open Internet are rendered irrelevant.
+
+Unfortunately, in practice, this assumption does not meet the operating reality of many non-profits and activists. Especially with the increased use of encryption technologies to secure communications and other sensitive information, attacks on the hardware in devices themselves and the software they run on them has become attractive strategy for obtaining or altering data than in the past. Coupled with the fact that many devices are shipped with tracking, advertising or other software that you may not expect or that may expose your device to risks, putting time into securing your devices is a critical task for securing your organization.
+
+This checklist provides a number of practices that can help you protect your devices from being a threat to the confidentiality, availability or integrity of your information. By implementing at a minimum these practices, you can better trust that any other secure systems or services your organization adopts are protecting you as expected. These are meant to be applicable to computers, phones, tablets except where otherwise indicated.
+
+**These practices do not constitute a complete set of endpoint protection activities and are especially ill suited at protecting you from targeted attacks on by well resourced and persistent organizations or entities. They will not fully protect you from losing physical control of your devices, or a technically capable group having physical access to your device such as may happen at an international border, in an arrest or detention situation or through theft. If your threat model includes these sorts of concerns, contact a digital security professional to help you build systems that will remain resilient to your specific context.**
+
+
+## Key
+:heavy_check_mark: Record actions  
+:rocket: Implementation management overhead rating   
+:wrench: Technical skill level required
+:fire: Work flow disruption for staff## General Endpoint Security Tasks
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Keep your devices in your control, always.**
+:rocket::wrench::fire::fire::fire:
+*The easiest way to attack someone's devices is to gain physical control of them. Consequently the most important practice you can follow to protect them is to keep them in your control at all times. In your control means you know where they are and can ensure that nobody is accessing them without your permission. Note that a hotel room desk drawer or even hotel safe does not meet this standard as both can usually be accessed by hotel staff such as cleaners or management. When working in a public place, don't leave your computer even for a couple of minutes. This can be inconvenient but ensures nobody can surreptitiously install software on or hardware in, your computer without you knowing.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Run the updating tool for your operating system and applications regularly and/or set updates to run automatically.**
+:rocket::wrench::fire::fire:
+*The operating system of a device is the most basic software it can run and every other program or application depends on it. Operating systems are often tied to specific hardware and major examples include Microsoft Windows, Apple's OSX (for computers) and iOS (for iPhones and iPads), Android, ChromeOS (for Chromebooks) and Linux. Anytime an operating system manufacturer or application creator provides an update that fixes a security vulnerability, you are at increased risk until you install that update since any bad actors have learned about it. Setting updates to run automatically will help, but you should still manually start the update process if you read or hear of a specific security issue with any of your software. Note that if you have specific software requirements or custom software created especially for your organization, automatic updates can cause work disruption and this recommendation must be vetted by your IT team or tech support provider.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Use built in full disk encryption on your devices and shut them down when not in use or at risk of loss.**
+:rocket::wrench::fire::fire:
+*Full disk encryption means that the contents of the storage inside your device -- the operating system, programs you have installed and your organizational data -- are scrambled in a way that they cannot be easily accessed when the computer isn't running and the contents unlocked. Without this feature, someone who steals your device, finds your lost device or otherwise accesses your hardware can easily read your files and possibly impersonate you to your systems. Full disk encryption is strongest when your computer is turned off.*
+*Although full disk encryption is increasingly enabled by default on mobile devices, it isn't on all platforms so must be manually setup. This feature is called Bitlocker on Windows, Filevault on OSX and LUKS on Linux. On Android devices you can turn on this feature in the Security section of Settings menu. Chromebooks and iOS devices have encryption enabled by default. This recommendation is best coupled with the following recommendations regarding device authentication and locking to make sure the encryption cannot be easily bypassed.*
+*It is important to know that full disk encryption requires your device to do complex math so turning this feature on will make your device work harder and may make older devices unreasonably slow to use. Full disk encryption will increase the risk of losing access to some of your information as a lost password or pin will generally mean you (as well as anyone else) cannot recover your data. Ensure you use syncing services and/or have regular backups of your data to minimize this risk.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Use a strong password or long pin code on your device, set your device to lock itself after a short period and manually lock the device if walking away from it. Be aware of your surroundings when entering this code or password to ensure someone isn't watching or your movements aren't being recorded on camera.**
+:rocket::wrench::fire::fire::fire:
+*Always setup a long (8 numbers or more) pin code or complex password to login to your device to ensure that a lost or stolen device remains locked down. Use the screen timeout feature of your device and require your password or pin to wake it back up to ensure that your information and your accounts are protected even if the device is found while turned on. The shorter the screen timeout period, the shorter the amount of time your device is vulnerable so choose as small a time as you can while still being able to do your work. If stepping away from a device, manually lock the screen. Nearly every operating system has a keyboard shortcut or other quick way to lock a device, which you can lookup in its documentation or can ask your technical support provider about. Be aware when entering a pin or password in public spaces to be sure nobody malicious is watching and that your keystrokes are not being recorded on camera. While biometric (fingerprints, facial recognition, etc.) unlocking mechanisms, swipe patterns and other locking mechanisms are becoming more common they can still be bypassed more easily than codes and passwords so are not yet recommended.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Run antivirus, ad blocking and anti-malware software on your devices.**
+:rocket::wrench::wrench::wrench::fire::fire:
+*Antivirus and anti-malware software are programs that run on your computer and scan all files coming in r out for files that are known to infect, steal data from or otherwise abuse your computer or data without your consent. While these tools only work against software already created, identified and added to their lists of what to scan for, a large amount of intrusions rely on these well known threats. However this software by its very nature has to have access to all the files on your computer and so can themselves be a vector of intrusion. For this reason, you are best off with software made by a well known manufacturer and vetted by your technical support provider. Don't trust "free" or "no cost" virus or malware scanning software, especially any that appears in a pop up advertisement in your web browser or on a computer or device, as it often is a cover for a virus itself. TechSoup offers low cost [Symantec](http://www.techsoup.org/symantec-catalog) and [Bitdefender](http://www.techsoup.org/bitdefender) antivirus software to most non-profit organizations. Nothe that this scanning takes power from your device's processor to work, often a fair bit of it,, so if it is already slow this may make your device unusable at times.
+* Ad blocking will keep advertisements from loading on your web browser or device. Because of the complexity of modern ads, they can be vectors of attack, so you are safer blocking them entirely. This is worth running no matter what as removing advertisements should also improve your device performance since it won't use your network connection to load, or use your process to run, all of that often fancy (and insecure) content.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Paint any exposed screws on your devices with sparkly nail polish or other paint that cannot be easily removed and replaced without notice. Whenever possible, put tamper revealing tape across places where devices open. Keep photographs accessible from someplace besides that device of how it appeared before leaving it unsecured anywhere.**
+:rocket::wrench::wrench::fire::fire::fire:
+*Although the idea of painting your computer or device with nail polish or covering it with tape may seem silly, this will allow you to ensure that, if lost or otherwise out of your control, that your device was not tampered with. The reason this is listed as difficult is that you will need to both remember to check these details after your device has been away from you. You will also be better off with a photograph (stored someplace you can get to even without your devices turned on) to help you ensure that nothing has changed about the device when it was out of your control.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Be exceptionally careful about what software you install on your computers and mobile devices.**
+:rocket::rocket::wrench::wrench::fire::fire::fire:
+*The proliferation of mobile apps, browser extensions and other "free" (as in zero cost, not open source) programs has caused numerous security problems. Avoid software that hasn't been created by a company you already have a trust relationship with (such as Google or Slack, if you use their tools internally). Software that appears to have good intentions (like antivirus scanning) or even beneficial features may be masking malicious activities in the background.*
+
+## Laptop and Desktop Computer Security Tasks
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Carefully source your USB and memory card devices, only plugging trusted and personally sourced ones into your computer.**
+:rocket::wrench::fire::fire::fire:
+*Don't plug other people's USB devices and memory cards such as flash drives, hard drives and phones into your computer, or any such devices that came to you in anything besides verifiable original packaging. This recommendation is especially important in regards to devices from unknown or untrusted sources (leaving USB sticks around an office is a classic intrusion technique) but also applies to any other devices, even if you trust the owner, as your trust in the person is not the same as trusting the devices they use. These devices can silently infect your computer in ways that are very hard to detect. Passing through trusted organizational systems, especially those that do virus scanning. Certain cloud services, including Google Drive and Box (but not Dropbox) automatically scan files (under 25MB for Google Drive) for viruses and will alert you if your files are infected. In this case a loss of some privacy to the third party provider may be worth the trade off of passing files through a sanitizing process.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; **Add a privacy filter to your computer's screen.**
+:rocket::wrench::fire::fire:
+*One of the easiest ways to accidentally leak information is for someone in a public place to see it on your screen. Purchasing and installing privacy filters (basically a piece of plastic that allows what is on your computer to be seen only by the person sitting right in front of it) on your computers -- especially for people that work frequently in cafes, coworking spaces or airplanes will protect you from this threat. Be aware that if you frequently share information by showing your actual laptop screen to others (as opposed to connecting your laptop to a projector or other display) this may cause you some disruption.*
+
+## Mobile Phone & Tablet Security Tasks
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Don't click links sent to you by SMS or other text message, especially from unknown parties.**
+:rocket::wrench::fire::fire:
+*There is rarely a reason to send links in this way and yet we continue to see situations where mobile devices are compromised through incoming links sent by text message (which can include not just by SMS text messages but by also messages from any instant messaging application that allows anyone who knows your number to send you a message.) The link may display what looks like a legitimate page, but could be installing malicious software in the background. If you absolutely need to click a link sent in this way, verify with the sender by phone or video call that the link you see is what they sent you.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Use either a charge only cable or a "USB condom" between to charge your device from anything other than a wall charger. Carry a backup battery to ensure you never have to charge your device from an untrusted source.**
+:rocket::wrench::wrench::fire::fire::fire:
+*Almost all modern professionals have been there: your mobile phone or tablet is dead and the only place to charge it is a random computer or device, whether a friend's laptop, an internet connected device or a public computer. Unfortunately that computer or device can become a route for virus or other malicious software infection to enter into your device. You can purchase a "USB condom" or charge only USB cable that disconnects the wires that are used for data transfer to be able to safely connect your device to any USB port you come across. Alternatively, and often easier, you can carry a USB enabled backup battery so you can always charge your device on the go. Just be sure to source and manage that battery as well (charging it from the wall or your main computer) so it isn't also a threat to your computer.*
diff --git a/5_authentication_checklist.md b/5_authentication_checklist.md
index 4c46e14..dcd3524 100644
--- a/5_authentication_checklist.md
+++ b/5_authentication_checklist.md
@@ -2,8 +2,8 @@
 document set: DIGITAL SECURITY CHECKLISTS FOR U.S. NON-PROFITS
 title: Password and Authentication Safety Checklist
 author: Jonah Silas Sheridan, Lisa Jervis
-version: "1.0, PEER REVIEWED VERSION FOR PUBLIC USE"
-last modified: 11/18/2015
+version: "2.0, DRAFT NOT FOR FOR PUBLIC USE"
+last modified: 9/2/17
 ---
 
 # Password and Authentication Safety Checklist
@@ -16,19 +16,19 @@ In the recommendations below, the term “organizational” is used to identify
 
 ## Key
 :heavy_check_mark: Record actions  
-:rocket: Difficulty rating   
-:wrench: Technical skill level  
-:fire: Work flow disruption  
-
-## Password and Authentication Safety Tasks
+:rocket: Implementation management overhead rating   
+:wrench: Technical skill level required
+:fire: Work flow disruption for staff
+## Password and Authentication Security
 
 :heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Use strong passwords for all accounts, organizational and everyday**  
 :rocket::wrench::fire:   
 *Strong passwords are generally longer that 8 characters, use a mix of symbols, numbers and both upper and lowercase letters, and do not include any dictionary words or personal information.*   
 
-*There are many ways to generate strong passwords. There is an online guide to creating passwords as part of the the excellent [Security In a Box website]("https://securityinabox.org/en/guide/passwords"). Most password managers will also make a random password for you, as will other available software for that specific purpose.*
+*There are many ways to generate strong passwords. There is an online guide to creating passwords as part of the the excellent [Security In a Box website]("https://securityinabox.org/en/guide/passwords"). Most password managers will also make a random password for you, as will other available software for that specific purpose. [Diceware]("http://world.std.com/~reinhold/diceware.html") is a fun and effective scheme for creating random yet memorable passwords using everyday objects and a word list.*
 
-*[Diceware]("http://world.std.com/~reinhold/diceware.html") is a fun and effective scheme for creating random passwords using everyday objects and a word list. If you trust a service's password reset process and it uses an email address that you are certain you will control in the future you can make and immediately forget a long random password for a site you seldom use or will never use again.*
+*If you never store a password, it can never get stolen from you. Most service providers allow you to reset a password by sending you an email. For any software or system where you register with an email address you are sure you will control in the future and to which you won't need immediate access, you can make and immediately forget a long random password and just use the reset process when you need to login again.*
+Protects you from;
 
 :heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Don't use the same password for more than one site or service**  
 :rocket::wrench::fire::fire:   
@@ -49,6 +49,13 @@ on the provider to protect your most important secret.*
 
 *The next time you need to login to that service you can hit the “forgot password link” to get a login link and repeat the process. This is a little slower , perhaps, than a stored password but the benefit is that you will never leak your password for that tool – because you don't know it! Of course you wouldn't do this with an account you use all the time or where the password reset process is difficult or uses an email address you may not always have access to - but it is useful to ease the password management load. Recognize that this reduces the security of the account using a “single use” password to the security of the associated email account (since you use that to get back into the service) so that email account's password needs to be strong and memorable.*
 
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Where you can, implement two factor authentication using a method other than text messaging as your second factor.**  
+:rocket::rocket::wrench::wrench::fire::fire::fire:
+
+*Many service providers have begun to offer login systems that rely on more that one piece of information to identify a user. Users will have to get used to having this extra step to login to new devices, but it protects from someone who obtains either item from getting into the account and makes it safer to have an less complex password. There can be several items used for authentication, but usually there are just two; your password and another code or device you have. Often this is a code generated by a program, such as Google Authenticator (which can be used with all sorts of accounts), that runs on your computer or phone or sent by text message.  Be aware that cell phone based authentication factors (whether text message or program based) require a working phone so if adopting them you may wish to also provide staff with backup batteries to assure they can always login to their accounts even on days with heavy telephone use. In some cases where login is only occasional a piece of paper with preprinted backup codes may suffice but then you need to protect that paper carefully.*
+*A newer, and very strong 2nd factor can is a code embedded on a special type of USB device also known as a "Universal 2nd Factor" (U2F) such as a the Yubikey (https://www.yubico.com). Not having a dependency on a working phone or cell signal is one of many advantages of U2F devices such as as the Yubikey, but as of the latest update to this document in Fall 2017, there are still relatively few services that support such U2F capable devices. Major services your organization may use that support U2F keys include Dashlane, Dropbox, Facebook, Google and Salesforce. You can read more about U2F at https://www.yubico.com/solutions/fido-u2f/.*
+***Text message based codes are not recommended as they have proven to be vulnerable to hijacking by malicious parties who can convince your cell phone provider to redirect your text messages*** *Instead adopt one of the other mechanisms above to secure your accounts.*
+
 :heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Have all staff use password manager software**  
 :rocket::rocket::wrench::wrench::fire::fire::fire:    
 *There are many passwords associated with modern work flows. Because they could be used to disrupt your work in various ways passwords need to be protected. They shouldn't be stored in spreadsheets, text files or word processor documents (even password protected ones as they are simple to break open).*
@@ -69,5 +76,4 @@ administrative control of your organization's information systems or online iden
 
 :heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Set minimum password lengths and enforce complexity rules on services where you can do so, and regularly monitor user password strength.**  
 :rocket::rocket::rocket::rocket::wrench::wrench::wrench::wrench::fire::fire::fire:   
-*On many platforms including Windows Active Directory and Google Apps you can set controls at an administrative level to ensure people use strong passwords. It takes some advance planning and staff training, as setting up these controls without being clear on the implications can
-lock people out of their computers or work files . In addition, someone will need to be designated as the point person for resolving problems that arise from these controls. This step does however improve the security of all users at one time so is highly recommended.*
+*On many platforms including Windows Active Directory and Google Apps you can set controls at an administrative level to ensure people use strong passwords. It takes some advance planning and staff training, as setting up these controls without being clear on the implications can confuse users and lock people out of their computers or work files . In addition, someone will need to be designated as the point person for resolving problems that arise from these controls. This step does however improve the security of all users at one time so is highly recommended.*
diff --git a/6_public_wireless_checklist.md b/6_public_wireless_checklist.md
index 953c3f9..f2fca7f 100644
--- a/6_public_wireless_checklist.md
+++ b/6_public_wireless_checklist.md
@@ -2,8 +2,8 @@
 document set: DIGITAL SECURITY CHECKLISTS FOR U.S. NON-PROFITS
 title: Password and Authentication Safety Checklist
 author: Jonah Silas Sheridan, Lisa Jervis
-last modified: 11/18/2015
-version: "1.0, PEER REVIEWED VERSION FOR PUBLIC USE"
+last modified: 9/2/17
+version: "2.0, DRAFT NOT FOR FOR PUBLIC USE"
 ---
 
 # Public Wireless Network Safety Checklist
@@ -13,15 +13,14 @@ This checklist provides a number or practices that can help protect you and your
 
 **If performing work using sensitive or confidential information including that required to be protected by law (such as personal health information) you are best off avoiding the use of public networks for those tasks.**
 
-**Key:**  
+## Key
 :heavy_check_mark: Record actions  
-:rocket: Difficulty rating   
-:wrench: Technical skill level  
-:fire: Work flow disruption  
-
+:rocket: Implementation management overhead rating   
+:wrench: Technical skill level required
+:fire: Work flow disruption for staff
 ## Public Wireless Network Safety Tasks
 
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Keep all web browser software, including extensions, updated to the latest version. Prefer Firefox or Chrome browsers. Only use Internet Explorer and Safari when required.**  
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Prefer Firefox or Chrome browsers. Only use Internet Explorer and Safari when required. Keep all web browser software, including extensions, updated to the latest version.**  
 :rocket::wrench::fire:  
 *Internet Explorer has had a much higher incidence of vulnerabilities than Chrome and Firefox while Safari has suffered some recent security concerns. Although nearly all of the latest browsers support “certificate pinning” which makes it harder to intercept secure connections, [Chrome]("https://google.com/chrome") and [Firefox]("https://getfirefox.com/") have led the development of this important feature.*
 
@@ -40,16 +39,7 @@ This checklist provides a number or practices that can help protect you and your
 :heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Prefer wireless networks that use a password, ideally a unique one for each person connecting, and preferably using WPA or WPA2 encryption rather than WEP encryption.**  
 :rocket::wrench::fire:  
 
-*A password on a wireless network means the information moving across it
-is less easily captured and decoded by someone nearby. If everyone has a
-unique password this gets even harder. WPA and WPA2 offer stronger
-protection than WEP, which is now relatively easily compromised. You can
-easily view what encryption is in use on most computers. In OSX, hold
-down the Option key and click the wireless indicator in the top right
-corner to reveal extra information about each wireless network. The
-method for viewing these details is different in each version of Windows
-so ask your tech support provider for assistance for the software you
-use..*
+*A password on a wireless network means the information moving across it is less easily captured and decoded by someone nearby. However in most cases everyone with that password can at least see some parts of your network connections so if everyone has a unique password this becomes quite hard to do. WPA and WPA2 offer stronger protection than WEP, which is now relatively easily compromised. You can easily view what encryption is in use on most computers. In OSX, hold down the Option key and click the wireless indicator in the top right corner to reveal extra information about each wireless network. The method for viewing these details is different in each version of Windows so ask your tech support provider for assistance for the software you use.*
 
 :heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Confirm the network details before you connect.**  
 :rocket::rocket::wrench::fire:  
@@ -58,30 +48,29 @@ use..*
 
 :heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Turn off the built-in file sharing functionality on your computer or device**  
 :rocket::wrench::fire::fire:  
-*Although handy for sharing files with peers, the built-in file sharing functionality on your computer is vulnerable to abuse or accidental information leakage. It is preferable to set up alternate tools and practices for sharing files, such as a central file repository.*
+*Although handy for sharing files with peers, the built-in file sharing functionality on your computer is vulnerable to abuse or accidental information leakage, especially on simple networks like one finds in cafes or on airplanes that don't provide "host isolation" meaning that any computer using the wireless can connect to any other one. It is preferable to set up alternate tools and practices for sharing files, such as a central file repository in your office or cloud file service.*
 
 *To turn off file sharing on a Mac, go to Apple menu \> System Preferences, then click Sharing and make sure all the boxes are unchecked. See [this article]("https://support.microsoft.com/en-us/kb/307874") for turning off file sharing on a Windows computer.*
 
 *Recognize that if you are currently using the built-in file sharing functionality to share files inside an office, doing this will disrupt current work practices.*
 
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Turn on your computer's firewall and disallow all external connections**  
-:rocket::rocket::wrench::wrench::fire::fire: 
-*A firewall prevents unauthorized connections from other computers on the wireless network. There is a built in firewall in every computer, but it is not turned on by default and may allow connections to certain services. The firewall settings can be found on Macs in System Preferences > Security. On Windows computers, the firewall settings are in the System and Security tool in Control Panel. More information about Windows Firewall can be found [here] ("http://www.microsoft.com/security/pc-security/firewalls-using.aspx")*
-
-
 :heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Ensure that the wireless network is not presenting false certificates**  
 :rocket::rocket::rocket::rocket::wrench::wrench::wrench::fire::fire::fire:  
-*Increasingly, networks are set up to monitor traffic for various reasons such as ad placement or content filtering. However, this potentially compromises all secure connections, as it allows traffic to be monitored via the same mechanism in what is called a Man-In-The-Middle (MITM) attack. The network device will replace the security certificate from the service you are connecting to with one of its own. Anyone with access to that device can see any communication between you and that service. Learning to view certificates in your web browser, or installing and learning to use a tool such as Certificate Patrol (available only for Firefox [here]("http://patrol.psyced.org/") will help you identify certificate changes but also causes many alert windows to appear.*  
+*Increasingly, networks are set up to monitor traffic for various reasons such as ad placement or content filtering. However, this potentially compromises all secure connections, as it allows traffic to be monitored via the same mechanism in what is called a Man-In-The-Middle (MITM) attack. The network device will replace the security certificate from the service you are connecting to with one of its own. Anyone with access to that device can see any communication between you and that service. Learning to view certificates in your web browser, or installing and learning to use a tool such as Certificate Patrol (available only for Firefox [here]("http://patrol.psyced.org/") will help you identify certificate changes but in normal operation also causes many alert windows to appear as vendors change their certificates.*  
 
 *Google has created [a document]("https://support.google.com/chrome/answer/95617?hl=en")on viewing certificate information in Chrome. Mozilla has [a similar document]("https://support.mozilla.org/en-US/kb/secure-website-certificate
 ") for Firefox as well as some [overall instructions] ("https://support.mozilla.org/en-US/kb/how-do-i-tell-if-my-connection-is-secure") on connection security that you may wish to review.*
 
 :heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 **Use a Virtual Private Network (VPN) to securely tunnel out of public networks**  
-:rocket::rocket::rocket::rocket::wrench::wrench::wrench::wrench::fire::fire::fire:  
+:rocket::rocket::rocket::wrench::wrench::wrench::fire::fire::fire:  
+
+*A VPN creates a secure connection for your computers to use to access the office network and the Internet. This connection, or tunnel, can be used to hide all information moving from your computers to the Internet or office network from the operator or other users of the wireless network. Use of a VPN severely limits the amount of trust you have to place in the owner and operator of the network you are on and so limits your exposure to them. These factors make VPNs a very effective way to protect your traffic from observation or interception on untrusted networks.*
+
+*A VPN is implemented via a device you own located in your office or at an offsite facility, or that a third party provides you use of for a fee. If hosting your own VPN hardware, budget for ongoing maintenance, licensing and software updates so that the device mediating your connection doesn't become a point of leverage against you. Also recognize that in setting up a device to use for VPN connections inside your office, many offsite staff will be dependent on your office Internet line for their work. If this Internet connection is unstable, undersized or asynchronous (made for downloading more than uploading, such as DSL or residential cable connections) the VPN will not work well for staff. For this reason, paying to "colocate" your own VPN device in a data center is the best way of getting a high trust, high performance VPN setup in place.*
 
-*A VPN creates a secure connection for your computers to use to access the office network and the Internet. This connection, or tunnel, can be used to hide all information moving from your computers to the Internet or office network from the operator or other users of the wireless network. Use of a VPN severely limits the amount of trust you have to place in the owner and operator of the network you are on and so limits your exposure to them. These factors make VPNs a very effective way to protect your self on untrusted networks.*
+*Because of the high cost of self hosted VPNs, most organizations choose to use a third party VPN service provider to meet this need. It is important to recognize that unless you setup, run and maintain your own VPN infrastructure, you are just offloading that trust to a different third party -- the owner and operator of the VPN service. Be very careful in your selection of VPN providers and review their policies and track record carefully. Specific recommendations for VPN providers is outside of the realm of this document.*
 
-*A VPN is implemented via a device you own located in your office or at an offsite facility, or that a third party provides you use of for a fee. Choosing a VPN provider and setting up computers to use it are not simple tasks, and critically important – a misstep in setup or use can expose your information or bring your work to a crawl. In addition VPNs add a layer of network traffic and will slow down your Internet access so your distance to and bandwidth available from your VPN provider (or office if hosting your own) will make a difference to performance.*
+*Choosing a VPN provider and setting up computers to use it are not simple tasks, and critically important – a misstep in setup or use can expose your information, bring your work to a crawl or expose your information. All VPNs add a layer of network traffic and will slow down your Internet access so your distance to and bandwidth available from your VPN provider (or, as noted above, your office or colocation facility if hosting your own) will make a difference to performance -- and in turn whether people actually use it.
 
-*Consider if the speed tradeoff is acceptable to you before choosing to implement a VPN. If you do, the investment in implementation, setup and hassle is repaid by a solution that increases connection security across many situations.*
+*Consider if you can absorb the costs to make the speed and trust tradeoffs acceptable to you before choosing to implement a VPN. If you can, the investment in hardware, implementation, setup and hassle is repaid by a solution that mitigates a range of threats associated with use of untrustworthy networks across many situations.*
diff --git a/4_email_safety_checklist.md b/7_email_safety_checklist.md
similarity index 58%
rename from 4_email_safety_checklist.md
rename to 7_email_safety_checklist.md
index 40f6464..1a8929e 100644
--- a/4_email_safety_checklist.md
+++ b/7_email_safety_checklist.md
@@ -2,8 +2,8 @@
 document set: DIGITAL SECURITY CHECKLISTS FOR U.S. NON-PROFITS
 title: Email Safety Checklist
 author: Jonah Silas Sheridan, Lisa Jervis
-last modified: 11/18/2015
-version: "1.0, PEER REVIEWED VERSION FOR PUBLIC USE"
+last modified: 9/2/17
+version: "2.0, DRAFT NOT FOR FOR PUBLIC USE"
 ---
 # Email Safety Checklist
 ## Introduction
@@ -17,10 +17,9 @@ Think about the emails you receive like a shut up envelope. If you don't know wh
 
 ## Key
 :heavy_check_mark: Record actions  
-:rocket: Difficulty rating   
-:wrench: Technical skill level  
-:fire: Work flow disruption  
-
+:rocket: Implementation management overhead rating   
+:wrench: Technical skill level required
+:fire: Work flow disruption for staff
 ## Email Safety Tasks
 
 :heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Train your organization not to send sensitive or controversial information over email whenever possible.**  
@@ -64,6 +63,11 @@ party service and if possible a dedicated mass email subdomain.**
 
 *This service comes included if you use [GMail]("https://google.com/mail"), [Electric Embers]("https://electricembers.coop") but doesn't with all email services. Filtering mail before it reaches your network lessens the chance of a virus or malware bearing link or attachment being clicked on. After initial setup this service will be nearly invisible to staff, but requires that someone is tasked with dealing with false positives and other email delivery problems. Be aware, however, that this item involves a significant tradeoff: filtering means that another company is viewing your email before it reaches you and so may increase risk of that information being exposed. The [Electric Embers Cooperative] ("https://electricembers.coop/") is an ethically aligned provider which offers such a service specifically for non-profits.*
 
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; **Use generic email addresses, and only those addresses, for critical functions such as finance, security or human resources management. Forward critical staff's email to someone else rather than exposing their absence through out of office replies so they cannot be abused.**
+:rocket::rocket::wrench::fire::fire:  
+*An increasingly common mechanism of attack on small business and non-profit finances is to lookup the names of financial responsible people and create fake emails to or from them requesting non-standard financial transactions due to some sort of emergency condition. This same strategy can be used to obtain all sorts of information or to get people to take other types of actions. By using generic email addresses, coupled with strong internal controls, in your internal management of sensitive processes you can help ensure these sorts of "person to person" social engineering attempts do not succeed.
+
+*Out of office replies have unfortunately become a way to gather intelligence about organizations and so during absences of key personnel when standard operating procedures may be suspended and less practiced processes engaged, choose to forward email from such employees and leaders during their absences. All of these practices are strongest when coupled with standard, documented and verifiable processes that require additional confirmation beyond just an email.*
 :heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Where email is accessed on mobile or laptop devices, configure email clients and web browser to store as little information as possible**  
 :rocket::rocket::wrench::wrench::wrench::fire::fire::fire::fire:
 *Most web browsers can and should be set to clear their cache when closed. Most email clients can be configured to not store email offline and to clear caches when closed. Both can be configured not to store passwords as well. By configuring both this way, a lost laptop or phone will potentially result in far less information disclosure. Note that it may also mean that you need to enter a password every time you start the program and cannot access emails when not connected to the Internet so may have extreme operational impact to your team. This practice can be made unnecessary by the use of hard drive encryption on your devices, which will be covered in the associated [Endpoint Protection Checklist]("#") which will be added to this document set in the future.*
@@ -72,10 +76,20 @@ party service and if possible a dedicated mass email subdomain.**
 :rocket::rocket::rocket::rocket::rocket::wrench::wrench::fire::fire::fire:  
 *“Phishing” is where emails are crafted to look as legitimate as possible in order to get you to click a link or attachment. This is actually a social engineering attack more than a technical one, and so addressing the human element through education is the best way forward. Testing people by sending fake, innocuous phishing emails, is a hard task, but recommended to give people a chance to practice without bad consequences. Be careful as you can create a fear response rather than lasting motivation with this practice so try to be playful and emphasize the positives of these practices There are multiple companies that offer this training if you don't have internal capacity to provide it yourself. [Contact Information Ecology]("https://iecology.org/contact") for referrals.*
 
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; **Setup correct DKIM and SPF records for your email domains and subdomains**  
-:rocket::rocket::rocket::rocket::wrench::wrench::wrench::wrench::fire:  
-*These are highly technical steps made in conjunction with your email and Domain Name Service providers to minimize the ability of spammers or phishers to fake emails from your organization. “Hard fail” settings are preferred for SPF records wherever possible. Once set up, this should have minimal impact on day to day operations, though it make changing your email provider or infrastructure more complex. Find more information at [the official DKIM website]("http://dkim.org/") and [the official SPF website] ("http://www.openspf.org/").*
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; **Register any domains that could be accidentally read as the domain you use for your email to prevent targeted phishing attacks using look-alike domains**
+:rocket::wrench::fire:
+*Phishing attacks are hardest to detect when they include sending people email from addresses with links to websites that appear to be official but are actually hosted by the attacker. One way that this can be done is by registering domain names that look like other domain names -- substituting a capital letter "i" for the letter "l," or an "m" for a double"nn" for example. It is wise, then, to note any ambiguous characters in your domain name(s) and proactively buy any that look similar. Although this will cost you some money, you can renew these at the same time as your other domains so there is little management overhead. You don't even need to setup any services on these domains.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; **Setup correct Domainkeys Identified Mail (DKIM) and Sender Policy Framework (SPF) records, and the associated Domain-based Message Authentication, Reporting & Conformance (DMARC) records that build upon these, for your email domains and subdomains.**  
+:rocket::rocket::rocket::rocket::wrench::wrench::wrench::wrench::fire::fire:  
+*These are highly technical steps made in conjunction with your email and Domain Name Service (DNS) providers to make it hard for  spammers or phishers to fake emails from your organization.*
+*Be aware that SPF records require identifying **all** * *the services that are currently sending email on your behalf (which could be databases, mass mailing tools, email list hosts, fundraising tools and more) and incorrect configurations can cause your email to be incorrectly marked as spam. Determining this list carefully is critical to implementing this recommendation in a way that does not interrupt ongoing operations. Once setup, you will need to maintain this list and make changes any time your organization adopts any other tools that send email from the same domain as your GSuite email addresses but otherwise should be invisible in operation.“Hard fail” settings (records ending in "-all") are preferred for SPF records wherever possible, but be careful as this can cause email bounces if your records are not carefully tuned.*
+*DKIM will help assure recipients that your designated mail servers sent the mail they are receiving. DMARC builds on these to tell recipient servers how to respond when the other two records help it identify spam or falsified messages. Once set up, this should have minimal impact on day to day operations, though it make changing your email provider or infrastructure more complex. Find more information at the official DKIM website at http://dkim.org/, the official SPF website at http://www.openspf.org/ and the official DMARC website at https://dmarc.org/. Note that these are easiest to setup using a platform such as GSuite, Office365 or other integrated cloud provider.*
 
-:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; **Use PGP encryption to secure your email “end to end”**  
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; **Use encryption, preferable "end to end" to secure your email.**  
 :rocket::rocket::rocket::rocket::wrench::wrench::wrench::wrench::fire::fire::fire::fire:  
-*This is a highly technical and labor-intensive initiative to undertake, but probably the most complete way to minimize any inadvertent disclosure of data through email. It will likely require significant changes to staff practices. The most common tools for using PGP encryption with email are the [Mozilla Thunderbird]("https://www.mozilla.org/en-US/thunderbird/") email client and the associated [Enigmail plugin]("https://www.enigmail.net/home/index.php"). You can find [a guide for that setup] at ("https://securityinabox.org/en/guide/thunderbird/windows") OSX's Mail program and open source add on [GPGTools] ("https://gpgtools.org") is also a workable tool set for using PGP encrypted email on Macs. Microsoft Outlook works best with a commercial add-on from [Symantec]("http://symantec.com") to use PGP encryption on Windows. For organizations with more resources, S/MIME is an alternate encryption scheme that works well with a Microsoft Exchange/Outlook environment or with GMail by installing the [Penango]("https://www.penango.com"). If interested in either of these solutions talk to your technical support provider and be prepared to invest some time and resources into planning, implementation and training.*
+*This is a highly technical and labor-intensive initiative to undertake, but probably the most complete way to minimize any inadvertent disclosure of data through email as hides all email content from any servers or network providers that pass your mail along. It will likely require significant changes to staff practices and inconvenience for your team, but provides far greater compliance with standards such as HIPAA as well as significant protection of sensitive information emailed within your organization. There are various ways to gain protection, but only some are truly "end to end" meaning that you don't have to trust any parties in the middle and encryption and decryption only happens on the devices communicating with each other.*
+
+*The most common type of end to end encryption is called Pretty Good Privacy (PGP) and has been around for a long time. Consequently there are both a lot of ways to use this type of encryption, it works across many platforms and lacks the ease and strength of some other, more modern encryption schemes. One major tool for for using PGP encryption with email is the [Mozilla Thunderbird]("https://www.mozilla.org/en-US/thunderbird/") email client and the associated [Enigmail plugin]("https://www.enigmail.net/home/index.php"). You can find [a guide for that setup at] ("https://securityinabox.org/en/guide/thunderbird/windows"). OSX's built in Mail program and open source add on [GPGTools] ("https://gpgtools.org") is also a workable tool set for using PGP encrypted email on Macs. Microsoft Outlook works best with a commercial add-on from [Symantec]("http://symantec.com") to use PGP encryption on Windows. [Mailvelope](https://www.mailvelope.com) is a powerful and well audited PGP add-on for web browsers that allows you to use PGP encryption with GMail and almost any other webmail service. Because of its position inside a web browser, its security is generally less assured than the other PGP options above, but is adequate for many organizations, especially when coupled with strong web browser profile controls and careful use of browser extensions as well as other safe browsing practices. Note that as of mid-2017, use of Mailvelope in Firefox is not recommended due to a security vulnerability discovered in it. If you want to use Mailvelope with Firefox, see this blog post for details of how to do so as safely as possible: https://www.mailvelope.com/en/blog/security-warning-mailvelope-in-firefox.*
+
+*For organizations with more resources, S/MIME is an alternate encryption scheme that works well with a Microsoft Exchange/Outlook environment or with GMail by installing the [Penango]("https://www.penango.com") plugin or using [Google's native offering](https://support.google.com/a/answer/6374496) which requires use of the GSuite Enterprise paid services. An alternate third party managed encryption tool called Virtru (https://virtru.com) is available for GMail and works best if used only with GMail users. Both Google's S/MIME option and the Virtru service are not true end-to-end offerings as you trust those companies to hold the keys that allow you to decrypt email. If interested in either of these solutions be aware that you are entering into a high trust relatioship with Google or Virtru respectively. If wanting to implement any encryption scheme mentioned here for your email, you will need to talk to your technical support provider and be prepared to invest some time and resources into planning, implementation and training.*
diff --git a/8_gsuite_security_checklist.md b/8_gsuite_security_checklist.md
new file mode 100644
index 0000000..3019e53
--- /dev/null
+++ b/8_gsuite_security_checklist.md
@@ -0,0 +1,86 @@
+
+---
+document set: DRAFT DIGITAL SECURITY CHECKLISTS FOR U.S. NON-PROFITS
+title: GSuite Security Checklist
+author: Jonah Silas Sheridan, Lisa Jervis for Information Ecology
+last modified: 8/23/17
+version: "2.0 DRAFT, NOT PEER REVIEWED"
+___
+
+# GSuite Security Checklist
+
+## Introduction
+
+As of this document's creation (in 2017) a significant portion of US non-profits rely on Google's free online "cloud" applications (GMail, Google Docs/Sheets GDrive, Google Calendar among them) to do their work. While many groups still depend on personal or other Gmail accounts made for their work (any login that ends with @gmail.com) for access to these services, Google also offers GSuite -- a version of these tools suited for use in organizations. GSuite provides significant advantages over personal accounts including organizational email addresses (which use a custom domain name, the part of an email address after the @ sign, which can match your website address), administrative controls, advanced settings and 24/7 tech support for use of the tools. These features can improve your organization's technology in many areas, including helping you improve your ability to secure your information by providing tighter management, control and monitoring of your systems and how they are used.
+
+Because of these advantages and the fact that Google offers the Basic version of GSuite for free to registered US 501c3 organizations, setting it up for your organization is highly recommended for all US organizations that already rely on Google's cloud based tools.
+While there are definitely risks associated with providing any third party corporation, especially one in the business of data mining, and advertisement targeting, access to all your information and the data about how and where you and your team use it, if you are already accepting this risk by relying on Google's tools, GSuite will at least help you secure that information from others. You can begin the sign up process and read about the offerings at https://www.google.com/nonprofits/products/apps-for-nonprofits.html.
+
+***Despite the recommendation above, this document should in no way be read as an explicit endorsement of GSuite or other Google tools for movement building, activist or other non-profit organizations. There are many other tools that can meet the needs that they fill with a range of associated security and operational tradeoffs. If any previous security risk assessment has shown the vulnerabilities and risks associated with these tools to be unacceptable for your organization, or for any reason you a strong trust relationship with a US based corporation is concerning to you, carefully consider the risk tradeoff before implementing GSuite for your non-profit.***
+
+For those that have already adopted GSuite in the non-profit sector, the checklist that follows offers direction on how to setup and use the administrative controls offered by the free GSuite Basic platform to "harden" your setup and improve your overall digital security level. Note that, as indicated in the associated description, many of these tasks are specific implementations of checklist items from elsewhere in this set.
+
+It is also noted that there are additional controls and security features available using other editions of GSuite, including GSuite for Business and GSuite Enterprise. While neither of these editions are provided for free and the price scales by the number of user accounts and devices in use, the additional functionality provided has value for organizations that have additional needs including but not limited to high compliance requirements for their work, a need to work with highly sensitive data or a wish to deploy tightly controlled mobile devices. You can review edition differences at https://gsuite.google.com/compare-editions/ and, if unsure which is best for your needs, should ask for help from your technical support provider in making the decision of which edition to deploy.
+
+## Key
+:heavy_check_mark: Record actions  
+:rocket: Implementation management overhead rating   
+:wrench: Technical skill level required
+:fire: Work flow disruption for staff
+
+## GSuite Setup Security Tasks
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Make a plan, preferably before deploying GSuite, detailing how your information is used by your staff, volunteers and others, to ensure you understand your security needs and can configure the tools correctly.**
+:rocket::rocket:rocket::wrench::fire:
+*GSuite is a powerful platform with a lot of moving parts and a lot of possible configurations. As with all tols, the more time and energy you put into understanding the different users and user types you have and what features they need to use, the more effective your implementation of security controls will be. First read through this checklist to familiarize yourself with some practices you may want to employ in your GSuite setup. Then make a list of all the different groups of people you have in your organizations that will be using your GSuite tools based on the work you expect them to do using those tools (such as volunteers, or part time staff or borad members). Think about and list which of those groups needs to send email, to edit documents, to access your shared contacts list, has calenders and so on. Think about whether anyone should have restricted access or special access to specific tools that nobody else needs, as well as specific shared roles (report intake, billing, etc.) that need to be filled. Google has produced a lot of documentation on how to plan your GSuite deployment which can be found here: https://support.google.com/a/answer/4514329 and can help you understand the applications and settings available to you in your setup process. At a minimum having a well crafted plan will allow you to ask specific questions to GSuite support as you go through the setup process but this planning will also guide you as you step through the administrative tools at https://admin.google.com.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; **Create at least one dedicated account with administrative control of GSuite that is not associated with any individual's work email address, and provide a recovery email address or phone number that is controlled by your organization or trusted tech support provider (and not an individual employee).**
+:rocket::wrench::wrench::fire::fire:
+*While convenient, giving everyday user accounts permission to control your GSuite install creates risk. If that person's device is lost or stolen or their password otherwise obtained, all of your organization's information could be at risk. Sign up with or create a unique email address (like gsuite@yourdomain.org, replacing yourdomain.org with your organization's domain name) for this purpose that isn't used for anything else. You should give this "Super Admin" permissions (full control over your Gsuite setup, including access to all calendars and accounts - which it automatically gets if used for setup), remove those permissions from any other accounts and store the password in a safe way like a password manager or safety deposit box, using it only when you need to change settings in GSuite. You will be asked to give recovery email or phone number  in case of a lost password. This email or phone should be controlled by your organization or trusted delegate such as a tech support provider or affiliate organization rather than by an individual employee. You can find instructions for giving or taking away Super Admin permissions for a user at https://support.google.com/a/answer/172176. Directions for setting up a recovery phone number or email are at https://support.google.com/accounts/answer/183723.*
+*There are multiple levels of administrative control available in GSuite as well, which you can use to offer limited permissions to other administrative users you create if you have multiple employees, tech support providers or volunteers with specific administrative tasks to perform. You can review the built in administrative groups and find a link on how to make custom roles of your own at https://support.google.com/a/answer/2405986. As an example you might make an account for tech support called helpdesk@yourdomain.org and give it Help Desk Admin permissions which will allow it to reset passwords for people, but not create users or groups. Now you can give control of that account to someone who does tech support without giving them total control of your systems.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Use the organizational units functionality in GSuite to make groupings of user accounts or devices and giving them the minimum level of access required to do their work.**
+:rocket::rocket::wrench::wrench:fire::fire:
+*While convenient, giving all users ability to use all the tools in any way they wany in your GSuite setup may present security risk for your organization. For that reason you should use the advanced management features available in the platform to practice the security concept of "least authority" meaning you give all users the minimum set of access required for them to do their work. For example you may want to be able to let volunteers enter information into Google Sheets but not to email on behalf of your organization. GSuite provides a structure called an organizational unit to allow you to separate users or devices you manage into groups, and then assign "policies" to each of those groups. These policies including the ability to access specific tools or "apps" or to apply certain settings to their accounts. You can read an overview of applying policies at https://support.google.com/a/topic/1227584. An article about organizational structures is at https://support.google.com/a/answer/4352075 and instructions for creating them at https://support.google.com/a/answer/182537.*
+*Once you have created these units, you can use them to control access to services as described at https://support.google.com/a/answer/182442 or to apply specific settings about those services as described at https://support.google.com/a/answer/2655363.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Use Google Groups and Google Drive Team Drive features to provide appropriate access to files to different groups of users, and to ensure that your organization always controls its own information.**
+:rocket::wrench::wrench::fire::fire::fire:
+*Historically one of the challenges of managing your organization's files using Google Drive has been the loss of access to key documents when employees or volunteers leave the team as well as the ability to lock down sensitive information such as that used for  human resources policy or reporting, anonymous donor tracking or sensitive program details. By setting up one or more Team Drives (as described at https://support.google.com/a/answer/7212025) you will assure that the Super Admin for your GSuite domain always has access to the files that are stored there. You can also apply permissions (as described in this article https://support.google.com/a/answer/7337635?hl=en) to a Team Drive to allow only the minimum access needed for different individual or groups of users. For example you might have policy documents that only certain staff members should be able to change and that all staff and volunteers need to be able to view or comment on. You can give these permissions by individual email address if your organization is small enough, or for larger groups and ease of management you can create groups in Google Groups (https://support.google.com/a/answer/33329) and give the permission to the group by entering its email address. This way when a new person comes on board or leaves a team or the organization, you only need to take them out of the relevant Google Groups or Team Drives to also remove their account's permissions to files. Note that by locking down your files in this way, your system becomes much less "self service" and someone will need to be in charge of and regularly available to change permissions and group settings as needed. The increased control of your files is well worth this task overhead.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Turn on two-factor authentication and after being sure everyone is using it successfully. Help staff use Google Authenticator codes or U2F hardware keys as a second factor rather than text message codes and make sure they report immediately if that factor is lost or stolen.**
+:rocket::rocket::rocket::wrench::wrench:wrench::fire::fire::fire:
+*One of the advantages of GSuite as a platform is its support for two-factor authentication whereby users login with two things that they know or control, one of which is their password and the other of which is a hardware key, code produced by a program running on their computer or phone, a text message code or even a printed code from a list. Unless your organization owns and manages the cell phones receiving a texted code as a second factor, it is highly advised that you help staff select another second factor with which to prove their identity when logging into Google services, especially for any accounts with Super Admin or other administrative rights to your GSuite domain.*
+*Google Authenticator is available in both the Google Play store for Android phones as well as the App Store for Apple devices. The most common U2F hardware key is called a Yubikey and can be ordered at a discount at this link: https://www.yubico.com/gafw/. You will need to log into your GSuite admin account but can order up to 50 keys at half price cost of $9 a piece.*
+*Setup of two factor authentication, as well as links to training materials for staff, is detailed in this document: https://support.google.com/a/answer/175197. Have staff print backup codes (see directions here: https://support.google.com/accounts/answer/1187538) so that they can still get into their account if their phone or hardware key is lost or stolen. Although those backup keys will allow them keep working, it is important to inform users to report a lost second factor or set of backup codes to whomever is responsible for administration of your GSuite domain. Once reported lost or stolen, a security key MUST be revoked (https://support.google.com/a/answer/2537800#seckey), backup codes MUST be regenerated by the user (https://support.google.com/accounts/answer/1187538) or a Google Authenticator app MUST be removed as a second factor to preserve your security levels.*
+*Be aware that separate passwords for applications such as email or calendaring clients that do not support the two factor process will become necessary and you will want to be sure you help staff create those as outlined in this document: https://support.google.com/a/answer/1032419. You can also use the Advanced Security Settings which can be applied to all of your users, or any group of users in an Organizational Unit, to require that two factor authentication is setup within a certain amount of time after their first login. Although this may put a strain on technical support resources, it is highly recommended. Directions to enforce two factor authentication can be found at https://support.google.com/a/answer/2548882.*
+*A more general version of this recommendation can be found in the Authentication Checklist that is part of this document set. Two factor authentication is a best practice for use with any service or tool that supports it, though each will have its own set of options available to you and your staff.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Implement controls that make it difficult for anyone to "spoof" email from your email addresses.**
+:rocket::rocket::rocket::wrench::wrench::wrench::wrench::fire::fire:
+*Google has produced a strong set of tools to allow other email systems to verify that email coming from your GSuite domain is in fact yours, preventing "spoofed" emails. Google uses the latest  Internet standards called Domainkeys Identified Mail (DKIM), Sender Policy Framework (SPF) records, and the associated Domain-based Message Authentication, Reporting & Conformance (DMARC) to do this, and has a set of documents that will guide you through setup that are available from this link: https://support.google.com/a/topic/4388154.
+*This is a highly technical set of tasks which also involve your Domain Name Servers (DNS) which may not be hosted at Google, but will make it very hard for your email addresses to be abused for phishing or other attacks against others as well as faked internally.*
+*Be aware that SPF records require identifying **all** * *the services that are currently sending email on your behalf (which could be databases, mass mailing tools, email list hosts, fundraising tools and more) and incorrect configurations can cause your email to be incorrectly marked as spam. Determining this list carefully is critical to implementing this recommendation in a way that does not interrupt ongoing operations. Once setup, you will need to maintain this list and make changes any time your organization adopts any other tools that send email from the same domain as your GSuite email addresses but otherwise should be invisible in operation.“Hard fail” settings (records ending in "-all") are preferred for SPF records wherever possible, but be careful as this can cause email bounces if your records are not carefully tuned.*
+*A more general version of this recommendation can be found in the Email Safety Checklist that is part of this document set but is more easily setup in an integrated platform like GSuite than in many other environments so here is rated slightly lower in difficulty and skill required.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Disable email forwarding for users so that any sensitive internal emails don't end up traveling insecurely to other email accounts or remain in less secured email systems that are vulnerable to attack.**
+:rocket::wrench::fire:
+*Although it is handy for people to be able to forward their organizational email to personal or other email accounts, your organization has no control over how that email gets there and how secured it is once it gets there. By allowing email forwarding to other systems, you create a point of potential disclosure for internal conversations that would be otherwise locked into Google's secured infrastructure and (assuming you follow this checklist in full) protected by strong passwords and two factor authentication. This is a simple setting that can be applied to all users or a set of users in an Organizational Unit as detailed in this document https://support.google.com/a/answer/2491924.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Educate your staff on file sharing, including the higher security of sharing by email address and risks associated with sharing files by link.**
+:rocket::rocket::wrench::fire:
+*All users should be trained on the exact options available to them for sharing files in GSuite both with peers in the organization and others outside. This help document provides a good overview https://support.google.com/drive/answer/2494822. Even if sharing this article, the complexity involved here is high and so in person or webinar training with live practice is always preferable.*
+*Although it is very easy to click the "Get shareable link" on a file or folder and send it to someone for collaboration, there are risks associated with this way of sharing. It is always better to avoid link sharing, as you cannot control that link after it has left your hands. The tightest sharing is by filling out the "People" field with email addresses associated with Google based accounts whether inside your domain or not. However, not everyone has a Google account or a you need to post a to another system and so sometimes a link is necessary. If using link sharing, be sure to watch out for accidentally making a file public, choosing "anyone with the link" instead. You should also teach users set an expiration date, even if far in the future so that the file or folder in question eventually becomes unshared. Last it is important to choose the most limited permissions appropriate -- allowing people with the link to only view or comment on a file if they do not need to change it's contents.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Make sure someone is assigned to regularly monitor what is happening in GSuite, has time to do so and knows how to identify and escalate any security incidents or other concerns about abnormal usage.**
+:rocket::rocket::wrench::wrench::fire:
+*Another advantage of an advanced integrated platform like GSuite is the availability of reporting on what is happening with your organizational tools and information over time. Generally this is an important security practice for all tools, but is much more accessible in GSuite that in other places. You want one individual or a team tasked with this ongoing monitoring, even if an outside tech support person, so that problems are caught quickly. Monitoring should be done on no less than a monthly basis and preferably more often. To make sure that happens, it is important to ensure that the person, team or outside party has time to perform the monitoring by incorporating it into their work plan or scope of work. The goal of this monitoring is to find unexplained account behavior such sudden growth in file sets or email activity so the person with this job should establish a baseline of activity and should look for trends outside of that baseline. Any questionable activity should be investigated with the user(s) involved or escalated to a tech support professional.*  
+*Activity Reports are available inside the administrative console including use of two factor authentication, external apps installed, emails sent/received and file activity in Google Drive. An article describing these basic reports is at https://support.google.com/a/answer/4580176. A broader explanation of all the reporting available to you in GSuite can be found at https://support.google.com/a/answer/6000239.*
+*It is important to always regularly review the security settings of your users, especially password strength for any users not enrolled in two factor authentication, as described here: https://support.google.com/a/answer/2537800#password. Google is constantly updating there password strength rating system to check for leaked passwords and other emerging threats so a password that is judged strong one week may not be the next. Of course this is less important for users with two factor authentication as their password is only half of what is needed to hijack their account.*
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Train users not to check the "Don't ask again on this computer" checkbox when using public or other untrusted computers, to logout after using such computers and to untrust computers that are lost, stolen or otherwise compromised**
+:rocket::wrench::fire:
+*This practice will help ensure that all your other efforts to create high barriers to accessing your information are successful. When a user checks the "Don't ask again on this computer" box when logging in with two factor authentication, they are telling Google not to ask for a password or 2nd factor for 30 days. In the case of a poorly managed (i.e. not regularly cleaned or reset) computer in a library, Internet cafe or other public place, this leaves an account wide open to abuse during that period. Though Google will prompt again for password changes and other sensitive actions, that computer retains the ability to access account information, send emails and read and edit documents. Trusted computers can always be reviewed, or the trust revoked, within a user's account settings as detailed here: https://support.google.com/accounts/answer/2544838.
+
+:heavy_check_mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Install Chrome browser on all staff computers, set as the default and make sure it is regularly updated. Make sure staff know to use Chrome with all of your GSuite tools.**
+:rocket::rocket::wrench::wrench::fire:
+*This practice will help you have strong security between your web browser and Google's services. Because they control both things, they have a lot of ways to verify that your connection is well secured, that newer features like two factor authentication work well, and can push out corrected software if they have a security incident in their infrastructure. Generally Chrome will self update, but you should teach your staff how to recognize when an update is available (as described here: https://support.google.com/chrome/answer/95414). Closing and reopening the browser will allow it to update to the latest, and most secure version.*
diff --git a/7_glossary.md b/9_glossary.md
similarity index 59%
rename from 7_glossary.md
rename to 9_glossary.md
index 48a08fa..5e5caba 100644
--- a/7_glossary.md
+++ b/9_glossary.md
@@ -1,18 +1,18 @@
 ---
-document set: DIGITAL SECURITY CHECKLISTS FOR U.S. NON-PROFITS
+document set: DRAFT DIGITAL SECURITY CHECKLISTS FOR U.S. NON-PROFITS
 title: Glossary
 author: Jonah Silas Sheridan, Lisa Jervis
-version: "1.0, PEER REVIEWED VERSION FOR PUBLIC USE"
-last modified: 11/18/2015
+version: "2.0 DRAFT - NOT FOR PUBLIC USE"
+last modified: 9/2/17
 ---
 
 # Digital Security Glossary
 
 **Backup**  
-Regularly updated copies of your digital assets, ideally stored in several different places, so that if access to or integrity of your data is disrupted for any reason (damage to computers due to accident or natural disaster, accidental or malicious deletion of files,etc.), the assets can be restored. Online backup services such as Mozy and CrashPlan are best supplemented by backups stored on organizational equipment and in secure offsite storage.  
+Regularly updated copies of your digital assets, ideally stored in several different places, so that if access to or integrity of your data is disrupted for any reason (damage to computers due to accident or natural disaster, accidental or malicious deletion of files,etc.), the assets can be restored. Online backup services such as Mozy and CrashPlan are best supplemented by backups stored on organizational equipment with at least one up to date copy in secure offsite storage.  
 
 **Cookies**  
-Small files placed on your computer by websites that youvisit; they are used to manage website features such as logins and can also be used to track behavior on the web. While not all cookies are a security risk, if poorly implemented they can expose the informationthey contain. More information about cookies is available at [http://www.allaboutcookies.org/]("http://www.allaboutcookies.org/").   
+Small files placed on your computer by websites that you visit; they are used to manage website features such as logins and can also be used to track behavior on the web. While not all cookies are a security risk, if poorly implemented they can expose the information they contain. More information about cookies is available at [http://www.allaboutcookies.org/]("http://www.allaboutcookies.org/").   
 
 **Digital assets**  
 Any and all data electronically stored or used by your organization. This includes your organization's files, website,emails, social media accounts, online banking accounts, etc. Some of these items may be ones that you administer yourself (e.g., the contents of staff hard drives, file repositories stored on servers owned and controlled by your organization); others may be maintained by third-party services on your behalf (e.g., files on Google Drive orBox). Others are services that you participate in that are owned and controlled by others (subject to terms of service), such as organizational Facebook pages.
@@ -29,24 +29,36 @@ A mechanism by which your data scrambled in order to protect it from being read
 **Encryption Key.**  
 An encryption key is a piece of information that you share with an authorized party so they can encrypt and/or decrypt information to or from you. In most cases this information is highly sensitive and needs to be protected however modern encryption schemes allow you to have a “public” key that you can safely share with anyone.  
 
-**Extensions**  
+**Extensions or Add-ons**  
 Small pieces of software that you install as part of your web browser in order to give your browser additional capabilities.
 
-**Firewall.**  
-A piece of software or hardware device that analyzes and selectively blocks or alters information passing between two networks.Common places to find firewalls are between your office network and the Internet and on your computer to protect you from other computers on your office network.
+**Firewall**  
+A piece of software or a hardware device that sits between a device or network and the Internet. It analyzes and selectively blocks or alters information passing between two sides. Common places to find firewalls are between your office network and the Internet and on your computer to protect you from other computers on your office network.
+
+**Full Disk Encryption**
+An encryption setup where the entirety of a storage device, or disk -- whether a USB stick, hard drive inside a computer or external drive for backups or any other -- is encrypted. This is the most secure way of protecting your information as unencrypted parts of disks can accidentally hold sensitive data, even if just used for "virtual memory" or you think the files on it have been deleted. This is important especially for devices that could be lost like laptops, mobile phones or backup drives -- but will also mean that no data on them can be accessed (including for starting up the system in the case of a computer or phone) without the encryption password.
 
 **Office network**  
 The equipment in your office that allows staff computers to connect to each other, on site resources such as fileservers and to the Internet. If you cannot trust that nobody else is controlling this network your security progress will be compromised.  
 
+**Operating system**
+The main program that lets you run all the other programs on your computer. This usually includes all the tools to make your devices (like keyboards or screens or storage devices) available and usually, but doesn't have to, includes some sort of file manager -- a way to find and access your files and programs. Common operating systems include Android, ChromeOS iOS, Linux, OSX and Windows but there are many others available used for all sorts of purposes.
+
 **Password manager software**  
 Software that keeps your passwords in an encrypted format, protected by a master password. This allows you to store multiple passwords by remembering only one. Password managers are available as software that you install (e.g., KeePass) and as a web-based service (e.g., LastPass). While web-based password managers can be secure enough to hold the passwords staff use to access their accounts for everyday purposes, they are not recommended to store the passwords that grant administrative access to core organizational systems.
 
 **Security certificates**  
 Security certificates are a specific kind of file that includes an encryption key, and often times additional information about that key. Websites such as used for banking and other services frequently use them to allow you to establish a secure connection with their servers.
 
+**Small Message Service (SMS)**
+Also known as a text message, SMS is generally an insecure way to send information to other people. It is relatively easy  for those with technical equipment and know how to intercept cellular network traffic. In addition many recent situations have shown that it is even easier to convince a cell company to hand over control of an account or to just steal a handset. SMS should especially be avoided as a second factor for authentication (See Two Factor Authentication below) for these reasons.
+
 **SPF records**  
 Sender Policy Framework (SPF) is a system that allows you to tell others what servers and services are allowed to send email for your organization's domain name. Setting up this record requires the assistance of your DNS provider and can have unintended negative consequences for your email delivery if not properly done.  
 
+**Two Factor or Multifactor Authentication**
+A way of identifying yourself to a computer or service that includes two or more items -- often something you have (like a phone or security key) and something you know (like a password). Commonly one of those methods is an cell phone text message (Small Message Service above) however this is ****no longer recommended and should be avoided due to the ease of gaining access to other people's cell service, phone or SIM card***.   
+
 **Virtual Private Network (VPN)**  
 A connection between computers or devices that allows them to exchange information in an encrypted form. This can allow you to both “tunnel out of” a network you don't trust or to get you access to information on your office network from someplace else on the Internet.
 
@@ -54,4 +66,4 @@ A connection between computers or devices that allows them to exchange informati
 A wireless access point (WAP) is a piece of hardware configured to host a wireless network. In many small networks the WAP will also be a firewall separating the network from the rest of the Internet.  
 
 **WEP, WPA and WPA2**  
-All are methods of encrypting wireless network traffic between a device like a computer or phone and a wireless access point. WEP is an older encryption method and it is far less secure than WPA and WPA2, which are newer methods.
+All are methods of encrypting wireless network traffic between a device like a computer or phone and a wireless access point. WEP is an older encryption method and it is far less secure than WPA and its more secure successor WPA2. Always choose WPA2 when possible.
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..fd662a7
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,428 @@
+Attribution-ShareAlike 4.0 International
+
+=======================================================================
+
+Creative Commons Corporation ("Creative Commons") is not a law firm and
+does not provide legal services or legal advice. Distribution of
+Creative Commons public licenses does not create a lawyer-client or
+other relationship. Creative Commons makes its licenses and related
+information available on an "as-is" basis. Creative Commons gives no
+warranties regarding its licenses, any material licensed under their
+terms and conditions, or any related information. Creative Commons
+disclaims all liability for damages resulting from their use to the
+fullest extent possible.
+
+Using Creative Commons Public Licenses
+
+Creative Commons public licenses provide a standard set of terms and
+conditions that creators and other rights holders may use to share
+original works of authorship and other material subject to copyright
+and certain other rights specified in the public license below. The
+following considerations are for informational purposes only, are not
+exhaustive, and do not form part of our licenses.
+
+     Considerations for licensors: Our public licenses are
+     intended for use by those authorized to give the public
+     permission to use material in ways otherwise restricted by
+     copyright and certain other rights. Our licenses are
+     irrevocable. Licensors should read and understand the terms
+     and conditions of the license they choose before applying it.
+     Licensors should also secure all rights necessary before
+     applying our licenses so that the public can reuse the
+     material as expected. Licensors should clearly mark any
+     material not subject to the license. This includes other CC-
+     licensed material, or material used under an exception or
+     limitation to copyright. More considerations for licensors:
+	wiki.creativecommons.org/Considerations_for_licensors
+
+     Considerations for the public: By using one of our public
+     licenses, a licensor grants the public permission to use the
+     licensed material under specified terms and conditions. If
+     the licensor's permission is not necessary for any reason--for
+     example, because of any applicable exception or limitation to
+     copyright--then that use is not regulated by the license. Our
+     licenses grant only permissions under copyright and certain
+     other rights that a licensor has authority to grant. Use of
+     the licensed material may still be restricted for other
+     reasons, including because others have copyright or other
+     rights in the material. A licensor may make special requests,
+     such as asking that all changes be marked or described.
+     Although not required by our licenses, you are encouraged to
+     respect those requests where reasonable. More_considerations
+     for the public: 
+	wiki.creativecommons.org/Considerations_for_licensees
+
+=======================================================================
+
+Creative Commons Attribution-ShareAlike 4.0 International Public
+License
+
+By exercising the Licensed Rights (defined below), You accept and agree
+to be bound by the terms and conditions of this Creative Commons
+Attribution-ShareAlike 4.0 International Public License ("Public
+License"). To the extent this Public License may be interpreted as a
+contract, You are granted the Licensed Rights in consideration of Your
+acceptance of these terms and conditions, and the Licensor grants You
+such rights in consideration of benefits the Licensor receives from
+making the Licensed Material available under these terms and
+conditions.
+
+
+Section 1 -- Definitions.
+
+  a. Adapted Material means material subject to Copyright and Similar
+     Rights that is derived from or based upon the Licensed Material
+     and in which the Licensed Material is translated, altered,
+     arranged, transformed, or otherwise modified in a manner requiring
+     permission under the Copyright and Similar Rights held by the
+     Licensor. For purposes of this Public License, where the Licensed
+     Material is a musical work, performance, or sound recording,
+     Adapted Material is always produced where the Licensed Material is
+     synched in timed relation with a moving image.
+
+  b. Adapter's License means the license You apply to Your Copyright
+     and Similar Rights in Your contributions to Adapted Material in
+     accordance with the terms and conditions of this Public License.
+
+  c. BY-SA Compatible License means a license listed at
+     creativecommons.org/compatiblelicenses, approved by Creative
+     Commons as essentially the equivalent of this Public License.
+
+  d. Copyright and Similar Rights means copyright and/or similar rights
+     closely related to copyright including, without limitation,
+     performance, broadcast, sound recording, and Sui Generis Database
+     Rights, without regard to how the rights are labeled or
+     categorized. For purposes of this Public License, the rights
+     specified in Section 2(b)(1)-(2) are not Copyright and Similar
+     Rights.
+
+  e. Effective Technological Measures means those measures that, in the
+     absence of proper authority, may not be circumvented under laws
+     fulfilling obligations under Article 11 of the WIPO Copyright
+     Treaty adopted on December 20, 1996, and/or similar international
+     agreements.
+
+  f. Exceptions and Limitations means fair use, fair dealing, and/or
+     any other exception or limitation to Copyright and Similar Rights
+     that applies to Your use of the Licensed Material.
+
+  g. License Elements means the license attributes listed in the name
+     of a Creative Commons Public License. The License Elements of this
+     Public License are Attribution and ShareAlike.
+
+  h. Licensed Material means the artistic or literary work, database,
+     or other material to which the Licensor applied this Public
+     License.
+
+  i. Licensed Rights means the rights granted to You subject to the
+     terms and conditions of this Public License, which are limited to
+     all Copyright and Similar Rights that apply to Your use of the
+     Licensed Material and that the Licensor has authority to license.
+
+  j. Licensor means the individual(s) or entity(ies) granting rights
+     under this Public License.
+
+  k. Share means to provide material to the public by any means or
+     process that requires permission under the Licensed Rights, such
+     as reproduction, public display, public performance, distribution,
+     dissemination, communication, or importation, and to make material
+     available to the public including in ways that members of the
+     public may access the material from a place and at a time
+     individually chosen by them.
+
+  l. Sui Generis Database Rights means rights other than copyright
+     resulting from Directive 96/9/EC of the European Parliament and of
+     the Council of 11 March 1996 on the legal protection of databases,
+     as amended and/or succeeded, as well as other essentially
+     equivalent rights anywhere in the world.
+
+  m. You means the individual or entity exercising the Licensed Rights
+     under this Public License. Your has a corresponding meaning.
+
+
+Section 2 -- Scope.
+
+  a. License grant.
+
+       1. Subject to the terms and conditions of this Public License,
+          the Licensor hereby grants You a worldwide, royalty-free,
+          non-sublicensable, non-exclusive, irrevocable license to
+          exercise the Licensed Rights in the Licensed Material to:
+
+            a. reproduce and Share the Licensed Material, in whole or
+               in part; and
+
+            b. produce, reproduce, and Share Adapted Material.
+
+       2. Exceptions and Limitations. For the avoidance of doubt, where
+          Exceptions and Limitations apply to Your use, this Public
+          License does not apply, and You do not need to comply with
+          its terms and conditions.
+
+       3. Term. The term of this Public License is specified in Section
+          6(a).
+
+       4. Media and formats; technical modifications allowed. The
+          Licensor authorizes You to exercise the Licensed Rights in
+          all media and formats whether now known or hereafter created,
+          and to make technical modifications necessary to do so. The
+          Licensor waives and/or agrees not to assert any right or
+          authority to forbid You from making technical modifications
+          necessary to exercise the Licensed Rights, including
+          technical modifications necessary to circumvent Effective
+          Technological Measures. For purposes of this Public License,
+          simply making modifications authorized by this Section 2(a)
+          (4) never produces Adapted Material.
+
+       5. Downstream recipients.
+
+            a. Offer from the Licensor -- Licensed Material. Every
+               recipient of the Licensed Material automatically
+               receives an offer from the Licensor to exercise the
+               Licensed Rights under the terms and conditions of this
+               Public License.
+
+            b. Additional offer from the Licensor -- Adapted Material.
+               Every recipient of Adapted Material from You
+               automatically receives an offer from the Licensor to
+               exercise the Licensed Rights in the Adapted Material
+               under the conditions of the Adapter's License You apply.
+
+            c. No downstream restrictions. You may not offer or impose
+               any additional or different terms or conditions on, or
+               apply any Effective Technological Measures to, the
+               Licensed Material if doing so restricts exercise of the
+               Licensed Rights by any recipient of the Licensed
+               Material.
+
+       6. No endorsement. Nothing in this Public License constitutes or
+          may be construed as permission to assert or imply that You
+          are, or that Your use of the Licensed Material is, connected
+          with, or sponsored, endorsed, or granted official status by,
+          the Licensor or others designated to receive attribution as
+          provided in Section 3(a)(1)(A)(i).
+
+  b. Other rights.
+
+       1. Moral rights, such as the right of integrity, are not
+          licensed under this Public License, nor are publicity,
+          privacy, and/or other similar personality rights; however, to
+          the extent possible, the Licensor waives and/or agrees not to
+          assert any such rights held by the Licensor to the limited
+          extent necessary to allow You to exercise the Licensed
+          Rights, but not otherwise.
+
+       2. Patent and trademark rights are not licensed under this
+          Public License.
+
+       3. To the extent possible, the Licensor waives any right to
+          collect royalties from You for the exercise of the Licensed
+          Rights, whether directly or through a collecting society
+          under any voluntary or waivable statutory or compulsory
+          licensing scheme. In all other cases the Licensor expressly
+          reserves any right to collect such royalties.
+
+
+Section 3 -- License Conditions.
+
+Your exercise of the Licensed Rights is expressly made subject to the
+following conditions.
+
+  a. Attribution.
+
+       1. If You Share the Licensed Material (including in modified
+          form), You must:
+
+            a. retain the following if it is supplied by the Licensor
+               with the Licensed Material:
+
+                 i. identification of the creator(s) of the Licensed
+                    Material and any others designated to receive
+                    attribution, in any reasonable manner requested by
+                    the Licensor (including by pseudonym if
+                    designated);
+
+                ii. a copyright notice;
+
+               iii. a notice that refers to this Public License;
+
+                iv. a notice that refers to the disclaimer of
+                    warranties;
+
+                 v. a URI or hyperlink to the Licensed Material to the
+                    extent reasonably practicable;
+
+            b. indicate if You modified the Licensed Material and
+               retain an indication of any previous modifications; and
+
+            c. indicate the Licensed Material is licensed under this
+               Public License, and include the text of, or the URI or
+               hyperlink to, this Public License.
+
+       2. You may satisfy the conditions in Section 3(a)(1) in any
+          reasonable manner based on the medium, means, and context in
+          which You Share the Licensed Material. For example, it may be
+          reasonable to satisfy the conditions by providing a URI or
+          hyperlink to a resource that includes the required
+          information.
+
+       3. If requested by the Licensor, You must remove any of the
+          information required by Section 3(a)(1)(A) to the extent
+          reasonably practicable.
+
+  b. ShareAlike.
+
+     In addition to the conditions in Section 3(a), if You Share
+     Adapted Material You produce, the following conditions also apply.
+
+       1. The Adapter's License You apply must be a Creative Commons
+          license with the same License Elements, this version or
+          later, or a BY-SA Compatible License.
+
+       2. You must include the text of, or the URI or hyperlink to, the
+          Adapter's License You apply. You may satisfy this condition
+          in any reasonable manner based on the medium, means, and
+          context in which You Share Adapted Material.
+
+       3. You may not offer or impose any additional or different terms
+          or conditions on, or apply any Effective Technological
+          Measures to, Adapted Material that restrict exercise of the
+          rights granted under the Adapter's License You apply.
+
+
+Section 4 -- Sui Generis Database Rights.
+
+Where the Licensed Rights include Sui Generis Database Rights that
+apply to Your use of the Licensed Material:
+
+  a. for the avoidance of doubt, Section 2(a)(1) grants You the right
+     to extract, reuse, reproduce, and Share all or a substantial
+     portion of the contents of the database;
+
+  b. if You include all or a substantial portion of the database
+     contents in a database in which You have Sui Generis Database
+     Rights, then the database in which You have Sui Generis Database
+     Rights (but not its individual contents) is Adapted Material,
+
+     including for purposes of Section 3(b); and
+  c. You must comply with the conditions in Section 3(a) if You Share
+     all or a substantial portion of the contents of the database.
+
+For the avoidance of doubt, this Section 4 supplements and does not
+replace Your obligations under this Public License where the Licensed
+Rights include other Copyright and Similar Rights.
+
+
+Section 5 -- Disclaimer of Warranties and Limitation of Liability.
+
+  a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
+     EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
+     AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
+     ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
+     IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
+     WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
+     PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
+     ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
+     KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
+     ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
+
+  b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
+     TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
+     NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
+     INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
+     COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
+     USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
+     ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
+     DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
+     IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
+
+  c. The disclaimer of warranties and limitation of liability provided
+     above shall be interpreted in a manner that, to the extent
+     possible, most closely approximates an absolute disclaimer and
+     waiver of all liability.
+
+
+Section 6 -- Term and Termination.
+
+  a. This Public License applies for the term of the Copyright and
+     Similar Rights licensed here. However, if You fail to comply with
+     this Public License, then Your rights under this Public License
+     terminate automatically.
+
+  b. Where Your right to use the Licensed Material has terminated under
+     Section 6(a), it reinstates:
+
+       1. automatically as of the date the violation is cured, provided
+          it is cured within 30 days of Your discovery of the
+          violation; or
+
+       2. upon express reinstatement by the Licensor.
+
+     For the avoidance of doubt, this Section 6(b) does not affect any
+     right the Licensor may have to seek remedies for Your violations
+     of this Public License.
+
+  c. For the avoidance of doubt, the Licensor may also offer the
+     Licensed Material under separate terms or conditions or stop
+     distributing the Licensed Material at any time; however, doing so
+     will not terminate this Public License.
+
+  d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
+     License.
+
+
+Section 7 -- Other Terms and Conditions.
+
+  a. The Licensor shall not be bound by any additional or different
+     terms or conditions communicated by You unless expressly agreed.
+
+  b. Any arrangements, understandings, or agreements regarding the
+     Licensed Material not stated herein are separate from and
+     independent of the terms and conditions of this Public License.
+
+
+Section 8 -- Interpretation.
+
+  a. For the avoidance of doubt, this Public License does not, and
+     shall not be interpreted to, reduce, limit, restrict, or impose
+     conditions on any use of the Licensed Material that could lawfully
+     be made without permission under this Public License.
+
+  b. To the extent possible, if any provision of this Public License is
+     deemed unenforceable, it shall be automatically reformed to the
+     minimum extent necessary to make it enforceable. If the provision
+     cannot be reformed, it shall be severed from this Public License
+     without affecting the enforceability of the remaining terms and
+     conditions.
+
+  c. No term or condition of this Public License will be waived and no
+     failure to comply consented to unless expressly agreed to by the
+     Licensor.
+
+  d. Nothing in this Public License constitutes or may be interpreted
+     as a limitation upon, or waiver of, any privileges and immunities
+     that apply to the Licensor or You, including from the legal
+     processes of any jurisdiction or authority.
+
+
+=======================================================================
+
+Creative Commons is not a party to its public
+licenses. Notwithstanding, Creative Commons may elect to apply one of
+its public licenses to material it publishes and in those instances
+will be considered the “Licensor.” The text of the Creative Commons
+public licenses is dedicated to the public domain under the CC0 Public
+Domain Dedication. Except for the limited purpose of indicating that
+material is shared under a Creative Commons public license or as
+otherwise permitted by the Creative Commons policies published at
+creativecommons.org/policies, Creative Commons does not authorize the
+use of the trademark "Creative Commons" or any other trademark or logo
+of Creative Commons without its prior written consent including,
+without limitation, in connection with any unauthorized modifications
+to any of its public licenses or any other arrangements,
+understandings, or agreements concerning use of licensed material. For
+the avoidance of doubt, this paragraph does not form part of the
+public licenses.
+
+Creative Commons may be contacted at creativecommons.org.
+
diff --git a/README.md b/README.md
index 867b367..a592497 100644
--- a/README.md
+++ b/README.md
@@ -1,33 +1,45 @@
 
 # Introduction  
-The documents in this repository comprise a set of digital security checklists for use by US based non-profit organizations with a focus on human practice and organizational management. One checklist is oriented towards assessing an organization's readiness to take on this type of work. Additional documents represent framing information and a glossary.  
+The documents in this repository comprise a set of digital security checklists for use by US based non-profit organizations with a focus on human practice and organizational management. They were created by [Information Ecology](https://iecology.org), an Oakland, California based consultancy focusing on technology management and capacity building for progressive organizations for use in the [Weathering The Storms project of RoadMap Consulting](https://roadmapconsulting.org/resource/weathering-the-storm/). They have been peer reviewed for readability and accuracy by both technical and operational professionals from the global non-profit community.
 
-**They are not appropriate for use in other countries without a thorough review and update to reflect conditions in that environment. It is not our fault if you do not heed this important concern, but would be happy to discuss updating the content in this way. [Contact us?]("https://iecology.org/contact")**
+This document set includes [a tool](2_readiness_assessment_tool.md) for assessing an organization's existing capacities and areas to develop in order to successfully take on this type of work which is recommended as a first step for all organizations. Additional documents represent framing information and a glossary both of which are also recommended for all users of these checklists wishing to understand how to use them. This content is released under a [Creative Commons Attribution-Share Alike License](https://creativecommons.org/licenses/by-sa/4.0/) and can be remixed, translated or amended freely as long as shared in turn and original documents attributed to Information Ecology.
+
+**These documents are not considered appropriate for use in other countries or in contexts beyond what is named in the  [Introduction](1_checklist_introduction.md) without a thorough review and update to reflect conditions in that environment. It is not our fault if you do not heed this important concern, but would be happy to support anyone wishing  updating the content in this way. [Contact us?](https://iecology.org/contact)**
 
 
 # Contents
 1. [Introduction](1_checklist_introduction.md)
 Framing remarks about the purpose, assumptions and limitations of these documents.  
 
-2. [Readiness Assessment](2_readiness_assessment.md)
-A tool for assessing whether an organization has pressing technology challenges that should be resolved to establish baseline security controls and practice before attempting to increase digital security levels through other means.
+2. [Readiness Assessment Tool](2_readiness_assessment_tool.md)
+A tool for assessing whether an organization has the requisite baseline capacities needed to successfully take on new digital security practices. Any challenges identified should be met before attempting to increase digital security levels through other means.
 
 3. [Legend](3_legend.md)
 What the symbols in these documents mean.
 
-4. [Email Safety Checklist](4_email_safety_checklist.md)
-A checklist of tasks related to safe(r) use of Email
+4. [Device Security Checklist](4_device_security_checklist.md)
+All security depends on the ability to control your devices. This checklist helps you do that.
 
 5. [Password and Authentication Checklist](5_authentication_checklist.md)  
-A checklist of tasks related to improving password and authentication practices.
+A checklist of tasks related to improving the way you identify, or "authenticate" yourself to the services you use, including password management practices.
 
 6. [Public Wireless Checklist](6_public_wireless_checklist.md)
 A checklist of tasks related to improving security levels when depending on public wireless networks
 
-7. [Glossary](7_glossary.md)
+7. [Email Safety Checklist](7_email_safety_checklist.md)
+A checklist of tasks related to safe(r) use of Email.
+
+8. [GSuite Security Checklist](8_gsuite_security_checklist.md)
+A checklist to help you setup and use the security controls in Google's domain based services.
+
+9. [Glossary](7_glossary.md)
 A glossary defining the technical terms used in these documents in as non-technical language as possible
 
 ## Finally...
-These documents could not exist without the support of a large group of readers, whose technical and operational review and feedback tuned these document, as well as [RoadMap Consulting](https://roadmapconsulting.org) who sponsored the project and with whom we are actively using these as a tool to support our clients and communities.
+These documents could not exist without the support of a large group of readers, whose technical and operational peer review and feedback tuned these document, as well as the financial support of [RoadMap Consulting](https://roadmapconsulting.org) with whom we are actively using these as a tool to support our clients and communities.
+
+**This work is dedicated to to the humans and organizations working on the front lines of important change making work everywhere.**
 
-**Our gratitude for these humans and organizations working on the front lines of important change making work is immense.**
+This content is licensed under a [Creative Commons Attribution-ShareAlike 4.0 International License](https://creativecommons.org/licenses/by-sa/4.0/)
+![Creative Commons Attribution-ShareAlike 4.0 International License Image](https://i.creativecommons.org/l/by-sa/4.0/88x31.png)"
+See [license file](LICENSE) for full text of licence terms.
-- 
GitLab