Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learn PowerShell Core 6.0

You're reading from   Learn PowerShell Core 6.0 Automate and control administrative tasks using DevOps principles

Arrow left icon
Product type Paperback
Published in Jul 2018
Publisher Packt
ISBN-13 9781788838986
Length 552 pages
Edition 1st Edition
Languages
Concepts
Arrow right icon
Authors (2):
Arrow left icon
David das Neves David das Neves
Author Profile Icon David das Neves
David das Neves
Jan-Hendrik Peters Jan-Hendrik Peters
Author Profile Icon Jan-Hendrik Peters
Jan-Hendrik Peters
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Current PowerShell Versions FREE CHAPTER 2. PowerShell ISE Versus VSCode 3. Basic Coding Techniques 4. Advanced Coding Techniques 5. Writing Reusable Code 6. Working with Data 7. Understanding PowerShell Security 8. Just Enough Administration 9. DevOps with PowerShell 10. Creating Your Own PowerShell Repository 11. VSCode and PowerShell Release Pipelines 12. PowerShell Desired State Configuration 13. Working with Windows 14. Working with Azure 15. Connecting to Microsoft Online Services 16. Working with SCCM and SQL Server 17. PowerShell Deep Dives 18. PowerShell ISE Hotkeys 19. Assessments 20. Other Books You May Enjoy

Principle of Least Privilege


Due to the dependencies of the users rights, one important approach for defenders to securing PowerShell is the well-known Principle of Least Privilege. The fewer rights the user has, the smaller the attack surface is; the reduction of the attack surface is probably the best way to increase security in an enterprise environment. Unfortunately, the implementation of this approach is not an easy or a small task and can be sorted under the category of Securing Privileged Access. The problem that comes with PowerShell security is that many enterprise customers tend to have too many admins. There are typical excuses for why they are necessary, but the reality is that these admins only in very rare cases need to have elevated rights. In most cases, laziness when it comes to creating processes and rules is why they still exist. But giving an attacker the chance to make use of PowerShell on a machine where local admin rights have been made available increases their potential...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at ₹800/month. Cancel anytime