ab3e18c8-5f9b-4a08-8474-ff10619965bd
Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Enabling PowerShell script block logging will record detailed information from the processing of PowerShell commands and scripts. This can provide additional detail when malware has run on a system.
Enabling PowerShell Transcription Logging: https://www.eventsentry.com/blog/2018/01/powershell-p0wrh11-securing-powershell.html#:~:text=Enabling%20Logging
https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.PowerShell::EnableScriptBlockLogging
To fix this configure the policy value for:
Computer Configuration
|_ Administrative Templates
|_ Windows Components
|_ Windows PowerShell
|_ "Turn on PowerShell Script Block Logging" to "Enabled".
STIG: Server:
2022: https://stigviewer.com/stigs/microsoft_windows_server_2022/2022-08-25/finding/V-254377
2019: https://stigviewer.com/stigs/microsoft_windows_server_2019/2022-09-06/finding/V-205639
Desktop:
W11: https://stigviewer.com/stigs/microsoft_windows_11/2022-08-31/finding/V-253414
W10: https://stigviewer.com/stigs/microsoft_windows_10/2022-04-08/finding/V-220860
NIST 800-53: AC-6(10), CAT|II
CCI: CCI-000135
CSCv6: 16.4
Vuln-ID: V-224957 / V-254377 / V-205639 / V-93175 / V-224957 / V-73591 / V-220860 / V-68819 / V-253414
For a quick fix, you can import this registry key from our GitHub repository
Manage your cookie preferences below:
To learn more about our use of cookies, please see our
Privacy Policy.