DOCSLIB.ORG

577741-Remote Credencial Guard.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
577741-Remote Credencial Guard.Pdf Agenda • A brief Introduction • Prerequisites • A very, very short Kerberos Introduction • What are Credentials? • Credential Guard • Restricted Admin • Remote Credential Guard • MS-CSSP • MS-RDPEAR What I Expect You to Already Know •Kerberos •Restricted Admin Mode •Credential Security Support Provider (CredSSP) Protocol •RPC Marshalling & ASN1 Serialization A Brief Introduction • Remote Credential Guard is the RDP version of Credential Guard • In Credential Guard, Virtualized Environment stores the Credentials • In Remote Credential Guard, instead of Virtualized Environment, RDP Client stores the Clear Credentials • In Credential Guard, LSASS exchange messages with Virtualized Environment when it needs a new ticket or authenticate message to login to a service • RDP server exchanges similar kind of messages with LSASS on the client when it needs a new ticket to authenticate to a service Demo of Remote Credential Guard What Problem We’re trying to Solve? • RDP requires User Credentials to create a User Session on Remote Target • CredSSP (NLA) is employed to ferry the Clear Text Credentials to Remote Target • While the Credentials in transit are doubly encrypted, they are decrypted on the Remote Target to pass to LsaLongonUser API • If the Remote Target is compromised, an attacker can steal the Credentials • Remote Credentials Guard fixes these issues by sending encrypted session key1 and TGT instead of clear text username and password 1. RCG also send encrypted NTOWF which is used to login to services that don’t support Kerberos A very, very short refresher to Kerberos • Require 3 entities to work: client, service, KDC1 (also hosts TGS2) • Client and Service both share long term secrets with KDC (password derived hashes a.k.a long term keys) • Client requests a ticket to authenticate to a service • At the time of logging on, client acquires a ticket for a TGS • The ticket for TGS is called TGT (Ticket Granting Ticket) • Once a TGT is issued, the long-term key is destroyed on client • TGT and associated session key are now the credentials. These need to be protected as they are used to request tickets for other services e.g. SMB (Server Message Block a.k.a File Sharing) 1. Key Distribution Center 2. Ticket Granting Service What are Credentials? • Username & Passwords • Certificates/key pairs • Derived Credentials • NTLM OWF hash of Password • Kerberos long term key • Kerberos TGT Session Key • Kerberos Service Ticket Session Key Credential Guard (CG) • An environment in which LSASS only stores Encrypted Credentials • Credentials are exposed for a very small amount of time when a user is logging in. • After that, the LSASS stores the encrypted credentials and a virtualized environment stores the encryption keys • Whenever LSASS needs to use credentials, it will communicate with virtualized environment • All communication between LSASS and virtualized environment is through RPC. Every message is signed and, as a result, no chance of tampering • Virtualized Environment will do encryption or decryption, since it has the keys (like TPM or SmartCard do). Restricted Admin • A mode for RDP where no credentials are sent to RDP server • The user is logged in without any credentials if they are an admin on the RDP host • The login session is running under machine account. • Cannot login to any other service from the RDP host • Prevents “pass the hash” attacks. • As name implies, it is very restricting. Remote Credential Guard • A improvement on Restricted Admin Mode • Encrypted Credentials are sent to RDP server (like LSASS in CG) • Only client can decrypt/encrypt the credentials (like virtualized environment in CG) • When the user in RDP session needs to login to another service, it send encrypted credentials to client with a specific requests • Client decrypts credentials, generates the requested data and sends it back to RDP server. • Server pass along the received data to service and usual authentication then happens. Requirement for Remote Guard • Client and Server must be domain joined • Client and Server must be running Windows 10 v.1607/WS2016 or later • On server, add DWORD DisableRestrictedAdmin and set it to 0 in the registry HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa • Only classical mstsc supports remote guard (not the store version) • On client: enable GP or on command line by running C:>Mstsc [.rdp filename] /remoteGuard • More details here: https://docs.microsoft.com/en-us/windows/access-protection/remote-credential-guard User’s Device Remote Remote Host Desktop User’s Session Connection User’s Session Credentials TGT NTLM NTOWF TGT key NTOWF Key Kerberos NTLM TGT NTOWF TGT key Kerberos TGT TGT Key User’s Device Remote Host TGS TGT key User’s Session User’s Session exchange Authenticator TGS-REP NTLM TGT key NTOWF Key Unsigned TGS-REQ Kerberos NTLM Signed TGS-REQ File TGT server TGT key TGT key Kerberos User’s TGS-REP ST Session TGT Authenticator ST Key TGT Key TGS-REP Changes to MS-CSSP • MS-CSSP is augmented to send encrypted credentials to RDP server • New ASN1 data type is introduced to carry the payload called TSRemoteGuardCreds TSRemoteGuardCreds ::= SEQUENCE{ logonCred [0] TSRemoteGuardPackageCred, supplementalCreds [1] SEQUENCE OF TSRemoteGuardPackageCred OPTIONAL, } TSRemoteGuardPackageCred ::= SEQUENCE{ packageName [0] OCTET STRING, credBuffer [1] OCTET STRING, } TSRemoteGuardCreds on the Wire 00000000: 30 82 0B 3E ; SEQUENCE (2878 bytes) 00000004: A0 82 0A 53 ; [0] (2643 bytes) 00000008: | 30 82 0A 4F ; SEQUENCE (2639 bytes) logonCred 0000000c: | A0 12 ; [0] (18 bytes) 0000000e: | | 04 10 ; OCTETSTRING (16 bytes) 00000010: | | 4B 00 65 Kerberos00 72 00 62 00 65 00 72 00 6F 00 73 00 ; K.e.r.b.e.r.o.s. 00000020: | A1 82 0A 37 ; [1] (2615 bytes) 00000024: | 04 82 0A 33 ; OCTETSTRING (2611 bytes) --------------------------------------Kerberos CredBuffer--------------------------------------- 00000a5b: A1 81 E4 ; [1] (228 bytes) supplementalCreds 00000a5e: 30 81 E1 ; SEQUENCE (225 bytes) 00000a61: 30 81 DE ; SEQUENCE (222 bytes) 00000a64: A0 0A ; [0] (10 bytes) 00000a66: | 04 08 ; OCTETSTRING (8 bytes) 00000a68: | 4E 00 54 00 NTLM4C 00 4D 00 ; N.T.L.M. 00000a70: A1 81 CF ; [1] (207 bytes) 00000a73: 04 81 CC ; OCTETSTRING (204 bytes) ------------------------------------------NTLM CredBuffer--------------------------------------- logonCred • Kerberos credentials are RPC marshalled KERB_TICKET_LOGON structure https://msdn.microsoft.com/en-us/library/windows/desktop/aa378143(v=vs.85).aspx typedef struct _KERB_TICKET_LOGON { KERB_LOGON_SUBMIT_TYPE MessageType; ULONG Flags; ULONG ServiceTicketLength; ULONG TicketGrantingTicketLength; PUCHAR ServiceTicket; PUCHAR TicketGrantingTicket; } KERB_TICKET_LOGON, *PKERB_TICKET_LOGON; TicketGrantingTicket • TicketGrantingTicket field of KERB_TICKET_LOGON structure is actually a KRB_CRED message • KRB_CRED message is specified in RFC4120, section 5.8.1 • The enc-part contains KERB_RPC_ENCRYPTION_KEY specified in MS-RDPEAR section 2.2.1.2.1 supplementalCreds • SupplementalCreds contain MSV1_0_REMOTE_ENCRYPTED_SECRETS • MSV1_0_REMOTE_ENCRYPTED_SECRETS are specified in MS-RDPEAR section 2.2.1.3.1 • These are encrypted secrets for NTLM • They are used in case of logging in to a service when use of Kerberos is not possible (e.g. due to absence of SPN) New Protocol MS-RDPEAR • Since the target does not possess the TGT session key, it needs help from the client to sign, encrypt and decrypt messages. • A new protocol is created to allow target to send data to client for cryptographic functions involving TGT session key. • The data is exchanged on a dynamic virtual channel (DVC) named Microsoft::Windows::RDS::AuthRedirection • Target Server acts as MS-RDPEAR client and initiate request • RDP client acts as MS-RDPEAR server and carry out requested cryptographic operations. Example Exchange of Messages For More Information • Credential Guard https://channel9.msdn.com/events/Ignite/Microsoft-Ignite-Orlando-2017/BRK2077 • Remote Credential Guard https://docs.microsoft.com/en-us/windows/security/identity-protection/remote-credential-guard • RFC4120 http://www.rfc-editor.org/rfc/rfc4120.txt.
Load more

