Impair Defenses: Impair Command History Logging

Created the Tuesday 07 February 2023. Updated 6 months, 3 weeks ago.

Adversaries may impair command history logging to hide commands they run on a compromised system. Various command interpreters keep track of the commands users type in their terminal so that users can retrace what they've done.

On Windows systems, the PSReadLine module tracks commands used in all PowerShell sessions and writes them to a file ($env:APPDATA\Microsoft\Windows\PowerShell\PSReadLine\ConsoleHost_history.txt by default). Adversaries may change where these logs are saved using Set-PSReadLineOption -HistorySavePath {File Path}. This will cause ConsoleHost_history.txt to stop receiving logs. Additionally, it is possible to turn off logging to this file using the PowerShell command Set-PSReadlineOption -HistorySaveStyle SaveNothing.

Adversaries may also leverage a Network Device CLI on network devices to disable historical command logging (e.g. no logging).

Technique Identifier

T1562.003

Technique Tags

Defense Evasion PSReadLine ConsoleHost_history.txt $env:APPDATA\Microsoft\Windows\PowerShell\PSReadLine\ Set-PSReadLineOption -HistorySavePath {File Path} Set-PSReadlineOption -HistorySaveStyle SaveNothing Network Device CLI APT38 disable logging disable historical command logging

Additional Resources

External Links

The resources provided below are associated links that will give you even more detailed information and research on current evasion technique. It is important to note that, while these resources may be helpful, it is important to exercise caution when following external links. As always, be careful when clicking on links from unknown sources, as they may lead to malicious content.

Impair Defenses: Impair Command History Logging, Sub-technique T1562.003 - Enterprise | MITRE ATT&CK®