diff --git a/windows/security/threat-protection/windows-security-baselines/windows-security-configuration-framework.md b/windows/security/threat-protection/windows-security-baselines/windows-security-configuration-framework.md
index fbd3d594b6..06fc71b69e 100644
--- a/windows/security/threat-protection/windows-security-baselines/windows-security-configuration-framework.md
+++ b/windows/security/threat-protection/windows-security-baselines/windows-security-configuration-framework.md
@@ -14,7 +14,7 @@ ms.topic: conceptual
 ms.date: 04/05/2018
 ---
 
-# Windows Security Configuration Framework
+# Introducing the SECCON Framework
 
 **Applies to**  
 
@@ -22,5 +22,38 @@ ms.date: 04/05/2018
 -   Windows Server 2016 
 -   Office 2016 
 
+Security configuration is complex. With thousands of group policies available in Windows, choosing the “best” setting is difficult. 
+It’s not always obvious which permutations of policies are required to implement a complete scenario, and there are often unintended consequences of some security lockdowns.
+
+Because of this, with each release of Windows, Microsoft publishes [Windows Security Baselines](https://docs.microsoft.com/windows/security/threat-protection/windows-security-baselines), an industry-standard configuration that is broadly known and well-tested. 
+However, many organizations have discovered that this baseline sets a very high bar. 
+While appropriate for organizations with very high security needs such as those persistently targeted by Advanced Persistent Threats, some organizations have found that the cost of navigating the potential compatibility impact of this configuration is prohibitively expensive given their risk appetite. 
+They can’t justify the investment in that very high level of security with an ROI. 
+Assuch, Microsoft is introducing a new taxonomy for Security Configurations for Windows 10: The SECCON Baselines.
+
+The SECCON Baselines organize devices into one of 5 distinct security configurations:
+
+![SECON Framework](./../images/seccon-framework.png)
+
+The SECCON Baselines divide configuration into Productivity Devices and Privileged Access Workstations. This document will focus on Productivity Devices
+(SECCON 5, 4, and 3). 
+Microsoft’s current guidance on [Privileged Access Workstations](http://aka.ms/privsec) are part of the [Securing Privileged Access roadmap](http://aka.ms/privsec).
+
+Microsoft recommends reviewing and categorizing your devices, and then configuring them using the prescriptive guidance for that SECCON level. 
+SECCON 5 should be considered the minimum baseline for an enterprise device, and Microsoft recommends increasing the protection based on both threat environment and risk appetite.
+
+## Security Control Classification
+
+The recommendations are grouped into three categories:
+
+![Security Control Classifications](./../images/security-control-classification.png)
+
+
+## Security Control Deployment Methodologies
+
+The way Microsoft recommends implementing these controls depends on the
+auditability of the control–there are two primary methodologies:
+
+![Security Control Deployment methodologies](./../images/security-control-deployment-methodologies.png)