DOCSLIB.ORG

Ways to a Better Password Management

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Ways to a Better Password Management St at e of IT Changes Survey Result s + Infographic Tips for a Bet t er Passw ord Securit y Policy Dat a Governance: The Key t o Com pliance Basic Rules How -t o: Ways t o a Bet t er Det ect ing Passw ord Changes in Act ive oPf aWsisnwdoowrds Server Direct ory SMecaunriatygem ent Contents Nine St eps t o a Bet t er Passw ord Managem ent 3 by Richard Muniz Why You Need t o Ensure Adm inist rat ors 5 Change Passw ords Regularly by Orin Thomas How t o St ore and Ret rieve Passw ords Securely 7 w it h Pow erShell by Adam Bertram 3 Ways t o Prot ect t he Keys t o Your Kingdom - 11 Dom ain Adm inist rat or Credent ials by Russell Smith June 2015 SysAdmin Magazine St at e of IT Changes Survey 2015: 13 Docum ent ing and Audit ing Dat a Governanm e: The Key t o Com pliance 16 by Deb Shinder Internet Usage Policy against Inappropriate 18 Content by Richard Muniz How to Detect Password Changes 20 in Active Directory June 2015 SysAdmin Magazine Nine Steps to a Better Passw ord Managem ent by Richard Muniz 20+ years in IT industry, a practicing systems administrator and a teacher Passwords remind me a bit of the Coyote. Not Monde and right on the background, taped to the one that chases the Road Runner, but the the wall, is a list of passwords (and you thought one that lives in my native South-West and howls you had it rough with people taping them under at the moon. No matter how hard humans have their keyboard). And after years and years, the tried to get rid of it, it hangs in there, and in most most popular password out there is still cases, even manages to gain ground back. Why ?Password?. do I compare passwords to the Coyote? For years We can try and try: by GPO implementation and now they?ve been saying it was heading for talking to people. But all we end up with is the extinction and here we are, years later, it?s still realization that we might be able to build a fool hanging in there. Somehow, I suspect they?ll be proof system, but we can?t build a damn-fool with us for a long time to come. And as long as proof system. And we?ll still see people making we still have them out there, people will continue passwords that match someone?s birthday or to abuse them. address and taping them in a place for the world I suppose I don?t need to point to much further to see. than a video floating around the Internet of an Why? People are weak. We have so many employee being interviewed on French TV5 passwords, that keeping track of them is difficult. 3 June 2015 SysAdmin Magazine We write them down, and we paste them under 3. Recording of usernames and passwords for the keyboard, and we continue to be our own worst enemy. certain sites How do we fix it? Well, the answer is in this little A nice feature, and possibly one that can bite story. Years ago I encountered a very dynamic you, but one that might endear itself to your preacher, and we got to talking. I asked him how users. it was that people changed, and he rocked back a bit, narrowed his eyes, and said, ?Son, if you want 4. Storing certain kinds of passwords to take an old bone away from a dog without Some will only play nice with Active Directory, getting bit, you?d better offer him a steak in its some will let you record almost anything into place.? them. We want to take their piece of paper away and have them play nice. Problem is that unless we 5. Reminding questions give them a secure tools to keep the passwords, Everyone forgets things, and we still need they?ll continue to use their post-it notes, and something to allow them access the vault in case keep putting them under their keyboards. they forget, or at least reset the password, or Strangely, there are tons of password give them a reminder. management tools there that will help us. We call them password managers and a simple internet 6. Password generators search will give you at least a dozen, just on the For users, it?s a waste. For service accounts . first try. Some cost money, others are free. Some Priceless. are meant for a single user on one system; others are network based and can serve 7. Dual authentication hundreds of users. Some you might already have A card token and a password ? great. A password and not even know it (a lot of cloud services and a question ? slightly better than useless. provide this as part of service). 8. Self-securing What do you look for in a password manager? While I?m sure these folks always double check 1. Supported platforms their house door when they leave in the It can be the best manager in the world, but if it morning, they won?t hesitate to leave a site open. only runs on Linux and you?re a Windows house, Since this has everything and then some, we it isn?t going to do you much good. Also, how you might want it to close after a certain amount of access it is important. Is it compatible with IE and time. Firefox, or does it just work with Chrome? 9. Managable 2. Storage capability Letting folks choose their own tools is OK, but then you end up supporting something you The idea behind a password vault is to provide might know nothing about. An enterprise-based your users with a nice, encrypted site to stash managing tool is best, and it also levels the their passwords away in. But it?s also a great playing field for everyone. place to put important documents, notes, and so forth. I know some folks who keep scans of their Want to read more articles like this? social security cards and passports. While it?s not Subscribe to our blog: a substitute for full disk encryption, it is better blog.netwrix.com than just leaving them out in the open. 4 June 2015 SysAdmin Magazine Why You Need to Ensure Administrators Change Passw ords Regularly by Orin Thomas 20+ years in IT industry; MVP, MCT and other Microsoft MCSE and MCITP certifications. Authored 30+ books for Microsoft Press and is a contributing editor at Windows IT Pro magazine. The first time I really felt like I was a system administrator was when the Unix systems administrator in the IT unit I worked for at an Australian University went on leave for three months. During this time I was responsible for all of the servers that he had managed, which included all minor departmental servers, not just the scattered ones I looked after, as well as the important faculty level servers. Although I?d been responsible for a couple of minor departmental servers before then, this was the first time I really worked without a safety net as, without this guy around, there was no one within reach who could help me out if something went wrong. 5 June 2015 SysAdmin Magazine When he was performing the handoff, I noticed Regularly changing administrator account something interesting. The administrator and passwords is even more important than regularly root accounts for all the servers he was changing unprivileged user account passwords. responsible for used exactly the same password. If an attacker gets the password of an The root account password for the faculty web administrative assistant, there is only a certain server (a DEC Alpha running UNIX) was the same amount of mischief that they can perpetrate. If as the password for the Administrator account in an attacker gets the password of a systems the faculty Windows NT 4 domain. I knew that administrator, the entire organization?s the process was questionable even if it did make infrastructure is at risk. Administrator passwords the handoff very simple. need to be subject to more stringent security requirements because the consequences if these After the administrator returned from his trip, he accounts are compromised are much greater. didn?t change passwords on any of the systems. When I left that position a year later, the servers It?s vital for organizations to perform regular all still had the same password. This was checks to ensure that system administrators are definitely a case where convenience triumphed updating their passwords on a regular basis. If over good security practice. these checks aren?t performed, there is little reason to believe that system administrators will People change passwords because do the right thing of their own accord. A system they have to, not because they have should be in place where notifications are raised each time a privileged account password is not any deep appreciation of the updated after a certain period of time. This arguments about password security. allows you to be sure that the passwords are being updated on a regular basis. Luckily, there are good free tools for that, which are easy to It?s no news to anyone that people hate the install and help streamline security. process of updating their passwords and that people hate having separate passwords for With Windows Server, it?s possible to run a query separate services and systems. Ordinary users against Active Directory to determine which don?t have much choice when it comes to having accounts are configured so that the associated to update their passwords because they can?t password never expires.
Load more