Recommended publications
  • Guide to Hardening Windows 10 Technical Guide
    NOVEMBER 2020 Guide to Hardening Windows 10 For Administrators, Developers and Office Workers TABLE OF CONTENTS Introduction .......................................................................................................................... 4 Prerequisites ............................................................................................................................ 4 User roles ................................................................................................................................. 4 EFI (BIOS) Configuration ...................................................................................................... 5 To be enabled: ......................................................................................................................... 5 To be disabled: ......................................................................................................................... 5 Windows Defender Firewall .................................................................................................. 6 Enable logging of dropped packets ............................................................................................. 6 Disable enforcement of local rules and disable notifications .......................................................... 7 Block outbound connections by default ....................................................................................... 8 Secure potentially vulnerable protocols ......................................................................................
    [Show full text]
  • Implementing Remote Credential Guard and Remote Admin Mode on Domain-Joined Windows 10 Clients
    INF258x: Implementing Remote Credential Guard and Remote Admin mode on Domain-joined Windows 10 Clients Estimated Time: 30 minutes You have a domain-joined Windows 10 client computer. You plan to take advantage of the Remote Desktop Credential Guard and Restrict Admin mode to protect credentials during Remote Desktop sessions between Windows 10 client and Windows Server 2016 computers. Objectives After completing this lab, students will be able to: • Implement Remote Credential Guard. • Implement the Restricted Admin mode. • Verify functionality of Remote Credential Guard and the Restricted Admin mode. Lab environment The lab consists of the following computers: • LON-DC1 – a Windows Server 2016 domain controller in the adatum.com single-domain forest. • LON-SVR1 – a Windows Server 2016 domain member server • LON-CL1 – a Windows 10 Pro or Enterprise version 1607 (or newer) domain member computer with Remote Server Administration Tools for Windows 10 All computers have Windows PowerShell Remoting enabled and have Internet connectivity Remote Desktop connections protected with Credential Guard have the following characteristics: • Require Windows 10 version 1607 (or newer) or Windows Server 2016 • Enforce of Kerberos authentication (NTLM is not allowed). • Require that both computers (a Remote Desktop client and a Remote Desktop host) are members of the same Active Directory domain or trusted Active Directory domains (Kerberos is enforced) • Support connecting with non-Administrative credentials (as a member of the Remote Desktop Users group)
    [Show full text]
  • Windows 10 Enterprise E3 in CSP - Windows Deployment | Microsoft Docs
    07/01/2020 Windows 10 Enterprise E3 in CSP - Windows Deployment | Microsoft Docs Windows 10 Enterprise E3 in CSP 08/23/2017 • 16 minutes to read • +5 In this article Compare Windows 10 Pro and Enterprise editions Deployment of Windows 10 Enterprise E3 licenses Deploy Windows 10 Enterprise features Related topics Windows 10 Enterprise E3 launched in the Cloud Solution Provider (CSP) channel on September 1, 2016. Windows 10 Enterprise E3 in CSP is a new offering that delivers, by subscription, exclusive features reserved for Windows 10 Enterprise edition. This offering is available through the Cloud Solution Provider (CSP) channel via the Partner Center as an online service. Windows 10 Enterprise E3 in CSP provides a flexible, per- user subscription for small- and medium-sized organizations (from one to hundreds of users). To take advantage of this offering, you must have the following: Windows 10 Pro, version 1607 (Windows 10 Anniversary Update) or later, installed and activated, on the devices to be upgraded Azure Active Directory (Azure AD) available for identity management Starting with Windows 10, version 1607 (Windows 10 Anniversary Update), you can move from Windows 10 Pro to Windows 10 Enterprise more easily than ever before— no keys and no reboots. After one of your users enters the Azure AD credentials associated with a Windows 10 Enterprise E3 license, the operating system turns from Windows 10 Pro to Windows 10 Enterprise and all the appropriate Windows 10 Enterprise features are unlocked. When a subscription license expires or is transferred to another user, the Windows 10 Enterprise device seamlessly steps back down to Windows 10 Pro.
    [Show full text]
  • Feature Description
    NTLM Feature Description UPDATED: 19 March 2021 NTLM Copyright Notices Copyright © 2002-2021 Kemp Technologies, Inc. All rights reserved. Kemp Technologies and the Kemp Technologies logo are registered trademarks of Kemp Technologies, Inc. Kemp Technologies, Inc. reserves all ownership rights for the LoadMaster and Kemp 360 product line including software and documentation. Used, under license, U.S. Patent Nos. 6,473,802, 6,374,300, 8,392,563, 8,103,770, 7,831,712, 7,606,912, 7,346,695, 7,287,084 and 6,970,933 kemp.ax 2 Copyright 2002-2021, Kemp Technologies, All Rights Reserved NTLM Table of Contents 1 Introduction 4 1.1 Document Purpose 6 1.2 Intended Audience 6 1.3 Related Firmware Version 6 2 Configure NTLM Authentication 7 2.1 Configure Internet Options on the Client Machine 7 2.2 Configure the LoadMaster 11 2.2.1 Enable NTLM Proxy Mode 13 2.2.2 Configure the Server Side SSO Domain 13 2.2.3 Configure the Client Side SSO Domain 15 2.2.4 Configure the Virtual Service 15 2.3 Configure Firefox to Allow NTLM (if needed) 17 2.4 Troubleshooting 18 References 19 Last Updated Date 20 kemp.ax 3 Copyright 2002-2021, Kemp Technologies, All Rights Reserved NTLM 1 Introduction 1 Introduction NT LAN Manager (NTLM) is a Windows Challenge/Response authentication protocol that is often used on networks that include systems running the Windows operating system and Active Directory. Kerberos authentication adds greater security than NTLM systems on a network and provides Windows-based systems with an integrated single sign-on (SSO) mechanism.
    [Show full text]
  • Implementing Microsoft Credential Guard for Iso 27001, Pci, and Fedramp
    IMPLEMENTING MICROSOFT CREDENTIAL GUARD FOR ISO 27001, PCI, AND FEDRAMP North America | Latin America | Europe 877.224.8077 | [email protected] | coalfire.com Coalfiresm and CoalfireOnesm are registered service marks of Coalfire Systems, Inc. All rights reserved. INTRODUCTION The threat of a cyber-attack is a constant factor all organizations must consider when developing their information security posture. A particular area of concern is the exploitation of information system derived domain credentials and credential artifacts, which present attackers the opportunity to pass-the-hash or pass-the-ticket with derived domain credentials such as NTLM password hashes or Kerberos tickets. Credential Guard is a set of new security features for Windows Server 2016 and the Windows 10 operating system which helps organizations prevent derived credentials from being compromised by advanced attacks or from being exposed during certain authentication workflows. In order to help customers implement this new capability for compliance with ISO, PCI, or FedRAMP, Microsoft worked closely with Coalfire, a recognized third-party IT compliance firm, to define each security and compliance objective in relation to the capabilities of Credential Guard. In addition, Appendix A contains mappings between Credential Guard and the security control requirements present in ISO 27001, PCI DSS, and FedRAMP. OVERVIEW OF CREDENTIAL GUARD Credential Guard provides robust protections against local pass-the-hash or pass-the-ticket attacks on derived credentials by providing advanced virtualization-based isolation for certain authentication workflows within normal Windows system operation. Previously, during authentication workflows that required NTLM or Kerberos authentication, Windows stored derived credentials in process memory associated with the Local Security Authority (LSA).
    [Show full text]
  • Better Protection Begins at the OS
    Windows Server 2016 Security Better protection begins at the OS 1 Contents Getting out in front of cyber attacks 3 How attacks work 3 Windows Server 2016: Active defense and compliance 4 Protect credentials and limit administrator privileges 5 Credential Guard 5 Remote Credential Guard 5 Just Enough and Just-in-Time Administration 5 Secure OS to run your applications and infrastructure 7 Device Guard 7 Control Flow Guard 7 Windows Defender 8 Enhanced security auditing 8 Secure virtualization 8 Shielded Virtual Machines 8 Host Guardian Service 10 Distributed network firewall using software-defined networking 10 Security for developers 11 Hyper-V containers 11 Nano Server 12 Conclusion 12 Windows Server begins at the OS 2016 Security: Better protection Getting out in front of cyber attacks n today’s business environment, cyber attacks file servers or locks employees out of their systems. Ihave become a normal occurrence for companies The attackers don’t even need to worry about of all sizes, across all industries. The attacker profile staying hidden on the network. has grown beyond independent actors, and now includes organized crime, nation states, and terror groups. These groups not only go after the biggest How attacks work companies to steal information for the biggest Most attackers use malware toolkits – available payoff, they are also focused on interrupting to anyone on the internet – to gain access to your businesses for profit or other malicious intent. network. Once inside, they immediately attempt Ransomware is another emerging threat used to to compromise administrator credentials, which disrupt business for financial gain. Attackers rely typically takes them 24 to 48 hours.
    [Show full text]
  • Securing the Path to Windows 10 How to Achieve the Benefits of Virtualization-Based Security Without a Hardware Refresh White Paper
    White Paper Securing the Path to Windows 10 How to Achieve the Benefits of Virtualization-based Security Without a Hardware Refresh White Paper Introduction “Bromium, a Microsoft partner, For enterprises the #1 reason to upgrade to Windows 10 is delivers hardware-enforced improved security, but the critical enhancements that rely on security to today’s deployed Windows endpoints. More hardware protection will be difficult to adopt until you buy importantly, Bromium enables new PCs. Bromium, a Microsoft partner, delivers hardware- IT organizations to easily upgrade existing PCs to Windows 10 with enforced security to today’s deployed Windows endpoints. More hardware-enforced security importantly, Bromium enables IT organizations to easily upgrade that extends the in-box security existing PCs to Windows 10 with hardware-enforced security that of Windows 10, without a hardware refresh, accelerating extends the in-box security of Windows 10, without a hardware Windows 10 rollouts.” refresh, accelerating Windows 10 rollouts. Windows 10 Security Windows 10 Enterprise promises many security enhancements over Windows 7 and 8, and introduces a family of hardware-assisted security technologies in Device Guard (DG). DG helps to ensure a secure boot, whitelists kernel code and offers credential protection and biometric authentication. The most important Figure 1: Windows 10 Device Guard SECURING THE PATH TO WINDOWS 10 2 White Paper “VBS uses endpoint CPU feature is virtualization-based security (VBS) which uses Hyper-V, enhanced with virtualization to isolate and elements of micro-virtualization, to help protect the operating system using protect two critical Windows hardware virtualization. The Bromium / Microsoft partnership aims to accelerate services: Windows Code Integrity service which protects the kernel the roadmap for VBS.
    [Show full text]
  • Intelligent Security
    Windows 10 Windows 10 Windows 10 Windows 10 Windows 10 Windows 10 commercial edition comparison Pro for Pro Business E3 E5 Workstation Per device Per device Per user Per user Per user Intelligent Security Threat protection Attack Surface Reduction ◑ ◑ ◕ ◕ ● Integrity enforcement of operating system boot up process Integrity enforcement of sensitive operating system components Advanced vulnerability and zero-day exploit mitigations Reputation based network protection for browsers Host-based firewall Ransomware mitigations Hardware based isolation for Microsoft Edge Application Control Device Control (e.g.: USB) Network protection for web-based threats Host intrusion prevention rules Enterprise management of hardware-based isolation for Microsoft Edge1 Customizable allow/deny lists (e.g.: IP/URL, Files, Certificates) Device-based conditional access Centrally manageable tamper protection of operating system Next Generation Protection ◑ ◑ ◑ ◑ ● Pre-execution emulation executables and scripts Runtime behavior monitoring In memory anomaly and behavior monitoring Machine learning and AI based protection from viruses and malware Published April 2020 v1909 1 Windows 10 Windows 10 Windows 10 Windows 10 Windows 10 Windows 10 commercial edition comparison Pro for Pro Business E3 E5 Workstation Per device Per device Per user Per user Per user Cloud protection for fastest responses to new/unknown web-based threats Protection from fileless based attacks Advanced machine learning and AI based protection for apex level viruses and malware threats Advanced
    [Show full text]
  • Enabling Windows Server 2019 Device Guard and Credential Guard on Lenovo Thinksystem Servers
    Front cover Enabling Windows Server 2019 Device Guard and Credential Guard on Lenovo ThinkSystem Servers Introduces the Device Guard and Provides steps to enable Device Credential Guard features Guard and Credential Guard Describes how to check the status Explains what Lenovo servers of the features support the features Guiqing Li Abstract Device Guard and Credential Guard are two important security features of the Microsoft Windows Server operating system that leverage virtualization capabilities from the hardware and the hypervisor to provide additional protection for critical subsystems and data. Customers can implement these features to secure their devices and data, such as user or system secrets, and hashed credentials. To benefit from these two features, the servers you are protecting must meet certain baseline hardware, firmware and software requirements. Lenovo® ThinkSystem™ servers support these two security features in conjunction with Windows Server 2019. This document introduces Device Guard and Credential Guard, and shows users how to enable them on supported Lenovo ThinkSystem servers. This paper is intended for IT specialists, technical architects and sales engineers who want to learn more about Device Guard and Credential Guard and how to enable them. It is expected that readers have some experience with Windows Server administration. At Lenovo Press, we bring together experts to produce technical publications around topics of importance to you, providing information and best practices for using Lenovo products and solutions to solve IT challenges. See a list of our most recent publications at the Lenovo Press web site: http://lenovopress.com Do you have the latest version? We update our papers from time to time, so check whether you have the latest version of this document by clicking the Check for Updates button on the front page of the PDF.
    [Show full text]
  • CIS Microsoft Windows Server 2019 RTM (Release 1809) Benchmark
    CIS Microsoft Windows Server 2019 RTM (Release 1809) Benchmark v1.0.0 - 08-30-2019 Terms of Use Please see the below link for our current terms of use: https://www.cisecurity.org/cis-securesuite/cis-securesuite-membership-terms-of-use/ 1 | P a g e Table of Contents Terms of Use ........................................................................................................................................................... 1 Overview ............................................................................................................................................................... 35 Intended Audience ........................................................................................................................................ 35 Consensus Guidance ..................................................................................................................................... 35 Typographical Conventions ...................................................................................................................... 36 Scoring Information ..................................................................................................................................... 36 Profile Definitions ......................................................................................................................................... 37 Acknowledgements ...................................................................................................................................... 39 Recommendations
    [Show full text]
  • What's New in Windows 10
    Contents What's new in Windows 10 What's new in Windows 10, version 1903 What's new in Windows 10, version 1809 What's new in Windows 10, version 1803 What's new in Windows 10, version 1709 What's new in Windows 10, version 1703 What's new in Windows 10, version 1607 What's new in Windows 10, versions 1507 and 1511 What's new in Windows 10 5/21/2019 • 2 minutes to read • Edit Online Windows 10 provides IT professionals with advanced protection against modern security threats and comprehensive management and control over devices and apps, as well as flexible deployment, update, and support options. Learn about new features in Windows 10 for IT professionals, such as Windows Information Protection, Windows Hello, Device Guard, and more. In this section What's new in Windows 10, version 1903 What's new in Windows 10, version 1809 What's new in Windows 10, version 1803 What's new in Windows 10, version 1709 What's new in Windows 10, version 1703 What's new in Windows 10, version 1607 What's new in Windows 10, versions 1507 and 1511 Learn more Windows 10 release information Windows 10 update history Windows 10 content from Microsoft Ignite Compare Windows 10 Editions See also Windows 10 Enterprise LTSC Edit an existing topic using the Edit link What's new in Windows 10, version 1903 IT Pro content 6/18/2019 • 10 minutes to read • Edit Online Applies to Windows 10, version 1903 This article lists new and updated features and content that are of interest to IT Pros for Windows 10 version 1903, also known as the Windows 10 May 2019 Update.
    [Show full text]
  • Commercial O365 Licensing Guide 2019
    Office 365 Licensing Guidance for Commercial Businesses 2019 This guide is provided and updated by the Summit 7 team on a biannual basis for the goal of giving the Microsoft Cloud community a foundation for licensing strategy and planning. Copyright ©2019 Summit 7 Systems, Inc. All rights reserved. Depending on your IT Security policies and functional requirements, you may require licensing that exceeds these recommendations. Nevertheless, this guidance covers most of what our clients request and what is presently available. If you are interested in other Office 365 environments, visit the Office 365 GCC Guide and the Office 365 GCC High Guide. Office 365 Commercial will not meet compliance requirements such as DFARS 7012 and ITAR. There are three primary types of licensing guidance provided in this document. Each one of these types are critical to providing the necessary features, functionality and controls that are required to provide your users with the appropriate security and compliance controls. Controls may vary by your industry, customer base, and/or respective government regulation. Table of Contents Page 2 Page 4 Enterprise Licensing Operating System Licensing Page 3 Page 7 Mobility and Security Other Licensing Licensing 1 Copyright ©2019 Summit 7 Systems, Inc. All rights reserved. Commercial Enterprise Licensing Back to top The first piece of the puzzle is the primary enterprise license. It comes in three versions (E1, E3, E5). This is the core of the feature set needed for your users and the foundational security platform for
    [Show full text]