Explanation & Hint:
- Changed the PowerShell execution policy to the default setting: Initially, the execution policy was set to “Unrestricted.” However, the user initiated the
Set-ExecutionPolicy cmdlet without specifying a particular policy, and the system prompted them to provide a value. The user chose “restrict,” which is the default execution policy for PowerShell. This action effectively reverted the execution policy back to the default setting.
- Configured the system to require digital signing only of externally-downloaded PowerShell scripts: This can be inferred from the user’s decision to change the execution policy to the default “restrict” policy. The “restrict” policy allows the execution of local scripts but requires digitally signed scripts when they are downloaded from external sources. This change is for enhanced security to protect against potentially malicious scripts.
|
