Book Image

Learn PowerShell Core 6.0

By : David das Neves, Jan-Hendrik Peters
Book Image

Learn PowerShell Core 6.0

By: David das Neves, Jan-Hendrik Peters

Overview of this book

Beginning with an overview of the different versions of PowerShell, Learn PowerShell Core 6.0 introduces you to VSCode and then dives into helping you understand the basic techniques in PowerShell scripting. You will cover advanced coding techniques, learn how to write reusable code as well as store and load data with PowerShell. This book will help you understand PowerShell security and Just Enough Administration, enabling you to create your own PowerShell repository. The last set of chapters will guide you in setting up, configuring, and working with Release Pipelines in VSCode and VSTS, and help you understand PowerShell DSC. In addition to this, you will learn how to use PowerShell with Windows, Azure, Microsoft Online Services, SCCM, and SQL Server. The final chapter will provide you with some use cases and pro tips. By the end of this book, you will be able to create professional reusable code using security insight and knowledge of working with PowerShell Core 6.0 and its most important capabilities.
Table of Contents (26 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
Index

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...