Local and Domain Logon User Accounts and Groups Access Tokens Objects and Security Descriptors the Register

Total Page:16

File Type:pdf, Size:1020Kb

Local and Domain Logon User Accounts and Groups Access Tokens Objects and Security Descriptors the Register 2017-01-28 Local and Domain Logon Windows XP evolved from Windows 2000 User accounts and groups Windows 10, 8, 7 and Vista evolved from XP Access tokens Similar security solution Objects and security descriptors Rich support for managing security The Register Standalone computers administered locally Some features in Windows 7 and Windows 8 Domains used for centralized administration Domain controller (DC) has information about users Acts as a trusted third party EIT060 - Computer Security 1 EIT060 - Computer Security 2 Security was designed to meet requirements for C2 rating in Winlogon.exe handles the logon and responds to the Secure Attention Sequence Orange Book (SAS) ◦ CTRL+ALT+DEL ◦ Secure logon – users must be uniquely identified Winlogon uses libraries that authenticates the user ◦ Discretionary access control – Owner determines access ◦ Can be libraries for passwords, smartcards, biometric data etc ◦ Auditing – Record security related events in a logfile Local Security Authority (LSA) creates an access token ◦ Object reuse protection – Initialize all objects before giving access ◦ LSA is responsible for the local security policy (who can log in, password policies, to users privileges, what should be audited etc) ◦ Trusted path – Functionality to detect trojan horses at authentication Password hashes are stored in SAM time (called SAS in Windows) ◦ Security Accounts Manager ◦ Trusted facility management – Separate accounts for users and administrators Client Server Windows NT 3.5 SP3 was the first Windows version to earn Winlogon LSA LSA C2 rating (1995) NTLM NTLM/Kerberos ◦ Windows NT 4 SP6a earned C2 rating in 1999 Library SAM SAM Local logon EIT060 - Computer Security 3 EIT060 - Computer Security 4 1 2017-01-28 Stores user account information Local accounts ◦ Username ◦ NTLM used as authentication protocol ◦ Full name Domain accounts ◦ Expiration date ◦ Password dates (date of last change, expiry, when it can be changed next ◦ Kerberos V5 used as authentication protocol time, if it can be changed) Mutual authentication ◦ Logon hours and workstations (thrown out a certain time or continue) This will be covered in detail later in the course ◦ Profile path and logon script name ◦ NTLM used in some cases ◦ Home directory Unilateral authentication ◦ Groups Locked while machine is running EIT060 - Computer Security 5 EIT060 - Computer Security 6 Can you find problems here? Can you find problems here? Challenge response If wanted, both NTLM and LM response are used Server sends 8 byte random challenge ◦ This was default before Windows Vista Response calculated as: LM hash calculated as ◦ MD4(password) gives 16 byte result (NTLM hash stored in SAM database) ◦ Convert password to uppercase and pad to 14 bytes ◦ Pad with 5 zero bytes → 21 bytes ◦ Split into two parts of 7 byte each → two DES keys ◦ Split into 3 DES keys and encrypt challenge with each key ◦ Encrypt ”KGS!@#$%” with the two keys to get 16 bytes LM hash ◦ 24 byte response NTLM hash which is stored in the SAM database password MD4 920a3bdfe12e5fa537d7e8b8c6a064fe LM response calculated same way as NTLM response 920a3bdfe12e5f 53454352455457 a5ef3810bf7aced4 KGS!@#$% DES 82745f14a56579af challenge DES SecreTWoRd SECRETWORD LM hash a537d7e8b8c6a0 910af3418cd8e9af response challenge DES 4f524400000000 fe52438160a64e6c KGS!@#$% DES 64fe0000000000 DES 72ad34ev019baf2d challenge EIT060 - Computer Security 7 EIT060 - Computer Security 8 2 2017-01-28 NTLM hash is stored in the SAM file (local accounts) Security Reference Monitor (SRM) is responsible for ◦ Problem 1: MD4 is a very fast hash function determining access control ◦ Problem 2: No salt is used so time-memory tradeoff attacks Three parameters are considered (rainbow tables) can be used ◦ Identity of subject (SID) Possibly, also the LM hash is stored in the SAM file ◦ Type of access ◦ Problem 3: DES is a fast block cipher ◦ Object security settings (Security Descriptor) ◦ Problem 4: No salt here either… ◦ Problem 5: Passwords up to 14 characters are never better SID than passwords of 7 characters Access type Yes/No ◦ Problem 6: There are no lowercase characters in the effective SRM character set Security Descriptor Generate Audit Message EIT060 - Computer Security 9 EIT060 - Computer Security 10 After successful authentication LSA builds an access Token is either a primary access token or an token impersonation access token Processes which run as the user has a copy of the token Primary access token – access token of the user account associated with the process. When a process interacts with a securable object, token ◦ Every process has this determines authorization level Impersonation access token – allows a thread to execute in a different security context than the process owner. ◦ A thread may additionally have an impersonation access token Example: Database server runs with high privileges ◦ Threads handle concurrent user requests ◦ Thread get token of user → restricted access e.g., restricting SIDs EIT060 - Computer Security 11 EIT060 - Computer Security 12 3 2017-01-28 Security Identifier Generic groups and users Unique for each user or group S-1-1-0 Everyone, a group that includes all users Format: S-1-5-20 Network Service S-R-I-SA-SA-SA-N S-1-5-18 SYSTEM, local operating system S: The letter S (just means that the string is a SID) S-1-5-SA-SA-SA-500 Administrator R: revision number (1) S-1-5-SA-SA-SA-501 Guest account (no password I: Identifier authority (5 for user accounts) required) SA: subauthority (specifies domain or computer) S-1-5-SA-SA-SA-512 Domain Admins (global group) ◦ Can be up to 14 groups, but 3 is typical N: relative identifier, incremented for each new principal EIT060 - Computer Security 13 EIT060 - Computer Security 14 The right to perform system related operations All resources are objects ◦ Shutting down ◦ Files, folders, printers, registry keys, processes, threads, access ◦ Change system time ◦ Backup files tokens, etc.. ◦ Generate audit Containers can hold other objects, e.g., folders Applies only to local computer. A user can have different privileges on Noncontainers can not hold other objects, e.g., files different machines in a domain. Privileges can be assigned to both users and groups Securable object – Any object that can be shared Access token is checked when user tries to perform privileged operation All securable objects can have a security descriptor Differs from access rights ◦ But it is not necessary ◦ Access to resources and tasks, not objects ◦ Stored with subject Object ◦ Admin assigns privileges Stored in access token produced at logon Security Descriptor EIT060 - Computer Security 15 EIT060 - Computer Security 16 4 2017-01-28 Contains security information associated with an object Identifies who is allowed or denied access to an object If an object has no DACL, everyone has full control SID for the owner Object An empty DACL results in everyone is denied access A SID can be allowed or denied access. SID for the primary group Security Descriptor All ”deny” entries are stored in the beginning of the DACL Owner SID Contains a list of access control entries DACL (Discretionary Access Primary group SID Control List) specifying access rights (ACEs) DACL Owner SID SACL Principal SID: Alice SACL (System Access Control List) Primary group SID ACE 1 Deny: write specifying types of events that should DACL generate audit records Principal SID: Alice SACL ACE 2 Allow: read, write Security descriptor EIT060 - Computer Security 17 EIT060 - Computer Security 18 Go through list of ACEs until all access requests are allowed Two processes (subjects) wants read access to an object or any access request is denied Process 1 Object Otherwise deny access Consequences Access Token Security Descriptor ◦ Deny has higher precedence than allow User SID: Alice Group SIDs: G1, G2 Owner SID: Charlie Privileges: Access allowed ◦ If user SID has read only access and user is member of group which SID Other info: Primary Group SID: G3 has read + write, then user has read + write access (Different from DACL Unix/Linux) ACE 1 Example, Alice is member of group ”Students” Process 2 Deny, Bob, Read Principal SID: Alice ACE 2 ACE 1 Allow, Alice, Read + Write Deny: write Result Access Token User SID: Bob ACE 3 • Read access allowed Allow, Group 3, Read Group SIDs: G3 Access denied → • Write access denied Privileges: Principal SID: Students Other info: ACE 2 • Read+Write access denied Allow: read, write SACL EIT060 - Computer Security 19 EIT060 - Computer Security 20 5 2017-01-28 Since there are so many different types of objects Since there are many different types of objects, access rights look different for different types there are very many different types of access rights Standard access rights apply to (almost) all objects Generic access rights FILE_EXECUTE FILE_READ_ATTRIBUTES gives a mapping to GENERIC_EXECUTE ◦ DELETE – delete the object STANDARD_RIGHTS_EXECUTE ◦ READ_CONTROL – read info in security descriptor (owner, specific access rights SYNCHRONIZE group and DACL) for a type of objects FILE_READ_ATTRIBUTES FILE_READ_DATA ◦ WRITE_DAC – write access to the DACL GENERIC_READ FILE_READ_EA ◦ WRITE_OWNER – write access to the field ”owner” in the STANDARD_RIGHTS_READ SYNCHRONIZE security descriptor Example – Files and directories FILE_APPEND_DATA ◦ SYNCHRONIZE – The right to synchronize with the object FILE_WRITE_ATTRIBUTES FILE_WRITE_DATA GENERIC_WRITE FILE_WRITE_EA STANDARD_RIGHTS_WRITE SYNCHRONIZE
Recommended publications
  • Supporting Operating System Installation | 3
    cc01SupportingOperatingSystemInstallation.indd01SupportingOperatingSystemInstallation.indd PagePage 1 08/10/1408/10/14 4:334:33 PMPM martinmartin //208/WB01410/XXXXXXXXXXXXX/ch01/text_s208/WB01410/XXXXXXXXXXXXX/ch01/text_s Supporting Operating LESSON 1 System Installation 70-688 EXAM OBJECTIVE Objective 1.1 – Support operating system installation. This objective may include but is not limited to: Support Windows To Go; manage boot settings, including native virtual hard disk (VHD) and multi-boot; manage desktop images; customize a Windows installation by using Windows Preinstallation Environment (PE). LESSON HEADING EXAM OBJECTIVE Using a Troubleshooting Methodology Viewing System Information Using the Event Viewer Supporting Windows To Go Support Windows To Go Creating and Deploying a Windows To Go Workspace Drive Booting into a Windows To Go Workspace Managing Boot Settings Manage boot settings, including native virtual hard disk (VHD) and multi-boot Using BCDEdit and BCDBoot Configuring a Multi-Boot System Manage boot settings, including native virtual hard disk (VHD) and multi-boot Configuring a Native VHD Boot File Manage boot settings, including native virtual hard disk (VHD) and multi-boot Understanding VHD Formats Installing Windows 8.1 on a VHD with an Operating System Present Installing Windows 8.1 on a VHD Without an Operating SystemCOPYRIGHTED Present MATERIAL Managing Desktop Images Manage desktop images Capturing Images Modifying Images using DISM Customizing a Windows Installation by Using Windows PE Customize a Windows
    [Show full text]
  • Windows 7 Bitlocker™ Drive Encryption Security Policy for FIPS 140-2 Validation
    Windows 7 BitLocker™ Security Policy Page 1 of 16 Windows 7 BitLocker™ Drive Encryption Security Policy For FIPS 140-2 Validation For Windows 7 Document version 1.0 08/31/2011 1. Table of Contents 1. TABLE OF CONTENTS ......................................................................................................................... 1 2. INTRODUCTION .................................................................................................................................. 2 2.1 List of Cryptographic Modules ........................................................................................................................... 2 2.2 Brief Module Description ................................................................................................................................... 3 2.3 Validated Platforms ........................................................................................................................................... 4 3. INTEGRITY CHAIN OF TRUST .......................................................................................................... 4 4. CRYPTOGRAPHIC BOUNDARIES ..................................................................................................... 5 4.1 Overall Cryptographic Boundary........................................................................................................................ 5 4.2 BitLocker™ Components Included in the Boundary .......................................................................................... 5 4.3 Other Windows
    [Show full text]
  • Guidelines for Designing Embedded Systems with Windows 10 Iot Enterprise
    Guidelines for Designing Embedded Systems with Windows 10 IoT Enterprise Version 2.0 Published July 15, 2016 Guidelines for designing embedded systems 1 CONFIDENTIAL Contents Overview .................................................................................................................................................................................................... 4 Building a task-specific experience ............................................................................................................................................ 4 General Group Policy settings ....................................................................................................................................................... 4 Application control ................................................................................................................................................................................ 5 Application boot options ................................................................................................................................................................. 5 Auto-boot Universal Windows apps ...................................................................................................................................... 5 Auto-boot Classic Windows apps ........................................................................................................................................... 5 Limit application access with AppLocker ...............................................................................................................................
    [Show full text]
  • Disabling Windows Logon Optimization
    Network : connection failures during startup : disabling Windows logon optimization 379 Camille Garick Wed, May 13, 2020 Authentication Accounting Module AAM)™ 61 Warning Modify the registry at your own risk. EnvisionWare does not provide Windows support. Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. We recommend that your Operating System support team undertake these changes. Microsoft optimized Windows to enhance the user experience by creating the impression that the operating system starts up faster. This is achieved by having the login prompt display before the network is fully initialized. Additionally, existing users may be logged in with cached credentials. Drawbacks in a domain or corporate environment are that login scripts might not run, drives and printers might not be mapped, policies might not get applied until after logon and GPO software distribution may be delayed. This logon optimization can affect some EnvisionWare Products. EnvisionWare products that make connections across a network may fail to start correctly if the application or associated Windows service starts before the network is fully initialized. We recommend turning off Windows Logon Optimization on PC’s where EnvisionWare products are running. The Logon optimization can be disabled in the following ways: 1. Via Local Policy - Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon 2. Via Group Policy - Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon 3. As a Policy via Windows registry - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\Winlogon with registry value SyncForegroundPolicy=dword:00000001 4.
    [Show full text]
  • AMP for Endpoints
    Windows Process Starts Before AMP Connector Workaround - AMP for Endpoints Contents Introduction Requirements Components Used Limitations Background Information Troubleshoot Steps to delay a Windows service Delay the process with the command line Introduction This document describes the steps to troubleshoot in Advanced Malware Protection (AMP) for Endpoints when a Windows process starts before System Process Protection (SPP). Contributed by Nancy Perez and Uriel Torres, Cisco TAC Engineers. Requirements Cisco recommends that you have knowledge of these topics: ● Windows OS ● AMP connector's engines Components Used The information in this document is based on these software and hardware versions: ● Windows 10 device ● AMP connector 6.2.9 version The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command. Limitations This is a bug that affects the System Process Protection engine when a process starts before the AMP connector CSCvo90440. Background Information The AMP for Endpoints System Process Protection engine protects critical Windows system processes from memory injection attacks by other processes. In order to enable SPP, on the AMP console, navigate to Management > Policies > click on edit in the policy you want to modify > Modes and Engines > System Process Protection, here you can find three options: ● Protect: blocks attacks
    [Show full text]
  • Windows XP Embedded Thin Client Manual
    ______________________________________________________________ Windows XP Embedded Thin Client Manual Version 1.2.1 ___________________________________________________________ Contents Contents Chapter 1 – Introduction 1 Overview 1 XPe File System 2 Chapter 2 - Startup and Configuration 2-1 Default Logon accounts 2-1 Logging On 2-1 XPe Management 2-3 1. Assign AutoLogon User 2-4 2. Setting Display Properties 2-4 3. Computer Management 2-5 4. XPe SNMP Control Utility 2-6 5. RAM Disk Size Properties 2-7 6. PopUp Main Menu 2-8 Network Connections 2-8 Microsoft Firewall 2-9 Chapter 3 - Applications 3-1 Installing New Applications / Device Drivers 3-1 Printer Driver Installation Example 3-1 Setup LPD printer on XPe 3-2 CITRIX Program Neighborhood 3-3 Remote Desktop Connection (RDP) 3-4 Internet Explorer 3-5 Kiosk Mode 3-6 Lock down IE using registry edits 3-6 TermPro Emulations 3-7 802.11a/b/g wireless adapter support 3-7 USB Device Support 3-7 GPEDIT (Group Edit) 3-7 SNMPadm - Remote Management 3-8 i Contents Chapter 4 – TermPro Emulations 4-1 Configure/Edit Sessions 4-3 Display Sessions 4-6 Printer Sessions 4-15 Using Emulation Sessions 4-20 Display Sessions 4-20 Printer Sessions 4-38 Appendix A – XPe Image Recovery A-1 Appendix B – Advanced Configuration Notes B-1 Expand User Access B-1 Auto-re-logon B-2 ii Introduction Chapter 1 – Introduction An overview of the XPe Thin Client is presented along with a description of its file system. Overview The XPe thin client, with its high quality, versatility, and flexibility, is an expandable high-performance terminal that gives users the ability to access Windows, Internet, multimedia, and legacy applications, at a lower total cost of ownership than PCs or other computing products.
    [Show full text]
  • PLATINUM Targeted Attacks in South and Southeast Asia
    PLATINUM Targeted attacks in South and Southeast Asia Windows Defender Advanced Threat Hunting Team This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. This document is provided “as-is.” Information and views expressed in this document, including URL and other Internet website references, may change without notice. You bear the risk of using it. Copyright © 2016 Microsoft Corporation. All rights reserved. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Table of contents PLATINUM: Targeted attacks in South and Southeast Asia........................................... 4 Adversary profile ............................................................................................................................ 4 Methods of attack .......................................................................................................................... 6 Technical details ............................................................................................................................. 11 Dipsind ................................................................................................................................................................................ 11 JPIN ..................................................................................................................................................................................... 15 adbupd ..............................................................................................................................................................................
    [Show full text]
  • Zenworks Application 2017 Update 4 January 2019
    ZENworks Application 2017 Update 4 January 2019 1 Documentation Updates This section contains information on documentation content changes that were made in ZENworks Configuration Management (ZENworks Application). The information can help you to keep current on updates to the documentation. The documentation was updated on the following date: 2 Overview ZENworks Application (ZAPP) leverages the capabilities of a unified endpoint management solution to provide an enhanced user experience, while using the same functionality as that of the old Novell Application Launcher (NAL) window. The features include: A brand new user interface that serves as a single place for all ZENworks end user functionality on Windows. An integrated search to help you find the app of your choice. The search includes full and split pattern matching by name, description, and contact information. A new branding policy that enables your organization to customize certain aspects of the ZENworks Application based on your own branding requirements, such as the ZAPP icon, wallpaper, and color. You can pin and unpin bundles to the Desktop, Taskbar, and Start menu tiles. An improved user experience, including: Providing remote assistance to end users from the ZAPP window. You do not need to go to the ZENworks system tray icon, you can click the menu from ZAPP itself to request remote assistance. This document includes the following: Section 2.1, “Launching ZAPP,” on page 2 Section 2.2, “Logging into ZENworks,” on page 2 Section 2.3, “Launching help,” on page 2
    [Show full text]
  • Advanced Authentication - Windows Client
    Installation and Configuration Guide Advanced Authentication - Windows Client Version 6.1 Legal Notices For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see https://www.netiq.com/company/legal/. Copyright © 2018 NetIQ Corporation, a Micro Focus company. All Rights Reserved. Contents About This Book 5 About NetIQ Corporation 7 1 System Requirements 9 2 Offline Support for Windows Client 11 3 Configuring the Preliminary Settings 13 Configuring the Mandatory Settings . 13 Using a Specific Advanced Authentication Server in a Non-DNS Mode . 13 Setting a DNS for Advanced Authentication Server Discovery . 14 Configuring Optional Settings . 17 Disabling 1:N . 18 Disabling the Local Accounts . 19 Configuration Settings for Multitenancy . 19 Selecting an Event . 19 Configuring Timeout for Card Waiting . 19 Enabling Login Failure After Card Timeout . 20 Configuring Automatic Login . 20 Customizing a Logo . 20 Configuring to Verify Server Certificates . 21 Configuring to Force Offline Login Manually . 21 Configuring the Enforced Cached Login . 22 Configuring Single Sign-on Support for Citrix and Remote Desktop . 22 Customizing the Login Page Background Screen . 23 Changing an Endpoint Name . 23 Configuring to Enable the Authentication Agent Chain . 24 Configuring Integration with Sophos SafeGuard 8. 25 Configuring the Credential Provider Chaining . 25 4 Installing and Uninstalling Windows Client 27 Installing Windows Client . 27 Uninstalling Windows Client . 27 Microsoft Windows 7 . 28 Microsoft Windows 8.1 . 28 Microsoft Windows 10 . 28 5 Client Login Extension Support for Windows Client 29 6 Troubleshooting for Windows Client 31 Debugging Logs for Advanced Authentication . 31 Using a Diagnostic Tool .
    [Show full text]
  • CIS Microsoft Windows Server 2012 Benchmarkv1.0.0
    CIS Microsoft Windows Server 2012 Benchmarkv1.0.0 01-31-2013 The CIS Security Benchmarks division provides consensus-oriented information security products, services, tools, metrics, suggestions, and recommendations (the “SB Products”) as a public service to Internet users worldwide. Downloading or using SB Products in any way signifies and confirms your acceptance of and your binding agreement to these CIS Security Benchmarks Terms of Use. CIS SECURITY BENCHMARKS TERMS OF USE BOTH CIS SECURITY BENCHMARKS DIVISION MEMBERS AND NON-MEMBERS MAY: Download, install, and use each of the SB Products on a single computer, and/or Print one or more copies of any SB Product that is in a .txt, .pdf, .doc, .mcw, or .rtf format, but only if each such copy is printed in its entirety and is kept intact, including without limitation the text of these CIS Security Benchmarks Terms of Use. UNDER THE FOLLOWING TERMS AND CONDITIONS: SB Products Provided As Is. CIS is providing the SB Products “as is” and “as available” without: (1) any representations, warranties, or covenants of any kind whatsoever (including the absence of any warranty regarding: (a) the effect or lack of effect of any SB Product on the operation or the security of any network, system, software, hardware, or any component of any of them, and (b) the accuracy, utility, reliability, timeliness, or completeness of any SB Product); or (2) the responsibility to make or notify you of any corrections, updates, upgrades, or fixes. Intellectual Property and Rights Reserved. You are not acquiring any title or ownership rights in or to any SB Product, and full title and all ownership rights to the SB Products remain the exclusive property of CIS.
    [Show full text]
  • Windows Internals
    Windows Internals David Solomon ([email protected]) David Solomon Expert Seminars www.solsem.com Mark Russinovich ([email protected]) Winternals www.winternals.com, www.sysinternals.com About the Speaker: David Solomon 1982-1992: VMS operating systems development at Digital 1992-present: Researching, writing, and teaching Windows operating system internals Frequent speaker at technical conferences (Microsoft TechEd, IT Forum, PDCs, …) Microsoft Most Valuable Professional (1993, 2005) Books Windows Internals, 4th edition PDF version ships with Server 2003 Resource Kit Inside Windows 2000, 3rd edition Inside Windows NT, 2nd edition Windows NT for OpenVMS Professionals Live Classes 2-5 day classes on Windows Internals, Advanced Troubleshooting Video Training 12 hour interactive internals tutorial Licensed by MS for internal use 2 About the Speaker: Mark Russinovich Co-author of Inside Windows 2000, 3rd Edition and Windows Internals, 4th edition with David Solomon Senior Contributing Editor to Windows IT Pro Magazine Co-authors Windows Power Tools column Author of tools on www.sysinternals.com Microsoft Most Valuable Professional (MVP) Co-founder and chief software architect of Winternals Software (www.winternals.com) Ph.D. in Computer Engineering 3 Purpose of Tutorial Give Windows developers a foundation understanding of the system’s kernel architecture Design better for performance & scalability Debug problems more effectively Understand system performance issues We’re covering a small, but important set of core topics: The “plumbing in the boiler room” 4 System Architecture System Processes Services Applications Environment Service Subsystems Control Mgr. POSIX LSASS SvcHost.Exe Task Manager WinMgt.Exe Explorer WinLogon SpoolSv.Exe User OS/2 User Session Services.Exe Application Mode Manager Subsystem DLLs Windows System NTDLL.DLL Threads Kernel Mode System Service Dispatcher (kernel mode callable interfaces) Windows I/O Mgr USER, GDI File ObjectPlug andPower Security ProcessesConfigura- Local Device & System ReferenceVirtual & tion MgrProcedure Mgr.
    [Show full text]
  • Bitlocker™ Drive Encryption Security Policy for FIPS 140-2 Validation
    BitLocker™ Security Policy Page 1 of 16 BitLocker™ Drive Encryption Security Policy For FIPS 140-2 Validation v 1.1 8/31/11 1. Table of Contents 1. TABLE OF CONTENTS ......................................................................................................................... 1 2. INTRODUCTION .................................................................................................................................. 1 2.1 List of Cryptographic Modules ........................................................................................................................... 2 2.2 Brief Module Description ................................................................................................................................... 2 2.3 Validated Platforms ........................................................................................................................................... 3 3. INTEGRITY CHAIN OF TRUST .......................................................................................................... 3 4. CRYPTOGRAPHIC BOUNDARIES ..................................................................................................... 4 4.1 Overall Cryptographic Boundary........................................................................................................................ 4 4.2 BitLocker™ Components Included in the Boundary .......................................................................................... 4 4.3 Other Server 2008 Components .......................................................................................................................
    [Show full text]