Recommended publications
  • Security Target
    Acronis SCS Acronis Cyber Backup 12.5 SCS Hardened Edition Server v12.5 Security Target Document Version: 0.14 Prepared for: Prepared by: Acronis SCS Corsec Security, Inc. 6370 E. Thomas Road, Suite 250 13921 Park Center Road, Suite 460 Scottsdale, AZ 85251 Herndon, VA 20171 United States of America United States of America Phone: +1 781 782 9000 Phone: +1 703 267 6050 www.acronisscs.com www.corsec.com Security Target, Version 0.14 August 19, 2020 Table of Contents 1. Introduction .......................................................................................................................................................4 1.1 Purpose .....................................................................................................................................................4 1.2 Security Target and TOE References .........................................................................................................4 1.3 Product Overview ......................................................................................................................................5 1.3.1 Product Components........................................................................................................................5 1.4 TOE Overview ............................................................................................................................................6 1.4.1 TOE Environment..............................................................................................................................7 1.5
    [Show full text]
  • Microsoft Windows Common Criteria Evaluation Security Target
    Microsoft Common Criteria Security Target Microsoft Windows Common Criteria Evaluation Microsoft Windows 10 version 1809 (October 2018 Update) Microsoft Windows Server 2019 (October 2018 Update) Security Target Document Information Version Number 0.05 Updated On June 18, 2019 Microsoft © 2019 Page 1 of 126 Microsoft Common Criteria Security Target Version History Version Date Summary of changes 0.01 June 27, 2018 Initial draft 0.02 December 21, 2018 Updates from security target evaluation 0.03 February 21, 2019 Updates from evaluation 0.04 May 6, 2019 Updates from GPOS PP v4.2.1 0.05 June 18, 2019 Public version Microsoft © 2019 Page 2 of 126 Microsoft Common Criteria Security Target This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. This work is licensed under the Creative Commons Attribution-NoDerivs- NonCommercial License (which allows redistribution of the work). To view a copy of this license, visit http://creativecommons.org/licenses/by-nd-nc/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA.
    [Show full text]
  • Microsoft Windows Vista and Windows Server 2008 EAL1 Security Target
    Microsoft Windows Vista and Windows Server 2008 EAL1 Security Target Version 1.0 August 14, 2008 Prepared For: Microsoft Corporation Corporate Headquarters One Microsoft Way Redmond, WA 98052-6399 Prepared By: Science Applications International Corporation Common Criteria Testing Laboratory 7125 Gateway Drive Columbia, MD 21046-2554 Version 1.0, 8/14/2008 This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. This work is licensed under the Creative Commons Attribution-NoDerivs-NonCommercial License (which allows redistribution of the work). To view a copy of this license, visit http://creativecommons.org/licenses/by-nd- nc/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
    [Show full text]
  • Encryption Enterprise Advanced Installation Guide V10.0 Notes, Cautions, and Warnings
    Dell Encryption Enterprise Advanced Installation Guide v10.0 Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2012-2018 Dell Inc. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.Registered trademarks and trademarks used in the Dell Encryption, Endpoint Security Suite Enterprise, and Data Guardian suite of documents: Dell™ and the Dell logo, Dell Precision™, OptiPlex™, ControlVault™, Latitude™, XPS®, and KACE™ are trademarks of Dell Inc. Cylance®, CylancePROTECT, and the Cylance logo are registered trademarks of Cylance, Inc. in the U.S. and other countries. McAfee® and the McAfee logo are trademarks or registered trademarks of McAfee, Inc. in the US and other countries. Intel®, Pentium®, Intel Core Inside Duo®, Itanium®, and Xeon® are registered trademarks of Intel Corporation in the U.S. and other countries. Adobe®, Acrobat®, and Flash® are registered trademarks of Adobe Systems Incorporated. Authen tec® and Eikon® are registered trademarks of Authen tec. AMD® is a registered trademark of Advanced Micro Devices, Inc. Microsoft®, Windows®, and Windows Server®, Internet Explorer®, Windows Vista®, Windows 7®, Windows 10®, Active Directory®, Access®, BitLocker®, BitLocker To Go®, Excel®, Hyper-V®, Outlook®, PowerPoint®, Word®, OneDrive®, SQL Server®, and Visual C++® are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.
    [Show full text]
  • Security Best Practices for Developing Windows Azure Applications
    Security Best Practices For Developing Windows Azure Applications Authors Andrew Marshall (Senior Security Program Manager, Security Engineering) Michael Howard (Principal Security Program Manager, Security Engineering) Grant Bugher (Lead Security Program Manager, OSSC) Brian Harden (Security Architect, OSSC) Contributors Charlie Kaufman (Principal Architect) Martin Rues (Director, OSSC) Vittorio Bertocci (Senior Technical Evangelist, Developer and Platform Evangelism) June 2010 (REVISION 2) The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights
    [Show full text]
  • Smarx OS Compendium 2020 for the CRYPTO-BOX
    2020 EDITION Smarx® Compendium d s p . ) r e v o C _ n a M x r a m S ( a s 2 1 v o N 7 2 - www.marx.com 0 2 We highly appreciate and value your comments and suggestions! Suggestions for improvements will be honored with: • Free Business Support for 6 months • Enrollment in our BE !" ester program Software security is a growing challenge and requires constant improving " be part of the process! $lease send sugestions and error report to: • $$%& software/hardware in general and documentation (including this Compendium*: support@mar,.com • WEB and online ordering system related: webmaster+mar,.com Smar, .S )ompendium November 2020 )opyright 1 2002, 2020 2!345 )ryptoTech 6$ 7 Table of Contents 8. What is this Compendium !bout?--------------------------------------------------------------------------------: 8-8. ;ntroduction--------------------------------------------------------------------------------------------------------: 8.2. What is /ew9-------------------------------------------------------------------------------------------------------: 8-7. What to Find Where in this )ompendium--------------------------------------------------------------< 8-=. $rofessional Software $rotection Secures 3evenue----------------------------------------------< 8->. he )3?$ ."BO45@ardware-----------------------------------------------------------------------------88 8->-8. )3?$ ."BOX 2odels--------------------------------------------------------------------------------88 8->.2. echnical Features of the )3?$ ."BO45----------------------------------------------------88
    [Show full text]
  • Invisimole: the Hidden Part of the Story Unearthing Invisimole’S Espionage Toolset and Strategic Cooperations
    ESET Research white papers TLP: WHITE INVISIMOLE: THE HIDDEN PART OF THE STORY UNEARTHING INVISIMOLE’S ESPIONAGE TOOLSET AND STRATEGIC COOPERATIONS Authors: Zuzana Hromcová Anton Cherepanov TLP: WHITE 2 InvisiMole: The hidden part of the story CONTENTS 1 EXECUTIVE SUMMARY � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 4 2 ATTACKS AND INVESTIGATION � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 4 2.1 InvisiMole’s toolset ������������������������������������������������������������������������������������������������������������������������ 5 2.2 Cooperation between InvisiMole and Gamaredon . 5 3 BUILDING BLOCKS � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 6 3.1 Structure ������������������������������������������������������������������������������������������������������������������������������������������6 3.1.1 InvisiMole blobs . 6 3.1.2 Execution guardrails with DPAPI ���������������������������������������������������������������������������������7 3.2 Payload ��������������������������������������������������������������������������������������������������������������������������������������������8 3.2.1 TCP downloader ��������������������������������������������������������������������������������������������������������������9 3.2.2 DNS downloader . 9 3.2.3 RC2CL backdoor �������������������������������������������������������������������������������������������������������������13
    [Show full text]
  • Dell Data Protection | Encryption Enterprise Edition Advanced Installation Guide V8.13 Notes, Cautions, and Warnings
    Dell Data Protection | Encryption Enterprise Edition Advanced Installation Guide v8.13 Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2017 Dell Inc. All rights reserved.Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. Registered trademarks and trademarks used in the Dell Data Protection Encryption, Endpoint Security Suite, Endpoint Security Suite Enterprise, and Dell Data Guardian suite of documents: DellTM and the Dell logo, Dell PrecisionTM, OptiPlexTM, ControlVaultTM, LatitudeTM, XPS®, and KACETM are trademarks of Dell Inc. Cylance®, CylancePROTECT, and the Cylance logo are registered trademarks of Cylance, Inc. in the U.S. and other countries. McAfee® and the McAfee logo are trademarks or registered trademarks of McAfee, Inc. in the US and other countries. Intel®, Pentium®, Intel Core Inside Duo®, Itanium®, and Xeon® are registered trademarks of Intel Corporation in the U.S. and other countries. Adobe®, Acrobat®, and Flash® are registered trademarks of Adobe Systems Incorporated. Authen Tec® and Eikon® are registered trademarks of Authen Tec. AMD® is a registered trademark of Advanced Micro Devices, Inc. Microsoft®, Windows®, and Windows Server®, Internet Explorer®, MS-DOS®, Windows Vista®, MSN®, ActiveX®, Active Directory®, Access®, ActiveSync®, BitLocker®, BitLocker To Go®, Excel®, Hyper-V®, Silverlight®, Outlook®, PowerPoint®, OneDrive®, SQL Server®, and Visual C++® are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.
    [Show full text]
  • Sari Haj Hussein Master's Thesis
    Double SSO – A Prudent and Lightweight SSO Scheme Master of Science Thesis in the Programme Secure and Dependable Computer Systems SARI HAJ HUSSEIN Chalmers University of Technology University of Gothenburg Department of Computer Science and Engineering Göteborg, Sweden, November 2010 The Author grants to Chalmers University of Technology and University of Gothenburg the non-exclusive right to publish the Work electronically and in a non-commercial purpose make it accessible on the Internet. The Author warrants that he/she is the author to the Work, and warrants that the Work does not contain text, pictures or other material that violates copyright law. The Author shall, when transferring the rights of the Work to a third party (for example a publisher or a company), acknowledge the third party about this agreement. If the Author has signed a copyright agreement with a third party regarding the Work, the Author warrants hereby that he/she has obtained any necessary permission from this third party to let Chalmers University of Technology and University of Gothenburg store the Work electronically and make it accessible on the Internet. Double SSO – A Prudent and Lightweight SSO Scheme SARI HAJ HUSSEIN © SARI HAJ HUSSEIN, November 2010. Examiner: DAVID SANDS Chalmers University of Technology University of Gothenburg Department of Computer Science and Engineering SE-412 96 Göteborg Sweden Telephone + 46 (0)31-772 1000 Cover: Stage A of Double SSO, see Chapter 5 Department of Computer Science and Engineering Göteborg, Sweden November 2010 Abstract User authentication means the verification of a user identity in a computer system. In a typical scenario, users in an organization have access to several independent services, each of them requires separate credentials (e.g., user name and password) for user authentication.
    [Show full text]
  • Notes on Cloud Computing Syllabus
    Notes on Cloud Computing Syllabus Understanding Cloud Computing: Introduction to cloud computing, are you Chapter 1 ready for cloud computing? Surveying the Role of Cloud Computing, developing the cloud services. Understanding Windows Azure Platform Architecture: The Windows Azure Developer Portal, Creating and running Projects in the Azure Development Platform, Chapter 2 Using Azure Application Templates for Visual Studio 2008, Taking advantage of Auxiliary Cloud Services, Deploying Application and Services to the Azure Cloud. Analyzing the Windows Azure Operating System: The Lifecycle, Securing Chapter 3 and Isolating Services and Data, Assuring Fabric Controller Availability, Virtualizing Windows Server for Azure. Scaling Azure Table and Blob Storage: Creating Storage Accounts, Using or Chapter 4 Wrapping the Azure Storage Services’ REST APIs, Understanding Azure Table Storage, Storing and retrieving Blobs Minimizing Risk When Moving to the Azure Cloud Service: Bypassing the Barrier to Cloud Computing, Implementing the Secure Sockets Layers Chapter 5 Transmission, Encryption for Web Roles, Encrypting Personal Information in Azure Storage Services, Auditing Conformance to Regulatory and Industry Standards. Authenticating and Authorizing Service User: Taking Advantage of ASP.NET Membership Services, Adapting ASP.NET Authentication and Role Management to Windows Azure Web Role, Analyzing the AspProviders Chapter 6 Library’s Classes, Moving the AspProvidersDemo’s Data Source to the Cloud, Integrating Membership Services with an Azure Service, Authenticating users with Windows Live ID. Optimizing the Scalability and Performance of Azure Tables: Assigning Primary Key Values to Entities, Handling Associated Entities, Taking Advantage Chapter 7 of Entity Group Transactions, Uploading the table data, Displaying the Data from Heterogeneous Tables in Grids. Massaging with Azure Queues: Creating and Processing Azure Queues and Chapter 8 Messages, Enhancing the Thumbnails.sin Sample Solution.
    [Show full text]
  • Security Policy for FIPS 140-2 Validation
    Enhanced Cryptographic Provider Security Policy for FIPS 140‐2 Validation Microsoft Windows 8 Microsoft Windows Server 2012 Microsoft Windows RT Microsoft Surface Windows RT Microsoft Surface Windows 8 Pro Microsoft Windows Phone 8 Microsoft Windows Storage Server 2012 Enhanced Cryptographic Provider (RSAENH.DLL) DOCUMENT INFORMATION Version Number 1.2 Updated On December 17, 2014 © 2014 Microsoft. All Rights Reserved Page 1 of 25 This Security Policy is non‐proprietary and may be reproduced only in its original entirety (without revision). Enhanced Cryptographic Provider The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. This work is licensed under the Creative Commons Attribution-NoDerivs- NonCommercial License (which allows redistribution of the work). To view a copy of this license, visit http://creativecommons.org/licenses/by-nd-nc/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
    [Show full text]
  • Cryptographically Verified Design and Implementation of a Distributed
    1 Cryptographically Verified Design and Implementation of a Distributed Key Manager Tolga Acar∗,Cedric´ Fournety,Dan Shumow∗ ∗ Microsoft Research, One Microsoft Way, Redmond, WA 98052, USA ftolga,[email protected] y Microsoft Research, 7 J J Thomson Ave, Cambridge CB3 0FB, UK [email protected] Abstract Enterprise IT departments used to assume that data We present DKM, a distributed key management system on the company intranet was secure as long as it was with a cryptographically verified code base. hidden behind firewalls and VPNs, Cloud computing DKM implements a new data protection API. It clearly invalidates this naive assumption: in outsourced manages keys and policies on behalf of groups of infrastructures, data security necessarily involves cryp- users that share data. To ensure long-term protection, tography. However, encrypted storage requires users to DKM supports cryptographic agility: algorithms, keys, manage their keys. Thus, cryptography shifts the burden and policies can evolve for protecting fresh data while from protecting data to protecting keys in distributed preserving access to old data. DKM is written in C# and systems. Managing cryptographic keys remains one currently used by several large data-center applications. of the hard problems in applied cryptography. With- To verify our design and implementation, we also out proper key management, an otherwise theoretically write a lightweight reference implementation of DKM secure system is in reality quite vulnerable. For ex- in F#. This code closes the gap between formal crypto- ample, TLS and IPsec are insecure without a proper graphic models and production code: PKI [15, 19, 20], and SSH is vulnerable to man-in- • Formally, the F# code is a very precise model of the-middle attacks without trusted public keys [29].
    [Show full text]