Script block logging in PowerShell - Mini Project: Build & Apply

Script Block Logging Setup in PowerShell

📖 Scenario: You are a system administrator who wants to enable script block logging on a Windows machine to monitor PowerShell script execution for security auditing.

🎯 Goal: Enable script block logging via PowerShell commands and verify that the logging is active by checking the registry setting.

📋 What You'll Learn

Create a registry path variable for script block logging

Create a configuration variable to enable logging

Set the registry key to enable script block logging

Verify and output the registry value to confirm logging is enabled

💡 Why This Matters

🌍 Real World

Script block logging helps security teams monitor and audit PowerShell script execution to detect suspicious activity.

💼 Career

System administrators and security engineers use script block logging to enhance security monitoring and compliance on Windows systems.

1

Create the registry path variable

Create a variable called $regPath and set it to the string 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging'.

PowerShell

# Create a variable called $regPath with the registry path string
# Your code here

Hint

Use single quotes around the registry path string and assign it to $regPath.

2

Create the configuration variable to enable logging

Create a variable called $enableLogging and set it to the integer 1 to enable script block logging.

PowerShell

$regPath = 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging'
# Create a variable called $enableLogging and set it to 1
# Your code here

Hint

Set $enableLogging to 1 to turn on logging.

3

Set the registry key to enable script block logging

Use the New-Item cmdlet with -Path $regPath and -Force to create the registry key if it does not exist. Then use New-ItemProperty with -Path $regPath, -Name 'EnableScriptBlockLogging', -Value $enableLogging, -PropertyType DWord, and -Force to set the registry value.

PowerShell

$regPath = 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging'
$enableLogging = 1
# Create the registry key and set EnableScriptBlockLogging to $enableLogging
# Your code here

Hint

Use New-Item to create the key and New-ItemProperty to set the DWORD value.

4

Verify and output the registry value

Use Get-ItemProperty with -Path $regPath and store the result in $result. Then print the value of $result.EnableScriptBlockLogging using Write-Output.

PowerShell

$regPath = 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging'
$enableLogging = 1
New-Item -Path $regPath -Force | Out-Null
New-ItemProperty -Path $regPath -Name 'EnableScriptBlockLogging' -Value $enableLogging -PropertyType DWord -Force | Out-Null
# Get the registry property and output the EnableScriptBlockLogging value
# Your code here

Hint

Use Get-ItemProperty to read the registry and Write-Output to print the value.

Practice

1. What is the main purpose of PowerShell script block logging?

easy

A. To automatically fix errors in scripts

B. To speed up script execution by caching commands

C. To record executed PowerShell commands for security and troubleshooting

D. To encrypt PowerShell scripts for protection

Solution

1. Step 1: Understand script block logging purpose

   Script block logging records the commands run in PowerShell scripts to help track activity.

2. Step 2: Compare options to purpose

   Only "To record executed PowerShell commands for security and troubleshooting" matches the purpose of recording commands for security and troubleshooting.

3. Final Answer:

   To record executed PowerShell commands for security and troubleshooting -> Option C

4. Quick Check:

   Script block logging = record commands [OK]

Hint: Remember: logging means recording actions, not speeding or fixing [OK]

Common Mistakes:

• Confusing logging with script optimization
• Thinking it encrypts scripts
• Assuming it auto-fixes errors

2. Which PowerShell command correctly enables script block logging by setting the registry key?

easy

A. Set-ExecutionPolicy -Scope LocalMachine -ExecutionPolicy ScriptBlockLogging

B. Enable-ScriptBlockLogging -Value 1

C. New-Item -Path 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell' -Name 'ScriptBlockLogging' -Value 1

D. Set-ItemProperty -Path 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging' -Name 'EnableScriptBlockLogging' -Value 1

Solution

1. Step 1: Identify correct registry path and property

   The registry path for script block logging is under HKLM\Software\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging with property EnableScriptBlockLogging.

2. Step 2: Match command syntax

   Set-ItemProperty sets a registry value correctly. Set-ItemProperty -Path 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging' -Name 'EnableScriptBlockLogging' -Value 1 uses correct path, property, and value 1 to enable logging.

3. Final Answer:

   Set-ItemProperty -Path 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging' -Name 'EnableScriptBlockLogging' -Value 1 -> Option D

4. Quick Check:

   Set-ItemProperty + correct path = enable logging [OK]

Hint: Use Set-ItemProperty with full registry path to enable logging [OK]

Common Mistakes:

• Using non-existent cmdlets like Enable-ScriptBlockLogging
• Incorrect registry paths
• Confusing execution policy with logging

3. Given the registry key is set to enable script block logging, what event log source will you check to see logged script blocks?

medium

A. Windows PowerShell

B. Application

C. Security

D. System

Solution

1. Step 1: Identify where PowerShell logs script block events

   PowerShell script block logging events appear in the Windows PowerShell event log under Applications and Services Logs.

2. Step 2: Match event log source

   The correct source is 'Windows PowerShell', not general logs like Application, Security, or System.

3. Final Answer:

   Windows PowerShell -> Option A

4. Quick Check:

   Script block logs appear in Windows PowerShell log [OK]

Hint: Check 'Windows PowerShell' log for script block events [OK]

Common Mistakes:

• Looking in Application or System logs
• Confusing Security log with script block logging
• Not knowing event log sources

4. You enabled script block logging but no events appear in the Windows PowerShell log. What is a likely cause?

medium

A. The registry key was set under the wrong registry hive

B. PowerShell script execution is disabled

C. The event log service is stopped

D. The script block logging feature is only for PowerShell 5.0 and above

Solution

1. Step 1: Check registry hive correctness

   Script block logging requires setting the key under HKLM (local machine). Setting it under HKCU or wrong hive causes no logging.

2. Step 2: Evaluate other options

   PowerShell execution policy does not block logging; event log service stopping would affect all logs; script block logging works in PowerShell 5.0+ but question assumes correct version.

3. Final Answer:

   The registry key was set under the wrong registry hive -> Option A

4. Quick Check:

   Wrong registry hive = no logs [OK]

Hint: Always set registry keys under HKLM for script block logging [OK]

Common Mistakes:

• Setting keys under HKCU instead of HKLM
• Assuming execution policy blocks logging
• Ignoring event log service status

5. You want to enable script block logging only for scripts running under a specific user account without affecting others. Which approach is best?

hard

A. Set the EnableScriptBlockLogging registry key under HKLM for all users

B. Modify the PowerShell profile script to log commands manually

C. Use Group Policy to enable script block logging for all users

D. Set the EnableScriptBlockLogging registry key under HKCU for that user

Solution

1. Step 1: Understand scope of script block logging

   Built-in script block logging is a machine-wide feature configured under HKLM or Group Policy, affecting all users.

2. Step 2: Identify per-user alternative

   HKCU does not enable script block logging (as it requires HKLM). Modifying the user's PowerShell profile to manually log commands (e.g., Start-Transcript) achieves per-user logging without affecting others.

3. Final Answer:

   Modify the PowerShell profile script to log commands manually -> Option B

4. Quick Check:

   Per-user logging = profile script [OK]

Hint: Use PowerShell profile for per-user command logging [OK]

Common Mistakes:

• Using HKLM or Group Policy which affects all users
• Setting HKCU key (does not enable built-in logging)
• Assuming built-in logging supports per-user config