Home » Security Bloggers Network » Introduction to Windows 10 Security

Introduction to Windows 10 Security

Introduction

Information security is becoming stronger, tighter and more effective. Microsoft is following this consumer trend, offering improved security within its Windows 10 operating system. 

This article will detail the current security functionality offered by Windows 10 and will introduce the new security configuration framework SECCON, Microsoft BitLocker and a slew of notable Windows Defender features including SmartScreen, Application Guard, Device Guard, Exploit Guard and Credential Guard, as well as a look at the new changes to Windows 10 security introduced in the 1903 feature release.

New security configuration framework

The most notable Windows 10 security feature is the new security configuration framework that Microsoft called SECCON (which is a play on the United States Department of Defense’s defense readiness condition DEFCON framework). 

Like DEFCON, SECCON uses five levels of readiness — ranging from the strictest security measures in Level 1 and regular security measures in Level 5. Below is a summary of each of these levels of cyberdefense readiness.

• Level 1: Administrator Workstation: Considered one of the most privileged access workstation levels along with Level 2, Level 1 faces the highest risk of data theft, alteration and service interruption
• Level 2: DevOps Workstation: Intended for developers and testers, this level is a target for credential theft attacks and supply chain attacks looking for access to systems and servers with high-value sensitive information
• Level 3: Enterprise VIP Security: Recommended for organizations with a sophisticated or large security team or organization users that face a uniquely high security risk. Security configurations for this level are complex and recommendations can take longer to fully implement than other levels (sometimes over 90 days)
• Level 4: Enterprise High Security: Intended for users with access to sensitive information. Controls may impact on app compatibility and will often need to use an audit-configure-enforce workflow (Read more...)